feat: a reading can be printed over its base text
Ruby, as both products' phonetic guide writes it: one element holding a base and its reading, so the editor keeps it as one inline atom and the browser sets it as a real <ruby>. ODF gets <text:ruby> plus a minted ruby-family style (centred, above — probed: LibreOffice writes that style back unchanged); Word a <w:ruby> run from a post-pack pass, the package having none. Both legs verified through a LibreOffice re-save, our .docx to .odt included.
This commit is contained in:
1 parent
405b175e49
commit
20e6dcad0e
17 files changed
+405
-6
No files matched your search
@@ -184,6 +184,16 @@
|
||||
background: rgba(255, 145, 0, 0.8);
|
||||
}
|
||||
|
||||
/* A ruby annotation (ruby.ts). The reading sits above its base at half its size,
|
||||
which is what both word processors print and what `w:hps` says. */
|
||||
.paper .tiptap ruby {
|
||||
ruby-position: over;
|
||||
}
|
||||
.paper .tiptap ruby rt {
|
||||
font-size: 0.5em;
|
||||
line-height: 1;
|
||||
}
|
||||
|
||||
/* The word being offered (wordCompletion.ts): after the caret, in the text's own
|
||||
font, greyed — it is not in the document until Enter takes it. */
|
||||
.paper .tiptap .word-completion {
|
||||
|
||||
Reference in new issue
Block a user