svn commit: r1790938 - /directory/site/trunk/content/apacheds/basic-ug/1.4.3-adding-partition.mdtext

[el...@apache.org]

Author: elecharny
Date: Tue Apr 11 08:10:11 2017
New Revision: 1790938

URL: http://svn.apache.org/viewvc?rev=1790938&view=rev
Log:
Replaced __ by _

Modified:
    directory/site/trunk/content/apacheds/basic-ug/1.4.3-adding-partition.mdtext

Modified: directory/site/trunk/content/apacheds/basic-ug/1.4.3-adding-partition.mdtext
URL: http://svn.apache.org/viewvc/directory/site/trunk/content/apacheds/basic-ug/1.4.3-adding-partition.mdtext?rev=1790938&r1=1790937&r2=1790938&view=diff
==============================================================================
--- directory/site/trunk/content/apacheds/basic-ug/1.4.3-adding-partition.mdtext (original)
+++ directory/site/trunk/content/apacheds/basic-ug/1.4.3-adding-partition.mdtext Tue Apr 11 08:10:11 2017
@@ -138,9 +138,9 @@ When the server starts for the first tim
 
 Therefore, if you would like to have your (empty) partition created immediately following installation, you should prevent your server from starting during or after installation, i.e. when config.ldif has not yet been migrated.
 
-Next, edit _config.ldif_ to change all occurrences of "__example__" to suit the name of your own partition. Once the server has started and you run your first ldapsearch as the admin user, you will see that the server has created your own empty partition (instead of the example one).
+Next, edit _config.ldif_ to change all occurrences of "_example_" to suit the name of your own partition. Once the server has started and you run your first ldapsearch as the admin user, you will see that the server has created your own empty partition (instead of the example one).
 
-Note that the entry for the "__example__" partition does NOT have an _ads-contextEntry_ attribute. This "signature" attribute is created during the "migration" process (see below for details).
+Note that the entry for the "_example_" partition does NOT have an _ads-contextEntry_ attribute. This "signature" attribute is created during the "migration" process (see below for details).
 
 Subsequent ldif changes to your new partition should work provided they use the default schema.
 
@@ -173,8 +173,8 @@ The _ads-contextentry_ attribute is a bi
 
 Base64 these four lines as a single string (with \n newlines, but without the prefix spaces). The result should match the _ads-contextentry_ value shown above.
 
-However, you need to be careful because simply adding an extra space or newline will change the base64 value and make it unacceptable to the server. Also, any valid UTF-8 attribute values which are not in the base64 character set (such as accented characters) ___MUST___ be base64-encoded strings, which effectively makes them double-encoded.
-e.g. ___"dn: cn=lécharny,dc=com"___ needs to be specified as ___"dn:: Y249bMOpY2hhcm55LGRjPWNvbQ=="___.
+However, you need to be careful because simply adding an extra space or newline will change the base64 value and make it unacceptable to the server. Also, any valid UTF-8 attribute values which are not in the base64 character set (such as accented characters) _MUST_ be base64-encoded strings, which effectively makes them double-encoded.
+e.g. _"dn: cn=lécharny,dc=com"_ needs to be specified as _"dn:: Y249bMOpY2hhcm55LGRjPWNvbQ=="_.
 
-You will probably want to create some associated index entries. You can use those of the "__example__" partition in _config.ldif-migrated_ for your templates (which do not require any special encoded attributes).
+You will probably want to create some associated index entries. You can use those of the "_example_" partition in _config.ldif-migrated_ for your templates (which do not require any special encoded attributes).