From: Shigeru Fukaya <shigeru.fukaya@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 13553@debbugs.gnu.org
Subject: bug#13553: 24.3.50; incorrect usage of IS_DIRECTORY_SEP
Date: Sun, 27 Jan 2013 17:36:48 +0900 [thread overview]
Message-ID: <B0CDFC69723E75shigeru.fukaya@gmail.com> (raw)
In-Reply-To: <8338xnje9r.fsf@gnu.org>
One more, please.
CharNextExA/CharPrevExA work based on dynamically specified codepage.
And, _mbspbrk/_mbslwr are also used in w32.c. They work based on MS
Window's locale setting.
Isn't it inconsistent? _mbsinc/_mbsdec would simply be sufficient?
(Besides, I don't know well, _mbslwr seems to me lower latin
characters' case on some locale. Is it true, or intended behavior?)
Thank you,
Shigeru
>> From: Stefan Monnier <monnier@iro.umontreal.ca>
>> Cc: shigeru.fukaya@gmail.com, 13553@debbugs.gnu.org
>> Date: Sat, 26 Jan 2013 17:24:37 -0500
>>
>> CharNextExA and CharPrevExA, in my mind, do perform the moral equivalent
>> of decoding the argument (just in an incremental way).
>
>No, they are the equivalents of NEXT_CHAR_BOUNDARY and
>PREV_CHAR_BOUNDARY, except that they can do this for many different
>encodings, not just for UTF-8.
next prev parent reply other threads:[~2013-01-27 8:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-26 5:52 bug#13553: 24.3.50; incorrect usage of IS_DIRECTORY_SEP Shigeru Fukaya
2013-01-26 10:26 ` Stefan Monnier
2013-01-26 11:16 ` Eli Zaretskii
2013-01-26 12:40 ` Stefan Monnier
2013-01-26 13:23 ` Eli Zaretskii
2013-01-26 22:24 ` Stefan Monnier
2013-01-27 7:06 ` Eli Zaretskii
2013-01-27 8:36 ` Shigeru Fukaya [this message]
2013-01-27 9:40 ` Eli Zaretskii
2013-01-26 12:56 ` Eli Zaretskii
2013-01-26 14:06 ` Eli Zaretskii
2013-01-26 16:33 ` Shigeru Fukaya
2013-01-26 17:37 ` Eli Zaretskii
2013-01-27 6:56 ` Shigeru Fukaya
2013-01-27 7:15 ` Eli Zaretskii
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=B0CDFC69723E75shigeru.fukaya@gmail.com \
--to=shigeru.fukaya@gmail.com \
--cc=13553@debbugs.gnu.org \
--cc=eliz@gnu.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.