public inbox for libc-locales@sourceware.org
 help / color / mirror / Atom feed
From: Keld Simonsen <keld@keldix.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: "Carlos O'Donell" <carlos@redhat.com>,
	"Ond??ej Bílka" <neleai@seznam.cz>,
	"Marko Myllynen" <myllynen@redhat.com>,
	"GNU C Library" <libc-alpha@sourceware.org>,
	libc-locales@sourceware.org
Subject: Re: [PATCH] Use Unicode code points for country_isbn
Date: Fri, 24 Jul 2015 22:39:00 -0000	[thread overview]
Message-ID: <20150724171504.GA31852@www5.open-std.org> (raw)
In-Reply-To: <55B26CE6.2090405@cs.ucla.edu>

On Fri, Jul 24, 2015 at 09:50:46AM -0700, Paul Eggert wrote:
> Keld Simonsen wrote:
> >it should be easier to create locales.
> >One could do that with a GUI that helped create and proofread and test 
> >locales.
> 
> I'm not aware of any such GUI, and even if one existed people would have to 
> be trained to use it.  In contrast, we already have GUIs (e.g., Emacs) that 
> people already know how to use and that work reasonably well with UTF-8 
> localedef sources.
> 
> Although the other goals you mention are laudable ones, surely they could 
> be achieved by an automatic transformation of UTF-8 localedef sources into 
> a less-readable equivalent with angle brackets, an equivalent that could be 
> processed even by hypothetical tools operating in legacy multibyte locales. 
> This shouldn't require a fancy GUI; it should be a relatively simple batch 
> program.  Any engineering effort in this area would likely need this kind 
> of transformation anyway, and any software developers in this specialized 
> area should be able to take on this relatively minor extra task.

We could have a utility to do that, and probably there was one developed 
when Ulrich converted the mnemonic style to UCS codepoints. But maybe
that is lost. Or it could be part of the localedef utility,
given that localedef understands the full syntax of locales, then a conversion
option to and from different charsets and symbolic representations could be
done, with some better chances of being maintained and updated for
new features, and not lost.

I was also thinking of testing, how would a date be output with this date format?
I think there may be someting like that lying around, eg for KDE localization,
which I think is based on some other data and formats than glibc locales,
but it is a much bigger work than just doing some conversion of characters.

Keld

  reply	other threads:[~2015-07-24 22:39 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-05 14:57 Marko Myllynen
2015-06-09  7:12 ` Ondřej Bílka
2015-06-09 10:12   ` Marko Myllynen
2015-07-21  8:55     ` Mike Frysinger
2015-07-21  8:55       ` keld
2015-07-21  8:55         ` Florian Weimer
2015-07-21  9:03           ` keld
2015-07-21  9:16             ` Florian Weimer
2015-07-21  9:37         ` Mike Frysinger
2015-07-21 11:59           ` Keld Simonsen
2015-07-21 12:12             ` Keld Simonsen
2015-07-22 19:34             ` Joseph Myers
2015-07-22 19:34               ` Keld Simonsen
2015-07-22 20:04                 ` Joseph Myers
2015-07-23 23:28                   ` Ondřej Bílka
2015-07-24  0:20                     ` Carlos O'Donell
2015-07-24 10:44                   ` Keld Simonsen
2015-07-24 22:39                     ` Joseph Myers
2015-07-25 13:42                       ` Keld Simonsen
2015-07-27 21:06                         ` Joseph Myers
2015-07-24  0:23   ` Carlos O'Donell
2015-07-24  2:54     ` Paul Eggert
2015-07-24  2:45       ` Carlos O'Donell
2015-07-24 10:24       ` Keld Simonsen
2015-07-24 22:39         ` Paul Eggert
2015-07-24 22:39           ` Keld Simonsen [this message]
2015-07-24 10:26       ` Keld Simonsen
2015-08-10 10:31     ` Marko Myllynen
2015-08-10 11:06       ` Keld Simonsen
2015-08-10 11:15         ` 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=20150724171504.GA31852@www5.open-std.org \
    --to=keld@keldix.com \
    --cc=carlos@redhat.com \
    --cc=eggert@cs.ucla.edu \
    --cc=libc-alpha@sourceware.org \
    --cc=libc-locales@sourceware.org \
    --cc=myllynen@redhat.com \
    --cc=neleai@seznam.cz \
    /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).