unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Benjamin Riefenstahl <Benjamin.Riefenstahl@epost.de>
Subject: Re: Can't make emacs use utf-8?? (on WinXP)
Date: Wed, 04 Jun 2003 14:52:43 +0200	[thread overview]
Message-ID: <m37k82m2ck.fsf@seneca.benny.turtle-trading.net> (raw)
In-Reply-To: bbje8m$9lsj5$1@ID-142197.news.dfncis.de

Hi Bjoern,


Bjoern <p2@blinker.net> writes:
> But wasn't Java the first programming language to promote Unicode?
> I haven't tried it yet, as untill yesterday I really stuck to ASCII.

The first thing for Unicode to rule the world (;-)) is that
programmers need to start writing programs that can do Unicode,
e.g. in Java.  Only when it is a common thing can you actually use it
*during* programming.  We are not there yet, there are still quite a
number of other encodings around, and the Java compiler has to cope
with them as any other tool.

So while Java accepts non-ASCII in a number of places (including
identifiers, I believe) for portability reasons you shouldn't just
write them without precautions IMO.  You can either use UCNs (those
\uXXXX codes), or you can use the native2ascii tool that comes with
the JDK to translate to UCNs, or you can just avoid using non-ASCII
characters in code altogether.  The last one is the easiest.

There are even those, like me, that believe that the language of
identifiers and comments should be simple English anyway, to maximize
reusability.


so long, benny

  reply	other threads:[~2003-06-04 12:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-02 23:55 Can't make emacs use utf-8?? (on WinXP) Bjoern
2003-06-03  7:19 ` Jason Rumney
2003-06-04 15:35   ` Stefan Monnier
2003-06-03 10:16 ` Benjamin Riefenstahl
2003-06-04  0:26   ` Bjoern
2003-06-04 12:52     ` Benjamin Riefenstahl [this message]
2003-06-04 13:16       ` Bjoern
2003-06-04 14:19         ` Robin Hu
2003-06-04 14:59         ` Benjamin Riefenstahl
2003-06-04 20:21         ` Jason Rumney
2003-06-10 17:53         ` Piet van Oostrum
2003-06-03 18:27 ` Eli Zaretskii
2003-06-05 14:14 ` Stefan Monnier
2003-06-06  8:58   ` Bjoern

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=m37k82m2ck.fsf@seneca.benny.turtle-trading.net \
    --to=benjamin.riefenstahl@epost.de \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).