Re: Hebrew translation and BiDi issues
Wilson Miner wrote: > Sure, sounds great. > Opened a ticket #1581 regarding translations of django and djangojs. The BiDi patches will follow (but those will take some time). Cheers -- Meir Kriheli http://mksoft.co.il --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django I18N" group. To post to this group, send email to [EMAIL PROTECTED] 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
Jeroen Ruigrok van der Werven wrote: > On 6/7/06, Wilson Miner <[EMAIL PROTECTED]> wrote: >> I think that makes sense - having one rtl.css that overrides the default >> styles. It's a lot more maintainable than trying to keep multiple rtl >> stylesheets in sync with the main stylesheets. >> >> You may need to use chained selectors or !important declarations in some >> places to successfully override the defaults. Let me know if I can make any >> changes to the core CSS to make things easier. > > Don't forget the dir="rtl" and dir="ltr" specifiers. We would need to > update the admin pages for that as well. And this is not CSS, but > straight into HTML of course. > > See http://www.w3.org/TR/i18n-html-tech-bidi/ for more information. > Actually that technique is rare around here. We don't specify dir="rtl" in the actual content. Most of the developers around here prefer to specify in a stylesheet "direction:rtl" for the body tag. Eases the development for multilingual sites, and it's working as it should. That's the method I'm planning to use with Django as well. Cheers -- Meir Kriheli http://mksoft.co.il --~--~-~--~~~---~--~~ 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
Jeroen Ruigrok van der Werven wrote: > On 6/8/06, Meir Kriheli <[EMAIL PROTECTED]> wrote: >> Actually that technique is rare around here. We don't specify dir="rtl" >> in the actual content. Most of the developers around here prefer to >> specify in a stylesheet "direction:rtl" for the body tag. Eases the >> development for multilingual sites, and it's working as it should. > > direction: has issues in IE 7 (especially with :hover) and in some > cases in IE 6 as well. dir="" syntax works for IE, Opera and Firefox > as it should. > > See http://www.webdevout.net/ for more information. > Someone should put that browser out of it's misery. Added it to base.html. Thanks -- Meir Kriheli http://mksoft.co.il --~--~-~--~~~---~--~~ 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 Ahmad, Ahmad Alhashemi wrote: > I've written a tool in Python that will automatically convert CSS from > LTR to RTL. It's been used successfully to ease the conversion of tens > of WordPress's themes. How do you think it could be used to help in > django? > > It basically takes a CSS file and converts all right or left rules to > the opposite and the same for values. It will preserves comments, > whitespace, .. etc. We don't want to maintain 2 (or more, since admin contains multiple) stylesheets, as they change from time to time (see Wilson's comment on this thread). We also can't replace (as is done in replacing themes' sheets) the original ones, since the system should work on multilingual site (i.e: have the ability to display ltr _and_ rtl, depending on user's chosen language). So the chosen (and implemented) path was to maintain a single rtl stylesheet which overrides only the ltr specific parts in all stylesheets. > > For Arabic websites, I see that most of them are using the dir > attribute instead of the direction CSS rule. I've always used dir to > comply with that W3C tech document (the tech document makes a lot of > sense to me). Thanks for the info :) It's already implemented both as a css rule and a dir attribute, see line 2 of base.html: http://code.djangoproject.com/browser/django/trunk/django/contrib/admin/templates/admin/base.html#L2 Cheers -- Meir Kriheli http://mksoft.co.il --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Problem with make-messages.py in utils/html.py
Hello, I'm trying to update the Hebrew translation, but getting the following error: ~/src/django_src/django $ make-messages.py -l he processing language he errors happened while running xgettext on html.py xgettext: Non-ASCII string at ./utils/html.py:10. Please specify the source encoding through --from-code. That line contains the following value: '\xe2\x80\xa2' Any ideas ? -- Meir Kriheli http://mksoft.co.il --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Updated Hebrew translation; Request for pre-releaese notification
Hi, I've updated the Hebrew translation: http://code.djangoproject.com/ticket/4229 Can we get a few days notice before a release is made, so that we can review and update the translations for the release ? 0.96, for example, caught me by surprise and the (at least Hebrew, don't know about the others) translation wasn't up to date. Cheers -- Meir Kriheli --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Updated Hebrew translation; Request for pre-releaese notification
On May 7, 4:37 am, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > On Sun, 2007-05-06 at 03:20 -0700, Meir Kriheli wrote: > > Hi, > > > I've updated the Hebrew translation: > >http://code.djangoproject.com/ticket/4229 > > > Can we get a few days notice before a release is made, so that we can > > review and update the translations for the release ? > > > 0.96, for example, caught me by surprise and the (at least Hebrew, > > don't know > > about the others) translation wasn't up to date. > > I would like to have a string freeze for a couple of weeks, ideally, > prior to 1.0 being released. > > We actually did give notification of the pending 0.96 release on this > mailing list (back on 24 Feb). It was titled "Introduction", rather than > "0.96 release coming up", but since it's a low-volume list and that was > the first post in quite a while to the list, expecting it to be read > isn't too much, I would hope. At that point I said it would be a week or > two away. It turned out to be more like a month, for various reasons. I see. > This list is the only really efficient way to communicate with > translators, so please try to stay current on the postings here. OK. Anyway, for those of us who are on dozens of mailing lists and forums a better title would be helpful ;-) Cheers -- Meir Kriheli http://mksoft.co.il --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Translating semi-names
ludvig.ericson wrote: > As some of you might've noticed, we in the Swedish translation 'team,' > if I dare call us that, have been bumping in to some difficulties when > it comes to semi-names such as "flatpage." > > The word 'flatpage' is obviously not a real English word, but a made- > up compound of "flat" and "page" to describe what the app does, had it > been "flat page," we'd be able to translate it more flexibly. > > As an example, Swedish doesn't really have that sort of "flat" that > English has, and some of the suggestions are static, flat as in not > elevated and plain flat, which doesn't really have the same meaning in > Swedish. > > So the real question is, how much do we dare bend the original name? > For a developer, seeing one's flatpage models appear as "statiska > sidor" (static pages) would be confusing, at least I'd like to think > so. Then again, for a non-developer, it'd make twice as much sense > compared to "flata sidor" (lit. non-elevated pages, or if you want to > interpret it colloquially, "feminine homosexual pages"). > > I don't think we'll ever reach a consensus on this one, so I ask: What > have you other translators done here? Surely, you've met these issues > too? > For Hebrew I've used what equals to "Simple page". Cheers -- Meir Kriheli http://mksoft.co.il --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: translation not applied
Hi, Aljosa Mohorovic wrote: > this is part of translation but only "Save" part is applied, any ideas > what i did wrong or why this could happen? > this isn't the only part that doesn't work. > > Aljosa > > 519 #: contrib/admin/templates/admin/submit_line.html:4 > 520 msgid "Save as new" > 521 msgstr "Spremi kao novi unos" > 522 > 523 #: contrib/admin/templates/admin/submit_line.html:5 > 524 #, fuzzy > 525 msgid "Save and add another" > 526 msgstr "Spremi i dodaj novi unos" > 527 > 528 #: contrib/admin/templates/admin/submit_line.html:6 > 529 #, fuzzy > 530 msgid "Save and continue editing" > 531 msgstr "Spremi i nastavi uređivati" > 532 > 533 #: contrib/admin/templates/admin/submit_line.html:7 > 534 msgid "Save" > 535 msgstr "Spremi" > "fuzzy" prevents the usage. Cheers -- Meir Kriheli --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: The road to 1.0: Translations status statistics
Ramiro Morales wrote: > Hi colleagues :), > > Just wanted to share the stats (as of r8423) of Django translations for the > different languages (variations) included in the source tree: > > ar: translated: 37%, fuzzy: 16%, untranslated: 45% > bg: translated: 62%, fuzzy: 5%, untranslated: 32% > bn: translated: 18%, fuzzy: 20%, untranslated: 60% > ca: translated: 95%, fuzzy: 3%, untranslated: 0% > cs: translated: 46%, fuzzy: 11%, untranslated: 41% > cy: translated: 28%, fuzzy: 19%, untranslated: 52% > da: translated: 37%, fuzzy: 17%, untranslated: 44% > de: translated: 64%, fuzzy: 0%, untranslated: 35% > el: translated: 40%, fuzzy: 21%, untranslated: 37% > en: translated: 0%, fuzzy: 0%, untranslated: 99% > es: translated: 97%, fuzzy: 1%, untranslated: 0% > es_AR: translated: 100%, fuzzy: 0%, untranslated: 0% > et: translated: 94%, fuzzy: 3%, untranslated: 1% > eu: translated: 54%, fuzzy: 3%, untranslated: 41% > fa: translated: 37%, fuzzy: 6%, untranslated: 56% > fi: translated: 64%, fuzzy: 9%, untranslated: 25% > fr: translated: 93%, fuzzy: 5%, untranslated: 0% > ga: translated: 32%, fuzzy: 0%, untranslated: 67% > gl: translated: 60%, fuzzy: 15%, untranslated: 24% > he: translated: 77%, fuzzy: 3%, untranslated: 19% > hr: translated: 94%, fuzzy: 4%, untranslated: 0% > hu: translated: 72%, fuzzy: 13%, untranslated: 13% > is: translated: 51%, fuzzy: 3%, untranslated: 44% > it: translated: 99%, fuzzy: 0%, untranslated: 0% > ja: translated: 99%, fuzzy: 0%, untranslated: 0% > ka: translated: 51%, fuzzy: 16%, untranslated: 32% > km: translated: 42%, fuzzy: 19%, untranslated: 38% > kn: translated: 40%, fuzzy: 17%, untranslated: 41% > ko: translated: 47%, fuzzy: 14%, untranslated: 37% > lt: translated: 50%, fuzzy: 14%, untranslated: 35% > lv: translated: 46%, fuzzy: 15%, untranslated: 38% > mk: translated: 95%, fuzzy: 3%, untranslated: 0% > nl: translated: 98%, fuzzy: 1%, untranslated: 0% > no: translated: 50%, fuzzy: 13%, untranslated: 35% > pl: translated: 99%, fuzzy: 0%, untranslated: 0% > pt: translated: 41%, fuzzy: 16%, untranslated: 41% > pt_BR: translated: 63%, fuzzy: 3%, untranslated: 32% > ro: translated: 94%, fuzzy: 4%, untranslated: 0% > ru: translated: 52%, fuzzy: 16%, untranslated: 31% > sk: translated: 49%, fuzzy: 10%, untranslated: 39% > sl: translated: 59%, fuzzy: 15%, untranslated: 24% > sr: translated: 51%, fuzzy: 8%, untranslated: 40% > sv: translated: 78%, fuzzy: 2%, untranslated: 19% > ta: translated: 42%, fuzzy: 16%, untranslated: 41% > te: translated: 33%, fuzzy: 14%, untranslated: 52% > tr: translated: 47%, fuzzy: 15%, untranslated: 36% > uk: translated: 24%, fuzzy: 17%, untranslated: 57% > zh_CN: translated: 54%, fuzzy: 16%, untranslated: 28% > zh_TW: translated: 53%, fuzzy: 16%, untranslated: 30% > > The report has been generated by a [1][2]script I've just uploaded to > [3]djangosnippets. > > The bad news: Surprisingly, there are some languages of world zones > where Django is very popular with very incomplete translations. > > The good news: We have 16 days left to do this work (1.0 launch date) > and we can make Django 1.0 rock also in the I18N department. > > Time to start updating and translating!. > How much of stats above is from local flavor ? Most of the stuff in it isn't relevant to translators (naturally) and most of time meaningless. Cheers -- Meir Kriheli --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Blog post about django i18N
On 09/19/2010 11:54 PM, madewulf wrote: Hello everybody, I just finished a blog post about i18n with Django. Comments/patches are welcome ! http://www.multitasked.net/2010/sep/19/django-i18n-tricks/ Martin De Wulf While at it, I gave a talk few months ago regarding RTL, l10n and i18n - general and Django specific: http://whatsup.org.il/meir/talks/django-i18n/django-i18n.html Cheers -- Meir Kriheli -- You received this message because you are subscribed to the Google Groups "Django I18N" group. To post to this group, send email to django-i...@googlegroups.com. To unsubscribe from this group, send email to django-i18n+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-i18n?hl=en.
Re: ANN: Translations of Django move to Transifex
Hi, On 01/23/2011 02:27 PM, Jannis Leidel wrote: > On 23.01.2011, at 12:29, Filip Dupanović wrote: > >> Great move! >> >> Can we expect new language teams to be created when 1.3's code-freeze >> sets in? > > Yes, defintely, but we are still in a somewhat early stage of the migration > process, and there are a few workflow issues to figure out. In other words, > please be patient in case we haven't responded to your language team request > yet. > > Since we already had a few people devoted to each language in our "old" > translation workflow, we'd like to politely ask those translators to step up > as coordinators of their language team. That will help us to keep the high > quality of the translations that we are used to. > > > Jannis > Hebrew translator, Transifex username: mksoft Cheers -- Meir Kriheli > > >> On Jan 21, 9:27 pm, Jannis Leidel wrote: >>> Hi all, >>> >>> I'm very happy to announce today the move of Django's own translation >>> efforts to a hosted platform based on the Open Source project Transifex: >>> >>> http://www.transifex.net/projects/p/django/ >>> >>> It will make it easier to submit updates for the 63 translations Django >>> currently has, lower the maintance burden for the core team and make it >>> trivially easy to add entirely new translations in the future. >>> >>> As part of this change we've moved the contrib app translations from the >>> django/conf/locale/ directories to their proper locations in the app >>> directories to get better translation statistics and isolate the >>> translation catalogues correctly. This of course only applies to trunk and >>> *not* the release branches. >>> >>> What this means for translators >>> --- >>> >>> Submitting translation updates requires an account >>> athttp://www.transifex.netfrom now on. You won't have to create patches >>> against the current Subversion trunk or create tickets anymore. >>> >>> See the Django contributing docs [1] and the Transifex User Guide [2] for >>> more details. >>> >>> What this means for core devs >>> - >>> >>> Updates to translations that have been made on Transifex.net will need to >>> be pulled using the transifex-client [3] just prior to rolling a release or >>> whenever it's convenient (e.g. after having added new strings). The >>> required configuraton file (``.tx/config``) has been added to trunk. More >>> information about the transifex-client can be found in its documentation. >>> [4] >>> >>> If there are any questions, please don't hesitate to ask :) >>> >>> Jannis >>> >>> 1:http://django.me/contributing-translations >>> 2:http://help.transifex.net/user-guide/ >>> 3:http://pypi.python.org/pypi/transifex-client/ >>> 4:http://help.transifex.net/user-guide/client/ > > > -- 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 django-i18n+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-i18n?hl=en.
Re: Hebrew
I've changed it in Transifex. Don't know which version will it go into. On Sun, Nov 3, 2019 at 8:45 PM אורי wrote: > Hi, > > I'm Uri and I speak Hebrew. I'm currently working on Speedy Net > <https://github.com/speedy-net/speedy-net>. I found a small error in the > Django Hebrew translation and I submitted a ticket - > https://code.djangoproject.com/ticket/30946, but I was referred to > Transifex. I tried to join Django in Hebrew on Transifex but I didn't > succeed. I would like to fix this small error in Hebrew and also to discuss > changes to ngettext_lazy and ngettext in Django 2.2, which prevent me from > upgrading Django to 2.2. You can read about it on tickets > https://code.djangoproject.com/ticket/30939, > https://code.djangoproject.com/ticket/30439 and > https://code.djangoproject.com/ticket/30945. > > > אורי > u...@speedy.net > > -- > 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 django-i18n+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-i18n/CABD5YeHiVf%2BzJ1ok3LdFEquwbHC%2Bd7VEq5PF0FDyFB_B-E%3DvOQ%40mail.gmail.com > <https://groups.google.com/d/msgid/django-i18n/CABD5YeHiVf%2BzJ1ok3LdFEquwbHC%2Bd7VEq5PF0FDyFB_B-E%3DvOQ%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- Meir Kriheli http://meirkriheli.com -- 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 django-i18n+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-i18n/CANDudSf%3DL8UUyYEX0m39revbHPdk_WcTueHEZXWfq0etuDMOFA%40mail.gmail.com.
Re: Request to join German localisation team
Hi Uri, I've just recently given Hebrew team permissions, added you. Cheers -- 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 django-i18n+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-i18n/CANDudSc0Xas7U%3DdM%2B_vFKWz88x8OUzu6vknOkSCVvw5nxY_8YQ%40mail.gmail.com.
