Gnus development mailing list
 help / color / mirror / Atom feed
From: "François Pinard" <pinard@iro.umontreal.ca>
Cc: xemacs-mule@xemacs.org
Subject: Re: More charset things
Date: 07 Feb 1999 15:43:18 -0500	[thread overview]
Message-ID: <oq90eaymft.fsf@titan.progiciels-bpi.ca> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "04 Feb 1999 18:49:14 +0100"

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> > > That's not my table.  :-) When MULE supports utf-8, Gnus will
> > > support utf-8.

> > That is not a nice way of thinking.

> I don't see any other way of thinking.  Grokking utf-8 is way outside
> the scope of Gnus -- it has to be an Emacs thing.

In a way, UTF-8 or Base64 are coding schemes.  I see no strong reason for
Gnus to be favourable to one without being to the other, except maybe that
Base64 is usable in CTE, while UTF-8 is probably not going to be.

UTF-8 is really simple, by comparison with other things in the field of
charsets, and much more simple that what Gnus already does about the whole
thing.  Lars, I can send you documentation and C code, if you feel like it.

> Could that someone (or someone else) re-recommend the book(s) that I
> should buy to get both an introduction and more in-depth knowledge about
> charset issues?

*The* reference, which I never seen (my librarian says the editor is out
of stock), is supposed to be the Ken Lunde book, in the ORA series.

  From: Brendan_Murray/DUB/Lotus@lotus.com
  Subject: Re: unicode <-> hex converter (fwd)
  To: pinard@IRO.UMontreal.CA
  Date: 1997-04-11 09:38:40 +01:00

  For information on Asian character sets, try picking up a copy of Ken
  Lunde's text for his next book. It should be on
  ftp://ftp.ora.com/pub/examples/nutshell/ujip/doc/cjk.inf. His first book,
  "Understanding Japanese Information Processing" is so good that it has been
  translated to Japanese, and is used over there by many developers (one of
  the guys in our Tokyo office thought Ken Lunde was Japanese - that's how
  good it is!) - if you're doing anything with the Japanese encoding systems,
  I heartily recommend this.

  By the way, you'll find code snippets sprinkled around that part of the FTP
  site, with different encoding transformations.

  Brendan

-- 
François Pinard                            mailto:pinard@iro.umontreal.ca
Join the free Translation Project!    http://www.iro.umontreal.ca/~pinard



  parent reply	other threads:[~1999-02-07 20:43 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-02-03 18:09 Lars Magne Ingebrigtsen
1999-02-04 14:56 ` Hrvoje Niksic
1999-02-04 17:08   ` Lars Magne Ingebrigtsen
1999-02-04 17:21     ` Hrvoje Niksic
1999-02-04 17:49       ` Lars Magne Ingebrigtsen
1999-02-05  0:47         ` Stephen J. Turnbull
1999-02-05  2:43           ` Hrvoje Niksic
     [not found]           ` <m3hft163aa.fsf@peorth.gweep.net>
1999-02-05 19:06             ` Vladimir Volovich
     [not found]               ` <m3sockqqjx.fsf@peorth.gweep.net>
1999-02-06 15:55                 ` Lars Magne Ingebrigtsen
     [not found]                   ` <m3lnia5922.fsf@peorth.gweep.net>
1999-02-07 21:02                     ` Hrvoje Niksic
1999-02-09 15:56                       ` Lars Magne Ingebrigtsen
1999-02-09 17:21                         ` Hrvoje Niksic
1999-02-09 17:31                           ` Alan Shutko
1999-02-09 17:37                           ` Lars Magne Ingebrigtsen
1999-02-09 18:06                             ` Hrvoje Niksic
1999-02-08 16:04                   ` Bill White
1999-02-09 16:04                     ` Lars Magne Ingebrigtsen
1999-02-06  8:17           ` Lars Magne Ingebrigtsen
1999-02-09 10:27           ` Displayed [ 0: Stephen J. Turnbull ] but it had lots of lines Alf-Ivar Holm
1999-02-09 16:14             ` Lars Magne Ingebrigtsen
1999-02-09 22:07           ` More charset things Jan Vroonhof
     [not found]           ` <m3hft163aa.fsf@p <byu2wv6xkb.fsf@bolzano.math.ethz.ch>
1999-02-09 22:13             ` Hrvoje Niksic
1999-02-07 20:43         ` François Pinard [this message]
1999-02-08  2:09           ` Martin Buchholz
1999-02-22 15:52             ` François Pinard
1999-02-08 14:49           ` Robert Bihlmeyer
     [not found]           ` <m37lttydo2.fsf@peorth.gweep.net>
1999-02-08  9:55             ` Kai.Grossjohann
1999-02-08 15:52             ` François Pinard
     [not found]               ` <m3n22ou09w.fsf@peorth.gweep.net>
1999-02-08 23:19                 ` François Pinard
1999-02-09  8:05               ` Steinar Bang
1999-02-14 18:10                 ` UTF-8 (Was: More charset things) Steinar Bang
1999-02-09 16:03               ` More charset things Lars Magne Ingebrigtsen
1999-02-08 17:29             ` Karl Eichwalder
1999-02-08 22:03             ` James H. Cloos Jr.
1999-02-09  5:29               ` Russ Allbery
1999-02-09  7:33                 ` James H. Cloos Jr.
1999-02-10  2:13                   ` Stephen Zander
1999-02-11 10:09           ` Jan Vroonhof
1999-02-07 19:37       ` François Pinard
1999-02-08  0:06         ` Kenichi Handa
1999-02-07 19:35     ` François Pinard
1999-02-08 13:37       ` Simon Josefsson
1999-02-08 23:43         ` Kenichi Handa

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=oq90eaymft.fsf@titan.progiciels-bpi.ca \
    --to=pinard@iro.umontreal.ca \
    --cc=xemacs-mule@xemacs.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).