
Hello, I'm currently setting up an OTRS demo server. I have a little problem which probably can make my demo less efficient. I'm retrieving customers from our LDAP (MS Active Directory). Every special character is displayed incorrectly. This only happens for LDAP source fields. Every other aspect of the frontend is correct. Here is my setup: OTRS 2.2.2 on Debian Etch DefautCharset is utf-8 (can be changed if needed, this is my last test) Mysql database is latin1 (can be changed if needed) MS Active Directory is ? (maybe iso-8859-1 but not sure. How can I verify ?) can probably not be changed for this demo purpose. Tried to change mysql to utf-8 using the following procedure: http://yoonkit.blogspot.com/2006/03/mysql-charset-from-latin1-to-utf8.html Also tried options SourceCharset => 'iso-8859-1', # incase LDAP/AD is iso-8859-1 like I think DestCharset => 'utf-8', With these options, customerid with special char are left blank on the user list. I'm not familiar with charset problems. Can you give me some help please ? Thank You Régis Oberlé

They just released an update to OTRS 2.2.3. Is this the version you have? Régis OBERLE wrote:
Hello,
I'm currently setting up an OTRS demo server. I have a little problem which probably can make my demo less efficient. I'm retrieving customers from our LDAP (MS Active Directory). Every special character is displayed incorrectly. This only happens for LDAP source fields. Every other aspect of the frontend is correct. Here is my setup:
OTRS 2.2.2 on Debian Etch DefautCharset is utf-8 (can be changed if needed, this is my last test) Mysql database is latin1 (can be changed if needed) MS Active Directory is ? (maybe iso-8859-1 but not sure. How can I verify ?) can probably not be changed for this demo purpose.
Tried to change mysql to utf-8 using the following procedure: http://yoonkit.blogspot.com/2006/03/mysql-charset-from-latin1-to-utf8.html
Also tried options SourceCharset => 'iso-8859-1', # incase LDAP/AD is iso-8859-1 like I think DestCharset => 'utf-8',
With these options, customerid with special char are left blank on the user list.
I'm not familiar with charset problems.
Can you give me some help please ?
Thank You
Régis Oberlé _______________________________________________ OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs Support or consulting for your OTRS system? =http://www.otrs.com/

No, I have version 2.2.2. Régis -----Message d'origine----- De : otrs-bounces@otrs.org [mailto:otrs-bounces@otrs.org] De la part de Jeff Shepherd Envoyé : mardi 18 septembre 2007 22:56 À : User questions and discussions about OTRS.org Objet : Re: [otrs] Charset problem with LDAP They just released an update to OTRS 2.2.3. Is this the version you have? Régis OBERLE wrote:
Hello,
I'm currently setting up an OTRS demo server. I have a little problem which probably can make my demo less efficient. I'm retrieving customers from our LDAP (MS Active Directory). Every special character is displayed incorrectly. This only happens for LDAP source fields. Every other aspect of the frontend is correct. Here is my setup:
OTRS 2.2.2 on Debian Etch DefautCharset is utf-8 (can be changed if needed, this is my last test) Mysql database is latin1 (can be changed if needed) MS Active Directory is ? (maybe iso-8859-1 but not sure. How can I verify ?) can probably not be changed for this demo purpose.
Tried to change mysql to utf-8 using the following procedure: http://yoonkit.blogspot.com/2006/03/mysql-charset-from-latin1-to-utf8. html
Also tried options SourceCharset => 'iso-8859-1', # incase LDAP/AD is iso-8859-1 like I think DestCharset => 'utf-8',
With these options, customerid with special char are left blank on the user list.
I'm not familiar with charset problems.
Can you give me some help please ?
Thank You
Régis Oberlé _______________________________________________ OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs Support or consulting for your OTRS system? =http://www.otrs.com/
_______________________________________________ OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs Support or consulting for your OTRS system? =http://www.otrs.com/

Does nobody here have any idea of where my problem comes from ? There is probably someone who has a setup close to mine, with Microsoft Active Directory, OTRS on Linux, etc. How does your config looks like ? I really need help about that. I spent a lot of time today on this issue, with no result. Thank you Régis -----Message d'origine----- De : otrs-bounces@otrs.org [mailto:otrs-bounces@otrs.org] De la part de Régis OBERLE Envoyé : mercredi 19 septembre 2007 09:04 À : User questions and discussions about OTRS.org Objet : RE: [otrs] Charset problem with LDAP No, I have version 2.2.2. Régis -----Message d'origine----- De : otrs-bounces@otrs.org [mailto:otrs-bounces@otrs.org] De la part de Jeff Shepherd Envoyé : mardi 18 septembre 2007 22:56 À : User questions and discussions about OTRS.org Objet : Re: [otrs] Charset problem with LDAP They just released an update to OTRS 2.2.3. Is this the version you have? Régis OBERLE wrote:
Hello,
I'm currently setting up an OTRS demo server. I have a little problem which probably can make my demo less efficient. I'm retrieving customers from our LDAP (MS Active Directory). Every special character is displayed incorrectly. This only happens for LDAP source fields. Every other aspect of the frontend is correct. Here is my setup:
OTRS 2.2.2 on Debian Etch DefautCharset is utf-8 (can be changed if needed, this is my last test) Mysql database is latin1 (can be changed if needed) MS Active Directory is ? (maybe iso-8859-1 but not sure. How can I verify ?) can probably not be changed for this demo purpose.
Tried to change mysql to utf-8 using the following procedure: http://yoonkit.blogspot.com/2006/03/mysql-charset-from-latin1-to-utf8. html
Also tried options SourceCharset => 'iso-8859-1', # incase LDAP/AD is iso-8859-1 like I think DestCharset => 'utf-8',
With these options, customerid with special char are left blank on the user list.
I'm not familiar with charset problems.
Can you give me some help please ?
Thank You
Régis Oberlé _______________________________________________ OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs Support or consulting for your OTRS system? =http://www.otrs.com/
_______________________________________________ OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs Support or consulting for your OTRS system? =http://www.otrs.com/ _______________________________________________ OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs Support or consulting for your OTRS system? =http://www.otrs.com/

Hi Regis,
Does nobody here have any idea of where my problem comes from ?
There is probably someone who has a setup close to mine, with Microsoft Active Directory, OTRS on Linux, etc.
I have had a similar problem (receiving garbled umlauts from an ISO LDAP into an UTF-8 OTRS). I opened a bug report on this: no 1912: http://bugs.otrs.org/show_bug.cgi?id=1912 I applied the patch described in the report to my system and now it works. Unfortunately, there are more places where the special characters are still broken and maybe (probably?) originate from the LDAP. I did not yet trace them down. HTH, Tobias -- Tobias Lütticke Systems Architecture inovex GmbH Pforzheim (Head Office) Karlsruher Strasse 71 D-75179 Pforzheim Tel.: +49 (0)72 31 / 31 91 - 84 Fax: +49 (0)72 31 / 31 91 - 91 mailto:t.luetticke@inovex.de http://www.inovex.de

Thanks a lot Tobias ! Applied the same patch and the problem has gone ! Strangely, I had to remove the SourceCharset and DestCharset entries in Config.pm (if not, some users are left blank on the search result in Customer User Management. Already had this problem before applying the patch). Only DefaultCharset is still set to utf-8. And I still don't know which charset is used in MS Active Directory. Again, thanks a lot for your help. I can now plan for a demo in my company. Regards, Regis (from France, next to the German border :-)) -----Message d'origine----- De : otrs-bounces@otrs.org [mailto:otrs-bounces@otrs.org] De la part de Tobias Lütticke Envoyé : mardi 25 septembre 2007 11:20 À : User questions and discussions about OTRS.org Objet : Re: [otrs] Charset problem with LDAP Hi Regis,
Does nobody here have any idea of where my problem comes from ?
There is probably someone who has a setup close to mine, with Microsoft Active Directory, OTRS on Linux, etc.
I have had a similar problem (receiving garbled umlauts from an ISO LDAP into an UTF-8 OTRS). I opened a bug report on this: no 1912: http://bugs.otrs.org/show_bug.cgi?id=1912 I applied the patch described in the report to my system and now it works. Unfortunately, there are more places where the special characters are still broken and maybe (probably?) originate from the LDAP. I did not yet trace them down. HTH, Tobias -- Tobias Lütticke Systems Architecture inovex GmbH Pforzheim (Head Office) Karlsruher Strasse 71 D-75179 Pforzheim Tel.: +49 (0)72 31 / 31 91 - 84 Fax: +49 (0)72 31 / 31 91 - 91 mailto:t.luetticke@inovex.de http://www.inovex.de _______________________________________________ OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs Support or consulting for your OTRS system? => http://www.otrs.com/
participants (3)
-
Jeff Shepherd
-
Régis OBERLE
-
Tobias Lütticke