Re: [poedit-users] Character encoding issue
Vaclav Slavik <[email protected]> Mon, 02 Feb 2009 09:57:54 +0100
| Newsgroups | gmane.editors.poedit.user |
|---|---|
| Message-ID | <1233565074.23548.52.camel@localhost> |
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
signature.asc
(application/pgp-signature, 197 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEABECAAYFAkmGtZIACgkQxDYa/UZSZMmPagCggzSm+SrB0Fz6X3V7SbXYPlj9 G0oAn1zrwDtZ5vwR/LbisL7E5oml66HG =hAma -----END PGP SIGNATURE-----