default] [protrusion=quality,...]
> >>
> >> which adds additional settings to the default set.
> >>
> >>> \definefontfamily [myfont][roman][xcharter]
> >>> \definefontfamily [myfont][sansserif][overpass][rscale=0.93]
> >>> \definefo
]
\definefontfamily [myfont][sansserif][overpass][rscale=0.93]
\definefontfamily [myfont][teletype][overpass][rscale=0.93]
\definefontfamily [myfont][mono][overpassmono][rscale=0.93]
\definetypeface [myfont][mathematics][math] [xcharter]
\setupbodyfont[myfont, 11pt]
\startTEXpage
\showfontkerns
font][mono][overpassmono][rscale=0.93]
> > \definetypeface [myfont][mathematics][math] [xcharter]
> >
> > \setupbodyfont[myfont, 11pt]
> >
> > \startTEXpage
> >
> > \showfontkerns
> >
> > Vitae, Vase, LT, VA, Y., Effizient, abcde
]
\definefontfamily [myfont][mono][overpassmono][rscale=0.93]
\definetypeface [myfont][mathematics][math] [xcharter]
\setupbodyfont[myfont, 11pt]
\startTEXpage
\showfontkerns
Vitae, Vase, LT, VA, Y., Effizient, abcdel™, \italic{effi
abcdel™}, \slanted{effi abcdel™}\\
\style[sans]{Vitae
][rscale=0.93]
\definefontfamily [myfont][mono][overpassmono][rscale=0.93]
\definetypeface [myfont][mathematics][math] [xcharter]
\setupbodyfont[myfont, 11pt]
\startTEXpage
\showfontkerns
Vitae, Vase, LT, VA, Y., Effizient, abcdel™, \italic{effi
abcdel™}, \slanted{effi abcdel™
[mainfont, 12pt]\showfontkerns \language[fr] % If commented, 2 kerns (che -0.180 v -0.120 ance), otherwise 1 kern (chev -0.120 ance)\mainlanguage[fr] % If commented, 2 kerns, otherwise 1 kern \starttext chevance \stoptext
ear list,> > Following MWE aims to reproduce the issue,> > \definefontfeature[default][default][kern=yes]> > \definefontfamily[mainfont][serif][EBGaramond]> > \setupbodyfont[mainfont]> > \showfontkerns> > \starttext> > Chapitre v.> > \stoptextah, went
On 3/19/2021 10:11 PM, Joseph wrote:
Dear list,
Following MWE aims to reproduce the issue,
\definefontfeature[default][default][kern=yes]
\definefontfamily[mainfont][serif][EBGaramond]
\setupbodyfont[mainfont]
\showfontkerns
\starttext
Chapitre v.
\stoptext
ah, went unnoticed because i
On 3/19/21 10:11 PM, Joseph wrote:
> Dear list,
>
> Following MWE aims to reproduce the issue,
Hi Joseph,
I’m afraid that kerning current latest from 2021.03.17 17:46 isn’t able
to deal with the OpenType kern feature (which is enabled by default):
\showfontkerns
\starttext
\sta
Dear list, Following MWE aims to reproduce the issue, \definefontfeature[default][default][kern=yes]\definefontfamily[mainfont][serif][EBGaramond]\setupbodyfont[mainfont]\showfontkerns \starttextChapitre v.\stoptext ThanksBest regards Joseph
will stay (who knows when it
comes un handy) but we will probably stick to font kerns as default.
\startTEXpage[offset=10pt]
\showfontkerns
\showglyphs
\strut average\par
\vskip-2ex
\enabledirectives[fonts.injections.method=advance]
{\red \strut average}\par
\stopTEXpage
eature[default][default][kern=yes]> > \definefontfamily[mainfont][serif][EBGaramond]> > \setupbodyfont[mainfont, 9pt]> > \showfontkerns> > \starttext> > Chapitre {\feature[-][xvicentury]v}. % no kerning between v and . indeed there should be no kerning because the
][default][kern=yes]
\definefontfamily[mainfont][serif][EBGaramond]
\setupbodyfont[mainfont, 9pt]
\showfontkerns
\starttext
Chapitre {\feature[-][xvicentury]v}. % no kerning between v and .
indeed there should be no kerning because there are two different font
setups (lmtx is a bit better in
][serif][EBGaramond]\setupbodyfont[mainfont, 9pt]\showfontkerns \starttextChapitre {\feature[-][xvicentury]v}. % no kerning between v and . Chapitre v.\stoptext
___
If your question is of interest to others as well
][default][kern=yes]\definefontfamily[mainfont][serif][EBGaramond]\setupbodyfont[mainfont, 9pt]\showfontkerns \starttextChapitre {\feature[-][xvicentury]v}. % double kerning between v and . compared to below line. Chapitre v.\stoptext
ypeset with 2 kerns (a
and v + v and o).
Thanks
\definefontfeature[myfeature][mode=node, kern=yes]
\definefontfamily[mainfont][serif][EBGaramond][features=myfeature]
\setupbodyfont[mainfont, 9pt]
\showfontkerns
\starttext
Scavoir
\stoptext
fixed in next upload (left over from experiment r
, kern=yes]\definefontfamily[mainfont][serif][EBGaramond][features=myfeature]\setupbodyfont[mainfont, 9pt] \showfontkerns \starttext Scavoir \stoptext
___
If your question is of interest to others as well, please add an
.
Thanks
Best regards
Joseph
\definefontfeature[base][mode=node, liga=yes, dlig=yes, hlig=yes, kern=yes]
\definefontfeature[xvicentury][]
\definefontfamily[mainfont][serif][EBGaramond][features=base]
\setupbodyfont[mainfont, 9pt]
\showfontkerns
\def\wrongheader{First book {\feature
sample : EBGaramond and KeterYG (can be found in
> various places).
>
> Thanks for advising
>
> Best regards
>
> Joseph
>
> \showfontkerns
>
> \definefontfeature[base][mode=node, kern=yes, script=latn, trep=yes]
>
> \definefontfeature[hebrew][defaul
are
> some hebrew letters. This only affects text after that hebrew letters up
> to end of paragraph.
>
> I use 2 fonts in sample : EBGaramond and KeterYG (can be found in
> various places).
>
> Thanks for advising
>
> Best regards
>
> Joseph
>
> \sh
.
I use 2 fonts in sample : EBGaramond and KeterYG (can be found in
various places).
Thanks for advising
Best regards
Joseph
\showfontkerns
\definefontfeature[base][mode=node, kern=yes, script=latn, trep=yes]
\definefontfeature[hebrew][default][mode=node, lang=heb, script=hebr
KeterYG (can be found in various
places).
Thanks for advising
Best regards
Joseph
\showfontkerns
\definefontfeature[base][mode=node, kern=yes, script=latn, trep=yes]
\definefontfeature[hebrew][default][mode=node, lang=heb, script=hebr]
\definefallbackfamily[mainfont][serif][KeterYG][preset
t give you some ideas:
\usemodule[art-01]\setupbodyfont[dejavu,12pt]
\defineruby[auto] [align=auto,color=darkred]
\defineruby[left] [align=flushleft,color=darkred]
\defineruby[right] [align=flushright,color=darkred]
\defineruby[spread][stretch=yes]
\showframe \showglyphs \showfontkerns \setupinte
=darkred]
\defineruby[spread][stretch=yes]
\showframe \showglyphs \showfontkerns \setupinterlinespace[22pt]
\starttext
\startbuffer
\dorecurse{20}{\ruby{XYZ}{a|bc|d} }\par
\dorecurse{20}{\ruby{PQR}{p|q|r} }\par
\dorecurse{20}{\ruby{XYZ}{1|22|333} }\par
\dorecurse{20}{\ruby{XYZ}{111|222
;
> \definefontfeature[base][mode=node, liga=yes, dlig=yes, hlig=yes, kern=yes]
>
> \definefontfeature[xvicentury][]
>
> \definefontfamily[mainfont][serif][EBGaramond][features=base]
>
> \setupbodyfont[mainfont, 9pt]
>
> \showfontkerns
>
> \def\wrongheader{Firs
[base][mode=node, liga=yes, dlig=yes, hlig=yes, kern=yes]
\definefontfeature[xvicentury][]
\definefontfamily[mainfont][serif][EBGaramond][features=base]
\setupbodyfont[mainfont, 9pt]
\showfontkerns
\def\wrongheader{First book {\feature[-][xvicentury]v} Psalme De David.}
%% \feature[-] seems to
, kern=yes]
\definefontfeature[xvicentury][]
\definefontfamily[mainfont][serif][EBGaramond][features=base]
\setupbodyfont[mainfont, 9pt]
\showfontkerns
\def\wrongheader{First book {\feature[-][xvicentury]v} Psalme De David.} %%
\feature[-] seems to cause problems in header
\def\headerok{First book v
ontfeature[default:b][default][blockligatures=yes]
\definefontfeature[default:k][default][blockligatures=yes,kernligatures=yes]
\showfontkerns
\starttext
{\definedfont[Serif*default @ 11pt]auflage}\par
{\definedfont[Serif*default:b @ 11pt]auflage}\par
{\definedfont[Serif*default:k @ 11pt]auflage
ligatures[u:fl:age] blocks
ligatures in auflegt and Aufl.
Minimal sample:
\starttext
\blockligatures[u:fl:age]
\definefontfeature[default:b][default][blockligatures=yes]
\setupbodyfont[times]\showfontkerns
\startTEXpage[offset=1em]
fl Auflage auflegt Aufl.
\definedf
]
\setupbodyfont[times]\showfontkerns
\startTEXpage[offset=1em]
fi ff fl Auflage auflegt
\definedfont[Serif*default:b]
fi ff fl Auflage auflegt
How do you catch "Aufl." (the abbreviation of Auflage),
which is written _with_ a ligature?
Herbert
\s
he following sample works:
\starttext
\blockligatures[fi,ff] \blockligatures[fl]
\blockligatures[u:fl:age, u:fl:eg]
\definefontfeature[default:b][default][blockligatures=yes]
\setupbodyfont[times]\showfontkerns
\startTEXpage[offset=1em]
fi ff fl Auflage
Am 24.08.2017 um 15:46 schrieb Hans Hagen:
you can enable some tracers:
\starttext
\bgroup
\showglyphs
\showfontkerns
\showmakeup[hbox]
»Tee for Two« shows negative kerning.
\input sapolsky \par
\egroup
\stoptext
thanks, works fine!
Herbert
(I will add a
:
\starttext
\bgroup
\showglyphs
\showfontkerns
\showmakeup[hbox]
»Tee for Two« shows negative kerning.
\input sapolsky \par
\egroup
\stoptext
(I will add a \showmakeup[line] that will mark lines
(probably never used) featurecreep but for sure will
forget to document it etc etc
Thanks Hans. The current development workflow could use an option to see
the bbox structure without seeing the glyphs (along with \showfontkerns as
well)... a "geometric" view of the font in action
visualization of spacing.
AFAIR ConTeXt can do that very nicely (while I never used it and don’t know how
to enable it).
\starttext
\start
\showfontkerns \showmakeup[glue]
\input tufte \par
\stop
\stoptext
ried all sort of
variants but the distance between V and A is wider then with
plaintex and \showfontkerns give no output.
--
Ulrike Fischer
http://www.troubleshooting-tex.de/
___
If your question is of interest t
h
\bye
(I used Arial so that one can see clearly that a text font is used)
you don't enable kerning but anyhow, here is a context example:
\usemodule[oldotf]
\starttext
\showfontkerns
\font\Urm=arial:mode=node;+tlig;+trep;+kern;
\font\Urm=lmroman10-regular:mode=base;+kern;
\textfont0\U
odule loaded kerning is as expected for the 12pt
regular face, the 8pt regular face, and the 8pt italic face. The
12pt italic face, however, is not kerned.
%\usemodule[oldotf]% uncomment to see previous otf handling
\showfontkerns
\setupbodyfont[ebgaramond]
\def\Test{Vowel Tavern
.
With the oldotf module loaded kerning is as expected for the 12pt regular face,
the 8pt regular face, and the 8pt italic face. The 12pt italic face, however,
is not kerned.
%\usemodule[oldotf]% uncomment to see previous otf handling
\showfontkerns
\setupbodyfont[ebgaramond]
\def\Test{Vowel
],
Latin Modern 8pt is substituted.
* With the oldotf module loaded kerning is as expected for the 12pt
regular face, the 8pt regular face, and the 8pt italic face. The
12pt italic face, however, is not kerned.
%\usemodule[oldotf]% uncomment to see previous otf handling
\showfontkerns
o "ans" could be too much in the typescript example, but is perfect
>>> >with Simplefont.
>>> >
>>> >Where does this difference in typography between Typescript and Simplefont
>>> >comes from?
>> Maybe a kerning issue, you can add \s
s" could be too much in the typescript example, but is perfect
with Simplefont.
>
>Where does this difference in typography between Typescript and Simplefont
comes from?
Maybe a kerning issue, you can add \showfontkerns at the begin of your document
to visualize the kerning.
Wolfgan
the Simplefont
> solution and your Typescript solution, both with hanging. Both works, but it
> is not the same output. It seems, that with Simplefont it is "nicer", in the
> following sence: The distance between a capital of a beginning word to the
>
s this
\showfontkerns only in versions newer than 2012.05.30 11:26
MKIV ?
in that version it was an add-on module, but in the meantime it's in
the core
That would explain part of my problems.
If possible, I would like to get the distro version working, before
moving to the lat
Hi Hans,
On Fri, Nov 30, 2012 at 4:38 PM, Hans Hagen wrote:
> On 11/30/2012 4:30 PM, luigi scarso wrote:
>
> What is the reason for installing the latest version of ConTeXt? Is this
>>> \showfontkerns only in versions newer than 2012.05.30 11:26 MKIV ?
>>>
>>
On 11/30/2012 4:30 PM, luigi scarso wrote:
What is the reason for installing the latest version of ConTeXt? Is this
\showfontkerns only in versions newer than 2012.05.30 11:26 MKIV ?
in that version it was an add-on module, but in the meantime it's in the
core
On Fri, Nov 30, 2012 at 3:25 PM, Steve White wrote:
> Hi Luigi,
>
> As I said, this example does not produce a PDF file for me. I will attach
> the output.
>
> Undefined control sequence ...
> ...and it points to \showfontkerns
>
> In previous attempts to load a f
Hi Luigi,
As I said, this example does not produce a PDF file for me. I will attach
the output.
Undefined control sequence ...
...and it points to \showfontkerns
In previous attempts to load a font file directly, I used a command
structures something like
[file:FreeSerif.otf*default],
but
On Fri, Nov 30, 2012 at 12:40 PM, Steve White wrote:
> Hi Luigi,
>
> I am lacking still
>
> * a working input (*.tex) file
%% test.tex
\usemodule[simplefonts][size=25pt]
\definefontfeature[latins][default][script=latn]
\setmainfont[FreeSerif]
\starttext
uess how it was built. I tried
> > the file quoted here as input to the 'context' command, but it chokes on
> the
> > \showfontkerns line. It would help very much to have a working example
> with
> > the proper command line to build it.
> it's ok with fr
I can only guess how it was built. I tried
> the file quoted here as input to the 'context' command, but it chokes on the
> \showfontkerns line. It would help very much to have a working example with
> the proper command line to build it.
it's ok with freefont-ttf-20120503
to the 'context' command, but it chokes on
the \showfontkerns line. It would help very much to have a working example
with the proper command line to build it.
2) I understood that ConTeXt only uses the old-style TrueType 'kern' table,
rather than the OpenType 'kern' GPOS
=latn]
\setmainfont[FreeSerif]
\starttext
\showfontkerns
dadedidodufafefifofufrflftlalelilolutatetitotu\par
\addfs{latins}
dadedidodufafefifofufrflftlalelilolutatetitotu\par
\stoptext
The first line has no GPOS kern enabled and the second line has it.
In order to report it to the font developer (I
\showfontkerns
dadedidodufafefifofufrflftlalelilolutatetitotu\par
\addfs{latins}
dadedidodufafefifofufrflftlalelilolutatetitotu\par
\stoptext
The first line has no GPOS kern enabled and the second line has it.
In order to report it to the font developer (I have the problem not with
ConTeXt, but with my
On 11/27/2012 8:34 PM, Pablo Rodríguez wrote:
On 27/11/12 18:56, Hans Hagen wrote:
On 11/27/2012 6:36 PM, Pablo Rodríguez wrote:
I see lots of kerns in:
\starttext
\startTEXpage[offset=10pt]
\definedfont[file:freeserif.ttf*default] \showfontkerns \input ward
tartTEXpage[offset=10pt]
>>>>>> \definedfont[file:freeserif.ttf*default] \showfontkerns \input
>>>>>> ward
>>>>>> \stopTEXpage
>>>>>> \stoptext
>>>>>
>>>>> Well, I don't see any k
On 27/11/12 18:56, Hans Hagen wrote:
> On 11/27/2012 6:36 PM, Pablo Rodríguez wrote:
>>>>> I see lots of kerns in:
>>>>>
>>>>> \starttext
>>>>>\startTEXpage[offset=10pt]
>>>>>\definedfont[file:free
On 11/27/2012 6:36 PM, Pablo Rodríguez wrote:
On 27/11/12 18:04, Hans Hagen wrote:
I see lots of kerns in:
\starttext
\startTEXpage[offset=10pt]
\definedfont[file:freeserif.ttf*default] \showfontkerns \input ward
\stopTEXpage
\stoptext
Well, I don't see any
On Tue, Nov 27, 2012 at 6:46 PM, Pablo Rodríguez wrote:
> On 27/11/12 18:42, luigi scarso wrote:
>> On Tue, Nov 27, 2012 at 6:36 PM, Pablo Rodríguez wrote:
>>> \starttext
>>>>>> \startTEXpage[offset=10pt]
>>>>>> \defined
On 27/11/12 18:42, luigi scarso wrote:
> On Tue, Nov 27, 2012 at 6:36 PM, Pablo Rodríguez wrote:
>> \starttext
>>>>> \startTEXpage[offset=10pt]
>>>>> \definedfont[file:freeserif.ttf*default] \showfontkerns \input
>>>>> ward
&
On Tue, Nov 27, 2012 at 6:36 PM, Pablo Rodríguez wrote:
> \starttext
>>>> \startTEXpage[offset=10pt]
>>>> \definedfont[file:freeserif.ttf*default] \showfontkerns \input
>>>> ward
>>>> \stopTEXpage
>>>> \stopt
On 27/11/12 18:04, Hans Hagen wrote:
>>> I see lots of kerns in:
>>>
>>> \starttext
>>> \startTEXpage[offset=10pt]
>>> \definedfont[file:freeserif.ttf*default] \showfontkerns \input
>>> ward
>>> \stopTEXpage
>
On 27/11/12 00:11, Wolfgang Schuster wrote:
> [...]
> Is there a difference between the two lines?
>
> \usemodule[simplefonts]
> \setmainfont[FreeSerif]
> \starttext
> \showfontkerns
> dadedidodufafefifofufrflftlalelilolutatetitotu\par
> {\def
On 26/11/12 23:46, Hans Hagen wrote:
> [...]
> Sure, kern tables are used and are quite valid in open type as well
> (open type includes truetype).
>
> I see lots of kerns in:
>
> \starttext
> \startTEXpage[offset=10pt]
> \definedfont[file:freeserif.
lolutatetitotu\par}
> \stoptext
>
> I'm using TrueType fonts of FreeSerif. Isn't the TrueType 'kern' enabled
> by default in ConTeXt? (The glyphs in the example above have no kerning
> at all, so I wonder whether at least the TrueType &#x
]
\definedfont[file:freeserif.ttf*default] \showfontkerns \input ward
\stopTEXpage
\stoptext
I assume simplefonts uses the default featureset
Hans
-
Hans Hagen | PRAGMA ADE
ource?
kerning is *always* driven by the font, given that the font has kerns
(not all fonts need them)
you can see kern sin action with:
\starttext
\showfontkerns \input ward
\stoptext
[builders.paragraphs.solutions.splitters.colors]
\startsimplecolumns
\showfontkerns
\setuptolerance[verytolerant]
\start \SomeTestFont
\input zapf \par
\stop
\column
\start \SomeTestFont \startfontsolution[solution]
\input zapf \par
\stopfontsolution \stop
\stopsimplecolumns
68 matches
Mail list logo
