#22635: Welcome page should be translatable
------------------------------+-------------------------------------------
Reporter: hakanw | Owner: giuliettamasina
Type: Bug | Status: assigned
Component: Translations | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------+-------------------------------------------
Comment (by erikr):
Conceptually, I agree with Claude, but I am wondering where this will end.
We throw many exceptions that use English strings as well, should those be
translated too? I'm concerned there would be much extra to translate,
which not everyone will find as valuable as end user facing strings. If
only parts are translated, that may lead to an inconsistent experience for
users.
So, whereas I can see how a translated welcome page is friendlier and I do
value consistency, I am a little concerned about the consequences of going
all or nothing. With that in mind, perhaps we should allow the
inconsistency here: the welcome page translated, because it is really the
first experience new developers have, but other items not translated, to
keep the translation burden manageable. I don't feel strongly though.
--
Ticket URL: <https://code.djangoproject.com/ticket/22635#comment:6>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.b837b9a1774dda85507ac3e37acbc512%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
