Re: Some questions about xml-i18n-tools
- From: Gediminas Paulauskas <menesis delfi lt>
- To: Carlos Perelló Marín <carlos gnome-db org>
- Cc: GNOME i18n list <gnome-i18n gnome org>,Setup Tool Hackers <setup-tool-hackers helixcode com>
- Subject: Re: Some questions about xml-i18n-tools
- Date: 21 May 2001 22:35:20 +0200
On 21 May 2001 21:48:26 +0200, Carlos Perelló Marín wrote:
> <ETableColumn model_col=\"4\" _title=\"Device\" expansion=\"1.0\"
> minimum_width=\"10\" resizable=\"true\" cell=\"string\"
> compare=\"string\"/> \
> </ETableSpecification>";
>
> </example>
>
> As you can see it's XML code inside a .c file, so It will never be
> extracted to be translated.
>
> Ideas?
> It's possible to modify xml-i18n-tools to handle those special things?
In evolution it is done by providing a copy of those strings in dummy define:
#ifdef JUST_FOR_TRANSLATORS
static char *strings[] = (
N_("Device"),
N_("Mount point"),
N_("Size")
);
#endif
so xgettext finds them and puts in .pot file. But when programmers change xml spec, they also need to update these copies.
The same thing is done, when a translatable string appears inside #define, where xgettext does not find them. Well, this example also was
#define SPEC "<?xml version=........."
but more complicated.
--
Gediminas Paulauskas
Kaunas, Lithuania |
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]