|
From: | Paul Eggert |
Subject: | bug#27270: display-raw-bytes-as-hex generates ambiguous output for Emacs strings |
Date: | Sun, 11 Jun 2017 10:26:28 -0700 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 |
Eli Zaretskii wrote:
Then maybe the new hex display should use the \N{U+nnn} format?
If we're going to do that, we might as well use \unnnn, which is shorter. A downside of either syntax, though, is the implication that the raw byte is intended to be Unicode, which it typically is not. That is partly why I was thinking \x{nn} would be better: it'd be clearer to users.
[Prev in Thread] | Current Thread | [Next in Thread] |