Hi Sergei
postgresql-8.4
might be a difference in mysql/pgsql ?
apache-2.2 modperl-2 freebsd-8.2For sure the above is not essential for the problem. Will try umlauts later.
What locale are you using - us or ru ?
Sure I tried FF and Chrome but also my Shell Testing Environment - with your utf8 flagging applied, the data passes the serialization successfully. I used a unicode aware regex (\p{Letter}) in Validator/CertSubjectParts to check what is moving in - surprisingly, setting only Encode::_utf8_on does leave the string in the "two bytes encoding" and the regex fails. I then applied a utf8:.decode and the regex passes - so at this point, I am sure it is valid utf8 data.Probably there is an issue with utf8 characters that have a latin-1 equivalent.That could be an issue with your browser. Of course you have tried Mozilla Firefox as a golden standard. Also you may want to provide me with configuration of your Apache, to see if it forces some obligatory code page substitutions or such.
The amazing point: If I do the decode call on the "global" data, I get a proper display on the UI but double encoding in the database and a broken character in the certificate. If I convert it only locally, the certificate is fine but the UI is broken - looks like there is some oher kind of conversion happening.
Oliver -- Protect your environment - close windows and adopt a penguin! PGP-Key: 3B2C 8095 A7DF 8BB5 2CFF 8168 CAB7 B0DD 3985 1721
smime.p7s
Description: S/MIME Cryptographic Signature
------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________ OpenXPKI-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openxpki-devel
