From: Henning Hraban Ramm <hraban@fiee.net>
Subject: Re: Umlaute etc.
Date: Sun, 23 Feb 2003 20:03:06 +0100 [thread overview]
Message-ID: <70FC69F6-4761-11D7-8395-0030659899AA@fiee.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0302221726270.1632-100000@laptop.rkc>
> Ahh! Works perfectly ... just to be correct: I am using a linux
> machine -
> is there a more appropriate command than [windows]? Or is it ok to
> leave
> it at that?
Patrich already answered "il1", that means "iso-latin1"; AFAIK there's
no difference to "windows". If you like you may try "utf" (for UTF-8)
with the latest beta.
Perhaps my german ConTeXt tutorial is of help for you. See link below.
Grüßlis vom Hraban!
--
http://www.fiee.net/texnique/
next prev parent reply other threads:[~2003-02-23 19:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-22 10:41 Raimund.Kohl
2003-02-22 12:01 ` Eckhart Guthöhrlein
2003-02-22 20:39 ` Raimund.Kohl
2003-02-23 10:45 ` Eckhart Guthöhrlein
2003-02-23 10:46 ` Eckhart Guthöhrlein
2003-02-22 12:07 ` Tobias Burnus
2003-02-22 16:28 ` Raimund.Kohl
2003-02-22 18:05 ` Patrick Gundlach
2003-02-23 19:03 ` Henning Hraban Ramm [this message]
2003-02-23 13:33 ` John Culleton
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=70FC69F6-4761-11D7-8395-0030659899AA@fiee.net \
--to=hraban@fiee.net \
--cc=ntg-context@ntg.nl \
/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).