Re: [poedit-users] Character encoding issue

Scott Hildebrand <klezmer41-/[email protected]> Tue, 3 Feb 2009 11:47:38 -0800 (PST)
Newsgroups gmane.editors.poedit.user
Message-ID <[email protected]>
There is obviously something going on here, and I don't care who's at fault so no need to be defensive. Maybe we can try to figure some of this out as a group. Here's the text of what's in my PO file, so I would appreciate if some of you could try it and see what you get. In my MO file
the funny e character shows up as é.

msgid ""
msgstr ""
"Project-Id-Version: \n"
"POT-Creation-Date: \n"
"PO-Revision-Date: \n"
"Last-Translator: \n"
"Language-Team: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Poedit-SourceCharset: utf-8\n"
"X-Poedit-Language: French\n"
"X-Poedit-Country: FRANCE\n"

msgid "first_name"
msgstr "prénom"

msgid "last_name"
msgstr "nom de famille"



--- On Mon, 2/2/09, Vaclav Slavik <[email protected]> wrote:

> From: Vaclav Slavik <[email protected]>
> Subject: Re: [poedit-users] Character encoding issue
> To: [email protected]
> Date: Monday, February 2, 2009, 12:57 AM
> On Mon, 2009-02-02 at 08:29 +0100, Johannes Mario Ringheim
> wrote:
> > Note that the solution was to open and save it in
> poedit on another 
> > operating system (Ubuntu), as opposed to the one I was
> using (Mandriva). 
> 
> Doubtful. You did something (as usual, unspecified) that
> did something
> (unspecified) to the files. By coincidence, you did that on
> another
> Linux distribution (which is not "different operating
> system" by any
> stretch of imagination, BTW) and you interpret this
> correlation as
> causation. 
> 
> > To me it seems to be an issue with how poedit
> interacts with encoding on 
> > different operating system, but as I don't have
> the insight I can only 
> > speculate..
> 
> The issue is precisely that -- lack of insight into
> encodings, Unicode
> and text handling in computers. Now that's perfectly
> fine, this is not
> required knowledge for a *translator*. Poedit lets you just
> save the
> file and be done with it if you don't understand
> encodings.
> 
> If, on the other hand, you are a programmer who uses or
> further
> processes .po files obtained from translators (be they
> written in Poedit
> or not), then having a firm grasp of these issues is a
> basic competency
> requirement.
> 
> FWIW, none of the posts on this topic ever showed any
> evidence of actual
> problem with the .po files Poedit creates (such as a
> Poedit-caused
> mismatch between the encoding claimed in file's headers
> and the one
> really used -- now that would be a serious bug).
> 
> Regards,
> Vaclav
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> SourcForge Community
> SourceForge wants to tell your story.
> http://p.sf.net/sfu/sf-spreadtheword_______________________________________________
> Poedit-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/poedit-users


      

------------------------------------------------------------------------------
Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
software. With Adobe AIR, Ajax developers can use existing skills and code to
build responsive, highly engaging applications that combine the power of local
resources and data with the reach of the web. Download the Adobe AIR SDK and
Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com