Re: [NTG-context] issue with optical bounds (OpenType)

2018-12-10 Thread Pablo Rodriguez
On 12/10/18 10:51 AM, Hans Hagen wrote: > On 12/9/2018 8:54 PM, Pablo Rodriguez wrote: >> [] >> 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

Re: [NTG-context] Spurious missing character reports

2018-12-10 Thread Hans Hagen
On 12/9/2018 10:35 PM, Rik Kabel wrote: 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

Re: [NTG-context] modifying kerning breaks opentype ligatures (and other features)

2018-12-10 Thread Hans Hagen
On 12/10/2018 6:16 PM, mf wrote: yes, the ligature would not get the same shrinkage or stretch of the rest, but i don't modify the kerning that much (factor=.02 is the maximum value). It's still acceptable. ok, then don't use this characterkerning but use expansion (hz) ... you can do that

[NTG-context] Drops Module

2018-12-10 Thread Aditya Mahajan
Hi Peter, I noticed that the drops module recently stopping running with the error: /home/adityam/texmf/tex/context/third/drops/t-drops.lua:1098: bad argument #3 to 'format' (number has no integer representation) stack traceback: [C]: in function 'string.format'

Re: [NTG-context] modifying kerning breaks opentype ligatures (and other features)

2018-12-10 Thread mf
character kerning is bad anyway ... I'm using it to get a paragraph one line shorter or longer, or to tune what in TeX is set with \parfillskip. I'm using ConTeXt with a mindset developed on other typesetting softwares. That's not right, i know, but for now i'm finding easier to work with

Re: [NTG-context] modifying kerning breaks opentype ligatures (and other features)

2018-12-10 Thread Hans Hagen
On 12/10/2018 4:26 PM, mf wrote: Hello list, i noticed that setting a different kerning breaks some features of opentype fonts; that is true, for example, for ligatures and fractions (frac feature). It looks like a modified kerning inserts something between two adjacent character, making

Re: [NTG-context] modifying kerning breaks opentype ligatures (and other features)

2018-12-10 Thread mf
An example of local correction, but it's not automatic: \definecharacterkerning[narrow][factor=-.02] \definecharacterkerning[wide][factor=.02] \definefontfeature[frac][frac=yes] \def\Narrow#1{\bgroup\setcharacterkerning[narrow]#1\egroup} \def\Wide#1{\bgroup\setcharacterkerning[wide]#1\egroup}

[NTG-context] modifying kerning breaks opentype ligatures (and other features)

2018-12-10 Thread mf
Hello list, i noticed that setting a different kerning breaks some features of opentype fonts; that is true, for example, for ligatures and fractions (frac feature). It looks like a modified kerning inserts something between two adjacent character, making them no more adjacent. That way the

Re: [NTG-context] Strange behaviour of TABLE with \currentTABLErow

2018-12-10 Thread Tomas Hala
Hi Wolfgang, thank you for your reply. The split=repeat -- my fault, sorry. But -- surprisingly -- this mistake helped me along understanding the problem. I discovered -- if head and next head are defined -- that the "line number 1" servers for the opening head at the beginning of a table

Re: [NTG-context] issue with optical bounds (OpenType)

2018-12-10 Thread Hans Hagen
On 12/9/2018 8:54 PM, Pablo Rodriguez wrote: 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