[development] Seeking help internationalizing Views (and Panels and maybe other modules for D6)
gerhard at killesreiter.de
Sun Apr 27 13:54:42 UTC 2008
-----BEGIN PGP SIGNED MESSAGE-----
Jakob Petsovits schrieb:
> On Saturday, 26. April 2008, Jose A. Reyero wrote:
>> Daniel F. Kudwien wrote:
>>> To translate a content correctly, translators are more comfortable with
>>> the approach taken by #translatable. They see the original form and
>>> thus, have an idea of how all strings and contents of an object relate.
>>> #translatable stores the translations and does not alter the original
>> I think: yes and no.
> KDE's i18n() function (same as t() for Drupal) has an optional "context"
> parameter that the developer specifies in order to help the translators out.
> (That context later appears as comment in the .pot file, I believe.)
> Maybe it would be an option to include something like this in some way, in
> order to provide an actual middle ground between "no UI-related context in
> the .pot file" and "no code-related context in the UI string".
Drupal already does something similar if you do not use pre-built PO
files. The PO comments are filled with the URLs of the places the string
was encountered first. Not perfect of course, but maybe someting to
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
-----END PGP SIGNATURE-----
More information about the development