[GSoC] Proposal. Translation of admin.

74 views
Skip to first unread message

Алексей Сидаш

unread,
Mar 21, 2014, 2:27:59 AM3/21/14
to django-d...@googlegroups.com
https://groups.google.com/forum/#!topic/django-developers/uxzcdHPDfTk - This is the original topic.
Hello, my name is Alexey, and I'm from Russia. I'm a first-year student in South-West State University, Faculty of Foundamental and Applied Informatics.

Admin localization for Russian language is poor.(See original thread, there was a message from the other russian speaking developer, where he says that problem actually exists.).
There are three grammatical genders in Russian, and all the words in sentense should match gender of subject. 
For example, we have two models. Article and Post
In English we say "Add new Article" and "Add new Post", right?
But in Russian article's grammatical gender is "female", but post's grammatical gender is "male", so we should say "Добавить новую Статью" for "Add new Article" and "Добавить новый Пост" for "Add new Post".
The suffix (bold) depends on noun's(Model name in this case) grammatical gender.
I believe, this problem takes place not only in Russian, but, unfortunately, I speak only Russian and English.
The main reason of translation troubles is dynamically generated strings, like this:
"Add new {{ model.verbose_name}}"
In some languages one cannot translate first part of sentense, then the other and then concatenate them. This will casuse grammatical errors in some languages, like Russian.

I strongly believe that sentense should be "atomical" unit of translation, that's why, let's provide 
django-admin.py translate-admin language-name  
command, which will create folder with translation files, and all the strings should be taken from theese files.
I believe that there is a better solution than requiring that all strings be retranslated for every new app that you create.
Comment in the first topic. 

Yes,  this problem seems to be serious problem. That's why I propose fallback to current solution when there are no translation files, because this solution is suitable enough for languages like English, without grammatical form matching between words in sentense.

Thanks for your time,
Regards,
Alexey

Florian Apolloner

unread,
Mar 21, 2014, 3:52:13 AM3/21/14
to django-d...@googlegroups.com
Hi Alexey,

first of all I hope you are aware that the deadline for proposal submission is today. That said, applications require a solid proposal similar to https://gist.github.com/chrismedrela/82cbda8d2a78a280a129 (length and structure wise). If this email is intended to be your proposal, I am sorry to tell you that it is not going to fly.


On Friday, March 21, 2014 7:27:59 AM UTC+1, Алексей Сидаш wrote:
I strongly believe that sentense should be "atomical" unit of translation, that's why, let's provide 
django-admin.py translate-admin language-name  
command, which will create folder with translation files, and all the strings should be taken from theese files.

I doubt this is going to fly, as I noted before:
  • This problem is not only limited to the admin, it's a problem for any app in russian itself
  • Your proposed solution doesn't work, there is simply no way to generate those translation units, parts of the strings are filled with database content.

I realize that it would be nice for you to have a properly translated admin, but I doubt this is the way to go.

Regards,

Florian

Reply all
Reply to author
Forward
0 new messages