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
_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context

Reply via email to