From: Hans Hagen <pragma@wxs.nl>
Cc: c <ntg-context@ntg.nl>
Subject: [Fwd: Re: ec encoding and tcaron]
Date: Tue, 16 Aug 2005 11:33:52 +0200 [thread overview]
Message-ID: <4301B300.8060202@wxs.nl> (raw)
[-- Attachment #1: Type: text/plain, Size: 652 bytes --]
Hi Jacko,
There is some confusion about tcaron. The problem si that when another
name is used, am2tfm cannot create proper small caps when there is no
matching upper/lowercase slot.
What do you advice in this. Should the ec enc file be changed?
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
[-- Attachment #2: [NTG-context] Re: ec encoding and tcaron --]
[-- Type: message/rfc822, Size: 4581 bytes --]
From: Patrick Gundlach <patrick@gundla.ch>
To: ntg-context@ntg.nl
Subject: [NTG-context] Re: ec encoding and tcaron
Date: Tue, 16 Aug 2005 10:57:43 +0200
Message-ID: <m2r7cudzso.fsf@levana.de>
[trightquote/tcaron]
> So it seems that fonts are using /tcaron; lm use /tquoteright only for sure.
ok, thanks
> Does anybody know who is responsibility/background for ec encoding?
Last time I asked about the encodings (xt2.enc in particular) I got
the following answer from Thomas Esser:
> That file comes from the fontname distribution (CTAN:info/fontname).
> If you request for a change in that file, please write either to the
> tex-fonts list or to Karl Berry.
Patrick
--
ConTeXt wiki and more: http://contextgarden.net
_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
[-- Attachment #3: Type: text/plain, Size: 139 bytes --]
_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
next reply other threads:[~2005-08-16 9:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-16 9:33 Hans Hagen [this message]
2005-08-16 18:41 ` Mojca Miklavec
2005-08-16 19:19 ` Hans Hagen
2005-08-17 12:45 ` Mojca Miklavec
2005-08-17 13:45 ` Hans Hagen
2005-08-17 14:29 ` Mojca Miklavec
2005-08-17 15:08 ` modules.pdf luigi.scarso
2005-08-17 15:19 ` modules.pdf Mojca Miklavec
2005-08-17 17:01 ` modules.pdf luigi.scarso
2005-08-17 19:13 ` modules.pdf Hans Hagen
2005-08-17 19:02 ` modules.pdf Hans Hagen
2005-08-17 15:18 ` [Fwd: Re: ec encoding and tcaron] Hans Hagen
2005-08-17 17:05 ` Mojca Miklavec
2005-08-17 19:48 ` Hans Hagen
2005-08-17 21:35 ` Hans Hagen
2005-08-17 19:35 ` 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=4301B300.8060202@wxs.nl \
--to=pragma@wxs.nl \
--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).