#31302: A lot of messages become untranslated after #30400 (typographic
improvement)
-------------------------------------+-------------------------------------
Reporter: rad164 | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Uncategorized | Version: 3.0
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Claude Paroz):
* status: new => closed
* resolution: => invalid
Comment:
Sorry, we knew that this change was going to give translators some work,
but translators had several weeks to translate them for 3.0, and even for
3.0.3. And as a translator myself, I can tell you that updating those
strings should not take much than 30 minutes on Transifex.
I have strong doubts about your affirmation that:
> these locales seems to be '100% translated' on transifex but shows
English message at many places...
It could be the case if translators did their work after January 31st, but
otherwise it shouldn't happen (and if it does, create a specific ticket
with example language/code).
I am against pushing ourselves changes in .po files, as this is the realm
of translators and it should stay so.
--
Ticket URL: <https://code.djangoproject.com/ticket/31302#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.f48d786f7d0c945a3d499f60a1fdf5fd%40djangoproject.com.
