From: David S. <dav...@gm...> - 2005-04-29 15:11:19
Attachments:
ja.po
|
SGkgYWxsLAoKQWZ0ZXIgY2xlYW5pbmcgb3V0IG15IC5lIGRpcmVjdG9yeSwgSmFwYW5lc2UgaW4g RTE3IGlzIHdvcmtpbmcgZ3JlYXQKKG5vIG1vcmUgc3F1YXJlIGJveGVzISkuIFRoZXJlIG11c3Qg aGF2ZSBiZWVuIHNvbWUgbmFzdHkgZm9udCBzZXR0aW5ncwpsZWZ0IGluIHRoZXJlIG9yIHNvbWV0 aGluZy4uLgoKQW55d2F5LCBJIGhhdmUgc3RhcnRlZCB0cmFuc2xhdGluZyB0aGUgamEucG8gZm9y IG15IHBlcnNvbmFsIHVzZSwKYm9ycm93aW5nIHNvbWUgaWRlYXMgZnJvbSB0aGUgb3JpZ2luYWwg ZTE2IGphLnBvIGZpbGUsIHdoaWNoIHNlZW1zIHRvCmhhdmUgYmVlbiBwdXQgdG9nZXRoZXIgYnkg dGhlIEVubGlnaHRlbm1lbnQtanAgbGlzdC4KSWYgdGhpcyBqYS5wbyBsb29rcyBvaywgZmVlbCBm cmVlIHRvIHB1dCBpdCBpbnRvIGN2cy4gSSBkaWQgY2hhbmdlIHRoZQoiRW5saWdodGVubWVudCIg a2F0YWthbmEgc3RyaW5ncyBiYWNrIGludG8gRW5nbGlzaC4uLiBteSBwZXJzb25hbApwcmVmZXJl bmNlLCBhdCBsZWFzdCA6LSkgSSBwbGFuIHRvIGtlZXAgd29ya2luZyBvbiBpdCBzbyBJJ2QgYmUg aGFwcHkKdG8gdXBkYXRlIGN2cyBkaXJlY3RseSB0b28gKG15IGFjY291bnQgbmFtZSBpcyAiZS10 YXJvIikuCgpJIGhhdmUgYSBxdWVzdGlvbiB0b28uIEkgYmVsaWV2ZSB0aGUgdGVtcGxhdGVzIGFy ZSBnZW5lcmF0ZWQKYXV0b21hdGljYWxseSwgYnV0IHRoZXJlIGlzIG9uZSBsaW5lIGluIHRoZSBm aWxlICBsaWtlIHRoaXM6CiM6IHNyYy9tb2R1bGVzL2Ryb3BzaGFkb3cvZV9tb2RfbWFpbi5jOjI1 NyBzcmMvbW9kdWxlcy9pYmFyL2VfbW9kX21haW4uYzo3NTQKbXNnaWQgIk1lZGl1bSIKbXNnc3Ry ICLW0CIKClNvIHRoZSBzdHJpbmcgIk1lZGl1bSIgaXMgZ2V0dGluZyB1c2VkIGZvciBib3RoIGRy b3BzaGFkb3cgKGluIHRlcm1zCm9mIHNoYXJwbmVzcykgYW5kIHRoZSBpYmFyIChpbiB0ZXJtcyBv ZiBzaXplKS4gVGhlIGNvbnRleHQgaXMgc2xpZ2h0bHkKZGlmZmVyZW50LCBzbyBpZGVhbGx5IEkg d291bGQgd2FudCB0byBkbyB0aGlzOgoKIzogc3JjL21vZHVsZXMvZHJvcHNoYWRvdy9lX21vZF9t YWluLmM6MjU3IAptc2dpZCAiTWVkaXVtIgptc2dzdHIgIjxkcm9wc2hhZG93IHRyYW5zPiIKCiM6 IHNyYy9tb2R1bGVzL2liYXIvZV9tb2RfbWFpbi5jOjc1NAptc2dpZCAiTWVkaXVtIgptc2dzdHIg IjxpYmFyIHRyYW5zPiIKCldvdWxkIHRoYXQgc2NyZXcgYW55dGhpbmcgdXA/CgpUaGFua3MsCgpE YXZpZAo= |
From: Massimo M. <mai...@in...> - 2005-04-29 18:11:38
|
Il giorno Sat, 30 Apr 2005 00:11:09 +0900 David scrisse: > I have a question too. I believe the templates are generated > automatically, but there is one line in the file like this: > #: src/modules/dropshadow/e_mod_main.c:257 > #src/modules/ibar/e_mod_main.c:754 > msgid "Medium" > msgstr "__" >=20 > So the string "Medium" is getting used for both dropshadow (in terms > of sharpness) and the ibar (in terms of size). The context is slightly > different, so ideally I would want to do this: >=20 > #: src/modules/dropshadow/e_mod_main.c:257=20 > msgid "Medium" > msgstr "<dropshadow trans>" >=20 > #: src/modules/ibar/e_mod_main.c:754 > msgid "Medium" > msgstr "<ibar trans>" >=20 > Would that screw anything up? perhaps your problem could affect other languages, so even if it works the way you say it could be better to change the source to have two different items in the generated enlightenment.pot. a similar thing was done to separate two occurences of the word "close", one referring to the distance of the dropshadow from the window, which has been modified in "near", and the other referring to the menu item to close an opened window. just my 2 cents :) --=20 Massimo Maiurana mailto:mai...@in... http://massimo.solira.org GPG keyID #7044D601 Articolo 11 - L'Italia ripudia la guerra come strumento di offesa alla libert=E0 degli altri popoli e come mezzo di risoluzione delle controversie internazionali.... |
From: David S. <dav...@gm...> - 2005-04-30 00:10:34
|
On 4/30/05, Massimo Maiurana <mai...@in...> wrote: > Il giorno Sat, 30 Apr 2005 00:11:09 +0900 David scrisse: > <snip>=20 > > Would that screw anything up? >=20 > perhaps your problem could affect other languages, so even if it works > the way you say it could be better to change the source to have two > different items in the generated enlightenment.pot. Actually, I spoke without trying - and msgfmt spits out an error complaining about duplicated messages for. I had wondered if there was something special about the #: line distinguishing the lines, but it doesn't look like it. Ah well. > a similar thing was done to separate two occurences of the word "close", > one referring to the distance of the dropshadow from the window, which > has been modified in "near", and the other referring to the menu item to > close an opened window. >=20 > just my 2 cents :) |
From: Carsten H. (T. R. <ra...@ra...> - 2005-05-01 02:15:57
|
On Sat, 30 Apr 2005 09:10:27 +0900 David Stevenson <dav...@gm...> babbled: > On 4/30/05, Massimo Maiurana <mai...@in...> wrote: > > Il giorno Sat, 30 Apr 2005 00:11:09 +0900 David scrisse: > > > <snip> > > > Would that screw anything up? > > > > perhaps your problem could affect other languages, so even if it works > > the way you say it could be better to change the source to have two > > different items in the generated enlightenment.pot. > > Actually, I spoke without trying - and msgfmt spits out an error > complaining about duplicated messages for. > I had wondered if there was something special about the #: line > distinguishing the lines, but it doesn't look like it. yeah. its a bad part about gettext. it basically does a big string hash lookup to translate - so ambiguous words used multiple times with different meanings by the same spelling and if the entire string is that 1 word - you will have these problems. its one of the problems of gettext combined with english. > Ah well. > > > a similar thing was done to separate two occurences of the word "close", > > one referring to the distance of the dropshadow from the window, which > > has been modified in "near", and the other referring to the menu item to > > close an opened window. > > > > just my 2 cents :) > > > ------------------------------------------------------- > This SF.Net email is sponsored by: NEC IT Guy Games. > Get your fingers limbered up and give it your best shot. 4 great events, 4 > opportunities to win big! Highest score wins.NEC IT Guy Games. Play to > win an NEC 61 plasma display. Visit http://www.necitguy.com/?r > _______________________________________________ > Enlightenment-intl mailing list > Enl...@li... > https://lists.sourceforge.net/lists/listinfo/enlightenment-intl > -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ra...@ra... 裸好多 ra...@de... Tokyo, Japan (東京 日本) |
From: David S. <dav...@gm...> - 2005-05-01 01:00:41
|
On 4/30/05, Massimo Maiurana <mai...@in...> wrote: > Il giorno Sat, 30 Apr 2005 00:11:09 +0900 David scrisse: >=20 > > I have a question too. I believe the templates are generated > > automatically, but there is one line in the file like this: > > #: src/modules/dropshadow/e_mod_main.c:257 > > #src/modules/ibar/e_mod_main.c:754 > > msgid "Medium" > > msgstr "__" > > > > So the string "Medium" is getting used for both dropshadow (in terms > > of sharpness) and the ibar (in terms of size). The context is slightly > > different, so ideally I would want to do this: <snip> > > Would that screw anything up? >=20 > perhaps your problem could affect other languages, so even if it works > the way you say it could be better to change the source to have two > different items in the generated enlightenment.pot. >=20 > a similar thing was done to separate two occurences of the word "close", > one referring to the distance of the dropshadow from the window, which > has been modified in "near", and the other referring to the menu item to > close an opened window. >=20 > just my 2 cents :) I was scratching around at the Gnone and KDE translation project pages, and it looks like there is a way of embedding "context information" into the messages. I couldn't really find details of what is involved though, just an overview... but it sounds useful here as well (^_^) |
From: Carsten H. (T. R. <ra...@ra...> - 2005-05-01 02:23:00
|
On Sun, 1 May 2005 10:00:32 +0900 David Stevenson <dav...@gm...> babbled: > On 4/30/05, Massimo Maiurana <mai...@in...> wrote: > > Il giorno Sat, 30 Apr 2005 00:11:09 +0900 David scrisse: > > > > > I have a question too. I believe the templates are generated > > > automatically, but there is one line in the file like this: > > > #: src/modules/dropshadow/e_mod_main.c:257 > > > #src/modules/ibar/e_mod_main.c:754 > > > msgid "Medium" > > > msgstr "__" > > > > > > So the string "Medium" is getting used for both dropshadow (in terms > > > of sharpness) and the ibar (in terms of size). The context is slightly > > > different, so ideally I would want to do this: > <snip> > > > Would that screw anything up? > > > > perhaps your problem could affect other languages, so even if it works > > the way you say it could be better to change the source to have two > > different items in the generated enlightenment.pot. > > > > a similar thing was done to separate two occurences of the word "close", > > one referring to the distance of the dropshadow from the window, which > > has been modified in "near", and the other referring to the menu item to > > close an opened window. > > > > just my 2 cents :) > > I was scratching around at the Gnone and KDE translation project > pages, and it looks like there is a way of embedding "context > information" into the messages. I couldn't really find details of what > is involved though, just an overview... but it sounds useful here as > well (^_^) and how is that done? :) -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ra...@ra... 裸好多 ra...@de... Tokyo, Japan (東京 日本) |
From: Carsten H. (T. R. <ra...@ra...> - 2005-05-01 02:23:00
|
On Sun, 1 May 2005 10:00:32 +0900 David Stevenson <dav...@gm...> babbled: > On 4/30/05, Massimo Maiurana <mai...@in...> wrote: > > Il giorno Sat, 30 Apr 2005 00:11:09 +0900 David scrisse: > > > > > I have a question too. I believe the templates are generated > > > automatically, but there is one line in the file like this: > > > #: src/modules/dropshadow/e_mod_main.c:257 > > > #src/modules/ibar/e_mod_main.c:754 > > > msgid "Medium" > > > msgstr "__" > > > > > > So the string "Medium" is getting used for both dropshadow (in terms > > > of sharpness) and the ibar (in terms of size). The context is slightly > > > different, so ideally I would want to do this: > <snip> > > > Would that screw anything up? > > > > perhaps your problem could affect other languages, so even if it works > > the way you say it could be better to change the source to have two > > different items in the generated enlightenment.pot. > > > > a similar thing was done to separate two occurences of the word "close", > > one referring to the distance of the dropshadow from the window, which > > has been modified in "near", and the other referring to the menu item to > > close an opened window. > > > > just my 2 cents :) > > I was scratching around at the Gnone and KDE translation project > pages, and it looks like there is a way of embedding "context > information" into the messages. I couldn't really find details of what > is involved though, just an overview... but it sounds useful here as > well (^_^) > > > ------------------------------------------------------- > This SF.Net email is sponsored by: NEC IT Guy Games. > Get your fingers limbered up and give it your best shot. 4 great events, 4 > opportunities to win big! Highest score wins.NEC IT Guy Games. Play to > win an NEC 61 plasma display. Visit http://www.necitguy.com/?r > _______________________________________________ > Enlightenment-intl mailing list > Enl...@li... > https://lists.sourceforge.net/lists/listinfo/enlightenment-intl > -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ra...@ra... 裸好多 ra...@de... Tokyo, Japan (東京 日本) |
From: Massimo M. <mai...@in...> - 2005-05-01 19:53:06
|
Il giorno Sun, 1 May 2005 10:00:32 +0900 David scrisse: > I was scratching around at the Gnone and KDE translation project > pages, and it looks like there is a way of embedding "context > information" into the messages. I couldn't really find details of what > is involved though, just an overview... but it sounds useful here as > well (^_^) >=20 actually it shouldn't be that hard to solve the problem, at least for what I can understand :) it should be enough to slightly change one of the two words in source, adding a space, a dot, changing a case, or something similar. for example, if the source would contain a string "Medium" and a string "medium", xgettext should see them as different and the translator could treat them differently. --=20 Massimo Maiurana mailto:mai...@in... http://massimo.solira.org GPG keyID #7044D601 Articolo 11 - L'Italia ripudia la guerra come strumento di offesa alla libert=E0 degli altri popoli e come mezzo di risoluzione delle controversie internazionali.... |
From: David S. <dav...@gm...> - 2005-05-01 06:15:16
|
Oops, forgot to address to the list... On 5/1/05, The Rasterman Carsten Haitzler <ra...@ra...> wrote: > On Sun, 1 May 2005 10:00:32 +0900 David Stevenson <dav...@gm...>= babbled: > > > I was scratching around at the Gnone and KDE translation project > > pages, and it looks like there is a way of embedding "context > > information" into the messages. I couldn't really find details of what > > is involved though, just an overview... but it sounds useful here as > > well (^_^) > > and how is that done? :) So, I did some more reading (but make no judgement on whether all this would be worth it)... From the translator's POV, as I alluded to before, they optionally have extra info in their PO files beginning with a msgid "_: <context information>" "<actual string to translate>" http://i18n.kde.org/translation-howto/gui-peculiarities.html From the developer's POV, they have added a second call to their gettext wrapper which takes the context information string as well as the string to translate. http://developer.kde.org/documentation/library/kdeqt/kde3arch/kde-i18n-howt= o.html#SECTION00031000000000000000 However, "KDE uses a patched version of gettext to use the above mentioned additional context information" http://developer.kde.org/documentation/library/kdeqt/kde3arch/kde-i18n-howt= o.html#foot527 Regards, David |
From: Carsten H. (T. R. <ra...@ra...> - 2005-05-18 04:16:33
|
On Sun, 1 May 2005 15:15:07 +0900 David Stevenson <dav...@gm...> babbled: > Oops, forgot to address to the list... > > On 5/1/05, The Rasterman Carsten Haitzler <ra...@ra...> wrote: > > On Sun, 1 May 2005 10:00:32 +0900 David Stevenson <dav...@gm...> babbled: > > > > > I was scratching around at the Gnone and KDE translation project > > > pages, and it looks like there is a way of embedding "context > > > information" into the messages. I couldn't really find details of what > > > is involved though, just an overview... but it sounds useful here as > > > well (^_^) > > > > and how is that done? :) > > So, I did some more reading (but make no judgement on whether all this > would be worth it)... > > >From the translator's POV, as I alluded to before, they optionally > have extra info in their PO files beginning with a > msgid "_: <context information>" > "<actual string to translate>" > http://i18n.kde.org/translation-howto/gui-peculiarities.html > > >From the developer's POV, they have added a second call to their > gettext wrapper which takes the context information string as well as > the string to translate. > http://developer.kde.org/documentation/library/kdeqt/kde3arch/kde-i18n-howto.html#SECTION00031000000000000000 > > However, "KDE uses a patched version of gettext to use the above > mentioned additional context information" > http://developer.kde.org/documentation/library/kdeqt/kde3arch/kde-i18n-howto.html#foot527 (better late than never... tackling the email beast) hmm - well for now lets just fix the english to not be ambiguous! :) we can always provide a en_US.po and make the english strings like "Large1" "Large2" and then translate into different english :) for now lets not worry too much as the strings will change a lot over time before e17 is released (when this stuff really counts) -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ra...@ra... 裸好多 ra...@de... Tokyo, Japan (東京 日本) |