LAROCHETTE Philippe wrote: > i don't know if it is a utf8 problem because i make several tests with some > utf8 conversion with notepad++ of the .bat script file or of the ldiff file > and nothing work exept the replacement of the character by the escape > sequence \c3\a9 > > The problem is the same in windows Seven... > > The application is an access process that produce some ldif files that are > launched with a .bat file, a solution is to move the script process of the > ldif files on the linux plateform but other process are managed with windows > server planified tasks.. but it is a solution... > > I found a solution, it's working if i use ldapmodify with -f and use "newrdn" > and "new superior" in the ldif file... i encode the ldif file in UTF-8 > without BOM > > Thank you for the idea of iconv, i try the same thing with notepad++ and now > it's working, the problem was the difference between UTF8 withous BOM and > UTF8 for the encoding. > > UTF8 without BOM it's ok but the native format UTF8 of the basic windows > notepad don't work.
The best solution for such issues is not to muck around with command-line tools but to use a full-blown scripting language with a decent LDAP module. Ciao, Michael.
smime.p7s
Description: S/MIME Cryptographic Signature
