3,897
edits
Changes
Jump to navigation
Jump to search
It should come as no surprise that Mark IV extends the <cmd>definefontfeature</cmd> to make full use of the lua opentype engine by adding '''mode=node''' generates different effects, but even with a traditional font setup and various opentype tags features that you want on or off. In the distribution, there are incompatibilies unless you use tfm-is only fonts. one case of this:
{{todo|This is unclear \definefontfeature [arabic] [mode=node,language=dflt,script=arab,ccmp=yes, init=yes,medi=yes,fina=yes,isol=yes, liga=yes,dlig=yes,rlig=yes,clig=yes,calt=yes, mark=yes,mkmk=yes,kern=yes,curs=yes] It should come as no surprise that such a '''mode-=node''' is undocumented generates different effects, but even with a traditional font setup there are incompatibilies unless you use tfm-only fonts, because the metric information of fonts used in mkii}}Mark IV (afm, ttf, otf) are often subtly different from the tfm metrics used by Mark II.
HH: this This is related to open type fonts metrics not having the limitations of traditional tfm metrics (and the fact that internally luatex has some limitations removed)
→Paragraph formatting: attempt to explain better
= Paragraph formatting =
== Actual font usage ==
If you have a font in both OpenType and traditional Type 1, then Mark IV will typically use one version and Mark II the other. There is no guarantee that both sets have the same metrics.
== Interword spacing ==
