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
Xiphos provides a "respect font faces" option, where embedded font directives are left alone vs aggressively going through the rendered HTML content to obliterate them. This is useful where poor publishers' choices can be overcome by letting the user's choice for the module as a whole remain in control. I use this in NET + NETnote because the "Galaxie Hebrew" and "Galaxie Greek" are plain ugly, and the FreeSerif or LinuxLibertine I normally use for most modules are quite beautiful by comparison.
This has 2 longstanding problems:
It's far too specific to "Galax" as a font face prefix. When this was implemented, I was far too concerned with one type of font use, from NET.
It obliterates the entire "[font face="..."]" and "[/font]" specifications, leaving a pile of spaces that make the embedded Heb/Grk content not flow properly, such as when following a parenthesis opening a comment, which renders at the end of the line, so the parenthesis is at line end and the Heb/Grk starts the next line.
Thus:
Get rid of the "Galax" prefix specificity: Annihilate any font.
Replace only the actual font name with some garbage, so that the font face does not actually change.
The text was updated successfully, but these errors were encountered:
Xiphos provides a "respect font faces" option, where embedded font directives are left alone vs aggressively going through the rendered HTML content to obliterate them. This is useful where poor publishers' choices can be overcome by letting the user's choice for the module as a whole remain in control. I use this in NET + NETnote because the "Galaxie Hebrew" and "Galaxie Greek" are plain ugly, and the FreeSerif or LinuxLibertine I normally use for most modules are quite beautiful by comparison.
This has 2 longstanding problems:
Thus:
The text was updated successfully, but these errors were encountered: