23:50:34 RRSAgent has joined #epub-locators 23:50:34 logging to https://www.w3.org/2021/06/16-epub-locators-irc 23:50:36 RRSAgent, make logs Public 23:50:38 please title this meeting ("meeting: ..."), wendyreid 23:50:47 meeting: Virtual Locators TF Telco June 16, 2021 23:50:55 date: 2021-06-16 23:50:59 chair: wendyreid 23:51:48 dauwhe has joined #epub-locators 23:57:36 toshiakikoike has joined #epub-locators 23:59:17 present+ 23:59:59 present+ 00:00:26 BenSchroeter has joined #epub-locators 00:01:46 pilarw2000 has joined #epub-locators 00:01:55 present+ 00:02:02 present+ 00:02:07 shiestyle has joined #epub-locators 00:02:23 present+ 00:02:59 dlazin has joined #epub-locators 00:03:01 present+ 00:03:13 pilarw2000 is scribe 00:03:51 q 00:04:26 Wendy: summarizing last meeting and noting we are unclear on Japanese reading systems and how they are handling page lists and lack thereof in ebooks. Do they want page #s? 00:04:30 scribe+ pilarw2000 00:04:38 VOYAGER'S Reading System converts from EPUB to internal format, and to identify the location, use both the number of charactors from the beginning and text strings around the location, then if the contents modify a little, Reading System can trace the original location. 00:05:10 And about page number, our RS renders all pages when openning the book, resizing window, and resizing font size, then has the index of pages. 00:05:40 q+ 00:06:11 wendy: do pages get rendered again when font changes? 00:06:29 ack pilarw 00:07:01 pilarw: I was asking about the use of the term index, how do you handle ebooks that have an index with listing of page numbers or locations 00:10:26 koike: sharing screenshot from reading system, position in text (from beginning) is used for indicating location. 00:12:08 wendy: is this unique? or is it common to other reading systems? 00:12:36 shinya: Voyager is doing its own thing, and other vendors in Japan seem to have each their own system. 00:14:08 wendy: bookmarking systems all rely on span tags 00:15:51 https://w3c.github.io/epub-specs/epub33/locators/ 00:16:09 https://github.com/w3c/epub-specs/blob/main/epub33/locators/index.html 00:16:10 dan: we can start drafting a note, which will help us focus and move forward. the actual algorithm itself is essentially an appendix. 00:16:29 link above is the draft, per wendy 00:18:18 dan: sample note we can follow? 00:18:41 https://w3c.github.io/epub-specs/epub33/multi-rend/ 00:18:57 example notes at links from wendy 00:20:26 wendy: similar style to specs, with supportive text, more than usual 00:20:51 wendy: will be good to say why current options don't work 00:21:54 wendy: review will not happen, rigor will apply should it be deemed acceptable to go ahead. 00:22:53 q+ 00:23:15 ack pilarw 00:23:40 dauwhe has joined #epub-locators 00:23:41 pilarw: My question was about the abstract, it doesn't seem clear 00:26:03 q+ 00:26:09 ack BenSchroeter 00:26:23 wendy: common writing program such as Google Docs might be appropriate 00:30:24 dan: we will ask page lists be included. algorithm for figuring alternative locators is secondary. 00:34:09 wendy: google and Adobe have similar approaches for designating where text is in an epub. readium does similar, compressed though. 00:34:40 wendy: "adobe page numbers" 00:35:52 wendy: internationalization group should be first reviewers of whatever we draft. 00:38:07 wendy: fixed-layout has page numbers, page list, but we should consider it as well 00:38:14 dauwhe has joined #epub-locators 00:38:38 dan: let's put in outline 00:39:45 https://docs.google.com/document/d/11GypOjE9xOTaINATl5bxVIA3Mc9jzNBGCr6GT_KNaQ4/edit?usp=sharing 00:41:49 ben: MobileRead wiki discussed all this, but it way out of date 00:42:56 q+ 00:43:01 ack BenSchroeter 00:46:03 q+ 00:46:47 ack pilarw 00:47:02 pilarw: 2 things, being a large number can interfere with index entires 00:47:12 ... readers could get frustrated 00:47:21 ... if the page they're looking for is many "screens" 00:47:28 q+ 00:47:34 ... phrasing of "absolute page numbers" 00:47:47 ... we're talking about a page number that doesn't change that's available to readers 00:47:54 s/entires/entries/ 00:47:56 ack BenSchroeter 00:51:44 ben: structured texts are cool 00:53:37 wendy: homework is to contribute to the draft note 00:58:05 zakim, end meeting 00:58:05 As of this point the attendees have been wendyreid, toshiakikoike, pilarw, BenSchroeter, shiestyle, dlazin 00:58:07 RRSAgent, please draft minutes 00:58:07 I have made the request to generate https://www.w3.org/2021/06/16-epub-locators-minutes.html Zakim 00:58:10 rrsagent, make logs public 00:58:11 I am happy to have been of service, wendyreid; please remember to excuse RRSAgent. Goodbye 00:58:15 Zakim has left #epub-locators 02:08:57 dauwhe has joined #epub-locators 02:13:12 dauwhe_ has joined #epub-locators 02:54:31 dauwhe has joined #epub-locators 03:46:35 dauwhe has joined #epub-locators 04:20:55 dauwhe has joined #epub-locators 06:09:06 dauwhe has joined #epub-locators 06:41:07 dauwhe has joined #epub-locators 08:05:21 dauwhe has joined #epub-locators 08:43:16 dauwhe has joined #epub-locators 09:21:50 dauwhe has joined #epub-locators 09:59:13 dauwhe has joined #epub-locators 10:40:01 dauwhe has joined #epub-locators 10:56:38 ivan has joined #epub-locators 11:16:13 dauwhe has joined #epub-locators 11:33:30 dauwhe has joined #epub-locators 11:45:01 dauwhe has joined #epub-locators 12:15:32 dauwhe has joined #epub-locators 12:35:46 dauwhe has joined #epub-locators