Re: fullpage and XeTeX typescript

["Yue Wang" <yuleopen@gmail.com>]

Concerning the second question, the following is the reply from Hans
months ago to me.
I think Hans is right, since fonts are quite complex, but it *will* be
a lot easier if we have that mechanism since this mechanism will be
applicable to most fonts.
If there are fonts that fontconfig cannot handle well, then the user
can define them in the old way.:

Yue Wang wrote:

> last question: is it possible to add fontconfig-like interface? if I
> define to use minion famaily, then all the alternatives are
> automatically defined like xetex?

i never looked into that interface so i cannot comment on it, but i've
learned my lessons with fonts ... they are all different and any 'clever
automated mechanism' will at some point fail, so then one ends up with
exeptions; when defining a document style one needs to know the font,
its usage (what variants, styles, etc) and often also it slimitations
(font feature are not that well defined and fonts might have incomplete
implementations)

the best one can do is make a typescript (or a collection, as with tex
gyre which tries to be consistent over the whole range) that implements
a definition and even then, a different version of a font (i mostly use
commercial fonts and font ABC may have different implementations) may
hav edifferent properties; also, there is not one good usage (typescript
combination) of a specific font, esp now that we have many features

actually, talking about features, you need to keep in mind that even
when you define a specific instance, applying such an instance to a
whole document might fail because some features may not cover the whole
possible set of combinations of characters (take frac as an example) and
so usage demands knowlegde

eventually we may have a set of predefined typescripts that cover most
system fonts

On Wed, Dec 24, 2008 at 1:44 AM, Mohamed Bana
<mbana.lists@googlemail.com> wrote:
> hi,
>
> 1.
>
> what's the equivalent of the \usepackage{fullpage} for ConTeXt?
>
>
> 2.
>
> it would be convenient if LuaTeX supported typescripts like XeTeX does
> instead of having to define font synonyms, e.g.,
>
> \definetypeface[mainface][rm][Xserif][Warnock Pro]
> \definetypeface[mainface][ss][Xsans][Cronos Pro]
> \definetypeface[mainface][tt][Xmono][Inconsolata][default]%[rscale=0.9] %
> use only for Monaco
> %\definetypeface[mainface][mm][Xmath][palatino]
> \definetypeface[mainface][mm][math][palatino][default]%[encoding=texnansi]
> \setupbodyfont[mainface, 13pt]
>
>
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
>
___________________________________________________________________________________
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
___________________________________________________________________________________