mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Рысь <lynx@sibserver.ru>
To: musl@lists.openwall.com
Subject: libintl: stubs or working functions?
Date: Thu, 5 Mar 2015 16:36:49 +0700	[thread overview]
Message-ID: <20150305163649.05a14b30@sibserver.ru> (raw)

I noticed that musl had got some gettext functions as a lightweight and
more saner interface. However, I now have a couple questions about them
as ordinary user.

A bit of history.
I had successfully built and used custom x86 musl based X11 root which
uses both Xfbdev and Xorg servers on different machines. It is based on
my previous musl on servers experience, just added X11 and major gui
libraries on top of it.

My root attracted a user because of it's small size to fit into budget
netbook with very small disk size (about 4GB I think). The problem is
that user does not speak (and understand) English at all, but he accepts
my preferred program set which I preinstalled into root.

So I faced a problem: I had built this root for myself and everywhere I
did seen "--disable-nls" in configure scripts I used it. Now, I tried
to rebuild untranslated programs, noticed that translation files (.po
-> *.gmo) were created and installed in /local/share/locale/.

However, trying to define LC_ALL and LANG environment variables as in
most of glibc systems does not change anything. The programs still
English translated.

And a couple questions here:

* Did I understand that right that I do not need GNU gettext anymore and
  I can use musl's interface for that?
* Do I still need original GNU gettext to translate *.po's to *.gmo's?
  (I used gettext-tiny)
* If musl can handle that, how I should configure it? Are environment
  variables work?

Whole story and questions may be stupid if I misunderstand the purpose
of those functions, so sorry.


             reply	other threads:[~2015-03-05  9:36 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-05  9:36 Рысь [this message]
2015-03-06 22:24 ` Rich Felker
2015-03-08  9:22   ` Рысь
2015-03-09  0:56     ` Rich Felker
2015-03-15 12:33       ` Рысь
2015-03-15 23:54         ` Rich Felker
2015-03-16  4:18           ` Рысь
2015-03-16 13:04             ` Szabolcs Nagy
2015-03-16 13:35               ` Szabolcs Nagy
2015-03-16 13:41             ` Szabolcs Nagy
2015-03-17  1:40               ` Рысь
2015-03-17  2:01                 ` Rich Felker
2015-03-17  6:59                   ` Рысь
2015-03-17 15:02                     ` Szabolcs Nagy
2015-03-17 15:38                       ` Rich Felker
2015-03-17 18:51                         ` Wermut
2015-03-18 14:10                         ` u-wsnj
2015-03-18 14:26                           ` Jens Gustedt
2015-03-19  8:29                           ` Justin Cormack
2015-03-19  8:55                             ` Jens Gustedt
2015-03-19 12:41                             ` u-wsnj
2015-03-19 17:25                               ` stephen Turner
2015-03-20  1:58                                 ` Weldon Goree
2015-03-20  3:11                                   ` Rich Felker
2015-03-19 17:54                               ` Rich Felker
2015-03-20  9:20                                 ` u-wsnj
2015-03-20 20:27                                   ` Rich Felker
2015-03-18  7:15                       ` Рысь
2015-03-24  3:59                     ` Рысь
2015-03-16  9:27           ` Szabolcs Nagy

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=20150305163649.05a14b30@sibserver.ru \
    --to=lynx@sibserver.ru \
    --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).