From: Giuseppe Bilotta <bourbaki@bigfoot.com>
Cc: ntg-context@ntg.nl
Subject: Re[2]: More font problems --- encoding errors
Date: Fri, 28 Dec 2001 22:35:06 +0100 [thread overview]
Message-ID: <1123868927.20011228223506@bigfoot.com> (raw)
In-Reply-To: <5.1.0.14.1.20011227141026.03c798e8@server-1>
Thursday, December 27, 2001 Hans Hagen wrote:
>>(1) encoding 8r (from enco-tbo.tex) does NOT define leftguillemot
>>and rightguillemot (they are there at positions 171 and 187)
HH> actually, that part was never really finished, the same for dashes -)
I think the font- and char- encoding should be a top priority.
Now, if ConTeXt was on CVS and I had access to it, I could really
give a hand in this very mechanical part.
HH> indeed, and if it goes wrong, then there is a bug; do you use the latest
HH> beta?
Looking better, it's version 2001.12.10 (Now which is the month
and which is the day?)
--
Giuseppe "Oblomov" Bilotta
next prev parent reply other threads:[~2001-12-28 21:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-26 15:44 Giuseppe Bilotta
2001-12-27 13:27 ` Hans Hagen
2001-12-28 9:48 ` Re[2]: " Giuseppe Bilotta
2001-12-28 21:35 ` Giuseppe Bilotta [this message]
2001-12-29 11:32 ` 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=1123868927.20011228223506@bigfoot.com \
--to=bourbaki@bigfoot.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).