From: "Carlos O'Donell" <carlos@redhat.com>
To: Keld Simonsen <keld@keldix.com>, Troy Korjuslommi <tjk@tksoft.com>
Cc: Steven Abner <pheonix@zoomtown.com>, libc-locales@sourceware.org
Subject: Re: locale encodings
Date: Tue, 12 Nov 2013 05:38:00 -0000 [thread overview]
Message-ID: <5281BEB1.2010909@redhat.com> (raw)
In-Reply-To: <20131112012257.GA31828@rap.rap.dk>
On 11/11/2013 08:22 PM, Keld Simonsen wrote:
> Well, the encoding of the source coode of all locales should be 7-bit ascii, for
> maximum portability. Then the target encoding should be recorded via the
> % charset specification, which gives a list of possible charsets, comma separated.
> UTF-8 should always be included there, but other encodings should also be available.
So one of the points that we've been trying to gather consensus on is:
Is it really important to have 7-bit ASCII? Why not use UTF-8 for the
the locale source? It's readily readable by all editors and allows
language specific comments in teh source files for maximum maintenance.
Cheers,
Carlos.
next prev parent reply other threads:[~2013-11-12 5:38 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 [this message]
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=5281BEB1.2010909@redhat.com \
--to=carlos@redhat.com \
--cc=keld@keldix.com \
--cc=libc-locales@sourceware.org \
--cc=pheonix@zoomtown.com \
--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).