From: James Cloos <cloos@jhcloos.com>
To: ding@gnus.org
Cc: Tassilo Horn <tassilo@member.fsf.org>
Subject: Re: imap-parse-fetch: End of file during parsing
Date: Wed, 26 Mar 2008 15:27:22 -0400 [thread overview]
Message-ID: <m3prthnv4e.fsf@lugabout.jhcloos.org> (raw)
In-Reply-To: <87bq51wec3.fsf@member.fsf.org> (Tassilo Horn's message of "Wed, 26 Mar 2008 19:05:32 +0100")
Just a quick aside:
| code point: 0x1B3D6E
The default charset now that the unicode-2 branch has been merged is
utf-8-emacs which is utf-8 extended to cover at least all of the +ve
integers elisp can handle on a 32-bit platform (which is 28 or 29 bits,
as I recall) if not the full 31 bits of an int32_t. The character codes
beyond U+10FFFF are used for things like differentiating C vs J vs K
forms of Han ideoglyphs and similar per-language or per-script differences.
I presume 0x1B3D6E is a language/script specific form of U+3D6E which is:
,----[ excerpt from Unihan.txt ]
| U+3D6E kCangjie EKTQ
| U+3D6E kCantonese seon4
| U+3D6E kDefinition clear (fresh) water
| U+3D6E kHanYu 31754.090
| U+3D6E kIRGHanyuDaZidian 31754.090
| U+3D6E kIRGKangXi 0655.201
| U+3D6E kIRG_GSource HZ
| U+3D6E kIRG_JSource A-2457
| U+3D6E kIRG_TSource 5-552E
| U+3D6E kMandarin CHUN2 WEN3
| U+3D6E kRSUnicode 85.13
| U+3D6E kTotalStrokes 16
`----
The 1B might be based on ISO 2022 codes?
international/mule-conf.el is probably the place to look for the
details....
-JimC
--
James Cloos <cloos@jhcloos.com> OpenPGP: 1024D/ED7DAEA6
next prev parent reply other threads:[~2008-03-26 19:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-26 9:17 Tassilo Horn
[not found] ` <m3wsnpo2it.fsf@lugabout.jhcloos.org>
2008-03-26 18:05 ` Tassilo Horn
2008-03-26 19:27 ` James Cloos [this message]
2008-03-27 9:04 ` Tassilo Horn
2008-03-27 9:37 ` Katsumi Yamaoka
2008-03-27 22:16 ` Tassilo Horn
2008-03-27 23:47 ` Katsumi Yamaoka
2008-03-26 22:35 ` Tassilo Horn
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=m3prthnv4e.fsf@lugabout.jhcloos.org \
--to=cloos@jhcloos.com \
--cc=ding@gnus.org \
--cc=tassilo@member.fsf.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 NNTP newsgroup(s).