Christoph Spielmann <cspielma(a)gup.jku.at> writes:
I added one whitespace to the syntax oids where it was missing in the
schema-file but this doesn't seem to be the cause of the problems (especially
as other schemas sometimes skip the additional whitespace too, and those get
processed correctly during the conversion process).
This must be a bug, because BNF notation is
AttributeTypeDescription = "(" whsp
[ "NAME" qdescrs ]
[ "DESC" qdstring ]
[ "OBSOLETE" whsp ]
[ "SUP" woid ]
[ "EQUALITY" woid
[ "ORDERING" woid
[ "SUBSTR" woid ]
[ "SYNTAX" whsp noidlen whsp ]
[ "SINGLE-VALUE" whsp ]
[ "COLLECTIVE" whsp ]
[ "NO-USER-MODIFICATION" whsp ]
[ "USAGE" whsp AttributeUsage ]
as you may notice, white space is required.
Do you have any other
ideas what could be the cause for the problems?
I'm not sure, but the plus character in gosa+samba3.schema may cause
problems, although syntax of commonName is directory string, therefor
+ is a valid character.
Dieter Klünter | Systemberatung
GPG Key ID:8EF7B6C6