#36579: yesno filter broken for some languages
------------------------------------+--------------------------------------
Reporter: Klaas van Schelven | Owner: (none)
Type: Uncategorized | Status: new
Component: Uncategorized | Version: dev
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------------+--------------------------------------
Comment (by Klaas van Schelven):
Looked at this a bit more.
The “missing comma” issue seems to have two causes across translations:
* Some locales use spaces instead of commas (e.g. Khmer).
* Others use locale-specific commas (e.g. Chinese 、,
Persian/Urdu/Uyghur/Kurdish ،).
So:
1. the updates to the locales should in most cases be replacing a local
comma into the latin/ascii one.
2. To avoid this recurring, the translator note could be strengthened to:
“Use ASCII commas (,) with no spaces for machine parsing. Do not
substitute local punctuation.” (or similar)
--
Ticket URL: <https://code.djangoproject.com/ticket/36579#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 django-updates+unsubscr...@googlegroups.com.
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/01070198f0902ba6-3cd0ab4d-5db6-4a45-b3cd-b7d33e033f58-000000%40eu-central-1.amazonses.com.
