all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: dmg <dmg@turingmachine.org>
Cc: 63434@debbugs.gnu.org
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	[thread overview]
Message-ID: <86ilcsmh0h.fsf@mail.linkov.net> (raw)
In-Reply-To: <m21qjg50sp.fsf@turingmachine.org> (dmg@turingmachine.org's message of "Mon, 15 May 2023 21:55:46 -0700")

[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.





      parent reply	other threads:[~2023-05-16 16:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-11  2:56 bug#63434: 29.0.60; eww does not handle properly ruby/rt elements (e.g. Japanese furigana) dmg
2023-05-11  6:21 ` Juri Linkov
     [not found]   ` <m21qjg50sp.fsf@turingmachine.org>
2023-05-16 16:49     ` Juri Linkov [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86ilcsmh0h.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --cc=63434@debbugs.gnu.org \
    --cc=dmg@turingmachine.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.