Thanks for response, Jannis.
On 8.11.2013 15:26, Jannis Leidel wrote: > Hey Vlada, thanks for your feedback, sadly I can’t see any specific > issue in your post that could be turned into a ticket. Main reason I discuss it here. :) I wished to get some notion whether anyone shares my view. It appears I'm alone. > The split of translation files between core and the contrib apps was > done to be able to have more accurate translation statistics as well > as being able to separate higher and lower importance translation > catalogs from each other. E.g. the core and the admin translations > for example are much more likely to be seen by a user by the rest of > the optional contrib apps. When we moved to Transifex we were given > the ability to also see this distinction in their user interface. Thanks for explanation. I just don't see it the same way. In my opinion entire django-core is important and should be translated and done well. It seems to me the current proposal of 80% minimal coverage of django-core is like supporting my view. The core+auth+admin translations outweight the sum of the others, but the translation management overhead is equal per file. I don't count localflavors into "the others" because I'm not sure it's right to have these 850+ strings translated to all languages. Plus the app is deprecated anyway. This app would also be the only reason I'd say the split is good, because this catalog importance in my eyes is lower. The deprecation decision agrees with me. > I’m eager to hear what you mean with “various troubles from system > administration”, care to elaborate? All consequences of having to deal with thousands of files instead of tens, like slower filesystem walking, slower un/archiving, slower search, harder to focus on what's important, much larger block usage... etc. > Also, what do you mean with “thousands of cumulative useless clicks > on Transifex or in poedit”? Before the split, each translator had only one file to download, browse, fix, upload. Now the translation is more about clicking, switching, reviewing percentages... When done online, it's also more about waiting for Transifex, which is still pretty slow... Multiple it with the number of all translators to get the notion of how much time is wasted. Translating itself is not quite a fun work. I believe it's largely done by people who are not paid for the work they feel it just should be done. I humbly think these people comfort should be number one priority, not some accurate statistics. But as it seems nobody else sees the split as a problem, I can go silent. Also I will continue work in either way. Cheers, Vlada > On 08.11.2013, at 14:38, Vlada Macek <[email protected]> wrote: > >> For the other topic: >> >> As an ordinary translator and a day to day avid >> Django-using-developer, I'd like to say that I'm also concerned >> about the /number of files/ in the distribution. >> >> /Consider how small and mighty the Django is without locale >> files./ >> >> The number grew to multiples when i18n was split to app-specific >> locales recently. It's not much about the hard disk space, I agree >> that the space is cheap. >> >> But the number of files (besides the fact most of us /only use a >> fraction/ of the i18n files!) causes various troubles from system >> administration, through translation itself to development. (At >> least I hope it's not slowing down the code runtime much.) >> >> I'm not very happy about splitting to app-specific locales, I >> understand the call of purity that was satisfied here. IMHO nothing >> terrible would happen if it stood in one file per language as an >> exception from the rule. >> >> I guess every serious translator processes all the core i18n files >> anyway. Consider the thousands of cumulative useless clicks on >> Transifex or in poedit this decision caused, the amount of >> cumulative time it took to review the state of work... >> >> Just my $.02. No big deal. Just that I like stuff compact and >> useful. >> >> V. -- You received this message because you are subscribed to the Google Groups "Django internationalization and localization" 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]. Visit this group at http://groups.google.com/group/django-i18n. For more options, visit https://groups.google.com/groups/opt_out.
