search

vernnobile / OswaldFont

repo for the Oswald font family
95 stars 40 forks source link

Non-spacing combining characters #1

Open moyogo opened 11 years ago

moyogo commented 11 years ago

U+030F, U+0311, U+0326 are non-spacing combining characters they should have zero advance-width. In Oswald they are spacing characters, this is not correct.

Furthermore, to be fully useable they should be positioned on top of base characters with anchors. Looking at the UFO files it seems anchors are already being used for those and for spacing characters used as references in precomposed glyphs. You might as well have the non-spacing combining characters with anchors as clones of the spacing ones (basically copy and set advance-width to zero: acute 00B4 -> acutecomb 0301, etc.).

vernnobile commented 11 years ago

Thanks Denis :) much appreciated. -vernon

On 12 Apr 2013, at 13:08, Denis Moyogo Jacquerye notifications@github.com wrote:

U+030F, U+0311, U+0326 are non-spacing combining characters they should have zero advance-width. In Oswald they are spacing characters, this is not correct.

Furthermore, to be fully useable they should be positioned on top of base characters with anchors. Looking at the UFO files it seems anchors are already being used for those and for spacing characters used as references in precomposed glyphs. You might as well have the non-spacing combining characters with anchors as clones of the spacing ones (basically copy and set advance-width to zero: acute 00B4 -> acutecomb 0301, etc.).

— Reply to this email directly or view it on GitHub.

moyogo commented 11 years ago

Oops sorry I used the term ‘anchors’ for two different things. The UFO files have anchors used to build precomposed glyphs in , but non-spacing combining characters need OpenType anchors in the generated fonts.