On Wed, Apr 1, 2009 at 12:51 PM, Ludvig Ericson
<ludvig.eric...@gmail.com> wrote:
>
> On Apr 1, 2009, at 12:25, TiNo wrote:
>> Two solutions:
>> 1) Change the Dutch translation into "Ga" (= literally "Go") (so that
>> would also be displayed after the search-box)
>> 2) Change the template to display the English word "Search" after the
>> search-box.
>
> Long-term, I'd say this kind of issue is one that requires changing
> the original string.
>
> However, I doubt it'll be worth breaking all the translations in a
> fairly obvious place at this time (just pre-1.1), so for now, you
> should probably opt in to make it natural in Dutch in both cases.
>
I've started to play with the new actions stuff from trunk in just now and
found that in Spanish we have the same problem.
Until now the msgstr used for the "Go" msgid wasn't the exact
Argentinian Spanish equivalent but "Buscar" ("Search") because the only
occurrence of the English word was in the button of the search box and
because, in Spanish, it describes better the action the user would get by
pressing it.
But now, with "Go" being also used on the actions block, this scheme
breaks as TiNo described above.
IMHO TiNo proposal 2 would be the best option because it would allow
translators to languages where better choices exist to describe and
differentiate the two different verbs to make use of them. This until we get
context-annotated translations in 1.2.
RC is delayed and string freeze isn't in effect yet so now (the stabilizing
period between the implementation of the [actions] feature and string freeze)
is the right time to make this kind of translatable literal changes.
What are translators to other languages opinion? Are you seeing the same
problem as we do in Dutch and Spanish?.
Regards,
--
Ramiro Morales
http://rmorales.net
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django I18N" group.
To post to this group, send email to Django-I18N@googlegroups.com
To unsubscribe from this group, send email to
django-i18n+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/Django-I18N?hl=en
-~----------~----~----~----~------~----~------~--~---
