I've updated the Hebrew translation:
http://code.djangoproject.com/ticket/13134
And added a small RTL fix:
http://code.djangoproject.com/ticket/13129
Please review.
P.S
##$%@#%!@$@! the localflavor, it's a bitch to translate (I'll be
thankful for it's removal from Django).
Bless the one with Indonesian geography knowledge reviewing the
translation patch.
Cheers
--
Meir Kriheli
http://mksoft.co.il
On Wednesday 17 March 2010, Meir Kriheli wrote:
>
> I've updated the Hebrew translation:
> http://code.djangoproject.com/ticket/13134
>
I went through the first 300 strings, and made a few corrections (all IMHO, of
course).
I'm attaching both the diff against trunk and the diff against Meir's version
(Meir, would you rather keep this activity on the bug?)
> And added a small RTL fix:
> http://code.djangoproject.com/ticket/13129
>
Looks fine to me...
Have fun,
Shai.
1) Maqaf־katef
I think this character is useful, and can serve in several places in the
translation (e.g. "redirect from" => "הפניה מ־"; today it says "הפניה מ").
However, I have seen fonts that make it look very bad (zero width). Should it
be used in translation of a web-based framework?
2) contrib.humanize
This is a little app which adds some template filters for a more pleasant
presentation of numeric data. These include intcomma (comma every 3 digits),
intword (12e8 => "1.2 billion"), ordinal, etc. The problem is that it is very
English-specific; one of the filters is even "apnumber", that uses the
Associated Press standard for numbers. In fact, ordinal is so English-specific
that it's a bug in every other language I'm aware of. Meir was kind enough to
translate entries there; I think if anything, the translations should strive
to keep the numbers as numerals. Opinions?
3) Boolean value names
Current translation is True=>אמת, False=>שקר. I think in the Django context,
it may be better to use כן\לא. Opinions?
4) format: תחביר או צורה?
In the context: "Enter a valid time in HH:MM[:ss[.uuuuuu]] format.", current
translation consistently uses "תחביר" for "format". Compare:
נא להזין זמן חוקי בתחביר HH:MM[:ss[.uuuuuu]].
with
נא להזין זמן חוקי בצורה HH:MM[:ss[.uuuuuu]].
Opinions?
Updated translation on the bug, http://code.djangoproject.com/ticket/13134
--
You received this message because you are subscribed to the Google Groups "PyWeb-IL" group.
To post to this group, send email to pywe...@googlegroups.com.
To unsubscribe from this group, send email to pyweb-il+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/pyweb-il?hl=en.
Google translate disagrees:
http://translate.google.co.il/translate_t?hl=&ie=UTF-8&text=Galician&sl=en&tl=iw#
I don't know how authoritative Wikipedia is.
> Please do not confuse with the Yiddish dialect.
A simple search shows Galician referred to as גליציאנית in many places.
There's also the "Google fight" argument: a search for "גליציאנית ספרדית"
yields more than twice as many results as "גליציאנית אידיש" and "גליציאנית
יידיש" combined; "גליסית", in comparison, is negligible.
That's you, but as I noted, the (google indexed) web includes tens of
references to Galician as גליציאנית for every reference to גליסית; it's one of
those terms that seem to be used by purists and nobody else.
I, personally, think switching languages with alt-shift is brain-dead, and I
set my keyboards to use alt-caps instead; but I realize that's just me. I
wouldn't suggest to make that the default in any system.
On Wednesday 24 March 2010 11:14:18 Amir Yalon wrote:That's you, but as I noted, the (google indexed) web includes tens of
> To me, גליציאנית looks like a hybrid between גליצית and Galician, which
> amounts to a redundant suffix. Just choose one suffix and stick with it,
> IMHO.
>
references to Galician as גליציאנית for every reference to גליסית; it's one of
those terms that seem to be used by purists and nobody else.
I hereby declare that I won't make any more changes to the translation of the
Galician language name. If you care enough about it, just fix the patch.
And if you care about things that actually matter, pay some attention to the
issues of boolean values and humanize.
Ofri, thanks; "תבנית" is indeed perfect for "format".
You're suggesting replacing True/False with Yes/No. I think that as
long as it is True/False in English it should remain that way in other
languages as well.
As a native speaker of both (American) English and Hebrew, to me the
difference seems slim; "False" has a strong negative connotation just
like "שקר" does. Us programmers are perhaps used to using "True/False"
in programming contexts, where they are more neutral.
It is true that in the relevant contexts the meaning of "True/False"
is more like "אמיתי/שקרי" or "נכון/לא נכון", but I think that using
anything other than "אמת/שקר" would end up causing too much confusion.
Those of you who care about the Hebrew translation of Django (with or without
specific reference to the Hebrew name of the Galician language), can now play
with a new version on http://code.djangoproject.com/ticket/13134 -- including
maqaf־katef. תבנית, and updated JavaScript translations.
Have fun,
Shai.