From: "Juanma Barranquero" <lekktu@gmail.com>
To: "Eli Zaretskii" <eliz@gnu.org>
Cc: rudalics@gmx.at, jasonr@f2s.com, emacs-devel@gnu.org
Subject: Re: filename coding systems and w32-*-file-name functions
Date: Sun, 30 Nov 2008 03:08:54 +0100 [thread overview]
Message-ID: <f7ccd24b0811291808o1de81c52n3d7a6ab38b249909@mail.gmail.com> (raw)
In-Reply-To: <uabbkgscr.fsf@gnu.org>
On Fri, Nov 28, 2008 at 09:36, Eli Zaretskii <eliz@gnu.org> wrote:
> I don't see anything wrong with this return value. So I think you can
> use it without any trouble.
I've committed that fix.
And, in a related note: some time ago, I changed `w32-list-locales'
(from w32-fns.el) to decode the output of `w32-get-locale-info'. But,
in fact, I don't think that should be done at the lisp level; there's
no reason why `w32-get-locale-info' shouldn't use DECODE_SYSTEM for
the long form of the locale name.
As for using DECODE_SYSTEM when the LONGFORM argument is a LCTYPE
constant, I'm not sure. On one hand, I don't think that
ELISP> (w32-get-locale-info (w32-get-current-locale-id) 2)
"Espa\361ol - Espa\361a (alfabetizaci\363n tradicional)^@"
is very useful. On the other hand, the LCTYPE results are
null-terminated strings so I don't know what it the intended use.
Comments?
TIA,
Juanma
next prev parent reply other threads:[~2008-11-30 2:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-25 1:38 filename coding systems and w32-*-file-name functions Juanma Barranquero
2008-11-27 13:41 ` martin rudalics
2008-11-27 14:24 ` Jason Rumney
2008-11-27 14:46 ` Juanma Barranquero
2008-11-27 14:59 ` Jason Rumney
2008-11-27 15:03 ` Juanma Barranquero
2008-11-27 19:53 ` Eli Zaretskii
2008-11-27 20:24 ` Juanma Barranquero
2008-11-27 20:40 ` Eli Zaretskii
2008-11-27 22:16 ` Juanma Barranquero
2008-11-28 8:36 ` Eli Zaretskii
2008-11-30 2:08 ` Juanma Barranquero [this message]
2008-12-10 10:57 ` Juanma Barranquero
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=f7ccd24b0811291808o1de81c52n3d7a6ab38b249909@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jasonr@f2s.com \
--cc=rudalics@gmx.at \
/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).