From: "Mojca Miklavec" <mojca.miklavec.lists@gmail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: XeTeX and OpenType LM
Date: Fri, 2 Feb 2007 16:40:15 +0100 [thread overview]
Message-ID: <6faad9f00702020740i481a92b7vd08ac37003055762@mail.gmail.com> (raw)
In-Reply-To: <45C341C3.6010508@wxs.nl>
On 2/2/07, Hans Hagen wrote:
> Mojca Miklavec wrote:
> > On 2/2/07, Hans Hagen wrote:
> >
> >> Mojca Miklavec wrote:
> >>
> >>> ... much much text .. begging for []'s ...
> >>>
> >>>
> >> How about this ... no quotes in specs, only file: or name: in front of
> >> the name, and for xetex we default to filenames using file:
> >>
> >
> > I would default to "name:"
> >
> no, because that way we can use existing context typescripts and i'm not
> going to add a complete extra set now (clows down too much); so, if
> names are used prefix it with name:
How do you mean "existing typescripts"? OpenType names
(lmroman12-regular) are different than Type1 names (ec-lmr12) anyway.
I already did it for Latin Modern (I can run a few regular expressions
on that file to replace \definexetexfontsynonym with something more
suitable), and I can do it for the rest of Polish font names as well
if needed.
But in any case: I guess that if there are two regimes (file & name),
at least for what's hidden from user, it would make sense to set it to
"file:" explicitely.
Btw: In the patch that I sent you in the first mail in this thread is
also a section which originally had a "TODO" in type-enc.tex:
\starttypescript [serif] [modern,latin-modern,computer-modern]
[uc,texnansi,ec,qx,t5]
\definefontsynonym [cmr5] [LMRoman5-Regular]
[encoding=\typescriptthree]
\definefontsynonym [cmr6] [LMRoman6-Regular]
[encoding=\typescriptthree]
\definefontsynonym [cmr7] [LMRoman7-Regular]
[encoding=\typescriptthree]
instead of
\definefontsynonym [cmr5] [lmr5] [encoding=\typescriptthree]
\definefontsynonym [cmr6] [lmr6] [encoding=\typescriptthree]
\definefontsynonym [cmr7] [lmr7] [encoding=\typescriptthree]
Do the corrections look OK?
> > I need to try to run these, but I like the syntax. Although it would
> > probably make sense to default to "name" (so: no brackets,
> > \def\fontfilesome#1{"#1"}) under XeTeX. Those fonts that come as .otf
> > are relatively rare and for those (I have Polish fonts in mind)
> > ConTeXt can provide ready typescripts with "file:" prefix. I assume
> > that for most users it would be an overhead having to write "name:"
> > for each single font that they want to use, and most such fonts are
> > probably installed on the system.
> >
> > There is one more thing though. I'm taking these from Adam's notes on the wiki:
> >
> > \definefontsynonym
> > [DidotCaps]
> > ['Didot:mapping=tex-text;
> > Letter Case=Small Capitals;Ligatures=!Common Ligatures']
> > [encoding=uc]
> >
> that will be done differently, with a features key:
> \definefont[...][...][features=]
>
> and lowlevel that one will be xetex'd or luatex'd
Great! It will be much better that way.
Mojca
prev parent reply other threads:[~2007-02-02 15:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-31 4:44 Mojca Miklavec
2007-01-31 11:09 ` Hans Hagen
2007-01-31 16:58 ` Mojca Miklavec
2007-01-31 17:16 ` Jonathan Kew
2007-01-31 19:12 ` Hans Hagen
2007-02-02 8:26 ` Hans Hagen
2007-02-02 13:23 ` Mojca Miklavec
2007-02-02 13:50 ` Hans Hagen
2007-02-02 15:40 ` Mojca Miklavec [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=6faad9f00702020740i481a92b7vd08ac37003055762@mail.gmail.com \
--to=mojca.miklavec.lists@gmail.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).