From: "Wolfgang Schuster" <schuster.wolfgang@googlemail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Cc: Jonathan Kew <jonathan_kew@sil.org>
Subject: Re: Bitstream Charter vs. Charis SIL
Date: Mon, 9 Jun 2008 08:59:32 +0200 [thread overview]
Message-ID: <115224fb0806082359q1a921d19y812419181aa6567f@mail.gmail.com> (raw)
In-Reply-To: <6faad9f00806070234j777520f4nc2343a82f3c7a2d9@mail.gmail.com>
On Sat, Jun 7, 2008 at 11:34 AM, Mojca Miklavec
<mojca.miklavec.lists@gmail.com> wrote:
>>> (/home/diego/tex/texmf-context/tex/context/base/type-xtx.tex)
>>> ! Font \*map7ptrmscss*:=CharterBT-SmallCap at 6.64998pt not loadable:
>>> Metric (TFM) file or installed font not found.
>>
>> That's because of
>>
>> \definefontsynonym [Charter-Roman [name:CharterBT-Roman] % or: [bchr8a]
>> \definefontsynonym [Charter-Italic] [name:CharterBT-Italic] % or: [bchri8a]
>> \definefontsynonym [Charter-Bold] [name:CharterBT-Bold] % or: [bchb8a]
>> \definefontsynonym [Charter-BoldItalic] [name:CharterBT-BoldItalic] % or: [bchbi8a]
>> \definefontsynonym [Charter-Slanted] [name:CharterBT-Italic] % or: [bchri8a]
>> \definefontsynonym [Charter-BoldSlanted] [name:CharterBT-BoldItalic] % or: [bchbi8a]
>> \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
>> The fonts are on
>> http://www.ctan.org/tex-archive/fonts/charter/
>> and I can add them, but there is still one problem.
>>
>> Since fonts are defined this way, you would need to configure
>> fc-config to look for fonts in that directory in order to find the
>> font. Or one would need to change the definition.
>>
>> 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.
> Now that I'm looking at it again at
> http://en.wikipedia.org/wiki/Bitstream_Charter:
>
>> This has resulted in derivatives of Bitstream Charter becoming available, including Charis SIL.
>
> What about adding
> http://scripts.sil.org/CharisSILfont
> to the distribution, possibly including TeX Live, and replacing the
> definitions to use CharisSIL in XeTeX/LuaTeX instead of Bitstream
> Charter? The same move that has happened with TeX Gyre? Any comments?
> Suggestions?
The fonts include more characters but come without any kerning information.
Wolfgang
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2008-06-09 6:59 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 [this message]
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
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=115224fb0806082359q1a921d19y812419181aa6567f@mail.gmail.com \
--to=schuster.wolfgang@googlemail.com \
--cc=jonathan_kew@sil.org \
--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).