From: Steven Abner <pheonix@zoomtown.com>
To: Troy Korjuslommi <tjk@tksoft.com>
Cc: Keld Simonsen <keld@keldix.com>,
libc-locales@sourceware.org, Steven Abner <pheonix@zoomtown.com>
Subject: Re: locale encodings
Date: Thu, 14 Nov 2013 21:17:00 -0000 [thread overview]
Message-ID: <D99BE38E-0152-45BC-A01A-9A93E8F3536D@zoomtown.com> (raw)
In-Reply-To: <D542FE62-7793-4B11-9146-A893ABD5025C@zoomtown.com>
If I understand now how your file data works, all locales are loaded as UTF-8.
Your modifiers were an attempt to limit the UTF-8 to a particular Charset?
Locales load, but the encoder/decoder weeds out input/output of the UTF-8 set.
This would imply that should the end user( guy at keyboard) select a set that can't
display his currency symbol, thats correct behavior!
I would assume, not looked into, that a modifier changes a "Keyword" and has nothing
to do with Charset.
So now only re-encoding old files, if want to view, is left from original question, IF my
understanding of your files you supply is correct?
Steve
next prev parent reply other threads:[~2013-11-14 21:17 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
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 [this message]
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=D99BE38E-0152-45BC-A01A-9A93E8F3536D@zoomtown.com \
--to=pheonix@zoomtown.com \
--cc=keld@keldix.com \
--cc=libc-locales@sourceware.org \
--cc=tjk@tksoft.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).