[Grok-dev] i18nextract doesn't handle utf-8
sebastian at urbantalk.se
Thu Jun 25 03:29:36 EDT 2009
Here goes... (with the relevant entry included)
"POT-Creation-Date: Wed Jun 24 13:34:37 2009\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
"Language-Team: Zope 3 Developers <zope3-dev at zope.org>\n"
"Content-Type: text/plain; charset=UTF-8\n"
#. Default: "Band s\303\266ker musiker"
24 jun 2009 kl. 18.31 skrev Maurits van Rees:
> Sebastian Ware, on 2009-06-24:
>> When I use bin/i18nextract to extract my pagetemplate i18n strings it
>> "Band söker musiker"
>> "Band s\303\266ker musiker"
>> the pagetemplate is stored with utf-8 encoding. Am I doing anything
>> obviously wrong, or is this a bug?
> As far as I know it is best to keep your msgids pure ascii.
> Or is your msgid something like label_band_soker_musiker (pure ascii)
> and has the Default value that i18nextract puts in the pot/po files as
> assistence got those escaped values?
> Can you post a snippet of the generated pot file?
> Maurits van Rees | http://maurits.vanrees.org/
> Work | http://zestsoftware.nl/
> "This is your day, don't let them take it away." [Barlow Girl]
> Grok-dev mailing list
> Grok-dev at zope.org
More information about the Grok-dev