svm: a metafile's text depends on fonts the browser does not have, and combining marks land in the wrong place
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 28/100
- Issue 类型
- 功能
- 描述清晰度
- 需要澄清
- 活跃度
- 冷清
- 技术栈
- cpp, html
调研方向
Reproduce the issue with translate "test/data/input/odr-private/odt/Vektoranalysis Zusammenfassung.odt" /tmp/va, then open /tmp/va/document.html in a browser without OpenSymbol. Read the SVM translation path and the existing internal/font machinery mentioned in the issue. The work is not yet defined: maintainers must choose documentation, supplied fonts, or geometry before implementation can be considered done.
由索引模型根据 Issue 内容生成。
描述
Split out of #772, which is closed. Not a regression — this predates the whole
#779–#793 stack and is unchanged by it.
Symptom
A metafile drawn by StarMath puts a vector arrow over a variable. In the
browser the arrow sits up and to the left of the letter it belongs to.
In odr-private/odt/Vektoranalysis Zusammenfassung.odt, 600 of its 1032
embedded metafiles are affected — 1022 arrows in one document.
What the translator emits
The arrow is U+20D7 COMBINING RIGHT ARROW ABOVE, written as its own <text>
at the position the metafile gives, exactly as the metafile draws it:
<text x="106" y="1085" style="font-family:OpenSymbol;font-size:423;">⃗</text>
<text x="106" y="1058" style="font-family:Times New Roman;font-size:423;">a</text>
That markup is correct, and renders correctly when OpenSymbol is
present. The arrow only goes astray when it is not.
Cause
A combining mark has zero advance and its outline is authored to the left of
the origin, so that it lands back over the character before it. StarMath
positions the glyph assuming OpenSymbol's own authoring. Every other font
implements U+20D7 as a proper combining mark — which is why it lands
somewhere else.
The font is the whole story. Measured, same markup, one font each:
| font | placement |
|---|---|
| OpenSymbol | correct, over the letter |
| Arial Unicode MS | correct |
| serif, sans-serif, Apple Symbols, STIX Two Math, Lucida Grande, Menlo, DejaVu Sans, Symbola, Segoe UI Symbol | all displaced up-and-left |
On macOS, LibreOffice's bundled fonts live inside the application bundle and
are not installed system-wide, so a browser never sees OpenSymbol even on a
machine that has LibreOffice.
What does not work
All measured in Chrome against the real OpenSymbol, not reasoned about:
- A generic fallback (
font-family:'OpenSymbol',serif) — no effect.
Browsers do per-glyph fallback for a missing codepoint regardless of the
stack. - Naming other symbol fonts — no effect, per the table above.
font-feature-settings: 'mark' 0, 'mkmk' 0— no effect, which tells us
the offset comes from the glyph outline and not from GPOS mark attachment.
There is no CSS property that reaches it.- A base character (
before the mark) — worse: the mark combines
with the space and the arrow disappears. - Merging the mark into the run of the letter it belongs to — worse: the
letter's font (Times New Roman) has noU+20D7, so it renders as tofu; and
forcing the mark to OpenSymbol with a nested<tspan>breaks the shaping
and puts the arrow beside the letter.
So there is nothing to fix in the markup. The lever is which font the browser
has.
Not vendoring the font
Embedding a subset of OpenSymbol via @font-face would fix it, and the
machinery exists (internal/font, cff/sfnt subsetting, already used for pdf).
We do not want to vendor the font, so this is recorded as the option that
was considered and declined, not as the plan.
What is left to decide
- Document it as a known limitation of svm output, which is honest and cheap:
the rendering is faithful only where the named fonts are installed, and
combining marks are the visible case rather than a special one. - Or let the embedder supply fonts, so an application that ships OpenSymbol
(the Android and iOS apps could) gets correct output while a bare browser
does not. - Or draw the mark ourselves as geometry for the handful of marks that matter,
which trades a font dependency for a positioning one — we would have to
decide the offset the font currently decides.
Reproducing
translate "test/data/input/odr-private/odt/Vektoranalysis Zusammenfassung.odt" /tmp/va
then open /tmp/va/document.html in a browser without OpenSymbol installed.
The formulas' vector arrows are displaced; installing OpenSymbol (or rendering
in LibreOffice, whose player is right) places them correctly.
- 主要语言
- C++
- 星标
- 41
- 派生
- 10
- 平均合并
- 12 小时 4 分钟
- 30 天内合并 PR
- 297
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
opendocument-app/OpenDocument.core 的其他 Issue
-
bug
难度 4/5 3-5 天 新手友好度 35/100
opendocument-app/OpenDocument.core#1211 ·
维护者通常 1 天内回复
-
bug
难度 3/5 1-2 天 新手友好度 42/100
opendocument-app/OpenDocument.core#1210 ·
维护者通常 1 天内回复
-
bug
难度 3/5 1-2 天 新手友好度 45/100
opendocument-app/OpenDocument.core#1209 ·
维护者通常 1 天内回复
-
bug
难度 4/5 3-5 天 新手友好度 38/100
opendocument-app/OpenDocument.core#1208 ·
维护者通常 1 天内回复
-
bug
难度 3/5 1-2 天 新手友好度 35/100
opendocument-app/OpenDocument.core#1207 ·
维护者通常 1 天内回复
查看 opendocument-app/OpenDocument.core 的全部 Issue
相似的 Issue
-
v9.6.0: CMake incorrectly enforces presence of libevdev可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭
难度 2/5 1-3 小时 新手友好度 67/100
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 65/100
mltframework/shotcut#1943 ·
维护者通常 1 天内回复
-
Rowan (2017) electron heating gives NaN for beta > beta_max; clip() then sets electrons to kel_min未关闭
难度 2/5 1-3 小时 新手友好度 72/100
parthenon-hpc-lab/kharma#213 · 1 条评论 ·
维护者通常 3 天内回复
-
enhancement
难度 2/5 1-3 小时 新手友好度 68/100
metasequoiaime/msime#9113 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 65/100
tone-3000/tone3000-plugin#257 · 1 条评论 ·
维护者通常 1 天内回复