unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: 33053@debbugs.gnu.org
Subject: bug#33053: scm_i_mirror_backslashes assumes ASCII-compatible locale encoding
Date: Fri, 19 Oct 2018 21:21:49 -0400	[thread overview]
Message-ID: <87va5x4dle.fsf@netris.org> (raw)
In-Reply-To: <87d0saq06q.fsf@netris.org> (Mark H. Weaver's message of "Mon, 15 Oct 2018 19:06:53 -0400")

tags 33053 + notabug
close 33053
thanks

Mark H Weaver <mhw@netris.org> writes:

> Mark H Weaver <mhw@netris.org> writes:
>
>> The 'scm_i_mirror_backslashes' in load.c operates on C strings in the
>> locale encoding, and assumes that the locale encoding is ASCII
>> compatible.  In the Shift_JIS encoding, used in the "JP_jp.sjis" locale,
>> backslash '\' is mapped to a multibyte character, and the Yen sign '¥'
>> is represented using code 0x5C, the same code as backslash '\' in ASCII.
>>
>> As a result, users of the "JP_jp.sjis" locale will have Yen signs '¥' in
>> their file names converted into slashes by this function.
>
> I miswrote the locale name above.  The locale name is "ja_JP.sjis".

It seems that I was mistaken in my assumption that '\' is mapped to a
multibyte character in Shift_JIS.  According to John Cowan, "the
character at #\x5C is *functionally* a backslash that is *displayed* as
a yen sign".

It seems that this is not actually a bug in 'scm_i_mirror_backslashes',
so I'm closing this bug.

      Mark





      reply	other threads:[~2018-10-20  1:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-15 20:45 bug#33053: scm_i_mirror_backslashes assumes ASCII-compatible locale encoding Mark H Weaver
2018-10-15 23:06 ` Mark H Weaver
2018-10-20  1:21   ` Mark H Weaver [this message]

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/guile/

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

  git send-email \
    --in-reply-to=87va5x4dle.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=33053@debbugs.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.
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).