14:56:02 RRSAgent has joined #manga-next 14:56:06 logging to https://www.w3.org/2024/09/25-manga-next-irc 14:56:06 RRSAgent, do not leave 14:56:07 RRSAgent, make logs public 14:56:08 Meeting: Next actions for digital manga and comics 14:56:08 Chair: Shinya Takami, Hadrien Gardeur 14:56:08 Agenda: https://github.com/w3c/tpac2024-breakouts/issues/58 14:56:08 Zakim has joined #manga-next 14:56:09 Zakim, clear agenda 14:56:09 agenda cleared 14:56:09 Zakim, agenda+ Pick a scribe 14:56:11 agendum 1 added 14:56:11 Zakim, agenda+ Reminders: code of conduct, health policies, recorded session policy 14:56:11 agendum 2 added 14:56:11 Zakim, agenda+ Goal of this session 14:56:12 agendum 3 added 14:56:12 Zakim, agenda+ Discussion 14:56:12 agendum 4 added 14:56:12 Zakim, agenda+ Next steps / where discussion continues 14:56:14 agendum 5 added 14:56:14 tpac-breakout-bot has left #manga-next 16:30:19 JackieFei has joined #manga-next 16:55:14 JackieFei has joined #manga-next 18:07:45 JackieFei has joined #manga-next 18:12:48 JackieFei has joined #manga-next 19:56:06 davidhall has joined #manga-next 20:06:59 shawn7 has joined #manga-next 20:07:53 shiestyle has joined #manga-next 20:08:04 JackieFei has joined #manga-next 20:10:10 toshiakikoike has joined #manga-next 20:11:40 zakim, start the meeting 20:11:40 RRSAgent, make logs Public 20:11:41 please title this meeting ("meeting: ..."), shiestyle 20:11:55 Meeting: Next actions for digital manga and comics 20:12:14 Chair: Shinya Takami 20:12:20 Chair: Hadrien Gardeur 20:12:41 Agenda: https://docs.google.com/presentation/d/1vep11WWx_gkRgZVaQmd6Rg_xa6mQiqoi/pub 20:13:00 rrsagent, make log public 20:13:08 Hadrien has joined #manga-next 20:13:10 rrsagent, draft minutes 20:13:12 I have made the request to generate https://www.w3.org/2024/09/25-manga-next-minutes.html shiestyle 20:13:20 present+ 20:13:23 CharlesL has joined #manga-next 20:13:31 present+ 20:13:32 present+ 20:13:42 rrsagent, make log public 20:14:05 present+ ShawnLawtonHenry(part) 20:14:10 Chair: Shinya Takami, Hadrien Gardeur 20:14:15 MasakazuKitahara has joined #manga-next 20:14:30 present+ 20:14:48 Tommy has joined #manga-next 20:15:43 present+ 20:16:01 Willy has joined #manga-next 20:16:43 wendyreid has joined #manga-next 20:16:49 present+ 20:17:01 present+ 20:17:14 ikkwong has joined #manga-next 20:17:19 present+ 20:17:25 duga has joined #manga-next 20:17:34 present+ 20:17:50 ivan has joined #manga-next 20:18:08 present+ 20:18:11 jkamata has joined #manga-next 20:18:18 scribe+ 20:18:20 present+ 20:18:39 hiroki_endo has joined #manga-next 20:18:40 hgo has joined #manga-next 20:18:49 shiestyle: This session is about next actions for digital manga and comics 20:18:53 mgarrish has joined #manga-next 20:19:01 ... I am Shinya Takami from Kadokawa, and joined by Hadrien Gardeur from EDR Lab 20:19:10 Hadrien: I've been interested in this topic for a long time 20:19:20 ... done my best to gather information from European publishers 20:19:36 ... hopefully this session will ba good mix of feedback from Japan, Europe, and more 20:19:39 kevin has joined #manga-next 20:19:53 shiestyle: We're going to stsrt with an overview of the situation in Japan, Europe, and NA 20:20:00 ... then next steps for manga and comics 20:20:04 ... four subtopics 20:20:15 ... and then we will finish with any other business 20:20:17 ... let's start 20:20:33 [Shinya shares slides] 20:20:46 s/stsrt/start/ 20:21:20 LaurentLM has joined #manga-next 20:21:27 Ozawa has joined #manga-next 20:21:51 shiestyle: The first presentation is from me, about EPUB in Japan 20:21:59 ... [slide 1] ebook market in Japan 20:22:12 ... 90% of the ebook market share is manga and comics 20:22:32 ... $4bn USD in comics, 0.5b USD for everything else 20:22:45 ... about 10% of the comics sold use the scrolled format 20:22:53 ... it's not a small market for the Japanese industry 20:23:07 ... the EPUB3 format is used mostly in Japan 20:23:17 ... SVG wrapped image is used, and other formats 20:23:33 ... many reading systems use only the images extracted from files 20:23:41 ... and do not render the XHTML extracted from files 20:24:00 ... SVG wrapped images to ensure images are scaled to the side of the screen 20:24:20 s/side/size/ 20:24:37 shiestyle: [example on screen] we use SVG to declare the image 20:24:54 ... in current web browsers, our XHTML is not rendered properly 20:25:00 ... example on the screen is from Chrome 20:25:15 ... differences in expected behaviour from browsers vs what we need 20:25:43 ... the current web technology and reading systems diverge 20:26:19 ... Japanese style only works on reading systems in Japan, XHTML and SVG are not necessary for reading systems, we only need the images 20:26:36 ... we can reduce the size of the files by eliminating the wrappers 20:26:49 ... if we don't use XHTML we lose accessibility, and image map 20:26:59 ... we use image maps in FXL for manga content in japan 20:27:18 ... If we don't use XHTML/SVG, we'll lose the image map features 20:27:30 swjoo has joined #manga-next 20:27:38 q+ 20:27:39 ... that is the situation in Japan right now 20:27:45 ack duga 20:27:50 q+ 20:28:00 duga: Question, you mentioned that markup is doubling the size of the files? 20:28:14 Hadrien: Doublingthe number of resources, not file size 20:28:23 shiestyle: Doubling the number of files in the EPUB 20:28:27 q+ 20:28:31 q+ 20:28:34 ack davidhall 20:28:44 davidhall: We seem to be using a few terms interchangeably 20:28:51 ... digital manga, comics, webtooms 20:29:01 ... I have a different idea in my head of that those are 20:29:08 florian_webirc has joined #manga-next 20:29:11 hiroshige has joined #manga-next 20:29:14 ... for me manga/comics are the same, paginated FXL content 20:29:24 ... webtoons is variable-height and scrolled 20:29:29 q+ 20:29:33 ... we may use the same solutions but there are differences 20:29:40 q? 20:29:50 ack wendyreid 20:29:52 shiestyle: We can discusss webtoons later 20:30:13 q? 20:30:30 wendyreid: What is the issue with the number of resources listed in the OPF? 20:30:40 shiestyle: Difference of cost to produce the EPUB files 20:30:48 ... there's complexity 20:30:52 ack kevin 20:30:59 kevin: Thanks, interested in the problem in slide 5 20:31:03 ... trying to work out what the problem is 20:31:06 garykac has joined #manga-next 20:31:35 q+ 20:31:35 ... from an accessibility perspective, more flexibility in layout options and settings would be more important than the image appearance in the viewport size 20:31:38 ... want to understand the nature of the problem presented 20:31:43 ? 20:31:46 q+ 20:31:50 ack Hadrien 20:32:01 Hadrien: I can try answering 20:32:17 ... one of the reasons bitmaps were wrapped in SVG was to achieve the accepted behaviour 20:32:26 ... it was at one point required to get the dimensions contained 20:32:34 q+ 20:32:43 ... it's not necessarily needed, it's a practice that has been followed, even though the historical reasons are not there 20:32:53 ... to reply to David, it is confusing the different formats 20:33:05 ... some is cultural, different terms and cultural expression in the media 20:33:13 ... Korean, Japanese traditions 20:33:23 ... it can be confusing, we are just trying to point out the variations 20:33:28 ... and some have variations in design 20:33:45 ack CharlesL 20:33:49 ... for example the requirement for bandes desinees are different, like resolution 20:34:14 CharlesL: For SVG wrapped bitmap images, is there any thought from publishers to use SVG directly, to benefit low-vision users in zoom? 20:34:22 shiestyle: No, we use it to fit to the screen 20:34:38 Hadrien: I'll mention this relating to Europe, there are some SVG use cases for other reasons 20:34:46 ack duga 20:34:46 q+ does XHTML play key role here? 20:34:55 duga: Wanted to come back to slide 5 20:35:00 ... not sure why this is a problem 20:35:11 ... rendering in the browser is different from reading system, yes it is 20:35:14 q+ 20:35:18 ... the reading system has EPUB to tell it what to do 20:35:27 ... the browser won't render EPUB as it is to be rendered 20:35:30 ... why is this a problem? 20:35:40 shiestyle: Many reading systems use browsers as their engines 20:35:51 ... we need to customize the reading sytems to make this work 20:36:01 duga: This is what HTML gives you, the viewport 20:36:16 ... yes, for instance, Play Books uses the webview to display the content 20:36:29 ... but we display it as a formatted EPUB, using web engines 20:36:34 ... regardless of browser 20:36:41 shiestyle: Depends on the reading system 20:36:45 ? 20:36:49 duga: There is a spec to follow 20:36:59 q? 20:37:06 q- 20:37:06 ack LaurentLM 20:37:07 Hadrien: Let's move to Daihei's presentation 20:37:40 hiroshige: How does the XHTML part play a role here? 20:37:54 ... do we need to keep it? 20:38:01 shiestyle: It's used by the EPUB format 20:38:52 [switching slides] 20:39:50 ack hiroshige 20:40:00 Daihei: I'm Daihei Shiohama of MediaDO international and a co-chair of the publishing business group 20:40:18 ... MediaDO is part of the Japanese market, and my part is based in the US digital publishing market 20:40:28 ... I'm going to talk to you about the US manga and comics market 20:40:39 ... manga dominates the comic and graphic novels market 20:40:59 ... in 2023, manga was about 49% of units 20:41:12 ... [stats on slides] 20:41:23 ... the US market is dominated by print book sales 20:41:57 ... the US manga market is projected to outpace the global manga market in growth 20:42:10 ... global market is valued at 13.7 billion USD 20:42:31 ... Japan, the US, and other regions will continue to grow 20:42:52 ... digital books market are not accurately reported right now 20:43:13 ... estimates are made, ebook sales are estimated at 10% of publisher sales 20:43:28 ... several publishers launched proprietary apps in 2022-2024 20:43:42 ... and several marketplace apps 20:43:56 ... manga specialized app launches in the US 20:44:06 ... ??? [which publishers?] 20:44:23 ... webtoons market is projected to be worth 7.63 billion USD in 2024 20:44:34 ... and reach 13.04 billion in 2032 20:44:39 ... webtoons is a huge market too 20:44:57 ... the top two webcomic platforms are owned by large asian companies, Naver and Kakao 20:45:00 hiroshige has joined #manga-next 20:45:09 ... different business models 20:45:26 ... print books are distributed and sold through different channels 20:45:36 ... stores, direct, physical and online stores, crowdfunding 20:46:17 ... manga is sold in Barnes and Noble, and ???? stores from Japan in the US 20:46:29 ... online retailers, subscription and a la carte sales 20:46:29 ????? = Kinokuniya 20:46:45 s/????/Kinokuniya/ 20:47:15 Daihei: Webcomics are primarily distributed through speciality apps like Webtoon 20:47:34 ... digital books are in EPUB 3 or PDF 20:47:55 ... different formats in different streams 20:48:44 Hadrien: Go quickly, to give a few numbers, in France comics and manga takes up about 16% of the market share 20:48:50 ... driven by large growth in manga 20:48:57 ... drop in 2023, but growth overall 20:49:08 ... comics have been driving growth in the book market in France 20:49:13 ... mainly print 20:49:21 ... digital about 506% 20:49:31 s/506%/5-6%/ 20:49:51 Hadrien: Webtoons is growing, driven from apps but small overall 20:50:05 ... production, for large publishers production is in-house and automated 20:50:20 ... different from what you see in EPUB production for reflowable content like novels 20:50:27 ... it's completely automated with bitmaps 20:50:39 ... big part is following the output from the automation 20:50:43 ... smaller publishers are different 20:50:56 ... unlike japan, there is no standard style 20:51:09 ... some publishers do bitmaps in XHTML, others use SVG 20:51:23 ... other examples of the visuals in bitmap, but the text is part of the SVG 20:51:37 ... the text was selectable and available to screenreaders or TTS 20:51:42 Daihei has joined #manga-next 20:51:50 present+ 20:51:54 ... even seen bitmaps in spine with fallbacks to XHTML 20:52:19 ... it's uncommon, but specialized platforms don't care about XHTML/SVG as long as they can get to the bitmap content 20:52:27 ... the requirements are driven by large retailers 20:52:43 ... many publishers mention Apple, their requirements for resolution drive their output 20:52:45 hiroshige has joined #manga-next 20:52:58 ... happy to have maximum resolution improved, and influenced by that 20:53:12 ... something that comes up a lot is the European Accessibility Act 20:53:23 ... we've discussed this in the publishing maintenance working group 20:53:37 ... they are concerned with the lack of information about FXL accessibility 20:53:44 q? 20:54:04 Hadrien: I'll take us to the next topic 20:54:18 ... it's been 10 years since EPUB for comics became common 20:54:24 ... we now see what is working, what is not 20:54:35 ... in the context of a future revision of EPUB, we have an opportunity 20:54:48 ... concept of spread, spread placement 20:54:56 ... placement is considered useful to publishers 20:54:58 ... happy to have it 20:55:10 ... it's fairly well implemented in reading systems 20:55:17 ... at the spine level 20:55:25 ... for each resource in the book, you can align it 20:55:33 ... what we see is 2 patterns 20:55:42 ... production workflows with 0 use of this property 20:55:54 ... or another workflow where every resource has it 20:55:56 ... I've seen many 20:56:07 ... and we don't see cases where it's only partially used 20:56:16 ... page-spead-centre is a bit strange, but useful 20:56:27 ... it's useful as its aliased to spread:none 20:56:32 ... good to avoid having a spread 20:56:43 ... or for content creators to put entire spread in a single image 20:56:48 ... it's used for covers 20:56:59 ... it makes properties like rendition:spread redundant 20:57:10 ... there's a disconnect between what the spec says and usage 20:57:33 ... EPUB creators should use the page-spread properties when they want to ensure a spread 20:57:39 ... we don't see this in practice 20:57:51 ... the spec is advocating to use the properties sporadically 20:57:52 Rain has joined #manga-next 20:57:55 present+ 20:58:04 ... they are used all the time, or none of the time, because of workflows 20:58:18 ... when it's never used, authors expect the behaviours we see in apps like Apple Books 20:58:33 ... there's an expectation of a behaviour that is not clear in the spec 20:58:37 .... people seem happy and it's well-implemented 20:58:42 ... it's useful 20:59:01 ... there's another property, rendition-spread, for the entire publicatrion 20:59:20 ... have a value at the publication level that is overridden at the spine level 20:59:47 ... publishers use a template that uses "both" or "none", they hint at spread usage but it's not useful 20:59:58 ... another miss is that the values are unclear 21:00:17 ... auto is useless, landscape is weird 21:00:25 ... gives content creators the illusion of content 21:00:31 s/content/control/ 21:00:43 Hadrien: It's always the user that decides what is best for them 21:00:55 ... users view one page at a time 21:00:56 ... scrolled 21:01:06 ... there is a need for something different than what is needed in the spec 21:01:24 ... I think what is needed is region-based navigation 21:01:40 ... in comics, there are use cases where the reading order crosses the fold 21:01:47 ... or usage where you need to see the entire spread 21:01:56 ... there are elements that cross the fold 21:02:06 ... [example shown] 21:02:17 q? 21:02:21 ... what is needed is the ability to display a spread when it is essential to the reading experience 21:02:26 ... important to accessibility 21:02:35 ... and let reading systems do smarter auto modes 21:02:45 florian_webirc has joined #manga-next 21:03:03 ... there are readers that scroll, but when you encounter a specific spread, it changes the interaction to side-to-side scroll 21:03:06 q+ 21:03:11 ... the expression of information we do not currently have 21:03:25 ... spread is hit and miss right now 21:03:40 duga: You talked about the illusion of control 21:03:49 ack duga 21:04:05 ... I believe PLay Books used to start with publisher said, but it was not beneficial to the user 21:04:13 ... so we deferred to the usrr 21:04:26 ... and in your example, that's a case where they needed to go together 21:04:46 ... how do we make something that works here, publishers can tell us when it is meaningful 21:04:55 ... how do we get the information when we really do need it 21:05:05 Hadrien: I don't think we need publication-level spread settings 21:05:10 ... this is where abuse most often happens 21:05:17 ... only allow at the spine 21:05:23 ... and we should change the values 21:05:31 ... none is handled by centre for example 21:05:36 q+ 21:05:42 ... we need more a boolean, "this spread matters" 21:05:51 ... if we had that, we could have modes that respect that 21:06:02 ... but still work with user preference 21:06:13 ... different information that is simplified to drive better defaults 21:06:24 ... like if you detect it's used everywhere 21:06:35 ... if we head off the abuse opportunities 21:06:35 ack Rain 21:06:47 Rain: I'm curious about anchoring on the spread as a publisher input 21:07:03 ... I'm not sure how the spread is useful, if someone is zoomed in, the spread could be problematic 21:07:15 ... I'm wondering if anchoring on the spread, you anchor on the cells 21:07:20 ... "here's the cell of meaning" 21:07:29 ... spread is outdated 21:07:44 fantasai has joined #manga-next 21:07:45 Hadrien: I fully agree, and I can touch on it later 21:07:46 q+ 21:07:52 I have made the request to generate https://www.w3.org/2024/09/25-manga-next-minutes.html fantasai 21:08:00 q- 21:08:01 shiestyle: Let's move to bitmap and accessibility 21:08:19 hober has joined #manga-next 21:08:23 present+ 21:08:50 Hadrien: What we see in practice is that HTML/SVG as containers is not often used 21:08:54 ... we've seen image maps 21:09:02 ... examples where text is in the SVG 21:09:10 ... vast majority is a bitmap 21:09:17 ... and container is there because it must be 21:09:36 ... for specilzed reading systems that just rasterize everything 21:09:50 ... SVG/XHTML was done for good reason 21:10:00 ... but it's not moving the needle for accessibility 21:10:20 ... one reason, unlike the rest of the EPUB ecosystem, there are a lot of specialized comics readers 21:10:28 ... and they just display comics 21:10:45 ... I think we cannot talk about that without talking about accessibility 21:11:08 ... what we see right now in terms of EPUB capabilities, all we can do is create a script per page 21:11:15 ... few EPUB out there that do it 21:11:30 ... the content creator creates a script, they provide that as a description of the image 21:11:37 ... and even that is inconsistent 21:11:48 ... what do we need to create accessible comics? 21:11:58 ... we need reading order at the fragment level 21:12:06 ... fragment of an image, of multiple images 21:12:14 ... useful to identify a unit of content 21:12:17 ... like a panel 21:12:18 present+ 21:12:19 q+ 21:12:27 ... another need is to have transcription of each fragment 21:12:33 q+ 21:12:40 ... in comics there are a lot of captions, speech, sound effects 21:12:46 ... it is often handwritten 21:12:58 ... having it as real text is needed 21:13:02 ... image description also needed at the fragment level 21:13:20 ... there is a lot of content within a page 21:13:30 ... we need to identify different areas 21:13:43 ... if there is a panel, and the speech bubble, you need to know who is speaking and what 21:13:49 ... there is a lot of visual information in comics 21:14:07 ... how they are speaking, lots of contextual information communicated through visual means 21:14:22 ... how to make all that conform to accessibility act requirements 21:14:48 ... if we had a method, we could do more to serve readers, resize text, change fonts, speak aloud 21:14:56 ... [gives example] 21:15:40 ... [example of serialization of this] 21:15:52 q? 21:16:07 ... we identify a region, role, character, description, children 21:16:15 ... there are other units of content 21:16:20 ... speech versus shouting 21:16:24 ... just an example 21:16:40 q+ 21:16:59 garykac: So I had a question about ordering and serialization 21:17:02 ack garykac 21:17:17 ... sound effects may not be in order, but things like furigana that need to be in order 21:17:27 ... in the example, how would I select a section or region of text 21:17:38 ... I want to select at the character level 21:17:46 q+ 21:17:48 ... doesn't seem useful for making the text accessible 21:17:58 Hadrien: I think you could define sub-regions 21:18:06 ... even in the context of adapted content 21:18:10 zakim, close the queue 21:18:10 ok, shiestyle, the speaker queue is closed 21:18:11 ... no one is doing this 21:18:21 ... at the granular level, it's complex 21:18:27 q? 21:19:04 shiestyle: For accessibility, as a publisher, it's not easy to prepare the pop-up text 21:19:13 ... the description for each image is hard to prepare 21:19:25 ack shiestyle 21:19:25 ... XHTML or SVG for EPUB is not valid in Japan for now 21:19:30 ack me 21:19:48 Hadrien: Publishers are concerned about the cost, especially in markets where comics are the fraction 21:19:49 ack ivan 21:20:09 ivan: Very practical question, we had the working group call 21:20:13 ... we discussed areas to explore 21:20:35 ... do you think what you described today, or part, is on the maturity level to be considered for EPUB 3 or needs more? 21:20:39 ... where are we with this? 21:20:55 Hadrien: I think the spread stuff is ready to discuss, pragmatic revision 21:21:04 ... if we're talking about accessible comics, it's very immature 21:21:10 ... at best, this is a CG project 21:21:16 ... way too early for the WG 21:22:19 Kamata: As a publisher, there was a significant cost to producing a frame-by-frame content view 21:22:19 ack florian_webirc 21:22:50 florian_webirc: To get the full benefits of what garykac described, it seems to be is to realize is to not enrich the meta information 21:22:55 ... but to have the text on the page 21:23:08 ... the cost of producing such a thing, and the workflow is considerable 21:23:17 ... vs text as markup on the page 21:23:29 ... there is considerations of changes to the workflow 21:23:44 q+ 21:23:45 garykac: My assumption is its not possible due to how the content is produced, fonts, workflows, etc 21:23:57 ... my assumption was it was not possible, but maybe? 21:24:21 florian_webirc: I'm uncertain we can realize the benefits of what you describe without doing the work to put the text on the page 21:24:53 duga: I saw a Japanese publisher show me a folio of the letterers and the fonts they developed for each one 21:25:08 ... perfectly reproduced the style of each letterer with a font 21:25:45 rrsagent, please draft minutes 21:25:46 I have made the request to generate https://www.w3.org/2024/09/25-manga-next-minutes.html wendyreid 21:29:15 zakim, end the meeting 21:29:15 As of this point the attendees have been Hadrien, davidhall, CharlesL, ShawnLawtonHenry(part), shiestyle, MasakazuKitahara, wendyreid, toshiakikoike, ikkwong, duga, ivan, jkamata, 21:29:18 ... Daihei, Rain, hober, garykac 21:29:18 RRSAgent, please draft minutes 21:29:19 I have made the request to generate https://www.w3.org/2024/09/25-manga-next-minutes.html Zakim 21:29:24 I am happy to have been of service, shiestyle; please remember to excuse RRSAgent. Goodbye 21:29:24 Zakim has left #manga-next 21:31:15 \ 21:36:03 CharlesL has joined #manga-next 21:44:51 wendyreid has left #manga-next 21:49:59 kevin has left #manga-next 22:18:26 shiestyle has joined #manga-next 22:19:24 Agenda slides on W3C: https://lists.w3.org/Archives/Public/www-archive/2024Sep/att-0010/W3C_Breakout_Session_at_TPAC_2024__Next_actions_for_digital_manga_and_comics_-_2024-09-25.pptx 23:22:32 shiestyle8 has joined #manga-next 23:23:33 shiestyle8 has left #manga-next