From: "Peter Münster" <pmlists@free.fr>
Subject: Re: Strange bug with ffr and \in[]
Date: Mon, 7 Jun 2004 17:51:56 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.58.0406071747390.29578@gaston.free.fr> (raw)
In-Reply-To: <Pine.LNX.4.58.0405211405590.31441@gaston.free.fr>
On Fri, 21 May 2004, Peter Münster wrote:
> On Fri, 21 May 2004, Hans Hagen wrote:
>
> > The reason is that the environment that handles the : is loaded after the
> > first access to the utility file;
> >
> > you can try to add this to your local cont-sys.tex file
> >
> > \enablemode[activecolon] \usemodule[tryout]
>
> Yes, it works. Thank you!
Oh, no, I was too fast. There is no more problem with \in[], but there is
no more space before a colon:
file env.tex:
\startenvironment env
\useencoding[ffr]
\mainlanguage[fr]
\stopenvironment
file test.tex:
\environment env
\starttext
bla: bla % no space before colon, if \useencoding[ffr] is in environment.
\stoptext
Do you know the reason?
Peter
--
http://pmrb.free.fr/contact/
_____________________________________
FilmSearch engine: http://f-s.sf.net/
prev parent reply other threads:[~2004-06-07 15:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-19 19:05 Peter Münster
2004-05-21 10:27 ` Hans Hagen
2004-05-21 12:24 ` Peter Münster
2004-06-07 15:51 ` Peter Münster [this message]
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=Pine.LNX.4.58.0406071747390.29578@gaston.free.fr \
--to=pmlists@free.fr \
--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).