Hello Oliver
Thank you very much for helping.
Indeed there seem to be some delay on the ml .
I reverted back to the "master" git branch , last log being on March 8th
(bda346f3639f7b251c3bd7c999178b53a9dff321 Merge branch 'release/v0.10.0' by
Martin) .
I believed this is the release the stable debian packages were based on (?). As
I'm supposed to deploy on Centos/RHEL I have to use git or tar balls, but the
tarballs on the website seem quite outdated.
Anyway I performed the same tests on the debian dpkg-based install too and the
(positive) results are the same.
I can confirm
- Your sample code returns the expected translation
- I have an environment problem with LC_CTYPE being set to a bare "UTF-8"
instead of "en_US.UTF-8" but that does not seem to affect openxpki. It only
produces a perl warning and explicitly setting the var solves it anyway. I
think this is related to the openvz container...
- The first problem obviously is myself. Indeed I overlooked the "fuzzy"
keyword in the .po fiels. So it is normal some strings are not translated
although defined in the mo. I see these strings when workflows are in an
intermediate state (i.e, generate a CRL or start certificate signing workflow
when CA key not ready/usable…). Putting a right translation and removing the
fuzzy keyword quickly fixes this as expected.
- There is only a tiny i18n "problem" with the deployment tool(s), or at least
openxpkictl. There, strings are not translated (but if I manually set the
domain to "openxpki" through dgettext() , it's ok):
# openxpkictl -config /path/to/nonexistent.xml start
Log4perl: Seems like no initialization happened. Forgot to call init()?
I18N_OPENXPKI_XML_CACHE_INIT_XML_ERROR; __ERRVAL__ => File does not exist:
/path/to/nonexistent.xml at
/usr/lib64/perl5/site_perl/5.8.8/x86_64-linux-thread-multi/OpenXPKI/XML/Cache.pm
line 115.
- In the openxpki.log file, the I18N_* strings are the workflow identifiers as
declared in the xml files. So I suppose it is expected not to be translated ?
- In the interface, most of the remaining strings seem to appear because a
reached "unexpected" screen (i.e. , CRL issuance stuck in CA_DETERMINED because
CA was not yet configured when I clicked on the "issue CRL" link, this gives a
button with I18N_OPENXPKI_WF_ACTION_GET_CRL_PROFILE but now after some code
reading, I understand how the mason client works.
NB: In your package, I see workflows defs (+ a "deprecated" template) not in
the master or devel git branch. Where are these coming from ?
Thanks again!
Gaetan
On 14/06/2012, at 08:42, Oliver Welter wrote:
> Hello Gaetan,
>
> it looks like sf has problems with the ml, as my mail yesterday didnt make it
> to the list.
>
> Basically the i18n stuff should do. I am not aware of the current state of
> the snapshots and the git head, but at least the debian packages at
> packages.openxpki.org are working.
> Anyway, the en_US locale is allways the default fallback, so I wonder that it
> is not working.
>
> Can you first try to set the locale to "C" in the config.xml - that should
> give you the en_US as default.
>
> You can also try the script below, which should confirm that the gettext
> stuff is working at all.
>
> Oliver
>
> #!/usr/bin/perl
>
> use OpenXPKI::i18n qw( i18nGettext set_language set_locale_prefix
> get_language);
>
> set_locale_prefix( '/usr/share/locale/' );
> set_language('en_US');
>
> print i18nGettext('I18N_OPENXPKI_CRYPTO_SECRET_PLAIN_INVALID_PARAMETER');
> print "\n";
>
>
> On 13.06.2012 14:40, Gaëtan Minet wrote:
>> 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
>> OpenXPKI-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/openxpki-users
>
> --
> Protect your environment - close windows and adopt a penguin!
> PGP-Key: 3B2C 8095 A7DF 8BB5 2CFF 8168 CAB7 B0DD 3985 1721
>
>
------------------------------------------------------------------------------
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
OpenXPKI-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openxpki-users
