From: Henning Hraban Ramm <hraban@fiee.net>
Subject: Re: mode dependend character handling
Date: Sun, 15 Jan 2006 00:31:15 +0100 [thread overview]
Message-ID: <7F1D6483-1B31-4D4B-A6B4-97AF0C8804C4@fiee.net> (raw)
In-Reply-To: <6faad9f00601141502s2429540o961af2e4333b836c@mail.gmail.com>
> OK, thanks Taco. Now I understand the problem. I always compiled
> with or without
> texexec --mode=swiss
> which worked fine. If mixing modes within the same document is
> required (\enablemode/\disablemode[swiss]), it fails of course (I
> didn't think about it).
Ah, ok, I didn't test with --mode, even if that will be my normal use
case.
Grüßlis vom Hraban!
---
http://www.fiee.net/texnique/
http://contextgarden.net
http://www.cacert.org (I'm an assurer)
next prev parent reply other threads:[~2006-01-14 23:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-02 13:36 Henning Hraban Ramm
2006-01-06 14:39 ` Taco Hoekwater
2006-01-14 13:50 ` Henning Hraban Ramm
2006-01-14 19:35 ` Mojca Miklavec
2006-01-14 21:10 ` Henning Hraban Ramm
2006-01-14 22:44 ` Taco Hoekwater
2006-01-14 23:02 ` Mojca Miklavec
2006-01-14 23:31 ` Henning Hraban Ramm [this message]
2006-01-15 18:16 ` Hans Hagen
2006-01-06 15:08 ` Mojca Miklavec
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=7F1D6483-1B31-4D4B-A6B4-97AF0C8804C4@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).