[yast-devel] y2makepot
Hi guys, I just had to bin Christian Jager's umlaut because y2makepot doesn't pass --from-code=UTF-8 to xgettext - he appears in a translated string you see, and without this xgettext demands ascii. Any chance of a fix for the next version ? Thanks, Michael. -- michael.meeks@novell.com <><, Pseudo Engineer, itinerant idiot -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
On Freitag, 21. November 2008, Michael Meeks wrote:
I just had to bin Christian Jager's umlaut because y2makepot doesn't pass --from-code=UTF-8 to xgettext - he appears in a translated string you see, and without this xgettext demands ascii.
Any chance of a fix for the next version ?
I don't quite understand this. xgettext searches the sources for strings in
the "translatable string" marker, in our case _( "foo" ). Do we have a "foo"
with non-ASCII characters?
CU
--
Stefan Hundhammer
Hi,
I don't quite understand this. xgettext searches the sources for strings in the "translatable string" marker, in our case _( "foo" ). Do we have a "foo" with non-ASCII characters?
Obviously we do: static const char *pkg_help = -"<h1>Purpose</h1>" +__("<h1>Purpose</h1>" .... -"Thanks to Christian Jäger for co-designing this tool.</i></blockquote>"; +"Thanks to Christian Jager for co-designing this tool.</i></blockquote>"); B. -- \\\\\ Katarina Machalkova \\\\\\\__o YaST developer __\\\\\\\'/_ & hedgehog painter -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
participants (3)
-
Katarina Machalkova -
Michael Meeks -
Stefan Hundhammer