You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i:cursiveCursive textl:bnBengali language & scriptl:hiHindi, Devanagari scriptl:paPunjabi, Gurmukhi scriptquestionFurther information is requesteds:bengBengali scripts:devaDevanagari scripts:guruGurmukhi script
In w3c/alreq#220 i describe a problem for cursive scripts, such as Arabic, caused by using -webkit-text-stroke: the glyph overlaps at the join acquire double breaks, as shown in this picture:
Devanagari and other indic scripts are not normally referred to as cursive, but they do have joining characters. My question is: should browsers also avoid break the top bar and other glyph joining points in the way you see it happening in this screen snap:
I ask, principally, because i know that the top bar can be broken when letter-spacing is applied, however, i suspect that the breaks should not appear when text-stroke is used - and at least, there should be some tidying up, such as in the त्म conjunct.
I'm about to raise a bug against the main browser implementations for the Arabic case, and would like to know whether to include the indic case too.
The text was updated successfully, but these errors were encountered:
No one expects there to be invisible gaps that somehow just get revealed by merely applying text strokes. It’s not text stroking’s responsibility to disconnect the headstroke.
Also it’s pretty much the same problem that darken bands are visible in the headstroke at the glyph gaps when text has transparency (or even just opaque, but resolution is low enough to reveal the semi-transparent, rasterized top/bottom edges of a headstroke).
i:cursiveCursive textl:bnBengali language & scriptl:hiHindi, Devanagari scriptl:paPunjabi, Gurmukhi scriptquestionFurther information is requesteds:bengBengali scripts:devaDevanagari scripts:guruGurmukhi script
In w3c/alreq#220 i describe a problem for cursive scripts, such as Arabic, caused by using
-webkit-text-stroke
: the glyph overlaps at the join acquire double breaks, as shown in this picture:Devanagari and other indic scripts are not normally referred to as cursive, but they do have joining characters. My question is: should browsers also avoid break the top bar and other glyph joining points in the way you see it happening in this screen snap:
I ask, principally, because i know that the top bar can be broken when letter-spacing is applied, however, i suspect that the breaks should not appear when text-stroke is used - and at least, there should be some tidying up, such as in the त्म conjunct.
I'm about to raise a bug against the main browser implementations for the Arabic case, and would like to know whether to include the indic case too.
The text was updated successfully, but these errors were encountered: