Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Fredrik Staxeng <fstx+u@update.uu.se>
Subject: Re: coding-system difficulties
Date: 14 Nov 2002 13:23:33 +0100	[thread overview]
Message-ID: <1misz0tk56.fsf@Tempo.Update.UU.SE> (raw)
In-Reply-To: <m3bs4sg069.fsf@swagbelly.net>

Cyprian Laskowski <swagbelly@yahoo.com> writes:

>Reiner Steib <4uce.02.r.steib@gmx.net> writes:
>
>> If Cyprian uses Emacs with X, the solution is to install proper
>> Latin-9 fonts. Or you may want to use ucs-tables, see
>> <URL:http://my.gnus.org/Members/rsteib/howto_unify/>.
>
>But since Emacs clearly is able to render this stuff, why would I need
>extra fonts?  

Because it's the right thing. :-) 

>Maybe this is precisely the kind of thing that I don't understand ...
>Can someone suggest a good reference (thorough, but not too
>intimidating) for someone who has had the mixed blessing of usually
>dealing exclusively with ascii/English, but who now wants to become
>comfortable with dealing with these kinds of issues, instead of
>running into a corner every time or pestering Emacs gurus?

I have found some useful information on czyborra.com. For the most
part he seems to describe existing practice in a fairly objective
way. 

When you you want to compare specific characters sets, you can use 
the files on http://www.unicode.org/Public/MAPPINGS. If download 
the files and run diff on them you will see which characters that
differ.

Some countries seem to have one dominant way of coding their language
in computers. Some countries have a few mostly compatible encodings.
Some countries have incompatible encodings, so software tend to
acquire auto-detection capabilities.

Language is highly politicized issue in some countries.  Some people
want to push Unicode/UTF-8 as the solution.  Microsoft have used
embrace and extend even in this arena, and are of course met with some
resistance from the other systems. Some people resent that English
has (almost) fulfilled the esperanto dream of becoming the world's
standard second language. This issue also holds some mystical
attraction for people who like to take small problems and do big
overcomplex solutions. (I'm thinking of certain Dane, not anybody
present here).

So there is plenty to fight about. The politics are complex, but when
looking closer I have always found the technical issues to quite simple.
This is not surprising after all. When you take a computer system
and make it able to represent your language, you take the easiest 
way. You also preserve compatibility with English, so using
English on a Thai computer is not a problem. Using Greek on Thai
computer probably is. 

(Except for bidirectional scripts. I don't see any reasonable way to
handle that. But some UTF-8 supporters seem to have come to the
conclusion that the only feasible technical solution is to change the
script, so I am not alone)

-- 
Fredrik Stax\"ang | rot13: sfgk@hcqngr.hh.fr


  parent reply	other threads:[~2002-11-14 12:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-13 15:21 Cyprian Laskowski
     [not found] ` <84y97x5utn.fsf@lucy.cs.uni-dortmund.de>
2002-11-14  5:33   ` Cyprian Laskowski
2002-11-14 14:18     ` Kai Großjohann
     [not found]       ` <m31y5oc8yo.fsf@swagbelly.net>
     [not found]         ` <843cq3hn3g.fsf@lucy.cs.uni-dortmund.de>
2002-11-15  5:49           ` Fredrik Staxeng
     [not found] ` <1mr8dps4ix.fsf@Tempo.Update.UU.SE>
     [not found]   ` <v9wunhckt2.fsf@marauder.physik.uni-ulm.de>
     [not found]     ` <m3bs4sg069.fsf@swagbelly.net>
2002-11-14 12:23       ` Fredrik Staxeng [this message]
2002-11-14 13:01       ` Hugh Baker

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=1misz0tk56.fsf@Tempo.Update.UU.SE \
    --to=fstx+u@update.uu.se \
    /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).