<Liisamk_> Daihei: thanks for joining, pleased at the outcome of the TPAC meetings and follow up on WOT discussion
<Liisamk_> ...how WOT relates to publishing business
<Liisamk_> ...each IOT (smart car, smart house) might have it’s own silo
<Liisamk_> ...WOT standard to integrate these businesses for lifestyles
<Liisamk_> ...available everywhere
liisamk: I can scribe if you don’t mind
<Liisamk_> ...aoolications interconnect with WOT to all the devices and tech silos
<Liisamk_> ...they need content
<Liisamk_> ...books go into movies, news, and then into a variety of verticals
<Liisamk_> ...content use cases for books and audiobooks, via smart speakers or on other devices
<Liisamk_> ...could include synced video or audio or VR for books
<Liisamk_> ...from paper to digital devices and could expand beyond use of smartphones to other great readin experiences
<Liisamk_> ...give intro to what might be possible in the future
<Liisamk_> ...will talk with WOT people about use cases before end of year and want to discuss potential use cases
<Daihei> Liisa: It is difficult to think about dividing one content into short segments.
<Daihei> Liisa: it will be a different experience from the regular book reading experiences
<liisamk> Zhengxu: could bring some use cases to CG as things evolve
<liisamk> Daihei: Could bring use cases discussed from WOT context and then maybe discuss with both PBG for business case and CG
<liisamk> ...for the technical cases
<Daihei> Liisa: At TPAC, Zheng and Daniel talked about the reading system issues.
<Daihei> Liisa: I want to bring out to our community as to what the priorities are for and what people are looking for, instead of just focusing broken items which are the current interests
<Daihei> Zheng: Exactly, what we discussed was that. The industry should discuss the reading experiences but also lots of other tech and focus should be discussed.
<Daihei> We can discuss this at potentially a task force
<Daihei> Liisa: In Japan, how much of digital books, audio books, on top of the print books users already purchased could be collected
<liisamk> jkamata present+
<liisamk> zhengxu present+
<liisamk> Murata present+
<Daihei> Sorry, "collections" above is supposed to be corrections
<liisamk> Shinya: reading systems that have already been implemented and not as much lately
<liisamk> ...corrections in print are size of letters changed, tables of contents and indexes
shiestyle: the size of letters,
font change, toc is something ppl are looking for in digital
book
... not much new tech recently
jkamata: digitalize book itself
has good value in Japan
... connection cross different books might be very
interesting.
... (did not catch last part…)
... it has it’s value as archive
... so WOT might be a way to connect books, discovery for end
user
Daihei: move on to FXL
liisamk: we have been talking
about reflow and fxl before. I am trying to get some example
here
... (showing a cook book displaying on Kindle)
... can we put image to full screen? and make it looks close to
print page?
... right now we can see cropping on phone and visually
difference with print book
... it’s important the image and next text can be more
collaborate (closer) together?
... (using example of kids book)
... can we put some of image as part of reflow and bleeding out
from current reflowable layout?
y-nagao: we are working with web
media
... the current displaying example of book is slightly
different from normal web media
... the anchor link example might be very difficult base on our
experience
... considering coding cost
... will need publisher to catch up
Daihei: next move on to fonts and ebooks
shiestyle: in Japan we are using
Japanese fonts which includes messiive amount of glyphs
... there is not any useful free font
... one concern we have right now is it seems Apple will force
integration from UIWebView to WKWebView
... current UIWebView has feature of customized font for
JP
... but WKWebView does not have this feature
... if iOS can not let publisher use customized font then we
can not use the same font for Android app
... we found some potential way to hack in iOS but it might not
be a good way
... we require Apple to let us use customized font
... because in Japan some vender really want to use customized
(licensed) font.
Daihei: Question to liisamk. do you think this needs to be discussed in some community
liisamk: I don’t think we have
best practice for font embedding yet.
... this might be some interesting for CG
... Apple is pushing woff
... and license is quite expensive
Daihei: this is kind of common concern in EU or if this is issue in Japan specifically?
liisamk: this needs to start from Japan as initialized issue
shiestyle: we don’t want to embed
font to book since font file is huge for Japan.
... so, yes, we can use embedded font in epub but it’s not
ideal for us
liisamk: so it’s unique issue in Japan
<liisamk> zhenxu: CG getting going and there are unique problems to solve for Asia
<MURATA> The Japanese DAISY consortium has submitted ruby discoverability requirements to the A11Y taskforce. Will submit two more. And will make proposal for Japanese A11Y metadata.
<liisamk> ...setting up a meeting for the timezone soon
thanks
This is scribe.perl Revision of Date Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00) Succeeded: s/other reading system people/Daniel/g Present: liisamk shiestyle Daihei No ScribeNick specified. Guessing ScribeNick: zhengxu Inferring Scribes: zhengxu WARNING: Date not understood: 10/11 November 2020 WARNING: No date found! Assuming today. (Hint: Specify the W3C IRC log URL, and the date will be determined from that.) Or specify the date like this: <dbooth> Date: 12 Sep 2002 People with action items: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option. WARNING: IRC log location not specified! (You can ignore this warning if you do not want the generated minutes to contain a link to the original IRC log.)[End of scribe.perl diagnostic output]