The /space glyph can be used in OT code in the same way as any other glyph, and it works well inside apps like Illustrator.
Fonts like Underware Liza relies on /space(*) to apply many of their tricks.
*
http://underware.nl/case-studies/random-vs-clever/And many fonts have kerning pairs like T/space or f/space, etc...
But sadly, on the web, everything related to the /space is ignored (OT features, kerning, etc).
Any idea way? or a workaround?
Are the browsers silently replacing the /space by other glyph?
Comments
This time I was trying to apply some magic to a whole sentence, instead of just isolated words. But can't do so without the space. It will work in illustrator, but not on the web... c'est la vie
As a quick test:
- Added a small box inside /space, and a big box inside /space.calt
- Inside 'liga', added: sub @lower space' @lower by space.calt;
Illustrator is showing the /space.calt big box as expected.
Both Firefox and Chome are drawing the /space small box, but ignoring the sub
They seem to be rendering the /space glyph contents, but still ignoring kerning and features.
But the Firefox and Chrome problem is a bummer for advanced web typography, for sure.
But I would not know how to properly describe the issue.
Perhaps some of you, more experienced, might want to do it?
But remember, we are working in a handicapped environment — to apps and OS, there are only two kinds of font spacing: monospaced and proportional. All styles that are proportionally spaced, according to apps and OS, are equally adept at tracking, kerning and justification, or not being tracked, kerned or justified? So is each glyph equally adept at tracking, kerning, justification and substitution as these things mix.. at all sizes? It is ridiculous, I think.
If we just had recommendations of some kind...;)