Hello
Could you please confirm me if the i18n (at least en_US) translations in the
code are supposed to be complete and up to date ?
The reason I ask is only because in the html mason client, I see here and there
some I18N_OPENXPKI_* remaining strings and so I wonder if something is broken
in my installations or if this is the expected behavior, and if I could then
"complete" it?.
Also, it looks like (my installation of) the sever daemon process is not using
the i18n strings id at all ? The messages in the logs are referencing i18n
strings ids, and any error message or exception returned to/through the html
mason client doesn't get translated either .
For example, I can get the following key in the web interface:
I18N_OPENXPKI_CRYPTO_SECRET_PLAIN_INVALID_PARAMETER
… although the string id and translation are in i18n/en_US/openxpki.po, which
has been installed in /usr/share/locale/en_US/LC_MESSAGES/openxpki.mo
in config.xml I have:
<i18n>
<locale_directory>/usr/share/locale</locale_directory>
<default_language>en_US</default_language>
</i18n>
Is something broken in my systems wrt locales ? Could you help me identify the
root cause ?
Please note I tested
- the midnight snapshots tarballs on a centos 5.8 box
- latest git code on a centos 5.8x box
- the prebuilt debian packages on a squeeze box
Should I use something older ?
Thank you
Regards
Gaetan
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
OpenXPKI-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openxpki-users
