Re: Hebrew translation and BiDi issues
Hi, to your questions: translations are merged to magic-removal, as are other changes in trunk. This is ok for translations, as those are never touched in m-r and ok for small patches that easily merge. But bigger patches should allways be done to magic-removal, as there are lots of differences and so the changes in trunk won't easily merge to m-r. And specifying the bidi languages in a LANGUAGES_BIDI tuple is fine. bye, Georg --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django I18N" group. To post to this group, send email to Django-I18N@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Django-I18N -~--~~~~--~~--~--~---
Re: Module name and filter_interface don't get translated in M-R
Hi, please post tickets for all issues. I'm often too busy currently to follow all discussions, but I usually react to tickets quite soon. And tickets make sure nothing is forgotten. bye, Georg --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django I18N" group. To post to this group, send email to Django-I18N@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Django-I18N -~--~~~~--~~--~--~---
Short status of me and I18N tickets
Hi, for the people waiting for theire tickets to be closed and translations applied: I didn't fall of the planet, I was just on vacation for the last two weeks and the actual MR-merge suprised me a bit ;-) I am just back to work, but due to work-related stuff this week might not be able to do much on the tickets, but I think I will be able to have a go on them the coming week at latest. Sorry for the inconvenience. bye, Georg --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django I18N" group. To post to this group, send email to Django-I18N@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Django-I18N -~--~~~~--~~--~--~---
el translation broken
Hi, the "el" translation is broken - it listed utf-8 as charset, but the content wasn't utf-8. I don't know what charset it is in, I just set it to iso-8859-1 to prevent aborts on it in the make-messages -a stage. Someone who can read that language: please look into it and tell me what charset it actually is. bye, Georg --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django I18N" group. To post to this group, send email to Django-I18N@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Django-I18N -~--~~~~--~~--~--~---
upated message files
Hi, I updated all message files for new message IDs from magic removal - all translators please update your message files to the new trunk. bye, Georg --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django I18N" group. To post to this group, send email to Django-I18N@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Django-I18N -~--~~~~--~~--~--~---
Re: el translation broken
Hi, >Please use either ISO8859-7 or UTF-8. At the moment it is in >ISO8859-7. I put an UTF-8 encoded one up at >http://www.in-nomine.org/~asmodai/django.po Thx, now it compiles fine. bye, Georg --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django I18N" group. To post to this group, send email to Django-I18N@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Django-I18N -~--~~~~--~~--~--~---
Re: el translation broken
>Per http://code.djangoproject.com/browser/django/trunk/django/conf/locale... >shouldn't the "Content-Type: text/plain; charset=iso-8859-1\n" line be >changed to reflect the UTF-8 encoding? Well - I just used your .po file under the given URI, so supposedly you should have changed that :-) Remember: I only put them in and my checks mostly are glancing over the file (if even) and running compile-messages.py. I depend on the .po file creators to deliver correct .po files :-) I fixed that in trunk. bye, Georg --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django I18N" group. To post to this group, send email to Django-I18N@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Django-I18N -~--~~~~--~~--~--~---
Re: Untranslated application names in admin
Hi, Rudolph wrote: > Same problem + solution is described here: > http://groups.google.com/group/Django-I18N/browse_thread/thread/5f262db230bb393d Yep, similar problem, only that you ask for builtin apps, while that was about user-written apps. > Hugo, how do you think this should be fixed and what should be the > default solution to put in the i18n docs? Well, I just reopened the ticket and put in a longer description on the problem, lets see what adrian thinks about it. It has an ugly note that you have to repeat the application name (which is currently taken from the module name!) and write it down explicitely, so the make-messages.py can take that up and put in a translation hook into the .po file. bye, Georg --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django I18N" group. To post to this group, send email to Django-I18N@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Django-I18N -~--~~~~--~~--~--~---
Re: RTL stylesheet startegy
Hi, > Since RTL changes are relatively small, maybe a better solution would > be to create an rtl.css which contains all the rtl needed overrides in > a single, and more maintainable file ? It would look better in the > templates as well. (loads the basic style, and in case of > LANGUAGE_BIDI, load rtl.css). Regardless on what path you take, better talk to Wilson Miner, as he is the guy in control of the Django stylesheets. bye, Georg --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django I18N" group. To post to this group, send email to Django-I18N@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Django-I18N -~--~~~~--~~--~--~---
resurfacing to drown again
Hi folks, as most of you will have noticed, I am even more absent from the project than before. It now takes on a level where I can't guarantee timely reaction to any tickets any more, and most definitely won't find the time to go at some of the proposed patches. For that I think it would be much better for the project if someone else steps up and takes over the job. Adding translation updates is very easy, I usually only did a cursory formal check of the translation content (mostly wether the header is set right and the encoding looked correct) and then added it to the trunk. Don't forget to run compile-messages after adding the .po file ;) Adding some of the patches would be better done by one of the other devs, too, because otherwise they might just sit there and rot until I find some time to work on django again. Which would be a shame, Django still is the framework with the best i18n infrastructure out there, despite all i18n problems that are there in software. Best would be if you would discuss in this list who could take up the job and get adrian and jacob on the board for getting a new i18n guy or girl set up. I won't be around much, you can reach me via eMail, but don't expect fast responses. bye, hugo --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django I18N" group. To post to this group, send email to Django-I18N@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Django-I18N?hl=en -~--~~~~--~~--~--~---
