#15168: feature request - New setting
------------------------------------------------+---------------------------
Reporter: zay2 | Owner: nobody
Status: closed | Milestone: 1.3
Component: Internationalization | Version: SVN
Resolution: wontfix | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 |
------------------------------------------------+---------------------------
Comment (by zay2):
You see things from your point of view, so lets give it one more
shot:[[BR]]
1) Browsers/Op systems are not available in many small languages and
therefore the speakers of languages like estonians have to use
browsers/systems in english and their browsers are therefore in english -
they may not desire it.[[BR]]
2) Those users do not know how to change their browsers language - you got
to know that you and are are HUGE minority - perhaps only 5% of users know
that they CAN change their browser language. Even less people know how and
want to change it. [[BR]]
3) those 95% of people who dont know that they CAN change their browser
language or know how to, usually visit pages, which are in their own
language (the language that they speak every day, not the language their
browser is set to).[[BR]]
4) I want to make pages that can be seen in default language - the
language that the target audience of the page uses.[[BR]]
Now im not saying - "i want to ignore this 1 language when it is not set
in a cookie"(quoting bpeschier). Im saying that i want the page be in
language used by target audience. I cant do this with this accept headers
based language discovery[[BR]]
"In your case I would extend the LocaleMiddleware to mirror that; check
the HTTP_ACCEPT_LANGUAGE in META before handing it to the
LocaleMiddleware-superclass and rewrite English to Estonian "(quoting
bpeschier) - There already is default language setting - it just does not
work in all cases. [[BR]]
"Without the detection, I would get your site in Estonian, which is
probably jibberish to me."(quoting lrekucki). Well in such cases - You are
not the target audience. [[BR]]
Ask your parents or grandparents, if they know what browser accept headers
or if they can change those. This probably is irrelevant if they come from
english speaking (or other countries which's languages are spoken by
millions and millions of people) countries, since they never need to do
anything like this anyway. Parents & grandparents in countries like
Estonia, Latvia, Lithuania and so on, dont know about the accept headers
or such either. But in most cases, their browsers are in english and they
dont even know that this could be a problem.[[BR]]
Now we are making the websites for our customers and our customers are
supposed to know their target audience. If we cant deliver the website
which its target audience can see in its default language then something
is wrong. I fixed this wrong by commenting out undesired code. Not very
DRY. getting everybody, who face similar problem, extending their
middleware is also not very DRY. Why would all those people have to repeat
themselves? I still say that such setting option would be best way to
solve this.
If i cant change your mind about this - so be it. If im gonna be the only
one to see sanity in this, then so be it - i know how to fix this. Just
thought, that this would be nice minor improvement. Moving discussion to
dev's
--
Ticket URL: <http://code.djangoproject.com/ticket/15168#comment:6>
Django <http://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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
