Re: Qt2 translation. tr() vs. _()

2001-08-28 Thread Juergen Vigna
On 27-Aug-2001 Lars Gullik Bjønnes wrote: >| I have no idea how the po/ stuff works. If so, we need to build in >| src/frontends/qt2/ui/ >| before doing this (it would be really really gross to have to add >| all the generated files to CVS) > > I do not find that gross at all... Me neighter!

Re: Qt2 translation. tr() vs. _()

2001-08-27 Thread John Levon
On Mon, Aug 27, 2001 at 09:04:17PM +0200, Lars Gullik Bjønnes wrote: > | + -I${top_builddir}/src/frontends/qt2 \ > > Ok, I have it compiling _and_ linking now. hurrah, thanks ! john, waiting to see where he was stupid ... -- "Premature generalization is the root of all evil." -

Re: Qt2 translation. tr() vs. _()

2001-08-27 Thread John Levon
On Mon, Aug 27, 2001 at 08:20:15PM +0200, Lars Gullik Bjønnes wrote: > Note: I always use srcdir != builddir when compiling. ah, I see, that explains it. Well the patch I sent should work right, yes ? thanks john -- "Premature generalization is the root of all evil." - Karl Fogel

Re: Qt2 translation. tr() vs. _()

2001-08-27 Thread John Levon
On Mon, Aug 27, 2001 at 07:29:14PM +0200, Lars Gullik Bjønnes wrote: > there are two options for the po stuff... genereate from the ui files ok, it looks like this can be done by grepping for some text good idea I think > ../../../../../src/frontends/qt2/QAboutDialog.h:11:33: ui/QAboutDialogBas

Re: Qt2 translation. tr() vs. _()

2001-08-27 Thread John Levon
On Mon, Aug 27, 2001 at 07:08:36PM +0200, Lars Gullik Bjønnes wrote: > | you don't ? You can't read diffs very much - editing them is a real pain. > > you lost me now... I make changes in qt2, then cvs diff >a.diff so I can read what I changed. With the generated files in CVS, I have to wade th

Re: Qt2 translation. tr() vs. _()

2001-08-27 Thread John Levon
On Mon, Aug 27, 2001 at 06:55:21PM +0200, Lars Gullik Bjønnes wrote: > | I have no idea how the po/ stuff works. If so, we need to build in >src/frontends/qt2/ui/ > | before doing this (it would be really really gross to have to add > | all the generated files to CVS) > > I do not find that gro

Re: Qt2 translation. tr() vs. _()

2001-08-27 Thread John Levon
On Mon, Aug 27, 2001 at 05:24:09PM +0200, Juergen Vigna wrote: > Why? This is a problem of the dialog-editor/converter which does not permit > to do it in another way, so you should then ask to fix this in the "designer". OK, I've just realised uic can output to stdout, so we can do the sed w/o

Re: Qt2 translation. tr() vs. _()

2001-08-27 Thread John Levon
On Mon, Aug 27, 2001 at 05:24:09PM +0200, Juergen Vigna wrote: > Why? This is a problem of the dialog-editor/converter which does not permit > to do it in another way, so you should then ask to fix this in the "designer". you're right, and I've just thought of a nice way. uic can output to stdou

Re: Qt2 translation. tr() vs. _()

2001-08-27 Thread Juergen Vigna
On 27-Aug-2001 John Levon wrote: > On Mon, Aug 27, 2001 at 11:29:03AM +0200, Juergen Vigna wrote: > >> Well I fix this stuff by a makefile and postprocessing the generated .C files >> (as we do in xforms) this is quite easy to do using 'sed'. > > this is a real last hope thing. Such things are

Re: Qt2 translation. tr() vs. _()

2001-08-27 Thread John Levon
On Mon, Aug 27, 2001 at 11:29:03AM +0200, Juergen Vigna wrote: > Well I fix this stuff by a makefile and postprocessing the generated .C files > (as we do in xforms) this is quite easy to do using 'sed'. this is a real last hope thing. Such things are pretty horrible ... regards john -- "Prem

RE: Qt2 translation. tr() vs. _()

2001-08-27 Thread Juergen Vigna
On 25-Aug-2001 John Levon wrote: > > The Qt2 frontend is currently using Qt's "tr()" in its dialogs. This is > obviously not going to get along with the rest of LyX using plain old gettext > _() > > Anyone ideas on how to solve this ? > > tr("") happens, which isn't allowable with gettext ap

Qt2 translation. tr() vs. _()

2001-08-25 Thread John Levon
The Qt2 frontend is currently using Qt's "tr()" in its dialogs. This is obviously not going to get along with the rest of LyX using plain old gettext _() Anyone ideas on how to solve this ? tr("") happens, which isn't allowable with gettext apparently. If we could allow this, we could just ad