Jürgen Spitzmüller wrote:
> No. Have a look at the method layouts_l10n in lyx_pot.py for a model.
You might also have to tweak Makefile and Scons. Have a look here for how I
did something similar to translate the external inset files (the first two
chunks of the patch are not relevant):
http://w
rgheck wrote:
> So, we need some code in po/lyx_pot.py. Do I then just pass the relevant
> strings through qt_()? E.g., something like: QString desc =
> qt_(module.getDescription())?
No. Have a look at the method layouts_l10n in lyx_pot.py for a model.
BTW I think the layouts/ folder gets a bit c
Jean-Marc Lasgouttes wrote:
Jürgen Spitzmüller <[EMAIL PROTECTED]> writes:
rgheck wrote:
By the way: Anyone have views about translation issues here? I haven't
addressed those and don't have much (well, any) experience with that
sort of issue. A proper solution would involve having tra
Jürgen Spitzmüller <[EMAIL PROTECTED]> writes:
> rgheck wrote:
>> By the way: Anyone have views about translation issues here? I haven't
>> addressed those and don't have much (well, any) experience with that
>> sort of issue. A proper solution would involve having translations of
>> the module de
rgheck wrote:
> By the way: Anyone have views about translation issues here? I haven't
> addressed those and don't have much (well, any) experience with that
> sort of issue. A proper solution would involve having translations of
> the module descriptions in the module files themselves, I would sup
