unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org, help-texinfo@gnu.org, karl@freefriends.org
Subject: Re: [help-texinfo] Re: coding systems vs. info files
Date: Sun, 12 Feb 2006 06:28:17 +0200	[thread overview]
Message-ID: <uy80hw68u.fsf@gnu.org> (raw)
In-Reply-To: <871wy9ime9.fsf@catnip.gol.com> (message from Miles Bader on Sun,  12 Feb 2006 07:03:10 +0900)

> From: Miles Bader <miles@gnu.org>
> Date: Sun, 12 Feb 2006 07:03:10 +0900
> Cc: help-texinfo@gnu.org, emacs-devel@gnu.org
> 
> karl@freefriends.org (Karl Berry) writes:
> > Right, it should not use LANG for output (this is nothing new), but
> > neither I nor anyone has implemented it yet.  (Bruno informed me it is
> > not so easy to switch languages in gettext, unfortunately, which is what
> > it boils down to.)
> 
> Hmm, I thought there was a function "dgettext" to allow explicitly
> specifying the language for a given lookup.

The problem is that makeinfo also has its messages to the user which
should be displayed in the current locale's language.  So it needs to
change the language back and forth, depending on the output stream.
And that is something gettext doesn't like too much.

  reply	other threads:[~2006-02-12  4:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-09  1:58 coding systems vs. info files Miles Bader
2006-02-09 14:54 ` Jesper Harder
2006-02-09 19:14   ` Juri Linkov
2006-02-11  0:13     ` [help-texinfo] " Karl Berry
2006-02-11  1:11       ` Juri Linkov
2006-02-12  1:40         ` Karl Berry
2006-02-12 10:01           ` Andreas Schwab
2006-02-12 21:44         ` Kevin Ryde
2006-02-13 17:48           ` Juri Linkov
2006-02-13 22:07             ` Kevin Ryde
2006-02-11 22:03       ` Miles Bader
2006-02-12  4:28         ` Eli Zaretskii [this message]
2006-02-09 17:28 ` Juri Linkov

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=uy80hw68u.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=help-texinfo@gnu.org \
    --cc=karl@freefriends.org \
    /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.savannah.gnu.org/cgit/emacs.git

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).