unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Juri Linkov <juri@jurta.org>
Cc: "Frédéric Perrin" <frederic.perrin@resel.fr>,
	emacs-devel@gnu.org, Schwab <schwab@suse.de>
Subject: Re: Woman path : adding l10n man pages
Date: Sun, 17 Feb 2008 18:15:42 -0500	[thread overview]
Message-ID: <ne8x1ji38h.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <87k5l4pg9j.fsf@jurta.org> (Juri Linkov's message of "Sun, 17 Feb 2008 02:43:08 +0200")

Juri Linkov wrote:

> (e.g. woman-manpath-add-locales can have the same code that
> currently sets woman-locale in mule-cmds.el).

The technical obstacle is that `locale', the fall-back value, isn't
available outside set-locale-environment (AFAICS).

> Also I don't understand why woman-locale is defcustom?  A defcustom
> option is supposed to be customized by the user, but the customized
> value of woman-locale always gets overridden at startup 

I had assumed that `set-locale-environment' runs before processing of
customization options, and by experiment this is the case.

LC_MESSAGES=en_US emacs --no-site-file
  -> woman-locale = en_US.ISO8859-1

Customize woman-locale to nil, save and exit

LC_MESSAGES=en_US emacs --no-site-file
  -> woman-locale = nil

> and on every call to `set-locale-environment'.

Arguably that is what should happen.

> Perhaps the code that uses the locale in woman.el should prefer the
> customized value if woman-locale is non-nil?

I see what you're saying and perhaps you're right. There could be a
general locale variable which woman should use, unless woman-locale is
non-nil, in which case it should be preferred.

But AFAICS there is no such general locale variable at present (no
Lisp variable, including system-messages-locale, seems to be set based
on LC_MESSAGES), so I'd have to add one, which would only be used
by... woman.




  reply	other threads:[~2008-02-17 23:15 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-31 13:47 Woman path : adding l10n man pages Frédéric Perrin
2008-01-08 14:14 ` Frédéric Perrin
2008-01-08 15:38   ` Andreas Schwab
2008-01-09 15:35     ` Frédéric Perrin
2008-01-12 18:01     ` Frédéric Perrin
2008-02-04 19:58     ` Glenn Morris
2008-02-16 20:01       ` Frédéric Perrin
2008-02-16 22:13         ` Glenn Morris
2008-02-16 23:32           ` Juri Linkov
2008-02-17  0:18             ` Glenn Morris
2008-02-17  0:43               ` Juri Linkov
2008-02-17 23:15                 ` Glenn Morris [this message]
2008-02-17 23:35                   ` Juri Linkov
2008-02-18  0:02                     ` Glenn Morris
2008-02-18  0:41                       ` Juri Linkov
2008-02-18  1:14                         ` Miles Bader
2008-02-18 23:35                           ` Juri Linkov
2008-02-19  0:18                             ` Miles Bader

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=ne8x1ji38h.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=frederic.perrin@resel.fr \
    --cc=juri@jurta.org \
    --cc=schwab@suse.de \
    /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).