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
Optical alignment is a type setting approach that lets punctuation characters bleed into the text's margins. This might occur at the beginning of a line, in which quotation marks might be shifted a bit left or – and significant if you're using justify alignment and hyphenation – on the end of a line to produce a more homogenous right border.
It would be cool if Prawn supported that. The manual layouting tools I've seen so far (Affinity Publisher et al.) use some default settings (see below) for certain characters.
The text was updated successfully, but these errors were encountered:
This is some rather advanced type of layouting and not seen in many tools. Pull requests for such a feature are definitely welcome but, just to set expectations right, the core team probably won't have time to implement this.
Thanks for the swift feedback. I had hoped you'd answer something different, but was afraid that we're reaching the limits of what can be achieved with a reasonable amount of effort.
Prawn is not designed to provide high-quality text output out of the box. It provides basic kerning and that's about it. However, since Prawn is quite extendable, one could provide an extension gem that provides all that functionality, probably using information found in the OpenType fonts themselves.
Optical alignment is a type setting approach that lets punctuation characters bleed into the text's margins. This might occur at the beginning of a line, in which quotation marks might be shifted a bit left or – and significant if you're using justify alignment and hyphenation – on the end of a line to produce a more homogenous right border.
It would be cool if Prawn supported that. The manual layouting tools I've seen so far (Affinity Publisher et al.) use some default settings (see below) for certain characters.
The text was updated successfully, but these errors were encountered: