public inbox for libc-locales@sourceware.org
 help / color / mirror / Atom feed
From: Troy Korjuslommi <tjk@tksoft.com>
To: Steven Abner <pheonix@zoomtown.com>
Cc: libc-locales@sourceware.org
Subject: Re: locale encodings
Date: Mon, 11 Nov 2013 12:58:00 -0000	[thread overview]
Message-ID: <1384174607.4028.8.camel@uno11.loco> (raw)
In-Reply-To: <31AACAB8-A716-47CC-B755-F33DD77BA51E@zoomtown.com>

If you mean the locale data files, they have a line such as 
"% Charset: ISO-8859-1"
which tell you the charset.

It would indeed be a good idea to tell the files' maintainers to use
UTF-8 from now on. For now you can use iconv or uconv to convert them.
E.g. iconv -f iso-8859-1 -t utf-8 < file > newfile

Troy



On Sun, 2013-11-10 at 19:03 -0500, Steven Abner wrote:
> Hi,
>  Can you tell me what file format "cs_CZ", "sk_SK", "sv_SE" and "wo_SN" are encoded in? I was going to try
> to fix it for my use, but can't open in a normal editor. I was doing a design test when these files tripped a non-POSIX portable character set code in my scanf()'s isspace(). I think they might be ISO8859-2 but not sure. Normal editor claims it can't be
> open in UTF-8. I'd rather not second guess someone else's work, if I can. If it is  ISO8859-2, I'll just decode/encode me a
> UTF file to examine. Two other files have UTF8 encodings, which is no problem. Others do but weren't within scope of
> the trap (comment character to first word after). I am only trying to verify the file parser is picking up exact data, and hopefully
> not being corrupted by unusual codes, as some have been.
> Thanks,
> Steve
> pheonix@zoomtown.com
> 


  parent reply	other threads:[~2013-11-11 12:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-11  1:28 Steven Abner
2013-11-11  5:19 ` Carlos O'Donell
2013-11-11 12:58 ` Troy Korjuslommi [this message]
2013-11-12  1:23   ` Keld Simonsen
2013-11-12  5:38     ` Carlos O'Donell
2013-11-12 13:36       ` Keld Simonsen
2013-11-12 14:39         ` Carlos O'Donell
2013-11-12 16:11           ` Keld Simonsen
2013-11-12 14:52         ` Steven Abner
2013-11-12 16:15           ` Steven Abner
2013-11-14  7:47             ` Troy Korjuslommi
2013-11-14 11:33               ` Keld Simonsen
2013-11-14 20:47               ` Steven Abner
2013-11-14 21:17                 ` Steven Abner
2013-11-14 21:17                 ` Keld Simonsen
2013-11-26 17:05 Marko Myllynen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1384174607.4028.8.camel@uno11.loco \
    --to=tjk@tksoft.com \
    --cc=libc-locales@sourceware.org \
    --cc=pheonix@zoomtown.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).