From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Bitstream Charter vs. Charis SIL
Date: Mon, 09 Jun 2008 10:35:58 +0200 [thread overview]
Message-ID: <484CEB6E.6090809@wxs.nl> (raw)
In-Reply-To: <6faad9f00806090124u2fd8bcc5r16be003ddfb1b8e4@mail.gmail.com>
Mojca Miklavec wrote:
> On Mon, Jun 9, 2008 at 10:04 AM, Hans Hagen wrote:
>> Wolfgang Schuster wrote:
>>
>>>>> \definefontsynonym [Charter-Roman-Caps] [name:CharterBT-SmallCap] % or: [bchrc8a]
>>> The last line should be removed, the Charter font on ctan has no
>>> smallcaps and the
>>> style is only commercial available
>> ok, remapped
>>
>>>>> Hans - what would be the implications for LuaTeX if
>>>>> name:CharterBT-Roman
>>>>> was changed into
>>>>> file:bchr8a
>>>>> ? Not suggesting that yet, only asking.
>>> There is no difference, the same fonts are loaded, I tried this a month ago.
>> indeed
>
> In that case: it would be much more XeTeX-friendly if filename can be
> provided, since XeTeX is not able to search for font names in TeX
> trees unless fontconfig is specifically configured that way.
maybe for those extra fonts provide a special definition file for xetex
then; at the top of the normal file we can do a check for xetex and then
load another file (it all depends on the quality of the filenames and
font filenames are often obscure and/or inconsistent)
anyhow, i suppose that this kind of definitions have to go in
type-sil.tex or so; in that case maybe we also need to define the other
sil fonts there
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
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2008-06-09 8:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-07 9:34 Mojca Miklavec
2008-06-07 9:51 ` Taco Hoekwater
2008-06-09 6:59 ` Wolfgang Schuster
2008-06-09 7:04 ` Taco Hoekwater
2008-06-09 7:44 ` Wolfgang Schuster
2008-06-09 8:04 ` Hans Hagen
2008-06-09 8:24 ` Mojca Miklavec
2008-06-09 8:35 ` Hans Hagen [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=484CEB6E.6090809@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).