[Grok-dev] i18nextract doesn't handle utf-8

[Sebastian Ware]

Here goes... (with the relevant entry included)

msgid ""
msgstr ""
"Project-Id-Version: Development/Unknown\n"
"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"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: zope/app/locales/extract.py\n"

#: src/boomtown/classified_templates/classifiedlisting.pt:23
#. Default: "Band s\303\266ker musiker"
msgid "band_searching_musician-text"
msgstr ""

Mvh Sebastian




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
>> turns:
>>
>>   "Band söker musiker"
>>
>> into:
>>
>>   "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
> http://mail.zope.org/mailman/listinfo/grok-dev