From: Noam Postavsky <npostavs@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 31376@debbugs.gnu.org, schwab@linux-m68k.org, eller.helmut@gmail.com
Subject: bug#31376: 26.0.50; print-charset-text-property not honored
Date: Sun, 13 May 2018 14:29:58 -0400 [thread overview]
Message-ID: <87r2mfjtnd.fsf@gmail.com> (raw)
In-Reply-To: <83r2mflgkh.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 13 May 2018 18:29:34 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> This LGTM, but the description of 'default' IMO is too
> implementation-centric, which doesn't help the user in understanding
> what to expect from that value. How about the variant below?
Yeah, I only understand it from the implementation myself.
> If the value is @code{default}, print only those @code{charset} text
> properties that are ``unusual'' for the respective characters under
> the current language environment. The @code{charset} property of a
> character is considered unusual if its value is different from what
> @code{char-charset} returns for that character.
Okay, when writing up some tests I may have found another minor bug, or
at least something which contradicts the text above. Is there supposed
to be an exception for ascii characters?
(char-charset ?a) ;=> ascii
(prin1-to-string
(propertize (string ?a) 'charset 'chinese-cns11643-15))
;=> "\"a\""
vs
(char-charset ?\xf6) ;=> unicode
(prin1-to-string
(propertize (string ?\xf6) 'charset 'chinese-cns11643-15))
;=> "#(\"ö\" 0 1 (charset chinese-cns11643-15))"
(Nothing special about chinese-cns11643-15, by the way, it's just the
first element in charset-list.)
next prev parent reply other threads:[~2018-05-13 18:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-07 6:48 bug#31376: 26.0.50; print-charset-text-property not honored Helmut Eller
2018-05-07 7:58 ` Andreas Schwab
2018-05-07 8:38 ` Helmut Eller
2018-05-07 12:57 ` Noam Postavsky
2018-05-07 18:08 ` Helmut Eller
2018-05-11 13:31 ` Eli Zaretskii
2018-05-11 17:44 ` Noam Postavsky
2018-05-11 18:45 ` Eli Zaretskii
2018-05-12 20:02 ` Noam Postavsky
2018-05-13 15:29 ` Eli Zaretskii
2018-05-13 18:29 ` Noam Postavsky [this message]
2018-05-13 18:51 ` Eli Zaretskii
2018-05-13 19:42 ` Noam Postavsky
2018-05-14 16:34 ` Eli Zaretskii
2018-05-14 23:15 ` Noam Postavsky
2018-05-15 17:19 ` Eli Zaretskii
2018-05-15 23:37 ` Noam Postavsky
2018-05-23 23:12 ` Noam Postavsky
[not found] ` <<837eoani9b.fsf@gnu.org>
2018-05-11 19:58 ` Drew Adams
2018-05-12 6:10 ` Eli Zaretskii
[not found] <<m2zi1c6jvo.fsf@caladan>
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=87r2mfjtnd.fsf@gmail.com \
--to=npostavs@gmail.com \
--cc=31376@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=eller.helmut@gmail.com \
--cc=schwab@linux-m68k.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.