[ckan-dev] [ckan-discuss] New i18n guidelines for CKAN

[David Megginson]

I agree with Ian on this point.  While in principle, it's unfortunate that
the current approach favours one language over others, I think it's more
useful for non-English visitors to see an untranslated English term than a
cryptic code reference.  In the project that I'm working on, we'll be
adding a fair bit of new text to the CKAN templates, and it's good to know
that at least *something* potentially useful will appear in every language
until we get around to modifying all the different *.po files.


D


On Wed, Apr 9, 2014 at 1:07 PM, Stefan Oderbolz <stefan.oderbolz at liip.ch>wrote:

>
> How would this work with variables and things like ngettext?
>>
>
> Well you could still use variables, but it looks a bit weird, I agree.
> Maybe there is a better solution for those cases:
>  msgid "{actor} activity_stream.start_follow {dataset}"
> which used to be:
> msgid "{actor} started following {dataset}"
>
> or:
>  msgid "1 activity_stream.new_activity_from_singular {site_title}"
>  msgid_plural "{n} activity_stream.new_activity_from_plural {site_title}"
> which used to be:
>  msgid "1 new activity from {site_title}"
>  msgid_plural "{n} new activities from {site_title}"
>
> Also, wouldn't this make CKAN really hard to use until it has been
>> completely translated into a new language?
>>
>
> It depends, you could still use the English translation as the template
> (i.e. copy/paste and start to change it). I'm not entiertly sure, but I
> think if you export a language from Transifex, it actually provides you all
> missing strings from the source language (=English).
>
>
> --
> Liip AG  //  Feldstrasse 133 //  CH-8004 Zurich
> Tel +41 43 500 39 80 // GnuPG 0x7B588C67 // www.liip.ch
>
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> https://lists.okfn.org/mailman/listinfo/ckan-dev
> Unsubscribe: https://lists.okfn.org/mailman/options/ckan-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20140410/0f6c18ab/attachment-0003.html>