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.
