From: Masanori Ogino <masanori.ogino@gmail.com>
To: musl@lists.openwall.com
Subject: gettext and locale names
Date: Wed, 4 May 2016 22:05:28 +0900 [thread overview]
Message-ID: <CAA-4+jcC7aM8XWo6gRVgfqD-WFC3ODvQYSMLdcJWK9wu9sgNbQ@mail.gmail.com> (raw)
Hello,
When I played with gettext API, I found that musl searches .mo files
with a directory named as current *full* locale names, e.g.
en_US.UTF-8. However, we often use shortened names too. Here is a list
of those names from those of my machine in /usr/share/locale: de,
en_GB, ru_UA.koi8u, sr@latin, etc.
Due to this mismatch, we can't get translations with musl's gettext
API for applications in wild. Thus, I'm considering to implement
locale searching with shortening. Does it make sense?
--
Masanori Ogino
next reply other threads:[~2016-05-04 13:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-04 13:05 Masanori Ogino [this message]
2016-05-04 21:39 ` Rich Felker
2016-05-09 12:46 ` Masanori Ogino
2016-05-11 23:26 ` Rich Felker
2016-05-20 14:55 ` Masanori Ogino
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=CAA-4+jcC7aM8XWo6gRVgfqD-WFC3ODvQYSMLdcJWK9wu9sgNbQ@mail.gmail.com \
--to=masanori.ogino@gmail.com \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).