Hi Kevin,
There should be a single leading space to continue the line. This is a
standard descibed in RFC 2849. Here's an example:
attributetypes: (1.3.6.1.4.1.2114.108.1.8.999.8
NAME ('inherent-3-D-shape-reverse')
SUP tsCaseIgnoreIA5String
SINGLE-VALUE)
-NGK
Kevin Peterson wrote:
>When creating a custom schema file, whitespace appears to be
>important. For example:
>
>attributetypes: (1.3.6.1.4.1.2114.108.1.8.999.8
>NAME ('inherent-3-D-shape-reverse')
>SUP tsCaseIgnoreIA5String
>SINGLE-VALUE)
>
>attributetypes: (1.3.6.1.4.1.2114.108.1.8.999.9
>NAME ('branch-continuity')
>SUP tsCaseIgnoreIA5String
>SINGLE-VALUE)
>
>will not work, while
>
>attributetypes: (1.3.6.1.4.1.2114.108.1.8.999.8 NAME
>('inherent-3-D-shape-reverse') SUP tsCaseIgnoreIA5String SINGLE-VALUE)
>attributetypes: (1.3.6.1.4.1.2114.108.1.8.999.9 NAME
>('branch-continuity') SUP tsCaseIgnoreIA5String SINGLE-VALUE)
>
>will work.
>
>I did not see any mention of whitespace in RFC 2252 and I am wondering
>1. Is this is expected behaviour, and 2. Is this documented anywhere,
>because if it is perhaps there are more formatting rules that I am
>missing.
>
>--
>Fedora-directory-users mailing list
>Fedora-directory-users at redhat.com
>https://www.redhat.com/mailman/listinfo/fedora-directory-users
>
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3174 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.fedoraproject.org/pipermail/389-users/attachments/20050603/5fdb1e8a/attachment.bin
