From: "Peter Münster" <pmlists@free.fr>
Subject: Re: enco-ffr again
Date: Tue, 12 Jul 2005 12:12:15 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.58.0507121210230.14396@gaston.free.fr> (raw)
In-Reply-To: <42CA89F1.3010107@wxs.nl>
On Tue, 5 Jul 2005, Hans Hagen wrote:
> Peter Münster wrote:
> > I've just discovered, that the problem is only with : and ; but not with ?
> > and !
> > Here my example files:
> >
> > file env.tex:
> > \startenvironment env
> > \useencoding[ffr]
> > \mainlanguage[fr]
> > \stopenvironment
> >
> > file test.tex:
> > \environment env
> > \starttext
> > No space before : nor ;
> > bla: bla; bla? bla!
> > \stoptext
>
> see proposed solution in wiki bug page
Thank you, Hans!
So, if your solution is in the kernel now, can we delete this page?
Cheers, Peter
--
http://pmrb.free.fr/contact/
next prev parent reply other threads:[~2005-07-12 10:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-14 16:51 Peter Münster
2005-07-05 13:24 ` Hans Hagen
2005-07-12 10:12 ` Peter Münster [this message]
2005-07-13 8:55 ` Hans Hagen
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.0507121210230.14396@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).