2007/12/10, Hans Hagen <[EMAIL PROTECTED]>:
> Wolfgang Schuster wrote:
> > On Fri, 07 Dec 2007 20:09:33 +0100
> > Hans Hagen <[EMAIL PROTECTED]> wrote:
> >
> >> Wolfgang Schuster wrote:
> >>> 2007/12/6, Steffen Wolfrum <[EMAIL PROTECTED]>:
> Am 06.12.2007 um 14:48 schrieb Hans Hagen:
>
>
Wolfgang Schuster wrote:
> On Fri, 07 Dec 2007 20:09:33 +0100
> Hans Hagen <[EMAIL PROTECTED]> wrote:
>
>> Wolfgang Schuster wrote:
>>> 2007/12/6, Steffen Wolfrum <[EMAIL PROTECTED]>:
Am 06.12.2007 um 14:48 schrieb Hans Hagen:
> something numbers=oldstyle could be supported but i see
On Fri, 07 Dec 2007 20:09:33 +0100
Hans Hagen <[EMAIL PROTECTED]> wrote:
> Wolfgang Schuster wrote:
> > 2007/12/6, Steffen Wolfrum <[EMAIL PROTECTED]>:
> >> Am 06.12.2007 um 14:48 schrieb Hans Hagen:
> >>
> >>> something numbers=oldstyle could be supported but i see no real reason
> >>> for it sin
Wolfgang Schuster wrote:
> 2007/12/6, Steffen Wolfrum <[EMAIL PROTECTED]>:
>> Am 06.12.2007 um 14:48 schrieb Hans Hagen:
>>
>>> something numbers=oldstyle could be supported but i see no real reason
>>> for it since then we end up in endless lists of possibilities
>>> (given all
>>> kind of combina
Steffen Wolfrum wrote:
> Am 06.12.2007 um 14:48 schrieb Hans Hagen:
>
>> something numbers=oldstyle could be supported but i see no real reason
>> for it since then we end up in endless lists of possibilities
>> (given all
>> kind of combinations)
>
> I have not yet played with Lua, thus I can'
Wolfgang Schuster wrote:
> And even worse both engines have their own default values for fonts.
add to that
-- they may implement feature support differently
-- fonts have bugs in lookup rules (obscured by processing engines)
-- we may want to control aspects of features
-- we may invent our own
Mojca Miklavec wrote:
> What about
> ['fin2'] = 'Terminal Forms #2',
> ['fin3'] = 'Terminal Forms #3',
> ['ccmp'] = 'Glyph Composition/Decomposition',
> ? :) :) :)
fonts.otf.tables.to_features["Mojca's Favourite Feature] = "smsc"
fonts.otf.tables.to_features["Mojca's Preferred Languag
Mojca Miklavec wrote:
> Well, to be honest, I wanted to ask you to do something similar to
> what you did with enco-utf :) once you finish the mkiv interface.
> That is, to auto-generate the list of feature mappings, so that the
> interface may remain the same in XeTeX as it is in LuaTeX, like
>
Steffen Wolfrum wrote:
> Am 06.12.2007 um 18:55 schrieb Hans Hagen:
>
>> something like that ...
>>
>> keep in mind that you don't need to define a font then,
>>
>> {\setfontfeature{smallcaps}Some Text}
>>
>> will automatically give you that featureset so in practice we can do
>> with only a few r
Am 06.12.2007 um 18:55 schrieb Hans Hagen:
> something like that ...
>
> keep in mind that you don't need to define a font then,
>
> {\setfontfeature{smallcaps}Some Text}
>
> will automatically give you that featureset so in practice we can do
> with only a few real font definitions; mkiv keeps t
Wolfgang Schuster wrote:
> 2007/12/6, Steffen Wolfrum <[EMAIL PROTECTED]>:
>> Am 06.12.2007 um 15:37 schrieb Wolfgang Schuster:
>>
>>> 2007/12/6, Steffen Wolfrum <[EMAIL PROTECTED]>:
Am 06.12.2007 um 14:48 schrieb Hans Hagen:
> something numbers=oldstyle could be supported but i see n
Wolfgang Schuster wrote:
> 2007/12/6, Mojca Miklavec <[EMAIL PROTECTED]>:
>> On Dec 6, 2007 5:09 PM, Steffen Wolfrum wrote:
>>> Am 06.12.2007 um 12:32 schrieb Mojca Miklavec:
>>>
The general approach would be something like:
\definefontfeature[mine][smcp=yes]
\definefontsynonym
2007/12/6, Mojca Miklavec <[EMAIL PROTECTED]>:
> On Dec 6, 2007 5:09 PM, Steffen Wolfrum wrote:
> >
> > Am 06.12.2007 um 12:32 schrieb Mojca Miklavec:
> >
> > > The general approach would be something like:
> > >\definefontfeature[mine][smcp=yes]
> > >\definefontsynonym[a][name:Warnock Pro]
2007/12/6, Steffen Wolfrum <[EMAIL PROTECTED]>:
> I ran sudo ctxtools --updatecontext about one hour ago and all this
> that you write here can't be found (s-pre-63.tex is the latest) ...
>
> Where did you mean should I "grep the sources for definefontfeature" ??
>
> Steffen
>
>
>
> Am 06.12.2007 u
2007/12/6, Steffen Wolfrum <[EMAIL PROTECTED]>:
>
> Am 06.12.2007 um 15:37 schrieb Wolfgang Schuster:
>
> > 2007/12/6, Steffen Wolfrum <[EMAIL PROTECTED]>:
> >>
> >> Am 06.12.2007 um 14:48 schrieb Hans Hagen:
> >>
> >>> something numbers=oldstyle could be supported but i see no real
> >>> reason
>
I ran sudo ctxtools --updatecontext about one hour ago and all this
that you write here can't be found (s-pre-63.tex is the latest) ...
Where did you mean should I "grep the sources for definefontfeature" ??
Steffen
Am 06.12.2007 um 17:35 schrieb Mojca Miklavec:
> On Dec 6, 2007 5:09 PM, St
On Dec 6, 2007 5:09 PM, Steffen Wolfrum wrote:
>
> Am 06.12.2007 um 12:32 schrieb Mojca Miklavec:
>
> > The general approach would be something like:
> >\definefontfeature[mine][smcp=yes]
> >\definefontsynonym[a][name:Warnock Pro][features=mine]
> >\showfont[a]
> > (grep the sources for
On Dec 6, 2007 2:48 PM, Hans Hagen wrote:
> Mojca Miklavec wrote:
>
> > But generally, LuaTeX is much more suitable for such previews (only
> > that there might be no "newshowfont" available yet - writing one is
> > doable if you know what you're interested in).
> >
> > My two cents: ConTeXt curren
Am 06.12.2007 um 12:32 schrieb Mojca Miklavec:
> The general approach would be something like:
>\definefontfeature[mine][smcp=yes]
>\definefontsynonym[a][name:Warnock Pro][features=mine]
>\showfont[a]
> (grep the sources for definefontfeature)
hmm ... the only hit is in /base/font-i
Am 06.12.2007 um 15:37 schrieb Wolfgang Schuster:
> 2007/12/6, Steffen Wolfrum <[EMAIL PROTECTED]>:
>>
>> Am 06.12.2007 um 14:48 schrieb Hans Hagen:
>>
>>> something numbers=oldstyle could be supported but i see no real
>>> reason
>>> for it since then we end up in endless lists of possibilitie
Am 06.12.2007 um 12:32 schrieb Mojca Miklavec:
> In this specific case you could use
> \showfont[SerifCaps]
Nice!
What about other fonts, are there other arguments besides SerifCaps ?
Steffen
___
If your questi
2007/12/6, Steffen Wolfrum <[EMAIL PROTECTED]>:
>
> Am 06.12.2007 um 14:48 schrieb Hans Hagen:
>
> > something numbers=oldstyle could be supported but i see no real reason
> > for it since then we end up in endless lists of possibilities
> > (given all
> > kind of combinations)
>
> I have not yet p
Am 06.12.2007 um 14:48 schrieb Hans Hagen:
> something numbers=oldstyle could be supported but i see no real reason
> for it since then we end up in endless lists of possibilities
> (given all
> kind of combinations)
I have not yet played with Lua, thus I can't follow your and Mojca's
discus
2007/12/6, Mojca Miklavec <[EMAIL PROTECTED]>:
> On 12/6/07, Steffen Wolfrum wrote:
> > Hi,
> >
> > when in february 2006 I asked for an alternative to fontspec that
> > could show me opentype features, Adam wrote:
> >
> > I find that the lcdf typetools are a tremendous help:
> >otfinfo -f ~/Li
Mojca Miklavec wrote:
> But generally, LuaTeX is much more suitable for such previews (only
> that there might be no "newshowfont" available yet - writing one is
> doable if you know what you're interested in).
>
> My two cents: ConTeXt currenty uses
> smcp=yes,script=latn,onum=yes,liga=yes.
On 12/6/07, Steffen Wolfrum wrote:
> Hi,
>
> when in february 2006 I asked for an alternative to fontspec that
> could show me opentype features, Adam wrote:
>
> I find that the lcdf typetools are a tremendous help:
>otfinfo -f ~/Library/Fonts/WarnockPro-Regular.otf
> and I can test the feature
Hi,
when in february 2006 I asked for an alternative to fontspec that
could show me opentype features, Adam wrote:
I find that the lcdf typetools are a tremendous help:
otfinfo -f ~/Library/Fonts/WarnockPro-Regular.otf
and I can test the features with:
\showfont["Warnock Pro: +smcp"]
To
27 matches
Mail list logo
