unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Thomas Morgan <tlm@pocketmail.com>
Cc: handa@etl.go.jp, bug-gnu-emacs@gnu.org
Subject: Re: decode-char & utf-8-fragment-on-decoding
Date: 05 Sep 2002 13:39:34 -0400	[thread overview]
Message-ID: <87ptvspc89.fsf@cricket.magic.csuhayward.edu> (raw)

I wrote:

   I understand now that utf-8-fragment-on-decoding has no direct effect
   on decoding, but it is still not clear to me what indirect effect it is
   supposed to have when it is set through Custom.  Right now it applies
   to CCL programs, but not to decode-char.  Is that correct?

   If so, perhaps that should be documented.

When I think about it more carefully, I see that decode-char's
doc string is unambiguous when it says "the result is translated
through the char table `utf-8-translation-table-for-decode'".

For the sake of careless readers like me, could something like this
be added after that sentence?

  (Note that this char table is independent of the translation table
  of the same name which CCL programs use, and it is not affected by
  the user's setting of utf-8-fragment-on-decoding.)

             reply	other threads:[~2002-09-05 17:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-05 17:39 Thomas Morgan [this message]
2002-09-05 22:50 ` decode-char & utf-8-fragment-on-decoding Dave Love
  -- strict thread matches above, loose matches on Subject: below --
2002-09-04  5:56 Thomas Morgan
2002-09-04  8:18 ` Kenichi Handa
2002-09-04 23:34   ` Dave Love
2002-09-05  1:25     ` Kenichi Handa
2002-09-05 22:45       ` Dave Love
2002-09-05  5:23     ` Thomas Morgan
2002-09-05 22:47       ` Dave Love
2002-09-06  1:13         ` Thomas Morgan
2002-09-07 23:14           ` Dave Love
2002-09-08  1:07             ` Thomas Morgan
2002-09-09 22:35               ` Dave Love

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

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

  git send-email \
    --in-reply-to=87ptvspc89.fsf@cricket.magic.csuhayward.edu \
    --to=tlm@pocketmail.com \
    --cc=bug-gnu-emacs@gnu.org \
    --cc=handa@etl.go.jp \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).