[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#63434: 29.0.60; eww does not handle properly ruby/rt elements (e.g.
From: |
Juri Linkov |
Subject: |
bug#63434: 29.0.60; eww does not handle properly ruby/rt elements (e.g. Japanese furigana) |
Date: |
Tue, 16 May 2023 19:49:34 +0300 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/30.0.50 (x86_64-pc-linux-gnu) |
[Cc'ed to debbugs to keep the bug report actionable]
>>> eww does not properly support the ruby/rt elements in HTML.
>>
>> Shouldn't the fallback element <rp> be used for browsers without ruby
>> support?
>>
>> https://developer.mozilla.org/en-US/docs/Web/HTML/Element/rp#without_ruby_support
>
> I think the ideal way would be to have a variable that configures the
> behaviour.
>
> In theory, the ruby is there to provide extra information to help with
> readability. But it only works if the reading medium provides support
> for placing the rt above the ruby.
>
> The simple solution would be to have a variable that:
>
> - when false, ignores the rt.
> - when true, renders it (using the fallback element if exists).
> - Otherwise, if it is a two characters string, the first char is
> used to open the ruby and the second to close it.
I agree. When customized to two characters, it could behave
as if the fallback element existed.