From: Eli Zaretskii <eliz@gnu.org>
To: HaiJun Zhang <netjune@outlook.com>
Cc: 38287-done@debbugs.gnu.org, michael.albinus@gmx.de
Subject: bug#38287: 26.3.50; filenotify.el: the Chinese file name in the event is messy code
Date: Thu, 21 Nov 2019 16:42:41 +0200 [thread overview]
Message-ID: <83tv6xxpcu.fsf@gnu.org> (raw)
In-Reply-To: <PS1PR03MB3606C0FEFD4A8D0CE74C07FFB74E0@PS1PR03MB3606.apcprd03.prod.outlook.com> (message from HaiJun Zhang on Thu, 21 Nov 2019 02:33:42 +0000)
> From: HaiJun Zhang <netjune@outlook.com>
> CC: "38287@debbugs.gnu.org" <38287@debbugs.gnu.org>
> Date: Thu, 21 Nov 2019 02:33:42 +0000
>
> It is fixed by your patch. Thanks.
Thanks, I installed it.
> I print the value of file and encoded_file with safe_debug_print in kqueue.c. The former is normal string. The
> latter is messy code. What is the encoding of encoded_file? The value of file-name-coding-system is
> utf-8-hfs. How much does utf-8-hfs diff with utf-8-unix? Is utf-8-hfs not really utf-8?
encoded_file is in UTF-8 on your system. What you perceive as "messy
code" is how Emacs displays unibyte strings, which are actually
sequences of raw bytes, not of characters.
utf-8 and utf-8-hfs are not exactly the same, but for Chinese
characters they produce the same results, because those characters
don't have decompositions.
prev parent reply other threads:[~2019-11-21 14:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <aeef7181-2c14-4b93-90fd-dd71993ed3c8@Spark>
2019-11-20 3:50 ` bug#38287: 26.3.50; filenotify.el: the Chinese file name in the event is messy code HaiJun Zhang
2019-11-20 16:32 ` Michael Albinus
2019-11-20 17:35 ` Eli Zaretskii
2019-11-20 17:49 ` Michael Albinus
2019-11-20 18:25 ` Eli Zaretskii
2019-11-20 18:45 ` Michael Albinus
2019-11-21 0:35 ` HaiJun Zhang
2019-11-21 2:33 ` HaiJun Zhang
2019-11-21 14:42 ` Eli Zaretskii [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83tv6xxpcu.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=38287-done@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
--cc=netjune@outlook.com \
/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.