Le 15. 05. 17 à 20:14, Ricardo Mendonça Ferreira a écrit :
Thanks, Claude! That was enlightening (and reassuring)! :)
My main concern was if the uses would see any English error messages at
all. Of course they might (depending of how I set up my app, server,
etc.), but that would be an exception
Thanks, Claude! That was enlightening (and reassuring)! :)
My main concern was if the uses would see any English error messages at
all. Of course they might (depending of how I set up my app, server, etc.),
but that would be an exception (no pun intended).
--
You received this message because
It's rather easy to change LANGUAGE_CODE to a custom value in your
active settings file.
Anyway, I think that we could find technical solutions for any problem,
giving options to keep messages in English.
The main issue is to find a real will among Django developers to offer a
developing experie
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