Re: Tons of useless translations???
Nick Lamb wrote: On Fri, Nov 26, 1999 at 01:03:08AM +0100, Sven Neumann wrote: In French I can say "Fichier-New" and then choose "Type d'image RVB, OK" Resulting image is called "SansTitre-0.0" Well, if would be working correctly, it would say "Fichier/Nouveau...". ... but people are busily re-arranging all the furniture in the Gimp menu hierarchy, so "working correctly" will have to live with what it can for now. After my last compile I am now getting File-Nouveau, so hopefully tomorrow I can expect Fichier-Nouveau... at last. No Fichier-Fichier-Fichier here, if there was I would be figuring out why it was broken (even though I don't speak French) does someone who IS seeing this bug have the time to investigate it properly? Well, the Fichier-Fichier-Fichier bug is actually fixed by my last checkin. I didn't fix it by tracking down the problem but by replacing all the useless translations of the .../tearoff1 entries by entries which actually define the menu branches. (gettext returned "Fichier" for just any string ending in .../tearoff1) My installation suffered from the old problem and still is not able to look up translations from "gimp-std-plugins" So my question to the deveopers: Does anyone have the plugin names (not the paths) correctly translated in the menu hierarchy??? ciao, --Mitch
Re: Tons of useless translations???
Mitch wrote: My installation suffered from the old problem and still is not able to look up translations from "gimp-std-plugins" So my question to the deveopers: Does anyone have the plugin names (not the paths) correctly translated in the menu hierarchy??? It seems your latest commit fixed the problem! Great work! Now it's time for the translators to update the po files and there are still a lot of plug-ins that need to be internationalized. Any volunteers? Salut, Sven
Re: Tons of useless translations???
On Fri, Nov 26, 1999 at 09:45:21PM +0100, Sven Neumann [EMAIL PROTECTED] wrote: It seems your latest commit fixed the problem! Great work! Now it's time for the translators to update the po files and there are still a lot of plug-ins that need to be internationalized. Any volunteers? We still need to work the perl plug-in names in. The problem is that gettext does not support this (and I see no way to modify the makerules without re-writing them totally. Just another reason why automake is evil). IAW: we just lost perl (although the general idea of putting the trabslations into the gimp is fine). PS: does gimp now translate by component or still using the whole path? -- -==- | ==-- _ | ---==---(_)__ __ __ Marc Lehmann +-- --==---/ / _ \/ // /\ \/ / [EMAIL PROTECTED] |e| -=/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+ The choice of a GNU generation | |
Re: Tons of useless translations???
On Sat, Nov 27, 1999 at 03:23:02AM +0100, Marc Lehmann wrote: We still need to work the perl plug-in names in. The problem is that gettext does not support this (and I see no way to modify the makerules without re-writing them totally. Just another reason why automake is evil). Doesn't Perl have its own i18n mechanism which GimpPerl could use? It make sense that GimpPerl would be consistent in behaving just like any other Perl component for i18n as much as it does for everything else? If Perl doesn't have any i18n, then (1) That sucks and (2) Gimp can't do much about it. If I missed some stupidly obvious obstacle to this then I apologise, I don't use GimpPerl so I don't know very much about it. Nick.
