i18nextract doesn't handle utf-8

View: New views
4 Messages — Rating Filter:   Alert me  

i18nextract doesn't handle utf-8

by Sebastian Ware :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

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?

Mvh Sebastian
_______________________________________________
Grok-dev mailing list
Grok-dev@...
http://mail.zope.org/mailman/listinfo/grok-dev

Re: i18nextract doesn't handle utf-8

by Maurits van Rees-3 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

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@...
http://mail.zope.org/mailman/listinfo/grok-dev

Re: i18nextract doesn't handle utf-8

by Sebastian Ware :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

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@ADDRESS>\n"
"Language-Team: Zope 3 Developers <zope3-dev@...>\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@...
> http://mail.zope.org/mailman/listinfo/grok-dev

_______________________________________________
Grok-dev mailing list
Grok-dev@...
http://mail.zope.org/mailman/listinfo/grok-dev

Re: i18nextract doesn't handle utf-8

by Maurits van Rees-3 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Sebastian Ware, on 2009-06-25:

> 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@ADDRESS>\n"
> "Language-Team: Zope 3 Developers <zope3-dev@...>\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 ""

Hm, confirmed, I get similar results:

#: src/barebonesblog/app_templates/index.pt:6
#. Default: "C\303\266ngr\303\241t\303\274lati\303\263ns!"
msgid "head_congrats"
msgstr ""

However, when I use i18ndude (which has the same origins as
i18nextract I think) it works fine:

#. Default: "Ädd réspönse"
#: ../browser/response.pt:80
msgid "title_add_response"
msgstr ""

Usually I either just keep everything in English (so ascii) and do
translations, or directly use the target language of the client (Dutch
in my case) in the templates and python files.

--
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@...
http://mail.zope.org/mailman/listinfo/grok-dev