- From: fantasai via GitHub <sysbot+gh@w3.org>
- Date: Tue, 15 Jan 2019 01:47:28 +0000
- To: public-css-archive@w3.org
The SVG specs are very vague as to what should be happening here, but I think what they're *supposed* to say is that the alphabetic baseline (a metric defined in the font file itself) is aligned to the alignment point you're specifying in the x and y attributes. In a correctly-developed font, that point will coincide exactly with the bottom of the capital T and lowercase x, and be slightly above the bottom of the lowercase e (due to optical alignment effects). Afaict, all those renderings are a bit off: that point should coincide exactly with the middle of the gray stroke. Variant of this testcase using Ahem: http://software.hixie.ch/utilities/js/live-dom-viewer/?<svg%20viewBox%3D"0%200%20200%20200"%20xmlns%3D"http%3A%2F%2Fwww.w3.org%2F2000%2Fsvg"%20font-family%3D"Arial"%20font-size%3D"64">%0A%20%20%20%20<path%20id%3D"crosshair"%20d%3D"M%2020%20100%20L%20180%20100%20M%20100%2020%20L%20100%20180"%20stroke%3D"gray"%20stroke-width%3D"0.5"%2F>%0A%20%20%20%20<text%20id%3D"text1"%20x%3D"120"%20y%3D"30"%20writing-mode%3D"tb"%20font-family%3D"Ahem">Épx<%2Ftext>%0A%20%20%20%20<rect%20id%3D"frame"%20x%3D"1"%20y%3D"1"%20width%3D"198"%20height%3D"198"%20fill%3D"none"%20stroke%3D"black"%2F>%0A<%2Fsvg> I think what needs to happen here is importing the testcase into WPT and filing bugs against all browsers. :( But thanks for the example and testcase! -- GitHub Notification of comment by fantasai Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3505#issuecomment-454236964 using your GitHub account
Received on Tuesday, 15 January 2019 01:47:29 UTC