Meeting minutes
Discussion for scrolled comics
invite RSSAgent pm-dc
invite RSSAgent
<shiestyle> https://
shiestyle: presenting slides for context. we discussed scrolled comics since long time. We have Apple and Amazon behavior and Hadrien proposal.
shiestyle: Japanese and Taiwan communities feedback show no strong opposition.
Hadrien: interesting that the feedback mentions scrolls not being a layout but a behavior. I agree in general, but in the context of webtoon, the content is often formatted to be scrolled, and won't render well if paginated.
Dale_Rogers: there is a difference between ignoring and trowing an error. How reading systems reacts here?
Hadrien: usually it's ignored if not supported.
Hadrien: for a RS, whatever we do, there will be work to support those contents.
shiestyle: the current way is supported by Apple and Amazon. I am not sure how long it will take to have support for the new value.
LaurentLM: because of the missing value, historically, it has been ignored.
LaurentLM: there will probably be a need for a RS rule if we want adoption.
Hadrien: Shinya created good examples, we can use them to test.
toshiakikoike: we don't use OPF metadata.
Dale_Rogers: i would love to see examples.
<Hadrien> https://
Hadrien: there are some on kadokawa website. There's also a gist. I would see ho to zip those and add them to an issue somewhere so people can check.
<Hadrien> Full proposal from 2024: https://
Hadrien: I suggest we work on a new proposal to get consensus.
Hadrien: this would combine a New feature and an update for compatibility. The same path we went thru when we discussed fixed layout.
shiestyle: agree. We have a proposal, we need feedback from Apple and Amazon.
LaurentLM: we can safely push as there is a fallback to support what is done by them. As it is, we won't break anything.
Hadrien: agree, there no reason for opposition here, it's win win.
shiestyle: so we can go to the WG with this proposal. I will write an explanation of it.
Hadrien: since we have time left, i suggest we discuss a second subject: referencing images.
referencing images
Hadrien: comics are images. Can we reference them in the spine so we don't need to open the HTML? I think it would improve production, maintenance and reading. And no change to the spec is needed.
LaurentLM: this one is more impactful, the RS must accepts html or svg. If we add images, that's possible with fallbacks. On EDRLab reading systems it's ok, we can get this, and that will improve the experience. I don't know for other RS.
shiestyle: we have dedicated RS for comics, they ingest images, to do that they extract them from HTML now, but they don't keep anything apart from images.
LaurentLM: accessability of comics should not be done as big alt text, it's not a suficient way, it should be done with guided navigation. So referencing images instead of HTML should not affect accessibility.
Hadrien: in the spine it's image first and HTML as feedback.
toshiakikoike: in manga we have TOC, for that it is usefull to have HTML. There's also image style used with HTML.
Hadrien: there's a change if you have a table of content in the content, I've seen ones in SVG. I understand that manga have more appeal(?) than webtoon. We can push something only for webtoon and explore more for manga.
shiestyle: do we have consensus to go forward?
shiestyle: yes, so let's open a PR.
shiestyle: next call in next month