[NTG-context] Spurious missing character reports
List,
I have one document that after the 2018-11-18 update (beginning with
12-01 and continuing to the current 12-07) has generated hundreds of
spurious missing character messages in the log. A short extract:
fonts > start missing characters:
C:/ConTeXt/tex/texmf/fonts/opentype/public/antt/AntykwaTorunskaCond-Regular.otf
fonts > 72 U+00021 ! EXCLAMATION MARK
fonts > 948 U+00022 " QUOTATION MARK
fonts > 1302 U+00026 & AMPERSAND
fonts > 345318 U+0002B + PLUS SIGN
fonts > 216 U+00030 0 DIGIT ZERO
fonts > 54270 U+00031 1 DIGIT ONE
fonts > 28590 U+00036 6 DIGIT SIX
fonts > 414 U+0003C < LESS-THAN SIGN
fonts > 116712 U+00040 @ COMMERCIAL AT
fonts > 1980 U+00042 B LATIN CAPITAL LETTER B
fonts > 373878 U+00046 F LATIN CAPITAL LETTER F
fonts > 48 U+00048 H LATIN CAPITAL LETTER H
fonts > 3282 U+00049 I LATIN CAPITAL LETTER I
fonts > 36 U+0004A J LATIN CAPITAL LETTER J
fonts > 1560 U+0004B K LATIN CAPITAL LETTER K
fonts > 12 U+0004C L LATIN CAPITAL LETTER L
fonts > 3810 U+0004E N LATIN CAPITAL LETTER N
fonts > 3402 U+00057 W LATIN CAPITAL LETTER W
fonts > 48 U+0005A Z LATIN CAPITAL LETTER Z
fonts > 64206 U+0005B [ LEFT SQUARE BRACKET
fonts > 3420 U+00062 b LATIN SMALL LETTER B
fonts > 3888 U+00063 c LATIN SMALL LETTER C
fonts > 2880 U+00069 i LATIN SMALL LETTER I
fonts > 1284 U+0006B k LATIN SMALL LETTER K
fonts > 336 U+00070 p LATIN SMALL LETTER P
fonts > 2118 U+0007B { LEFT CURLY BRACKET
fonts > 258 U+0007C | VERTICAL LINE
fonts > 12 U+0007E ~ TILDE
fonts > stop missing characters
There are similar reports for the other fonts used in the document
(Antykwa Torunska is used for heads, EBGaramond with Libertinus fallback
for the body).
I have pared down the files to the following example which demonstrates
the problem. I do not understand now all the features interact to cause
this, but the reports disappear upon removing any (such as the
seemingly-redundant \definebodyfontenvironment or the
\switchtobodyfont[small]).
\enabletrackers
[fonts.missing]
\definebodyfontenvironment
[11pt]
[a=1]
\definefontfallback
[fb:ebgr]
[file:libertinusserif-regular]
[0x204A]
\starttypescript [serif] [ebgaramond]
\definefontsynonym [Serif]
[file:ebgaramond-regular]
[fallbacks=fb:ebgr]
\stoptypescript
\define\Test{¡Missing!}
\setupbodyfont
[ebgaramond,11pt]
\setupbodyfont
[libertinus,11pt]
\starttext
\dorecurse{6}{
\switchtobodyfont[small]
\Test\par}
\stoptext
While the messages appear to be incorrect, there is no apparent problem
associated with them. I do not know if they point to some problem I have
not recognized, or are truly spurious. (And I can eliminate them by
turning off the tracker when I am sure that I have the needed coverage
in the fallbacks.)
Of course, if I am doing something wrong I would like to correct it.
--
Rik
___
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
Re: [NTG-context] issue with optical bounds (OpenType)
On 12/9/18 6:53 PM, Hans Hagen wrote: > On 12/9/2018 5:35 PM, Pablo Rodriguez wrote: >> [...] >> -Is there any way that I can apply pure raw lfbd/rtbd values to >> protrusion with no other protrusion calculation at all in opbd? > > you can create your own vectors if you want My own vectors wouldn’t solve the issue, because the variable would be: lfbd(Ὧ) = glyph.width(Ω) - glyph.width(Ὧ) I need to place glyphs accurately, not characters. Character dimensions wouldn’t help to get hanging diacritics. >> -In order to avoid editing all the Greek fonts to get hanging >> diacritics: is there any way to replicate the lfbd feature with >> "fonts.handlers.otf.addfeature"? > > probably with some lua magic one can do a lot but these are typical > things i do when i need them (also because one needs to check the whole > of unicode and cook up categories, this kind of stuff is: do it all > robust and well or don't do it; also one doesn't know how consistent > font designs are) The variable is so simple that the glyph with diacritical marks should be placed in the beginning of the line as it had no such marks. If the font has all glyphs for uppercase letters with the same width for the letter strokes, a general approach (such as the menttioned above, I guess it) would work. Many thanks for your help, Pablo -- http://www.ousia.tk ___ 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] disableXML
On 12/9/2018 6:58 PM, Hans van der Meer wrote: I already tried \starttexcode...\stoptexcode, but in vain. then you need to be more explicit in what you want Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl - ___ 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] issue with optical bounds (OpenType)
On 12/9/2018 5:35 PM, Pablo Rodriguez wrote: On 12/9/18 2:22 PM, Hans Hagen wrote: [...] you confuse mechanism: - protrusion only happen at the start and end of the line - kerning (like single does) happens everywhere so, you need to extend "lfbd" and not use some own kerning feature "leftbounds" which applyu it everywhere while "lfbd" is treated special i.e. sets the protrusion values (when "opbd" is enabled) ... no other way to do this In that case, I have some questions: -Is it possible to enable standard protrusion with opbd? (I mean, I don’t any other character protruded when opbd is enabled.) well, you want to use what the font provides and if the font is incomplete i'd not trust the bits that are there either when opbd is enabled protrusion is taken from that so you should add all chars that you want to prodrude then in an addendum to is (k -Is there any way that I can apply pure raw lfbd/rtbd values to protrusion with no other protrusion calculation at all in opbd? you can create your own vectors if you want -In order to avoid editing all the Greek fonts to get hanging diacritics: is there any way to replicate the lfbd feature with "fonts.handlers.otf.addfeature"? probably with some lua magic one can do a lot but these are typical things i do when i need them (also because one needs to check the whole of unicode and cook up categories, this kind of stuff is: do it all robust and well or don't do it; also one doesn't know how consistent font designs are) Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl - ___ 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] issue with optical bounds (OpenType)
On 12/9/18 2:22 PM, Hans Hagen wrote: >> [...] > you confuse mechanism: > > - protrusion only happen at the start and end of the line > - kerning (like single does) happens everywhere > > so, you need to extend "lfbd" and not use some own kerning feature > "leftbounds" which applyu it everywhere while "lfbd" is treated special > i.e. sets the protrusion values (when "opbd" is enabled) ... no other > way to do this In that case, I have some questions: -Is it possible to enable standard protrusion with opbd? (I mean, I don’t any other character protruded when opbd is enabled.) -Is there any way that I can apply pure raw lfbd/rtbd values to protrusion with no other protrusion calculation at all in opbd? -In order to avoid editing all the Greek fonts to get hanging diacritics: is there any way to replicate the lfbd feature with "fonts.handlers.otf.addfeature"? Many thanks for your help, Pablo -- http://www.ousia.tk ___ 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] disableXML
On 12/9/2018 4:51 PM, Hans van der Meer wrote: I remember there existed a macro \disableXML, which at this time is undefined. Or does my memory fails me here? very old memories ... mkii Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl - ___ 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] fontfamily not loaded anymore
On 12/9/18 1:52 PM, Wolfgang Schuster wrote:
> Hi Pablo,
>
> where did you get the files for GFS Didot from because all packages
> I found use the name GFSDidot.otf for the upright style of the font while
> you have a file with the name GFSDidot-Regular.otf on your system.
Hi Wolfgang,
I modified the font myself to add OpenType lfbd values, but the problem
is that I created a new font (Typographica Didot) with the same XUID
and UniqueID as the already existing GFSDidot.odt.
Although FontForge reported not using them, renewing thee value of the
XUID for Typographica Didot solved the problem.
Sorry for the noise,
Pablo
> Pablo Rodriguez schrieb am 09.12.18 um 09:02:
>> Dear list,
>>
>> I have the following source:
>>
>> \definefontfamily[mainface][rm][GFS Bodoni]
>> \definefontfamily[mainface][hw][GFS Artemisia]
>> \definefontfamily[mainface][ss][GFS Neohellenic]
>> \definefontfamily[mainface][tt][GFS Didot]
>> %[tf=file:{GFSDidot-Regular.otf}]
>> \setupbodyfont[mainface]
>> \startbuffer
>>α β γ δ ε ζ\\
>>{\em α β γ δ ε ζ}\\
>>{\bf α β γ δ ε ζ}\\
>>{\bf α β γ δ ε ζ}\\
>> \stopbuffer
>> \starttext
>>\startTEXpage[offset=1em]
>> \getbuffer
>> \tt\getbuffer
>> \ss\getbuffer
>> \hw\getbuffer
>>\stopTEXpage
>> \stoptext
>>
>> All typefaces are loaded fine, except GFS Didot. Unless I specify the
>> file for tf, any GFS Didot font isn’t loaded. I’m experiencing this with
>> the latest betas.
>>
>> The error I get from ConTeXt is:
>>
>> selectfont > The requested font 'GFS Didot' has no files for the
>> 'tf' alternative, Latin Modern is used instead.
>>
>> "mtxrunjit --script --fonts --list --all" shows in the relevant lines:
>>
>> gfsartemisiabold gfsartemisia gfsartemisiabold GFSArtemisiaBold.otf
>> gfsartemisiabolditalic gfsdidot gfsartemisiabolditalic
>> GFSArtemisiaBoldIt.otf
>> gfsartemisiaitalic gfsartemisia gfsartemisiaitalicGFSArtemisiaIt.otf
>> gfsartemisianormal gfsartemisia gfsartemisiaregular GFSArtemisia.otf
>> gfsartemisiaregulargfsartemisia gfsartemisiaregular GFSArtemisia.otf
>> gfsbodonibold gfsbodoni gfsbodoniboldGFSBodoniBold.otf
>> gfsbodonibolditalicgfsbodoni gfsbodonibolditalic GFSBodoniBoldIt.otf
>> gfsbodoniitalic gfsbodoni gfsbodoniitalic GFSBodoniIt.otf
>> gfsbodoninormal gfsbodoni gfsbodoniregular GFSBodoni.otf
>> gfsbodoniregular gfsbodoni gfsbodoniregular GFSBodoni.otf
>> gfsdidotboldgfsdidot gfsdidotbold GFSDidotBold.otf
>> gfsdidotbolditalic gfsdidot gfsdidotbolditalicGFSDidotBoldItalic.otf
>> gfsdidotitalicgfsdidot gfsdidotitalic GFSDidotItalic.otf
>> gfsdidotnormalgfsdidot gfsdidotregular GFSDidot-Regular.otf
>> gfsdidotregular gfsdidot gfsdidotregular GFSDidot-Regular.otf
>> gfsneohellenicbold gfsneohellenic gfsneohellenicbold
>> GFSNeohellenicBold.otf
>> gfsneohellenicbolditalic gfsneohellenic gfsneohellenicbolditalic
>> GFSNeohellenic-BoldItalic.otf
>> gfsneohellenicitalic gfsneohellenic gfsneohellenicitalic
>> GFSNeohellenicIt.otf
>> gfsneohellenicnormal gfsneohellenic gfsneohellenicregular
>> GFSNeohellenic.otf
>> gfsneohellenicregulargfsneohellenic gfsneohellenicregular
>> GFSNeohellenic.otf
>>
>> Why is the specification of the file for the tf style with GFS Didot needed?
>>
>> Many thanks for your help,
>>
>> Pablo
--
http://www.ousia.tk
___
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
[NTG-context] disableXML
I remember there existed a macro \disableXML, which at this time is undefined. Or does my memory fails me here? dr. Hans van der Meer ___ 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___
Re: [NTG-context] issue with optical bounds (OpenType)
On 12/9/2018 1:34 PM, Pablo Rodriguez wrote:
On 12/7/18 11:25 PM, Hans Hagen wrote:
On 12/7/2018 9:14 PM, Pablo Rodriguez wrote:
[...]
The issue is that, although opbd values are used, that results from opbd
and from single placement in addfeature are different (although LuaTeX
reports the same values for lfbd).
because you implement it as kerning and not as opbd (protrusion is not
kerning) ... you can try to change the name to "lfbd" (if you would
enable lfbd as feature for sure you would get funny kerning so opbd
picks up from those instead)
If protrusion has to apply other values than the ones besides opbd, the
values for optical bounds aren’t reliable for accurate glyph
positioning. Sorry, but otherwise there is no need for optical margins
in OpenType (standard protrusion would be all that is needed).
Kerning might be selectively applied, such as in:
\startluacode
fonts.handlers.otf.addfeature {
name = "leftbounds",
type = "single",
data = {
Ἠ = { -212, 0, -212, 0 },
Ὧ = { -196, 0, -196, 0 },
}
}
\stopluacode
\definefontfeature[default][default][protrusion=quality]
\definefontfeature[leftbounds][leftbounds=yes]
\setupfirstline
[alternative=word, n=1, style={\feature[+][leftbounds]}]
\showframe
\setuplayout[page]
\definefontfamily[mainface][rm][Typographica Old Standard]
\definefontfamily[mainface][tt][Latin Modern Mono]
\setupbodyfont[mainface, 300pt]
\setupalign[hanging]
\startbuffer
«a\par
«b\par
Ω\par
Ὧ\par
Ἠ\par
\stopbuffer
\starttext
\setupparagraphintro[each][\setfirstline]
\getbuffer
\stoptext
At least to get Greek hanging diacritics, I think this is the way to go.
It would be extremely useful to enable a \setuplineintro for verse.
It would be also useful to have a function that substracts the width of
two given glyphs. (This is exactly the amount to get hanging diacritics
properly kerned.)
you confuse mechanism:
- protrusion only happen at the start and end of the line
- kerning (like single does) happens everywhere
so, you need to extend "lfbd" and not use some own kerning feature
"leftbounds" which applyu it everywhere while "lfbd" is treated special
i.e. sets the protrusion values (when "opbd" is enabled) ... no other
way to do this
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-
___
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
Re: [NTG-context] fontfamily not loaded anymore
Hi Pablo,
where did you get the files for GFS Didot from because all packages
I found use the name GFSDidot.otf for the upright style of the font while
you have a file with the name GFSDidot-Regular.otf on your system.
Wolfgang
Pablo Rodriguez schrieb am 09.12.18 um 09:02:
Dear list,
I have the following source:
\definefontfamily[mainface][rm][GFS Bodoni]
\definefontfamily[mainface][hw][GFS Artemisia]
\definefontfamily[mainface][ss][GFS Neohellenic]
\definefontfamily[mainface][tt][GFS Didot]
%[tf=file:{GFSDidot-Regular.otf}]
\setupbodyfont[mainface]
\startbuffer
α β γ δ ε ζ\\
{\em α β γ δ ε ζ}\\
{\bf α β γ δ ε ζ}\\
{\bf α β γ δ ε ζ}\\
\stopbuffer
\starttext
\startTEXpage[offset=1em]
\getbuffer
\tt\getbuffer
\ss\getbuffer
\hw\getbuffer
\stopTEXpage
\stoptext
All typefaces are loaded fine, except GFS Didot. Unless I specify the
file for tf, any GFS Didot font isn’t loaded. I’m experiencing this with
the latest betas.
The error I get from ConTeXt is:
selectfont > The requested font 'GFS Didot' has no files for the
'tf' alternative, Latin Modern is used instead.
"mtxrunjit --script --fonts --list --all" shows in the relevant lines:
gfsartemisiabold gfsartemisia gfsartemisiabold GFSArtemisiaBold.otf
gfsartemisiabolditalic gfsdidot gfsartemisiabolditalic
GFSArtemisiaBoldIt.otf
gfsartemisiaitalic gfsartemisia gfsartemisiaitalicGFSArtemisiaIt.otf
gfsartemisianormal gfsartemisia gfsartemisiaregular GFSArtemisia.otf
gfsartemisiaregulargfsartemisia gfsartemisiaregular GFSArtemisia.otf
gfsbodonibold gfsbodoni gfsbodoniboldGFSBodoniBold.otf
gfsbodonibolditalicgfsbodoni gfsbodonibolditalic GFSBodoniBoldIt.otf
gfsbodoniitalic gfsbodoni gfsbodoniitalic GFSBodoniIt.otf
gfsbodoninormal gfsbodoni gfsbodoniregular GFSBodoni.otf
gfsbodoniregular gfsbodoni gfsbodoniregular GFSBodoni.otf
gfsdidotboldgfsdidot gfsdidotbold GFSDidotBold.otf
gfsdidotbolditalic gfsdidot gfsdidotbolditalicGFSDidotBoldItalic.otf
gfsdidotitalicgfsdidot gfsdidotitalic GFSDidotItalic.otf
gfsdidotnormalgfsdidot gfsdidotregular GFSDidot-Regular.otf
gfsdidotregular gfsdidot gfsdidotregular GFSDidot-Regular.otf
gfsneohellenicbold gfsneohellenic gfsneohellenicbold
GFSNeohellenicBold.otf
gfsneohellenicbolditalic gfsneohellenic gfsneohellenicbolditalic
GFSNeohellenic-BoldItalic.otf
gfsneohellenicitalic gfsneohellenic gfsneohellenicitalic
GFSNeohellenicIt.otf
gfsneohellenicnormal gfsneohellenic gfsneohellenicregular
GFSNeohellenic.otf
gfsneohellenicregulargfsneohellenic gfsneohellenicregular
GFSNeohellenic.otf
Why is the specification of the file for the tf style with GFS Didot needed?
Many thanks for your help,
Pablo
___
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
Re: [NTG-context] issue with optical bounds (OpenType)
On 12/7/18 11:25 PM, Hans Hagen wrote:
> On 12/7/2018 9:14 PM, Pablo Rodriguez wrote:
>> [...]
>> The issue is that, although opbd values are used, that results from opbd
>> and from single placement in addfeature are different (although LuaTeX
>> reports the same values for lfbd).
>
> because you implement it as kerning and not as opbd (protrusion is not
> kerning) ... you can try to change the name to "lfbd" (if you would
> enable lfbd as feature for sure you would get funny kerning so opbd
> picks up from those instead)
If protrusion has to apply other values than the ones besides opbd, the
values for optical bounds aren’t reliable for accurate glyph
positioning. Sorry, but otherwise there is no need for optical margins
in OpenType (standard protrusion would be all that is needed).
Kerning might be selectively applied, such as in:
\startluacode
fonts.handlers.otf.addfeature {
name = "leftbounds",
type = "single",
data = {
Ἠ = { -212, 0, -212, 0 },
Ὧ = { -196, 0, -196, 0 },
}
}
\stopluacode
\definefontfeature[default][default][protrusion=quality]
\definefontfeature[leftbounds][leftbounds=yes]
\setupfirstline
[alternative=word, n=1, style={\feature[+][leftbounds]}]
\showframe
\setuplayout[page]
\definefontfamily[mainface][rm][Typographica Old Standard]
\definefontfamily[mainface][tt][Latin Modern Mono]
\setupbodyfont[mainface, 300pt]
\setupalign[hanging]
\startbuffer
«a\par
«b\par
Ω\par
Ὧ\par
Ἠ\par
\stopbuffer
\starttext
\setupparagraphintro[each][\setfirstline]
\getbuffer
\stoptext
At least to get Greek hanging diacritics, I think this is the way to go.
It would be extremely useful to enable a \setuplineintro for verse.
It would be also useful to have a function that substracts the width of
two given glyphs. (This is exactly the amount to get hanging diacritics
properly kerned.)
Many thanks for your help,
Pablo
--
http://www.ousia.tk
___
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
[NTG-context] fontfamily not loaded anymore
Dear list,
I have the following source:
\definefontfamily[mainface][rm][GFS Bodoni]
\definefontfamily[mainface][hw][GFS Artemisia]
\definefontfamily[mainface][ss][GFS Neohellenic]
\definefontfamily[mainface][tt][GFS Didot]
%[tf=file:{GFSDidot-Regular.otf}]
\setupbodyfont[mainface]
\startbuffer
α β γ δ ε ζ\\
{\em α β γ δ ε ζ}\\
{\bf α β γ δ ε ζ}\\
{\bf α β γ δ ε ζ}\\
\stopbuffer
\starttext
\startTEXpage[offset=1em]
\getbuffer
\tt\getbuffer
\ss\getbuffer
\hw\getbuffer
\stopTEXpage
\stoptext
All typefaces are loaded fine, except GFS Didot. Unless I specify the
file for tf, any GFS Didot font isn’t loaded. I’m experiencing this with
the latest betas.
The error I get from ConTeXt is:
selectfont > The requested font 'GFS Didot' has no files for the
'tf' alternative, Latin Modern is used instead.
"mtxrunjit --script --fonts --list --all" shows in the relevant lines:
gfsartemisiabold gfsartemisia gfsartemisiabold GFSArtemisiaBold.otf
gfsartemisiabolditalic gfsdidot gfsartemisiabolditalic
GFSArtemisiaBoldIt.otf
gfsartemisiaitalic gfsartemisia gfsartemisiaitalicGFSArtemisiaIt.otf
gfsartemisianormal gfsartemisia gfsartemisiaregular GFSArtemisia.otf
gfsartemisiaregulargfsartemisia gfsartemisiaregular GFSArtemisia.otf
gfsbodonibold gfsbodoni gfsbodoniboldGFSBodoniBold.otf
gfsbodonibolditalicgfsbodoni gfsbodonibolditalic GFSBodoniBoldIt.otf
gfsbodoniitalic gfsbodoni gfsbodoniitalic GFSBodoniIt.otf
gfsbodoninormal gfsbodoni gfsbodoniregular GFSBodoni.otf
gfsbodoniregular gfsbodoni gfsbodoniregular GFSBodoni.otf
gfsdidotboldgfsdidot gfsdidotbold GFSDidotBold.otf
gfsdidotbolditalic gfsdidot gfsdidotbolditalicGFSDidotBoldItalic.otf
gfsdidotitalicgfsdidot gfsdidotitalic GFSDidotItalic.otf
gfsdidotnormalgfsdidot gfsdidotregular GFSDidot-Regular.otf
gfsdidotregular gfsdidot gfsdidotregular GFSDidot-Regular.otf
gfsneohellenicbold gfsneohellenic gfsneohellenicbold
GFSNeohellenicBold.otf
gfsneohellenicbolditalic gfsneohellenic gfsneohellenicbolditalic
GFSNeohellenic-BoldItalic.otf
gfsneohellenicitalic gfsneohellenic gfsneohellenicitalic
GFSNeohellenicIt.otf
gfsneohellenicnormal gfsneohellenic gfsneohellenicregular
GFSNeohellenic.otf
gfsneohellenicregulargfsneohellenic gfsneohellenicregular
GFSNeohellenic.otf
Why is the specification of the file for the tf style with GFS Didot needed?
Many thanks for your help,
Pablo
--
http://www.ousia.tk
___
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___
