On 08.11.2013, at 11:52, Ramiro Morales <cra...@gmail.com> wrote:

> Claude,
> 
> On Fri, Nov 8, 2013 at 6:31 AM, Claude Paroz <cla...@2xlibre.net> wrote:
>> Le jeudi 07 novembre 2013 à 20:25 -0200, Ramiro Morales a écrit :
>> 
>> I would support this proposal but with one condition, we should lift the
>> restriction that apps can only provide translations for which Django has
>> also a translation. Imagine an app writer which doesn't reuse any Django
>> string, but would like to provide translation for language xx, and
>> language xx has only 4% of Django translated. The fact that Django
>> contains only 4% of translated string doesn't affect him at all, but if
>> we remove those translations, the xx translations for his app cannot be
>> used at all (if the docs still reflect the reality).
> 
> From what I understand this restriction was lifted a long time ago.
> See [1]commit and [2]ticket
> 
> IIRC, author of the change was a Transifex staff member.
> 
> Problem is it didn't include tests nor documentation [updates] and so
> far we haven't got around to fix that.
> 
> This means this sentence is wrong since three years ago:
> 
>  
> https://github.com/django/django/blob/master/docs/topics/i18n/translation.txt#L1220-L1231
> 
> 
> 1. 
> https://github.com/django/django/commit/e1e3f243715c400bc6e2cec5bd650ac90ecb7f44
> 2. https://code.djangoproject.com/ticket/14461

Good catch, Ramiro, mind opening a ticket?

Jannis

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

Reply via email to