Am 27.08.2008 um 23:10 schrieb Zarro Boogs per Child:
#8163: Mongolian is not rendered correctly
+--------------------------------------------- Reporter: bert | Owner: etoys Type: defect | Status: new Priority: high | Milestone: 8.2.0 (was Update.2) Component: etoys-activity | Version: not specified Resolution: | Keywords: Next_action: code | Verified: 0 Blockedby: | Blocking:
+---------------------------------------------
Comment(by ohshima):
Replying to [comment:2 korakurider]:
How about having special entry in PO (not message at all actually) that
msgstr is switch whether Pango is to be used, then we could configure appropriate setting for each languages. (like that Scratch have language dependent configurations in POs)
Yes. That would be good. And language name can be supplied (#8150), too, as Scratch does.
I'm writing a change set that "exports" the extra information into the .pot file (the keys are exactly the same as Scratch; we can interpret it to figure our whether pango should be used or not). In the worst case, within 24 hours it should show up on the pootle server.
So the new strings are at the top of
http://etoys.laptop.org/src/po/templates/etoys.pot
but it is not quite clear what values a translator would have to fill in. Example values should be added as comment.
Also, which of these enables Pango? And why is there a space in " Language-Name"?
Anyway, this gives power to the translators, so it is good. But I'm not sure Scratch is the best example to base this on, it has rather simple needs font-wise ...
- Bert -
Oops. I probably sent an email prematurely...
At Thu, 28 Aug 2008 00:20:42 +0200, Bert Freudenberg wrote:
Also, which of these enables Pango? And why is there a space in " Language-Name"?
That is a type. Sorry.
Anyway, this gives power to the translators, so it is good. But I'm not sure Scratch is the best example to base this on, it has rather simple needs font-wise ...
The information already provided to Scratch can be borrowed, and that would help us at the beginning. We would probably add more specs for font size, etc.
-- Yoshiki
On Thu, Aug 28, 2008 at 7:34 AM, Yoshiki Ohshima yoshiki@vpri.org wrote:
Oops. I probably sent an email prematurely...
At Thu, 28 Aug 2008 00:20:42 +0200, Bert Freudenberg wrote:
Also, which of these enables Pango? And why is there a space in " Language-Name"?
That is a type. Sorry.
For language name why not use '<language display name>'. (see http://dev.laptop.org/ticket/8150#comment:1)
/Korakurider
Anyway, this gives power to the translators, so it is good. But I'm not sure Scratch is the best example to base this on, it has rather simple needs font-wise ...
The information already provided to Scratch can be borrowed, and that would help us at the beginning. We would probably add more specs for font size, etc.
-- Yoshiki
Etoys mailing list Etoys@lists.laptop.org http://lists.laptop.org/listinfo/etoys
That is a type. Sorry.
And above was a typo, too.
For language name why not use '<language display name>'. (see http://dev.laptop.org/ticket/8150#comment:1)
That might have been better to use the result from past. But I didn't want to add #translatedNoop etc (which I didn't have to).
As you wrote, we just can't load all of these mo files to construct the language menu however, and for language names like Japanese. we should better use the bitmaps in general. So, there should be another round of fixing needed.
-- Yoshiki
On 8/28/08, Yoshiki Ohshima yoshiki@vpri.org wrote:
That is a type. Sorry.
And above was a typo, too.
:-)
For language name why not use '<language display name>'. (see http://dev.laptop.org/ticket/8150#comment:1)
That might have been better to use the result from past. But I didn't want to add #translatedNoop etc (which I didn't have to).
Well, my point is that without #translatedNoop you could generate POT with your changes to GetTextExporter2 but with traditional magic name. does it make sense? But as you suggested in below, we should drop the translation by MO.
As you wrote, we just can't load all of these mo files to construct the language menu however, and for language names like Japanese. we should better use the bitmaps in general. So, there should be another round of fixing needed.
Yes, though it would be big deal to build the bitmaps... Small tweak trying to avoid loading MO has been implemented (#translateWithoutLoading:toLocaleID:) but this doesn't scale very well if we have many MOs...
/Korakurider
-- Yoshiki _______________________________________________ Etoys mailing list Etoys@lists.laptop.org http://lists.laptop.org/listinfo/etoys
etoys-dev@lists.squeakfoundation.org
-
Bert Freudenberg -
Korakurider -
Yoshiki Ohshima