This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
blog:2021:the_case_for_furigana [2021/11/08 17:52] – created admin | blog:2021:the_case_for_furigana [2021/11/08 18:11] (current) – admin | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== The Case for Furigana ====== | ====== The Case for Furigana ====== | ||
- | This is largely a rewriting of the original case I lifted for the use of ruby / [[wp> | + | This is largely a rewriting of the original case I lifted for the use of [[wp> |
The idea is, English is good at taking stuff from other languages. Why not take then from East Asian languages the concept of annotations to enhance pronunciation, | The idea is, English is good at taking stuff from other languages. Why not take then from East Asian languages the concept of annotations to enhance pronunciation, | ||
- | |||
- | ---- | ||
===== FYC: Support Furigana Annotations ===== | ===== FYC: Support Furigana Annotations ===== | ||
Line 30: | Line 28: | ||
< | < | ||
</ | </ | ||
+ | |||
+ | Strangely enough, on AO3 (//Archive of Our Own//) these tags already work — on the drafting views. Once you reload a draft or once you post to published work however, not only are the ruby elements lost but their semantic separation from the surrounding content as well; I figure out there is some sort of bug about it, so I've sent a bug report / feature request to AO3 dated 2021-10-25. Let's see what happens. | ||
The implementation of ruby in BBCode compatible forums is also quite simple and could be done in one of at least two alternatives that hereby I introduce: | The implementation of ruby in BBCode compatible forums is also quite simple and could be done in one of at least two alternatives that hereby I introduce: |
Hosting provided by the tropi.us community.