Re: Translations for upcoming Django 1.9

[Fòram na Gàidhlig]

"Scottish Gaelic" and "Gàidhlig", please.

I have also just sent a pull request for the datetime formats etc.

https://github.com/django/django/pull/5723

I don't understand the flake8 error, could somebody please have a look?

Thank you :)



Sgrìobh Claude na leanas 25/11/2015 aig 19:23:
> Sure, I can plan to merge translations on the 30th.
> 
> By the way, we've got at least two new languages (Gaelic, Scottish /
> Colombian Spanish), with core strings fully translated. We'll have to
> add them as new available languages in settings.LANGUAGES, which means
> that two new strings will appear soon.
> 
> Fòram, could you tell us how you would like the language name to appear?
> Scottish Gaelic or simply Gaelic?
> We'd also need the native name of the language (Gàidhlig?).
> 
> I've created https://code.djangoproject.com/ticket/25815 to track that.
> 
> Claude
> 
> Le 25. 11. 15 19:47, Tim Graham a écrit :
>> Hi Claude,
>>
>> We're on track for the final release on December 1. Do you want to plan
>> to push the translations on the day before or so?
>>
>> Thanks!
>> Tim
>>
>> On Sunday, October 11, 2015 at 3:04:09 PM UTC-4, claudep wrote:
>>
>> Hi,
>>
>> I'd just like to let you know that I updated the translation
>> templates
>> on Transifex with updated strings for Django 1.9.
>> Strings will not be officially freezed before the RC release planned
>> for
>> November 16, but we can expect very few changes from now, if any.
>>
>> https://www.transifex.com/django/django/
>> 
>>
>> Happy translating,
>>
>> Claude
>> --
>> www.2xlibre.net 
> 
> 
> -
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2016.0.7227 / Virus Database: 4460/11062 - Release Date: 11/25/15
> 
> 

-- 
-BEGIN PGP PUBLIC KEY BLOCK-
Version: GnuPG v2.0.22 (MingW32)

mQINBFNbSyEBEADh+uhohycnZgPPnyMs5pZQG6pKyLzFZoIKbVjY31ZoPZ2SdltB
elrwn6kFZkQiDx4K6nkZFHsPh8RMvWoFWg1rGiWkdsZessLFawraC8YEZDwtlaU5
SFXbE4+QnMfbPhe9tmC8Nbhec3dfV9zcXAhxc+zkIUsKFhSkpJ2Syvo9FCA/5adW
UZgWWKFwlSg4+/lrhJ6QJnldPlXfWcuEasKF7fjdafDIdS5hdKu8Lv+CiPQWvgsi
J2BDlZLzEZf3PD+NMujUbJa0nilD2ltu3/qRvR2f86YV6wRwt4E2OD8JJQOau4X2
Pg7vqkIbnB9rMiQ6T17rQ4rc80eesGCxQ6XOba9oa1eRRZDwY7HJtYwvPdw9HZaN
Lq2RRbGDGO0q7fxrzbp1WuNN+UXOA/pmVzWWczPfPHVcNIehGf3wQI+Vgh/qa+IZ
jLJ25I1Tv85cDzvv5gdtI8PR4JTfK6Db+gUJmsuIg2fmsljxA7OmeTgSPR7nEVq5
VlHYfx1T0uKlthWw/eDwlS44vTgm6HZzIdYqdPMPa/PU1U+WVuDejyDJTn/1TY78
oJMT/IixFR+N+smohhKASprewcsO2ClWGptSG0sRTiCrVHFD3Mt6SCVaxsQLHvek
KuNAUXhR2KSvYuqGT0Nv3bplN6svCp4CuAGZ3lyOIt/Sb7OFUwzcx2sOdwARAQAB
tC5Gw7JyYW0gbmEgR8OgaWRobGlnIDxmaW9zQGZvcmFtbmFnYWlkaGxpZy5uZXQ+
iQI5BBMBAgAjBQJTW0shAhsPBwsJCAcDAgEGFQgCCQoLBBYCAwECHgECF4AACgkQ
UHP09XBr75NHNBAAxv2C/G13Z1kCFOSOnbPpzqcIDcMuP7RK1Mv5XfOZLfqSw4le
gdDmZggX2/EBH6xFTXFPLSE6rVUKTkHLA7IY8D43GBtDWjcIyyuLnIjtR+LhRKCP
3/Sm8MyZMQvUH1CBpUXFNnP/HCR6xjm1Mog5kXxFeCR9PMjeEiobKXIVuMfuNlBD
WzoR2Nh+oroXLjZw3VMFewiCyhu4Pe7F3sLpVldiI3PBOyPQOBZ3HEIM490D/Lrh
rl3Wwmoug8j8rqkh/Fr+kKaToRJik4PkcxsfepzhMdNfCpr7I3jE5XQHzib5Ubv8
wsSaVNBG92NTnGKoAntWXBUaiDN84St9l+Zm/BgedRk+7wdESHBuOuFXoRc0yEjF
4tLOhyO9u5bYGQWHyJiwhbw51R8G+Kh3OPq/tr4KmsuueEI2v5cLkoDzwCpYyMnu
BfU8d0mt5eULbQCWcy7LYeQs6E+CEB+tPL3Qz2zaAAvwt7N2PLMjHf5Fcqj5LqrV
mzQfcB9zQFq9Rtld/IIIDkE1y/q/SNFYsFNW/u/bxWsu+lMOYtBco++O5DJhAq6t
7rJXUBirju50hhogHfBL2v6RG1b8/uiWm0m8713ZhiSvpr4Dd+V+DU9nPli5nTmU
En6gP7TTYJKETMf7O9i873Z8yG6zd0/fBzFyruS2KRTPV2GiVT6CI37gUtw=
=fcOW
-END PGP PUBLIC KEY BLOCK-

-- 
You received this message because you are subscribed to the Google Groups 
"Django internationalization and localization" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-i18n+unsubscr...@googlegroups.com.
To post to this group, send email to django-i18n@googlegroups.com.
Visit this group at http://groups.google.com/group/django-i18n.
For more options, visit https://groups.google.com/d/optout.

How to test my translation?

[Fòram na Gàidhlig]

Hi all,

First of all, a big thanks to the devs to reacting to all my queries
that fast! Also, string design is generally very good :)

I have now managed to set up a Django environment for testing and have
done some in-context proofreading on the admin interface. I would also
like to do that for core and the other modules. Is there a ready-made
application somwhere that I can use? I tried searching for one, but the
search results get me info on unit tests, which isn't what I need here,
or a plethora of unrelated test_djanngo repositories on Github.

GunChleoc

-- 
You received this message because you are subscribed to the Google Groups 
"Django internationalization and localization" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-i18n+unsubscr...@googlegroups.com.
To post to this group, send email to django-i18n@googlegroups.com.
Visit this group at http://groups.google.com/group/django-i18n.
For more options, visit https://groups.google.com/d/optout.

Re: No answers from project maintainers on Transifex

[Fòram na Gàidhlig]

Sgrìobh Aymeric Augustin na leanas 12/05/2016 aig 08:18:
> 
> Unfortunately we appear to have a non-negligible attrition rate among
> coordinators. Unmaintained languages are more likely to attract new
> contributions, which makes the problem worse.
> 
> I think we should adopt rules such as:
> 
> - if a coordinator doesn't respond in two weeks, we accept a contributor
>   who want to join their team
> 
> - if a coordinator doesn't respond in two weeks, we promote a contributor
>   who wants to coordinate the team
> 
> What do you think?

Sounds good to me.

-- 
You received this message because you are subscribed to the Google Groups 
"Django internationalization and localization" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-i18n+unsubscr...@googlegroups.com.
To post to this group, send email to django-i18n@googlegroups.com.
Visit this group at https://groups.google.com/group/django-i18n.
For more options, visit https://groups.google.com/d/optout.

Re: Another Trasifex Issue- Language does not apear on drop down list

[Fòram na Gàidhlig]

Also, if somebody has already requested the language, Transifex will
hide it from the list - even if it hasn't been added yet.


Sgrìobh Aymeric Augustin na leanas 13/05/2016 aig 06:46:
> The screenshot talks about the “django-docs” project. You should join
> the “django” project instead.
> 
> The docs are only translated into a handful of languages as it’s a
> significant endeavour (equivalent to a 1000 - 1500 pages book) that
> requires a large translation team.
> 
> -- 
> Aymeric.
> 
>> On 13 May 2016, at 00:33, Oksidans > > wrote:
>>
>> 
>>
>> I now have to admit that I am confused. I wanted to ask permission to
>> join django project's team for Serbian language. The language is
>> listed below, but not appearing on drop down list. I provide a
>> screenshot for you to see. Other languages appear on the list, Even
>> Klingon language!  I find this very disturbing and unpleasant.
>>
>>
>> -- 
>> You received this message because you are subscribed to the Google
>> Groups "Django internationalization and localization" group.
>> To unsubscribe from this group and stop receiving emails from it, send
>> an email to django-i18n+unsubscr...@googlegroups.com
>> .
>> To post to this group, send email to django-i18n@googlegroups.com
>> .
>> Visit this group at https://groups.google.com/group/django-i18n.
>> For more options, visit https://groups.google.com/d/optout.
> 
> -- 
> You received this message because you are subscribed to the Google
> Groups "Django internationalization and localization" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to django-i18n+unsubscr...@googlegroups.com
> .
> To post to this group, send email to django-i18n@googlegroups.com
> .
> Visit this group at https://groups.google.com/group/django-i18n.
> For more options, visit https://groups.google.com/d/optout.

-- 
-BEGIN PGP PUBLIC KEY BLOCK-
Version: GnuPG v2.0.22 (MingW32)

mQINBFNbSyEBEADh+uhohycnZgPPnyMs5pZQG6pKyLzFZoIKbVjY31ZoPZ2SdltB
elrwn6kFZkQiDx4K6nkZFHsPh8RMvWoFWg1rGiWkdsZessLFawraC8YEZDwtlaU5
SFXbE4+QnMfbPhe9tmC8Nbhec3dfV9zcXAhxc+zkIUsKFhSkpJ2Syvo9FCA/5adW
UZgWWKFwlSg4+/lrhJ6QJnldPlXfWcuEasKF7fjdafDIdS5hdKu8Lv+CiPQWvgsi
J2BDlZLzEZf3PD+NMujUbJa0nilD2ltu3/qRvR2f86YV6wRwt4E2OD8JJQOau4X2
Pg7vqkIbnB9rMiQ6T17rQ4rc80eesGCxQ6XOba9oa1eRRZDwY7HJtYwvPdw9HZaN
Lq2RRbGDGO0q7fxrzbp1WuNN+UXOA/pmVzWWczPfPHVcNIehGf3wQI+Vgh/qa+IZ
jLJ25I1Tv85cDzvv5gdtI8PR4JTfK6Db+gUJmsuIg2fmsljxA7OmeTgSPR7nEVq5
VlHYfx1T0uKlthWw/eDwlS44vTgm6HZzIdYqdPMPa/PU1U+WVuDejyDJTn/1TY78
oJMT/IixFR+N+smohhKASprewcsO2ClWGptSG0sRTiCrVHFD3Mt6SCVaxsQLHvek
KuNAUXhR2KSvYuqGT0Nv3bplN6svCp4CuAGZ3lyOIt/Sb7OFUwzcx2sOdwARAQAB
tC5Gw7JyYW0gbmEgR8OgaWRobGlnIDxmaW9zQGZvcmFtbmFnYWlkaGxpZy5uZXQ+
iQI5BBMBAgAjBQJTW0shAhsPBwsJCAcDAgEGFQgCCQoLBBYCAwECHgECF4AACgkQ
UHP09XBr75NHNBAAxv2C/G13Z1kCFOSOnbPpzqcIDcMuP7RK1Mv5XfOZLfqSw4le
gdDmZggX2/EBH6xFTXFPLSE6rVUKTkHLA7IY8D43GBtDWjcIyyuLnIjtR+LhRKCP
3/Sm8MyZMQvUH1CBpUXFNnP/HCR6xjm1Mog5kXxFeCR9PMjeEiobKXIVuMfuNlBD
WzoR2Nh+oroXLjZw3VMFewiCyhu4Pe7F3sLpVldiI3PBOyPQOBZ3HEIM490D/Lrh
rl3Wwmoug8j8rqkh/Fr+kKaToRJik4PkcxsfepzhMdNfCpr7I3jE5XQHzib5Ubv8
wsSaVNBG92NTnGKoAntWXBUaiDN84St9l+Zm/BgedRk+7wdESHBuOuFXoRc0yEjF
4tLOhyO9u5bYGQWHyJiwhbw51R8G+Kh3OPq/tr4KmsuueEI2v5cLkoDzwCpYyMnu
BfU8d0mt5eULbQCWcy7LYeQs6E+CEB+tPL3Qz2zaAAvwt7N2PLMjHf5Fcqj5LqrV
mzQfcB9zQFq9Rtld/IIIDkE1y/q/SNFYsFNW/u/bxWsu+lMOYtBco++O5DJhAq6t
7rJXUBirju50hhogHfBL2v6RG1b8/uiWm0m8713ZhiSvpr4Dd+V+DU9nPli5nTmU
En6gP7TTYJKETMf7O9i873Z8yG6zd0/fBzFyruS2KRTPV2GiVT6CI37gUtw=
=fcOW
-END PGP PUBLIC KEY BLOCK-

-- 
You received this message because you are subscribed to the Google Groups 
"Django internationalization and localization" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-i18n+unsubscr...@googlegroups.com.
To post to this group, send email to django-i18n@googlegroups.com.
Visit this group at https://groups.google.com/group/django-i18n.
For more options, visit https://groups.google.com/d/optout.

Translation issues for Django 1.10

[Fòram na Gàidhlig]

I am unable to complete my translation for django-contrib-comments due
two some issues. I have filed them on Transifex, but nobody has reacted
to them yet:

https://www.transifex.com/django/django-contrib-comments/translate/#issues

Where is te appropriate place to file translation issues?

Thanks

GunChleoc

-- 
You received this message because you are subscribed to the Google Groups 
"Django internationalization and localization" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-i18n+unsubscr...@googlegroups.com.
To post to this group, send email to django-i18n@googlegroups.com.
Visit this group at https://groups.google.com/group/django-i18n.
For more options, visit https://groups.google.com/d/optout.

Re: Translation issues for Django 1.10

[Fòram na Gàidhlig]

>> I am unable to complete my translation for django-contrib-comments due
>> two some issues. I have filed them on Transifex, but nobody has reacted
>> to them yet:
>>
>> https://www.transifex.com/django/django-contrib-comments/translate/#issues
>>
>>
>> Where is te appropriate place to file translation issues?
> 
> When the issue is about the source strings, you are supposed to report
> it with the "normal" bug tracker for the package, that is Github in this
> particular case.

https://github.com/django/django

Does not give me an Issues tab, so it seems like I'm not allowed to file
any there.


> I've personally disabled much of Transifex notifications because of too
> much noise.

It is possible to access the issues from the Transifex dashboad without
using notification e-mails - maybe once per release cycle for it not to
become too much work? I am also seeing a bunch of open language requests.


My 2 issues for django-contrib-comments are:

==

admin.py:78

1 comment was successfully %(action)s.
%(count)s comments were successfully %(action)s.

Please change "1 comment was successfully %(action)s." to "%(count)s
comment was successfully %(action)s." - otherwise, my translation will
show 1 for 11 comments. If I translate this properly, I get "Error: The
expression '%(count)s' is not present in the original phrase."

==

forms.py:99

Comment

Is this a noun or a verb?

==

And I found 2 more issues there that were filed by somebody else:

models.py:179

flag

noun or verb ?
literal translation seldomly used in Dutch.
Need more context to translate correctly.

==


templates/comments/preview.html:16

or make changes

not translatable, need more context

==

Only the first is an actual source string issue, the other 3 are
requests for information - if somebody supplied the information on this
mailing list, I would be happy to post the information on Transifex.

-- 
You received this message because you are subscribed to the Google Groups 
"Django internationalization and localization" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-i18n+unsubscr...@googlegroups.com.
To post to this group, send email to django-i18n@googlegroups.com.
Visit this group at https://groups.google.com/group/django-i18n.
For more options, visit https://groups.google.com/d/optout.

Re: Translation issues for Django 1.10

[Fòram na Gàidhlig]

> https://github.com/django/django-contrib-comments/issues

Thanks - issues opened

https://github.com/django/django-contrib-comments/issues/103

https://github.com/django/django-contrib-comments/issues/104

-- 
You received this message because you are subscribed to the Google Groups 
"Django internationalization and localization" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-i18n+unsubscr...@googlegroups.com.
To post to this group, send email to django-i18n@googlegroups.com.
Visit this group at https://groups.google.com/group/django-i18n.
For more options, visit https://groups.google.com/d/optout.

Re: German translation of language "Dutch" is wrong

[Fòram na Gàidhlig]

Sgrìobh Richard la Croix na leanas 06/01/2017 aig 18:13:
> Hello,
> 
> In my opinion, the current german translation for the language "Dutch"
> in django/conf/locale/de/LC_MESSAGES is not correct.
> 
> Currently it is translated as "Holländisch", which is the colloquial
> form. It really should be "Niederländisch" if you want it to look
> professional.
> 
> regards,
> Richard
> 
> PS. I hope this is the right place to bring this up...


I'm a German speaker and I agree. I'm not a member of the German team
though, so somebody else will have to change this.

-- 
You received this message because you are subscribed to the Google Groups 
"Django internationalization and localization" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-i18n+unsubscr...@googlegroups.com.
To post to this group, send email to django-i18n@googlegroups.com.
Visit this group at https://groups.google.com/group/django-i18n.
For more options, visit https://groups.google.com/d/optout.

Re: Wrong plural form used in Polish translation when the number is 14.

[Fòram na Gàidhlig]

You can contact Transifex here:

https://www.transifex.com/contact/

You sould also compare with the plural rule in the CLRD, to make sure
that the error isn't there already. Transifex updated the Polish Plural
forms recently to match the CLDR.

http://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html#pl

If thee is a problem in the CLDR, you can file a ticket:

http://unicode.org/cldr/trac/newticket

See also:

http://unicode.org/cldr/trac/ticket/2556

http://unicode.org/cldr/trac/ticket/3685


Sgrìobh Claude Paroz na leanas 27/04/2017 aig 20:37:
> Hi Diego,
> 
> May I request your expertise on this question? Would you be able to
> answer Rafał's question?
> 
> Claude
> 
> Le 27. 04. 17 à 19:17, Rafał P. a écrit :
>> Thanks Claude and Maciej.
>> So I guess the rule Transifex uses for Polish is wrong; in the .po file
>> downloaded from there it is:
>> |
>> Plural-Forms:nplurals=4;plural=(n==1?0:(n%10>=2&&n%10<=4)&&(n%100<12||n%100>=14)?1:n!=1&&(n%10>=0&&n%10<=1)||(n%10>=5&&n%10<=9)||(n%100>=12&&n%100<=14)?2:3);
>>
>> |
>> notice "(n%100<12 || n%100>=14)"
>> -
>> http://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html
>> states
>> that for 'few' the rule is
>> |
>> v =0and
>>   i %10=2..4and
>>   i %100!=12..14
>> |
>> Seems like an 'off-by-one' mistake for me. Any idea where should I file
>> a bug report about that?
>>
>> W dniu czwartek, 27 kwietnia 2017 13:23:58 UTC+2 użytkownik Maciek Olko
>> napisał:
>>
>> Hello,
>>
>> Relevant on Transifex:
>> https://www.transifex.com/django/django/translate/#pl/core/12374783
>>
>>  .
>>
>> Rules to figure out which one is to be corrected:
>>
>> https://github.com/django/django/commit/96ec72e298cd359648e1cf408d3c506ee3b1f297#diff-1f70fc8fac8bc7919babacddb8222445R41
>>
>>
>> 
>>
>> .
>>
>> Regards,
>> Maciej
>>
>> czw., 27 kwi 2017 o 09:05 użytkownik Claude Paroz
>> > napisał:
>>
>> Le 26. 04. 17 à 21:03, Rafał P. a écrit :
>> > Hello,
>> > encountered this bug in timesince() - the result is '14
>> minuty' or '14
>> > godziny' instead of 'minut' / 'godzin'. Please see
>> > https://code.djangoproject.com/ticket/28136
>>  for additional
>> information.
>> > Tried to find anything relevant on Transifex, but with no luck.
>>
>>
>> Hey Rafał,
>>
>> Transifex changed plural rules for Polish recently. Read for
>> example:
>>
>> https://github.com/mumble-voip/mumble/issues/2854
>> 
>> https://wl.widelands.org/forum/topic/2814/?page=1
>> 
>>
>> I know some translators are not happy with that, but we have no
>> other
>> choice as users of that platform.
>>
>> I think Polish translators should now review all plural
>> strings for
>> Django. Inform us when you are done and we'll update the
>> translations in
>> a further 1.11.x Django release.
>>
>> Claude
>> --
>> www.2xlibre.net 
> 

-- 
-BEGIN PGP PUBLIC KEY BLOCK-
Version: GnuPG v2.0.22 (MingW32)

mQINBFNbSyEBEADh+uhohycnZgPPnyMs5pZQG6pKyLzFZoIKbVjY31ZoPZ2SdltB
elrwn6kFZkQiDx4K6nkZFHsPh8RMvWoFWg1rGiWkdsZessLFawraC8YEZDwtlaU5
SFXbE4+QnMfbPhe9tmC8Nbhec3dfV9zcXAhxc+zkIUsKFhSkpJ2Syvo9FCA/5adW
UZgWWKFwlSg4+/lrhJ6QJnldPlXfWcuEasKF7fjdafDIdS5hdKu8Lv+CiPQWvgsi
J2BDlZLzEZf3PD+NMujUbJa0nilD2ltu3/qRvR2f86YV6wRwt4E2OD8JJQOau4X2
Pg7vqkIbnB9rMiQ6T17rQ4rc80eesGCxQ6XOba9oa1eRRZDwY7HJtYwvPdw9HZaN
Lq2RRbGDGO0q7fxrzbp1WuNN+UXOA/pmVzWWczPfPHVcNIehGf3wQI+Vgh/qa+IZ
jLJ25I1Tv85cDzvv5gdtI8PR4JTfK6Db+gUJmsuIg2fmsljxA7OmeTgSPR7nEVq5
VlHYfx1T0uKlthWw/eDwlS44vTgm6HZzIdYqdPMPa/PU1U+WVuDejyDJTn/1TY78
oJMT/IixFR+N+smohhKASprewcsO2ClWGptSG0sRTiCrVHFD3Mt6SCVaxsQLHvek
KuNAUXhR2KSvYuqGT0Nv3bplN6svCp4CuAGZ3lyOIt/Sb7OFUwzcx2sOdwARAQAB
tC5Gw7JyYW0gbmEgR8OgaWRobGlnIDxmaW9zQGZvcmFtbmFnYWlkaGxpZy5uZXQ+
iQI5BBMBAgAjBQJTW0shAhsPBwsJCAcDAgEGFQgCCQoLBBYCAwECHgECF4AACgkQ
UHP09XBr75NHNBAAxv2C/G13Z1kCFOSOnbPpzqcIDcMuP7RK1Mv5XfOZLfqSw4le
gdDmZggX2/EBH6xFTXFPLSE6rVUKTkHLA7IY8D43GBtDWjcIyyuLnIjtR+LhRKCP
3/Sm8MyZMQvUH1CBpUXFNnP/HCR6xjm1Mog5kXxFeCR9PMjeEiobKXIVuMfuNlBD
WzoR2Nh+oroXLjZw3VMFewiCyhu4Pe7F3sLpVldiI3PBOyPQOBZ3HEIM490D/Lrh
rl3Wwmoug8j8rqkh/Fr+kKaToRJik4PkcxsfepzhMdNfCpr7I3jE5XQHzib5Ubv8
wsSaVNBG92NTnGKoAntWXBUaiDN84St9l+Zm/BgedRk+7wdESHBuOuFXoRc0yEjF
4tLOhyO9u5bYGQWHyJiwhbw51R8G+Kh3OPq/tr4KmsuueEI2v5cLkoDzwCpYyMnu
BfU8d0mt5eULbQCWcy7LYeQs6E+CEB+tPL3Qz2zaAAvwt7N2PLMjHf5Fcqj5LqrV
mzQfcB9zQFq9Rtld/IIIDkE1y/q/SNFYsFNW/u/bxWsu+lMOYtBco++O5DJhAq6t
7rJXUBirju50hhogHfBL2v6RG1b8/uiWm0m8713ZhiSvpr4Dd+V+DU9nPli5nT

Re: Translation of error messages

[Fòram na Gàidhlig]

Somebody in the bug raised the point that whether it's translated should
be a user/developer option. I agree - it can become very difficult to
search the internet for error messages when they're translated, and to
deal with bug reports where all error messages are localized.

Anything the user sees in the UI should be translated, command line
should be up to the user (except for help-related stuff like command
descriptions, man pages etc., which should be translatable in all cases).


Sgrìobh Claude Paroz na leanas 13/05/2017 aig 19:39:
> Hi Ricardo,
> 
> Until now, developer-facing strings are not translated in Django.
> Read https://code.djangoproject.com/ticket/13860 and you'll see I
> already tried to convince other devs :-)
> 
> You can still try to relaunch a discussion on the main django-developers
> list if you have the energy.
> 
> Claude
> 
> Le 13. 05. 17 à 20:13, Ricardo Mendonça Ferreira a écrit :
>> Hello, Django i18n World!
>>
>> I've just started playing around with Django 1.11, and I noticed that
>> there are no translations for most (if any) Django error messages.
>>
>> I have set [LANGUAGE_CODE = 'pt-br'] and the admin pages are in
>> Portuguese, yet 404 errors and others are still in English:
>>
>> 
>>
>>
>>
>> The above image was produced by following the tutorial03
>> .
>>
>> Notice, for example, the "No Question matches the given query", produced
>> by the shortcuts module.
>> In /usr/local/lib/python3.5/dist-packages/django/shortcuts.py the
>> strings (such as 'No %s matches the given query.') are not
>> "translatable" (the module doesn't even import ugettext).
>>
>> Is this a "bug" or a "feature"?
>>
>> I.e., are error messages not being translated for a specific reason? And
>> if so, what reason? Or is it possible to tag them for translation in the
>> next release?
>>
>> Thanks!
> 

-- 
-BEGIN PGP PUBLIC KEY BLOCK-
Version: GnuPG v2.0.22 (MingW32)

mQINBFNbSyEBEADh+uhohycnZgPPnyMs5pZQG6pKyLzFZoIKbVjY31ZoPZ2SdltB
elrwn6kFZkQiDx4K6nkZFHsPh8RMvWoFWg1rGiWkdsZessLFawraC8YEZDwtlaU5
SFXbE4+QnMfbPhe9tmC8Nbhec3dfV9zcXAhxc+zkIUsKFhSkpJ2Syvo9FCA/5adW
UZgWWKFwlSg4+/lrhJ6QJnldPlXfWcuEasKF7fjdafDIdS5hdKu8Lv+CiPQWvgsi
J2BDlZLzEZf3PD+NMujUbJa0nilD2ltu3/qRvR2f86YV6wRwt4E2OD8JJQOau4X2
Pg7vqkIbnB9rMiQ6T17rQ4rc80eesGCxQ6XOba9oa1eRRZDwY7HJtYwvPdw9HZaN
Lq2RRbGDGO0q7fxrzbp1WuNN+UXOA/pmVzWWczPfPHVcNIehGf3wQI+Vgh/qa+IZ
jLJ25I1Tv85cDzvv5gdtI8PR4JTfK6Db+gUJmsuIg2fmsljxA7OmeTgSPR7nEVq5
VlHYfx1T0uKlthWw/eDwlS44vTgm6HZzIdYqdPMPa/PU1U+WVuDejyDJTn/1TY78
oJMT/IixFR+N+smohhKASprewcsO2ClWGptSG0sRTiCrVHFD3Mt6SCVaxsQLHvek
KuNAUXhR2KSvYuqGT0Nv3bplN6svCp4CuAGZ3lyOIt/Sb7OFUwzcx2sOdwARAQAB
tC5Gw7JyYW0gbmEgR8OgaWRobGlnIDxmaW9zQGZvcmFtbmFnYWlkaGxpZy5uZXQ+
iQI5BBMBAgAjBQJTW0shAhsPBwsJCAcDAgEGFQgCCQoLBBYCAwECHgECF4AACgkQ
UHP09XBr75NHNBAAxv2C/G13Z1kCFOSOnbPpzqcIDcMuP7RK1Mv5XfOZLfqSw4le
gdDmZggX2/EBH6xFTXFPLSE6rVUKTkHLA7IY8D43GBtDWjcIyyuLnIjtR+LhRKCP
3/Sm8MyZMQvUH1CBpUXFNnP/HCR6xjm1Mog5kXxFeCR9PMjeEiobKXIVuMfuNlBD
WzoR2Nh+oroXLjZw3VMFewiCyhu4Pe7F3sLpVldiI3PBOyPQOBZ3HEIM490D/Lrh
rl3Wwmoug8j8rqkh/Fr+kKaToRJik4PkcxsfepzhMdNfCpr7I3jE5XQHzib5Ubv8
wsSaVNBG92NTnGKoAntWXBUaiDN84St9l+Zm/BgedRk+7wdESHBuOuFXoRc0yEjF
4tLOhyO9u5bYGQWHyJiwhbw51R8G+Kh3OPq/tr4KmsuueEI2v5cLkoDzwCpYyMnu
BfU8d0mt5eULbQCWcy7LYeQs6E+CEB+tPL3Qz2zaAAvwt7N2PLMjHf5Fcqj5LqrV
mzQfcB9zQFq9Rtld/IIIDkE1y/q/SNFYsFNW/u/bxWsu+lMOYtBco++O5DJhAq6t
7rJXUBirju50hhogHfBL2v6RG1b8/uiWm0m8713ZhiSvpr4Dd+V+DU9nPli5nTmU
En6gP7TTYJKETMf7O9i873Z8yG6zd0/fBzFyruS2KRTPV2GiVT6CI37gUtw=
=fcOW
-END PGP PUBLIC KEY BLOCK-

-- 
You received this message because you are subscribed to the Google Groups 
"Django internationalization and localization" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-i18n+unsubscr...@googlegroups.com.
To post to this group, send email to django-i18n@googlegroups.com.
Visit this group at https://groups.google.com/group/django-i18n.
For more options, visit https://groups.google.com/d/optout.

Re: Transifex, was: Re: How to make our language show on django docs ?

[Fòram na Gàidhlig]

Sgrìobh Claude Paroz na leanas 27/03/2018 aig 09:22:
> Le 26. 03. 18 à 10:30, Vláďa Macek a écrit :
> (...)
>>> In the email you sent me, there is also a reference to the language
>>> codes. I am not sure I have completely understood what you are trying to
>>> do but please note that both languages are supported. Please note that
>>> different language codes for the same languages are used in Transifex,
>>> because they have to do with the framework each and every single
>>> customer
>>> of ours uses/prefers. So, if you are a localization manager, then you
>>> can
>>> decide which of them is ideal for your localization goals.
>>>
>>> I hope that this helps.
> 
> This is interesting news, indeed. However, I didn't find the way to
> change locale codes in the Transifex interface as I see no gear icon
> beside teams in the list, and didn't find any hint in
> https://docs.transifex.com/ either.

I guess you will have to start new translations, copy everything over
and then have everybody in the team sign up to the new locale, then
delete the old locale. Is this important enough for spending the time it
would take?

-- 
You received this message because you are subscribed to the Google Groups 
"Django internationalization and localization" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-i18n+unsubscr...@googlegroups.com.
To post to this group, send email to django-i18n@googlegroups.com.
Visit this group at https://groups.google.com/group/django-i18n.
For more options, visit https://groups.google.com/d/optout.

Re: Question about grammatical case when “humanizing” dates

[Fòram na Gàidhlig]

Hi Max,

thanks for looking into this!

To answer your question: Always, always, always present the translators
with full sentences, no exceptions. Even if the current hard-coding
should work for 50 languages that have been tested, language #51 will
come along and have a different word order and screw things up.

So, the string markup should be "X days ago" and "In X days", with no
hard-coded word order at all. You're already taking the plural forms
into account by using npgettext, so that bit is correct.

Scottish Gaelic examples:

2 days ago:
2 latha air ais

3 days ago:
3 làithean air ais

In 2 days:
An ceann 2 latha

In 3 days:
An ceann 3 làithean

I hope that helps.

Cheers

GunChleoc



Sgrìobh Max Merz na leanas 16/04/2018 aig 14:08:
> Hello everybody,
> 
> I am the author of a pull request to fix Django bug #21408
> , which concerns the German
> translation of the phrases “X days ago” and “X days from now”. Up until
> now, these phrases were translated into German with “vor X Tage” and “in
> X Tage”, while the correct translation would have been “vor X Tagen” and
> “in X Tagen” (this corresponds to the Dative inflection of the word “Tag”).
> The problem lies in the fact that Django's implementation does not
> translate the phrase “X days ago” as one, but rather translates the
> phrases “… ago” and “X days” separately, and puts the two translations
> together afterwards. I tried to fix the bug for the German language by
> introducing a `naturaltime` context to pass to `npgettext_lazy` when
> translating “X days”, so that it would translate to “X Tagen”. (The same
> holds for “… from now”.)
> 
> When reviewing the changes in my pull request
> , Claude Paroz noted that
> there might be languages in which a differentiation between “X days ago”
> and “X days from now” is needed.
> My (our) question is now: Are there any such languages, and if yes,
> could you provide an example?
> 
> Thank you very much in advance :)
> 
> Cheers
> Max
> 
> -- 
> You received this message because you are subscribed to the Google
> Groups "Django internationalization and localization" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to django-i18n+unsubscr...@googlegroups.com
> .
> To post to this group, send email to django-i18n@googlegroups.com
> .
> Visit this group at https://groups.google.com/group/django-i18n.
> For more options, visit https://groups.google.com/d/optout.

-- 
-BEGIN PGP PUBLIC KEY BLOCK-
Version: GnuPG v2.0.22 (MingW32)

mQINBFNbSyEBEADh+uhohycnZgPPnyMs5pZQG6pKyLzFZoIKbVjY31ZoPZ2SdltB
elrwn6kFZkQiDx4K6nkZFHsPh8RMvWoFWg1rGiWkdsZessLFawraC8YEZDwtlaU5
SFXbE4+QnMfbPhe9tmC8Nbhec3dfV9zcXAhxc+zkIUsKFhSkpJ2Syvo9FCA/5adW
UZgWWKFwlSg4+/lrhJ6QJnldPlXfWcuEasKF7fjdafDIdS5hdKu8Lv+CiPQWvgsi
J2BDlZLzEZf3PD+NMujUbJa0nilD2ltu3/qRvR2f86YV6wRwt4E2OD8JJQOau4X2
Pg7vqkIbnB9rMiQ6T17rQ4rc80eesGCxQ6XOba9oa1eRRZDwY7HJtYwvPdw9HZaN
Lq2RRbGDGO0q7fxrzbp1WuNN+UXOA/pmVzWWczPfPHVcNIehGf3wQI+Vgh/qa+IZ
jLJ25I1Tv85cDzvv5gdtI8PR4JTfK6Db+gUJmsuIg2fmsljxA7OmeTgSPR7nEVq5
VlHYfx1T0uKlthWw/eDwlS44vTgm6HZzIdYqdPMPa/PU1U+WVuDejyDJTn/1TY78
oJMT/IixFR+N+smohhKASprewcsO2ClWGptSG0sRTiCrVHFD3Mt6SCVaxsQLHvek
KuNAUXhR2KSvYuqGT0Nv3bplN6svCp4CuAGZ3lyOIt/Sb7OFUwzcx2sOdwARAQAB
tC5Gw7JyYW0gbmEgR8OgaWRobGlnIDxmaW9zQGZvcmFtbmFnYWlkaGxpZy5uZXQ+
iQI5BBMBAgAjBQJTW0shAhsPBwsJCAcDAgEGFQgCCQoLBBYCAwECHgECF4AACgkQ
UHP09XBr75NHNBAAxv2C/G13Z1kCFOSOnbPpzqcIDcMuP7RK1Mv5XfOZLfqSw4le
gdDmZggX2/EBH6xFTXFPLSE6rVUKTkHLA7IY8D43GBtDWjcIyyuLnIjtR+LhRKCP
3/Sm8MyZMQvUH1CBpUXFNnP/HCR6xjm1Mog5kXxFeCR9PMjeEiobKXIVuMfuNlBD
WzoR2Nh+oroXLjZw3VMFewiCyhu4Pe7F3sLpVldiI3PBOyPQOBZ3HEIM490D/Lrh
rl3Wwmoug8j8rqkh/Fr+kKaToRJik4PkcxsfepzhMdNfCpr7I3jE5XQHzib5Ubv8
wsSaVNBG92NTnGKoAntWXBUaiDN84St9l+Zm/BgedRk+7wdESHBuOuFXoRc0yEjF
4tLOhyO9u5bYGQWHyJiwhbw51R8G+Kh3OPq/tr4KmsuueEI2v5cLkoDzwCpYyMnu
BfU8d0mt5eULbQCWcy7LYeQs6E+CEB+tPL3Qz2zaAAvwt7N2PLMjHf5Fcqj5LqrV
mzQfcB9zQFq9Rtld/IIIDkE1y/q/SNFYsFNW/u/bxWsu+lMOYtBco++O5DJhAq6t
7rJXUBirju50hhogHfBL2v6RG1b8/uiWm0m8713ZhiSvpr4Dd+V+DU9nPli5nTmU
En6gP7TTYJKETMf7O9i873Z8yG6zd0/fBzFyruS2KRTPV2GiVT6CI37gUtw=
=fcOW
-END PGP PUBLIC KEY BLOCK-

-- 
You received this message because you are subscribed to the Google Groups 
"Django internationalization and localization" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-i18n+unsubscr...@googlegroups.com.
To post to this group, send email to django-i18n@googlegroups.com.
Visit this group at https://groups.google.com/group/django-i18n.
For more options, visit https://groups.google.com/d/optout.

Re: Question about grammatical case when “humanizing” dates

[Fòram na Gàidhlig]

Sgrìobh Claude Paroz na leanas 07/05/2018 aig 07:54:
> Le 07. 05. 18 à 08:34, Fòram na Gàidhlig a écrit :
>> Hi Max,
>>
>> thanks for looking into this!
>>
>> To answer your question: Always, always, always present the translators
>> with full sentences, no exceptions. Even if the current hard-coding
>> should work for 50 languages that have been tested, language #51 will
>> come along and have a different word order and screw things up.
>>
>> So, the string markup should be "X days ago" and "In X days", with no
>> hard-coded word order at all. You're already taking the plural forms
>> into account by using npgettext, so that bit is correct.
> 
> Hey GunChleoc,
> 
> You know I'm already convinced with this rule, however it's very
> difficult (if possible at all) in the present use case, because the
> composed string is highly dynamic. It can be:
> 
> 3 days ago
> 2 weeks, 3 days ago
> 1 year, 3 months ago
> ...
> 
> We'll try to come with an improved situation with the patch. Anyone with
> a still better implementation idea is welcome to participate.
> 
> Claude
> 
>>> When reviewing the changes in my pull request
>>> <https://github.com/django/django/pull/9777
> 


That's a tougher situation - I guess we'll need to separate the "x days"
bit then with npgettext and have a "X, Y ago" string? Or maybe 2 of
those, one for day/month and one for month/year?

-- 
You received this message because you are subscribed to the Google Groups 
"Django internationalization and localization" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-i18n+unsubscr...@googlegroups.com.
To post to this group, send email to django-i18n@googlegroups.com.
Visit this group at https://groups.google.com/group/django-i18n.
For more options, visit https://groups.google.com/d/optout.

Re: translation for djangoproject.com

[Fòram na Gàidhlig]

Sgrìobh Claude Paroz na leanas 23/02/2019 aig 07:44:
> Le 23.02.19 à 02:41, Maciek Olko a écrit :
>> Thinking it off I would set 100% for translated strings as initial
>> whitelist-joining requirement and I am all-in for "onlyreviewed" mode
>> here to prevent vandalisms and assure quality (aren't those
>> requirements too strict?).
> 
> I would be against the "onlyreviewed" mode, because depending on the
> team, it is difficult to do it properly. If there is only one
> translator, marking its own strings reviewed (which she would be forced
> to do) goes against the spirit of the review functionality.
> 
> Claude

I agree with Claude's statement. My locale does not have the resources
to follow a review process. Fortunately, Transifex has a bulk review
function where I can mark everything as reviewed fairly quickly and save
me the time, but:

- I need to remember to do so every time. Every time I forget,
  finished strings will be missing from the product.

- I can't use the review function for actual reviewing any more

-- 
You received this message because you are subscribed to the Google Groups 
"Django internationalization and localization" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-i18n+unsubscr...@googlegroups.com.
To post to this group, send email to django-i18n@googlegroups.com.
Visit this group at https://groups.google.com/group/django-i18n.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature