Re: i18n of menupaths - perl

1999-11-27 Thread Daniel . Egger
On 25 Nov, Michael Natterer wrote: > Well, I don't know how to solve this... > ...but I'd vote to put the gimp + plugin + perl + > whatever-is-in-cvs-gimp into _one_ catalog. Hm, but how would you do this... don't forget that some of the plugins are built conditionally > What do you thi

Re: i18n of menupaths - perl

1999-11-27 Thread Daniel . Egger
On 24 Nov, Marc Lehmann wrote: > How do I get the perl menupaths into the gimp .po file? it is no > problem to mark them, but the standard xgettext program is not able to > parse perl source. > Should these go into the gimp-std-plugins-file? Should I put all > translations into that file then?

Re: i18n of menupaths - perl

1999-11-25 Thread Michael Natterer
Marc Lehmann wrote: > > How do I get the perl menupaths into the gimp .po file? it is no problem > to mark them, but the standard xgettext program is not able to parse perl > source. Well, I don't know how to solve this... > Should these go into the gimp-std-plugins-file? Should I put all > tra

Re: I18N

1999-11-10 Thread Daniel . Egger
On 9 Nov, Sven Neumann wrote: > Daniel Eggert wrote: BTW: My name spelled E g g e r without any 't' > Ok, here's my setup: > glib: uptodate from CVS (1.2 branch) > gtk+: uptodate from CVS (1.2 branch) > gimp: uptodate from CVS > glibc: libc-2.0.7 > Well, my version is glibc is a bit

Re: I18N

1999-11-09 Thread Sven Neumann
Daniel Eggert wrote: > On 1 Nov, David Monniaux wrote: > > > The stupid I18N behaviour of the week: when menus are translated, any > > string for which the system finds no translation gets translated to > > "Fichier" (in French), which means "File". > > > I don't know the innards of the transla

Re: i18n problem

1999-11-07 Thread Daniel . Egger
On 5 Nov, Sven Neumann wrote: > I just used LANG=de, but using LANG=de_DE.ISO_8859-1 doesn't change > the behaviour here. Okay, let's start with something simple: - Version of Gtk+ used - Version of libc used (compiled when?) - CVS date of your GIMP version? - Settings of ALL of your loca

Re: i18n problem

1999-11-07 Thread Daniel . Egger
On 5 Nov, SHIRASAKI Yasuhiro wrote: > What menuitems are replaced by Datei? > I could not reproduce the problem. Me, too... I'll try to investigate the problem -- Servus, Daniel

Re: i18n problem

1999-11-07 Thread Daniel . Egger
On 4 Nov, Sven Neumann wrote: > If it is, the german de.po is broken too, since I experience the same > weird problem here. No, the catalogs are definitely all right (but the French one, but that incorrectness can't cause the explained behaviour) -- Servus, Daniel

Re: i18n problem

1999-11-07 Thread Daniel . Egger
On 4 Nov, SHIRASAKI Yasuhiro wrote: > Is your translation table fr.po ? > It seems to be broken when I tried to "make update-po". Duplicated entries, possibly a merging problem. Patch is on its way... -- Servus, Daniel

Re: I18N

1999-11-07 Thread Daniel . Egger
On 1 Nov, David Monniaux wrote: > The stupid I18N behaviour of the week: when menus are translated, any > string for which the system finds no translation gets translated to > "Fichier" (in French), which means "File". > I don't know the innards of the translation system, but a fact is that > t

Re: i18n fix for AlienMap

1999-10-12 Thread SHIRASAKI Yasuhiro
> Never ever translate a menupath directly. I know we used this system > (even more bad, I introduced it :)) but that leads to bad problems. I know that, but how will we handle the query like menu_translate("/Filters/Animation"), menu_translate("/Filters/Artistic"), etc ? I could not found the b

Re: i18n fix for AlienMap

1999-10-12 Thread Daniel . Egger
On 10 Oct, SHIRASAKI Yasuhiro wrote: > Here is a small i18n fix for AlienMap (2). > Check it. No, this is WRONG! Never ever translate a menupath directly. I know we used this system (even more bad, I introduced it :)) but that leads to bad problems. So either leave the path alone or just m

Re: i18n problem

1999-01-03 Thread Sven Neumann
> When I start gimp as follows: > > % env LANG=de_DE.ISO_8859-1 gimp > > I can see only 2 "Datei"s. "/Datei" and "/Datei". > No other "Datei"s ... > I just used LANG=de, but using LANG=de_DE.ISO_8859-1 doesn't change the behaviour here. Salut, Sven

Re: i18n problem

1999-01-03 Thread SHIRASAKI Yasuhiro
>As far as I can see all menu-items that are provided by >plug-ins. Additionally the Dialogs entry in the image menu (not the >one in the toolbox) and eventually a few more. Looks somewhat strange >to have over hundred filters that are called Datei and are ordered in >submenus labelled Datei... W

Re: i18n problem

1999-01-03 Thread Sven Neumann
> >If it is, the german de.po is broken too, since I experience the same weird > >problem here. > > What menuitems are replaced by Datei? I could not reproduce the > problem. > As far as I can see all menu-items that are provided by plug-ins. Additionally the Dialogs entry in the image menu (no

Re: i18n problem

1999-01-02 Thread SHIRASAKI Yasuhiro
>If it is, the german de.po is broken too, since I experience the same weird >problem here. What menuitems are replaced by Datei? I could not reproduce the problem. -- yasuhiro

Re: i18n problem

1999-01-02 Thread Sven Neumann
> >In recent 1.1.11 or CVS Gimp, there is a problem with i18n. All not-translated > >menuitems show up as "File" (in their respective i18n equivalent). > > Is your translation table fr.po ? > It seems to be broken when I tried to "make update-po". > If it is, the german de.po is broken too, sin

Re: i18n problem

1999-01-02 Thread SHIRASAKI Yasuhiro
>In recent 1.1.11 or CVS Gimp, there is a problem with i18n. All not-translated >menuitems show up as "File" (in their respective i18n equivalent). Is your translation table fr.po ? It seems to be broken when I tried to "make update-po". -- yasuhiro