From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
Subject: Re: mode dependend character handling
Date: Sun, 15 Jan 2006 00:02:24 +0100 [thread overview]
Message-ID: <6faad9f00601141502s2429540o961af2e4333b836c@mail.gmail.com> (raw)
In-Reply-To: <43C97EBF.5050603@elvenkind.com>
Taco Hoekwater wrote:
> Henning Hraban Ramm wrote:
> >> \startencoding[ec]
> >> \startmode[swiss]
> >> \definecharacter ssharp {ss}
> >> \stopmode
> >> \stopencoding
> >> than the order of commands doesn't matter any more (but then the
> >> automatic conversion will only work for the ec encoding).
>
> mode processing is based on modes that are in effect
> at the execution time of the \startmode macro, not
> the typeset time. This would work:
>
> \enablemode[swiss]
> \startencoding[ec]
> \startmode[swiss]
> \definecharacter ssharp {ss}
> \stopmode
> \stopencoding
>
> but then it would be on always, since it effectively becomes
>
> \startencoding[ec]
> \definecharacter ssharp {ss}
> \stopencoding
>
> whereas without the \enablemode it becomes only:
>
> \startencoding[ec]
> \stopencoding
>
> which does nothing.
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).
Mojca
next prev parent reply other threads:[~2006-01-14 23:02 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 [this message]
2006-01-14 23:31 ` Henning Hraban Ramm
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=6faad9f00601141502s2429540o961af2e4333b836c@mail.gmail.com \
--to=mojca.miklavec.lists@gmail.com \
--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).