19:28:53 RRSAgent has joined #ebook 19:28:53 logging to http://www.w3.org/2013/03/22-ebook-irc 19:28:58 Zakim has joined #ebook 19:29:05 zakim, this will be ebook 19:29:05 ivan, W3C_(eBookChair)3:00PM is already associated with an irc channel; use 'move ebook to here' if you mean to reassociate the channel 19:29:29 ??? 19:29:51 zakim, move ebook to here 19:29:52 ok, ivan; that matches W3C_(eBookChair)3:00PM 19:30:26 il y a qq. chose qui cloche 19:30:49 W3C_(eBookChair)3:00PM has been moved to #ebookchairs by ivan 19:32:13 zakim, this will be styl_ebook 19:32:13 ok, ivan; I see Styl_Ebook()4:00PM scheduled to start in 28 minutes 19:32:25 rrsagent, set log public 19:32:36 zakim, code? 19:32:36 the conference code is 32665 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), ivan 19:37:15 plinss has joined #ebook 19:41:23 liam has joined #ebook 19:46:55 hober has joined #ebook 19:51:12 mgylling has joined #ebook 19:56:47 Styl_Ebook()4:00PM has now started 19:56:49 Zakim, code ? 19:56:49 the conference code is 32665 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), glazou 19:56:55 + +81.46.647.aaaa 19:57:12 +??P1 19:57:16 Zakim, ??P1 is me 19:57:16 +glazou; got it 19:57:36 janina has joined #ebook 19:57:43 Zakim, aaaa is makoto-san 19:57:43 +makoto-san; got it 19:57:49 +??P4 19:57:53 +[Apple] 19:58:00 zakim, ??P4 is Janina 19:58:00 +Janina; got it 19:58:04 Zakim, Apple is me 19:58:05 +hober; got it 19:58:05 +Liam 19:58:41 +Ivan 19:58:47 plh has joined #ebook 19:59:17 Zakim, who is noisy? 19:59:28 glazou, listening for 10 seconds I heard sound from the following: makoto-san (18%) 20:00:23 +mgylling 20:00:25 +plinss 20:00:27 +Plh 20:00:32 stearns has joined #ebook 20:00:34 Bert_ has joined #ebook 20:00:37 + +33.6.48.38.aabb 20:00:47 duga has joined #ebook 20:00:49 jeff has joined #ebook 20:00:50 Zakim, aabb is Luc 20:00:50 +Luc; got it 20:00:58 -makoto-san 20:01:13 +Stearns 20:01:45 + +1.760.214.aacc 20:02:05 +Jeff 20:02:24 Zakim, aacc is duga 20:02:24 +duga; got it 20:03:05 +[IPcaller] 20:03:06 tmichel has joined #ebook 20:03:26 Zakim, [IPcaller] has makoto-san 20:03:26 +makoto-san; got it 20:03:31 +[IPcaller.a] 20:03:33 +[IPcaller.aa] 20:03:43 fantasai has joined #ebook 20:04:02 Zakim, [IPcaller].a has fantasai 20:04:02 sorry, glazou, I do not recognize a party named '[IPcaller].a' 20:04:10 r12a has joined #ebook 20:04:10 Zakim, [IPcaller] has fantasai 20:04:10 +fantasai; got it 20:04:22 Zakim, [IPcaller] has takeshi-san 20:04:22 +takeshi-san; got it 20:04:22 zakim, dial richard please 20:04:23 ok, r12a; the call is being made 20:04:24 +Richard 20:04:33 +??P15 20:04:52 Zakim, ??P15 is tmichel 20:04:52 +tmichel; got it 20:04:57 Zakim, who is here? 20:04:57 On the phone I see glazou, Janina, hober, Liam, Ivan, mgylling, plinss, Plh, Luc, Stearns, duga, Jeff, [IPcaller], [IPcaller.a], [IPcaller.aa], Richard, tmichel 20:04:58 zakim, who's here ? 20:05:01 [IPcaller] has takeshi-san 20:05:01 On IRC I see r12a, fantasai, tmichel, jeff, duga, Bert_, stearns, plh, janina, mgylling, hober, liam, plinss, Zakim, RRSAgent, ivan, glazou 20:05:01 On the phone I see glazou, Janina, hober, Liam, Ivan, mgylling, plinss, Plh, Luc, Stearns, duga, Jeff, [IPcaller], [IPcaller.a], [IPcaller.aa], Richard, tmichel 20:05:01 [IPcaller] has takeshi-san 20:05:02 On IRC I see r12a, fantasai, tmichel, jeff, duga, Bert_, stearns, plh, janina, mgylling, hober, liam, plinss, Zakim, RRSAgent, ivan, glazou 20:06:16 Scribe: fantasai 20:06:42 glazou: My name is Daniel Glazman. Am co-chair of CSSWG in W3C. Will be one co-chair for this telecon. Other is Markus Gylling 20:06:57 mgylling: I work in IDPF on Epub spec and also with DAISY consortium 20:07:02 glazou: Let's do intros 20:07:46 janina: Janina, will be fly on wall. Chair PF and will pay attention to a11y 20:08:08 hober: I'm Ted from WebKit team at Apple, a CSSWG rep, also participate on IDPF side with some colleagues from iBooks 20:08:21 Liam Quin 20:08:24 liam: Liam Quinn, with W3C. Background is in XML and digital typography 20:08:31 s/Quinn/Quin/ 20:08:42 ?: Also W3C, sort of leader of digital publishing effort 20:08:53 plh: Philippe Le Hegaret, W3C. 20:08:53 plinss: Peter Linss, other CSSWG co-chair 20:09:00 plh: [...] 20:09:00 s/?/Ivan Herman/ 20:09:16 Luc Audrain 20:09:19 Luc: Work [...] XML, HTML, etc. Supposed to digitalize their (?) content 20:09:34 Luc: metadata and digital formats in IDPF. Metadata with editorX, EPUB3 with IDPF 20:09:44 stearns: Alan Stearns, CSSWG rep from Adobe 20:09:50 Brady Duga, /wave 20:09:59 duga: Longtime EPUB person 20:10:07 jeff: Jeff Jaffe, W3C 20:10:15 jjaffe: CEO W3C, here for high-level questions, otherwise mostly fly on wall 20:10:23 takeshi: Working in Ebook area for more than 10 years 20:10:56 makoto: Longtime ago was member of original XMLWG, but now participate in IDPF. Leader of EGLS (i18n-focus) of IDPF, also co-chair of Advanced Layouts subgrou of EPUBWG 20:11:43 fantasai: CSSWG, write a lot of specs, also worked in testing and little bit of browser implementation, ~13yrs 20:11:43 Richard Ishida 20:11:44 Thierry MICHEL W3C Team contact 20:11:51 r12a: i18nwg 20:12:05 Thierry: Working in vairous WGs, working recently on digital publishing effort with Ivan 20:12:20 glazou: Bert said his comp crashed, he'll be back asap 20:12:36 glazou: We decided to have this dicussion after workship on electronic books ~1mo ago 20:12:51 +Bert 20:12:57 glazou: Goal of this call is to identify the areas of CSS that need a better focus from the W3C to help the electronic books industry and publishing industrly 20:13:21 i/asap/Bert: Bert Bos, W3C Staff Contact for CSSWG/ 20:13:45 zakim, mute me 20:13:45 Ivan should now be muted 20:13:51 glazou: Markus and I will chair the call, but mostly want to listen, esp. to IDPF side, on what we miss and what should be our focuse. What are your current requirements, how can we help you guys. 20:14:17 glazou: We will carefully note what you say, and extract the best of the minutes after end of call to provide feedback to future Interest Group that will be formed at W3C. 20:14:54 Luc: We produce associative ebooks as .. version of our books 20:15:17 Luc: We expect at soft level, but can produce quality Ebooks at top of what is possible of many centuries of typography 20:15:26 Luc: .. don't think at the level of ... 20:15:50 Luc: We think also that there is something like page-padding in ebooks, that is quite contrary to what is a page and what is a web page 20:15:59 Luc: Web page is very long, it has no length, it is continuous 20:16:25 Luc: But epub & web technology, there is something that appears on screen that we call a "page", you have experience of turning pages, but those are not HTML files each, 20:16:36 Luc: It's not what's a web page, but also not what's a print page 20:16:42 Luc: In CSS we also lack vertical justification 20:16:54 Luc: As soon as certain height in pages, we have problems that have been solved in pages 20:17:00 Luc: widows & orphans, lines, etc. 20:17:26 Luc: As soon as we're going through these kind of new paradigm of pages inside open web platform, we should have some new abilities to code with vertical justification we don't have today 20:17:54 glazou: Seems you are interested most in CSS3 Fonts, Paged Media, and layout mechanisms for better positioning on the page 20:18:12 Luc: Not quite in terms of absolute positioning, but the composition and ? that is available in ??? 20:18:20 Luc: This engine is available as HTML composition engine 20:18:31 Luc: In this case there should be more possibilities to code with vertical elements 20:18:44 Luc: Fonts, you're right, because ... one of 2 ppl sent to workshop in NYC 20:18:51 Luc: One of those papers was about fonts 20:18:57 +plinss.a 20:19:02 -plinss 20:19:11 Luc: Because we experience that any time we are unable for technical reasons or legal reasons to put fonts... not able to put original fonts in the file. 20:19:32 Luc: Would like some mechanism to switch ?????, available in PDF world 20:20:04 fantasai, microphone to close to kbd 20:20:04 Zakim, mute janina 20:20:04 Janina should now be muted 20:20:14 Luc: Original font that was used in PDF to print, to be substituted by more generic fonts, embed to use by CSS instructions 20:20:15 ah thanks hober 20:20:26 Luc: focus size and position 20:20:48 glazou: Not sure if it's specific to CSS, or specific to converter 20:20:53 Zakim, unmute janina 20:20:53 Janina should no longer be muted 20:20:56 glazou: Thank you Luc, others? 20:21:35 makoto: Support of bopomofo ruby is important for Taiwanese 20:22:09 mgylling: Can I ask you and Takeshi, in scenario of pagination driven by CSS, would page progression direction be a concern? 20:22:27 [relation to Ruby, see also HTML Ruby Extensions as well: http://darobin.github.com/html-ruby/ ] 20:22:30 makoto: Some issues wrt page progression direction, but they are IDPF issues, such as having more than one content document 20:22:49 plh, ruby is almost not active in csswg 20:22:49 makoto: Page progression between them. This is purely and IDPF issue. Don't have any requests wrt CSS page progresion direction. 20:22:54 s/esio/essio 20:23:14 duga: Something that came up from Japanese publishers were things like hanging punctuation and other typographic features that are required 20:23:22 duga: Lots of little things, like what are legal line breaks, etc. 20:23:33 http://www.w3.org/TR/css3-text/ 20:23:46 takeshi: Each publisher has different line breaking rules, but now we only have 4 sets of rules in CSS3 Text 20:23:58 takeshi: If possible to customize line-breaking rules somehow, very helpful to Japanese publishers 20:24:08 takeshi: On other hand, not sure if such a capability is good for CSS or HTML 20:24:48 glazou: Implementors of readers and authoring environments? 20:25:03 duga: One area that is Wild West right now, but nobody knows how to do correctly, is user styling. 20:25:10 duga: User styling is much more common in ebooks than on the Web. 20:25:20 duga: They want to switch their reading font, or ? 20:25:32 duga: It's very difficult to handle with publisher styling 20:25:44 duga: Being able to apply in user styling, been a nightmare for very long time 20:26:04 glazou: That probably requires additions in CSS, but also on API side 20:26:30 fantasai: In what way is the cascade insufficient here? 20:26:37 glazou: Might be wrt detecting fonts 20:26:49 duga: Applying Sepia mode 20:26:56 duga: How do you decide to do that? 20:27:05 duga: Switching day-night mode, or low-contrast mode or extended reading 20:27:16 duga: Difficult to apply that styling without butting heads with whatever publisher has done 20:27:27 duga: Do you apply that bg color with !important rule to everything? 20:27:35 glazou: Alan, do you think CSS filters could help? 20:28:12 fantasai: Could maybe use MQ. A11y has been requesting ability to query for contrast settings. 20:28:24 janina: Happy that a11y req is also mainstream req 20:28:41 janina: Question would be, don't necessarily want to change all the pixels on the screen, just some of them. E.g. not affect pictures 20:28:41 I don't know that filters would be the right tool to use - it certainly could work 20:29:01 glazou: Sounds like extending MQ to device apis 20:29:12 duga: Not looking for solution, but pointing out areas of pain 20:29:14 + +1.303.475.aadd 20:29:15 (sorry, was muted) 20:29:26 glazou: Trying to convert your input to something we can do on CSSWG side. Only thinking out loud... 20:29:30 +Casey from Apple 20:29:34 Zakim, aadd is Casey 20:29:34 +Casey; got it 20:29:38 glazou: Anyone else? 20:29:45 stearns: One thing I get a lot of request for is some form of a baseline grid 20:30:03 stearns: If you have one columnof content, you have no problem, but multiple columns, it's a problem 20:30:28 hober: Yeah, CSSWG has heard that, but hasn't prioritized 20:30:49 glazou: iBooks uses old versions of @slot or ::slot or whatever. What are your expectations/wishes, because you never told us 20:30:56 hober: Talking about content created with ???, which is not EPUB 20:31:03 hober: So kindof orthogonal to this meeting 20:31:14 casey: iBooks author has nothing to do with EPUB. Separate file extension, etc. 20:31:19 s/???/iBooks Author 20:31:24 casey: Still supporting EPUB, happy to talk about that 20:31:34 glazou: iBooks format was not far away from EPUB 20:32:09 hober: Suggestion: AHL group at IDPF has been working on Regions Of Interest (ROI) 20:32:18 hober: Imagine a comic book in an EPUB, different panels 20:32:39 hober: Imagine a zoomed UI, where book author can say what panel regions are, and what order should be read 20:32:46 hober: Good feature, doesn't make sense to limit to books 20:33:05 hober: E.g. NYT homepage has regions of interest 20:33:13 hober: UA could zoom around on that in similar way 20:33:29 makoto: Two approaches for defining ROIs. One is use SVG content documents 20:33:38 makoto: Regions are purely described by SVG elements 20:33:54 makoto: Other is external region file. This is being heavily discussed. Haven't made final decision wrt that. 20:34:03 makoto: Think this has overlap with SVG, plan to speak with them 20:34:11 makoto: Maybe also overlap with CSSWG. 20:34:18 casey: Much overlap, or adoption, that we can do betst 20:34:30 casey: History of EPUB is taking in other existing standards that are already embraced and solid 20:34:37 casey: EPUB benefits by having something broadly adopted 20:34:51 casey: Important to have broadly adopted, to have something standard and not fractured 20:35:05 makoto: ... uses SVG elements, and introduces nothing new 20:35:22 makoto: If we introduce new thing, will try to reuse that 20:35:34 casey: ... part of existing standards, vs only part of EPUB 20:35:54 makoto: We had concerns wrt limitations in SVG, but now know we are not limited wrt that. Already in contact with SVGWG wrt that. 20:36:02 mgylling: Setting up formal liaison between SVGWG and IDPF 20:36:15 glazou: Do you mind if I share the URL for your SVG-based regions for manga document? 20:36:20 makoto: Not a public work 20:36:30 glazou: Could access it without being logged. 20:36:36 glazou: I'm not connected and I can view it; it's public 20:36:55 https://docs.google.com/document/d/1WQ2lX-zVfJKFVimb7AZauDwJnqSzlv_0rbBq1jA8HFA/edit?usp=sharing 20:37:39 mgylling: What's your view on running headers and footers? Do you hear lots of request from publishers? 20:37:43 duga: Yeah 20:37:46 duga: 10-15 years now 20:38:02 duga: But we've had a mechanism in EPUB, arguably rather poor. Not very well adopted. Few implemented in past, nobody now afaik 20:38:10 duga: Being able to carry info across pages would be very useful 20:38:17 glazou: This is something I started working on. 20:38:26 glazou: There is a mechnism, rough one, in CSS3 Paged media 20:38:39 glazou: Started something more powerful called something future, proposals for CSS4 Paged Media 20:38:52 glazou: My main goal is to be able to import a docx document and preserve all the headers/footers, and running ones 20:39:02 glazou: Currently when you convert, we are not able to preserve all the headers and footers 20:39:21 glazou: Given fact that publishers receive lot of documents in docx format, and main offering format for authors, it's a big hole in our publishing chain 20:39:41 glazou: The document is mostly a skeleton; will send as soon as there is content to read 20:39:59 casey: I'm surprised you've had lots of request for headers/footers. Not one I normally get. Only got one request for that. 20:40:13 mgylling: I was surprised also. Had a property for it in EPUB, but nobody complained it's not working 20:40:20 Luc: We did complain 20:40:45 Luc: We tried in 2010 to build line guide in EPUB2 and not successful. One reason was lack of headers. 20:40:53 Luc: When you go from index to page, like travel guide or whatever 20:41:01 Luc: don't know from the name of the hotel or restaurant, where you are 20:41:05 Luc: Could be any name in any city 20:41:20 Luc: Location is in header at beginning of chapter 20:41:30 glazou: I guess that many of you are interested in Paged Media, that it is top request 20:41:48 glazou: Side question, where do you take the @page rule in EPUB right now? 2.1 or 3? 20:42:17 [some confusion wrt this question] 20:42:59 http://www.w3.org/TR/css3-page/ 20:43:21 fantasai explains what @page rule is 20:43:41 fantasai: I think when I asked about css3-page headers, EPUB said they had their own mechanism and didn't need css3-page stuff 20:44:07 mgylling: Was reading Bert's document that he sent out 20:44:30 mgylling: Think many publishers would sign up for things in there. 20:44:31 http://www.w3.org/Style/2013/paged-media-tasks.html 20:44:36 mgylling: Publishing industry, High Design Layout 20:44:47 http://idpf.org/epub/pgt/ 20:44:49 mgylling: IDPF published an informational document last autumn called EPUB-adapted Layouts 20:45:02 mgylling: Alan Stearns can talk more about this 20:45:11 mgylling: Originated in InDesign, ships today in InDesign 6 20:45:20 mgylling: Adobe offered to make a spec of it for IDPF 20:45:33 mgylling: This is around page templates, and surrounding technology such as regions/exclusions 20:45:45 mgylling: Applies to magazine-type publications, less so to books 20:45:58 mgylling: Future document talking wrt page templtaes 20:46:04 mgylling: Publishers are very hopeful 20:46:25 mgylling: In absence of this kind of technology, must go back to fixed-layout publication, which is not fantastic choice to make 20:46:34 mgylling: Page-template mechanisms priority 20:47:06 takeshi: Publisher use page-template mechanism, high quality layout 20:47:17 takeshi: On other hand, most ebook reading systems don't support it 20:47:21 jdovey has joined #ebook 20:47:45 takeshi: Also to create high-quality layouts, also need to think about how to display this image efficiently 20:47:51 takeshi: In different screen types 20:48:12 takeshi: Not only page templates, but also CSS mechanism like CSS device adaptation and CSS image values and replaced content module 20:48:25 takeshi: Also need that to complete high-level layout publications 20:48:32 http://www.w3.org/TR/css-device-adapt/ 20:48:39 http://www.w3.org/TR/css3-images/ 20:48:57 ?: Page appearing in reading system in EPUB 20:49:10 ?: iBooks you have spread on left, and margin at top, and author of book and the top to the right page, title of book 20:49:29 ?: If you have taken into account the number of page in paper, you will have in the margins, external margins, the number of the page 20:49:41 ?: There is a page template, but should have better hand of it than having reading system design for us 20:50:00 mgylling: Interesting comparison of ebook reading system and web browser 20:50:28 s/?/Luc 20:50:30 s/?/Luc 20:50:31 s/?/Luc 20:50:32 s/?/Luc 20:50:45 Luc: There is in any reading system a layout that shows pages 20:50:50 Luc: Even if the EPUB is a reflowable EPUB 20:50:57 Luc: Chapters are in unique HTML file 20:51:07 Luc: Displayed by the reading system, displayed in something that looks like a page 20:51:13 Luc: This appearance mimic paper page 20:51:28 Luc: Even sometimes have turning-page animation 20:51:32 Luc: But it's not the paper page as it was 20:51:36 Luc: Not page as HTML pages can be 20:51:50 Luc: It's a template that designs some margins and this design is completely in the hands of the reading system developer 20:51:54 Luc: It's not in our hands as publisher 20:51:58 Luc: as we have on paper 20:52:05 Luc: We design the margins, the page, etc. as publisher 20:52:18 Luc: I agree that we should be able to have the possibility to design the page templtes 20:52:21 Luc: As we can do in paper 20:52:26 + +1.416.716.aaee 20:52:33 Luc: So that we can play the marigns, and say what we want at the bottom and the top 20:52:39 jdovey, you just joined ? 20:52:44 zakim, aaee is me 20:52:44 +jdovey; got it 20:52:45 Luc: Engine that displays the HTML in the 2D of the screen, this is a composition 20:52:49 ok jdovey welcome 20:52:56 Luc: It takes fonts, calculates size characters, hyphenation, line breaks, etc. 20:53:06 Luc: It puts the text inside the rectangle of the screen, calls it a page 20:53:11 Luc: But it is not very sophisticated 20:53:30 stearns: Interesting point that it's the readers that have these templates, and useful to move that to control of authors 20:53:39 stearns: But there are different levels of templates that can be authored 20:53:46 stearns: First is, here is template for margin area vs. content 20:53:53 stearns: Single template for all of your document's content 20:54:08 stearns: Next is have multiple templates, different template for first page of chapter 20:54:14 q+ to ask about other i18n issues 20:54:22 liam, lol 20:54:30 stearns: Then more complicated, adaptive layout, template selection based on content flowing through the page, so if you have a page with a image, it will use a different template than a page without a template 20:54:30 cdougherty has joined #ebook 20:54:48 ack r12a 20:54:48 r12a, you wanted to ask about other i18n issues 20:54:55 s/without a template/without an image/ 20:55:07 r12a: curious, earlier on, Japanese people mentioned things like bopomofo that are required and need better support 20:55:32 r12a: Can think of many other things needed in japanese layout, and wondering if we have an exhaustive list of features that are needed at the moment, or whether those were just examples. 20:55:49 r12a: Also interested to know whether guys on this call recognize that there are different requirements for other languages 20:56:06 r12a: e.g. working on Korean requirements document. Hoping to get Chinese requirements doc sometime as well 20:56:14 r12a: Also in i18n work on things like Arabic 20:56:21 r12a: fantasai works on things like numbering, text decoration 20:56:29 r12a: Lots of things of interest 20:56:38 r12a: line composition, avoidign spaces 20:56:44 r12a: Am I right to think that there is a lot more stuff? 20:56:58 r12a: 2nd question, have you been requirements from other languages/scripts that have particular needs? 20:57:38 Zakim, Casey is cdougherty 20:57:38 +cdougherty; got it 20:57:42 takeshi: Working with Japanese publishers, and they have requests for high-quality text layout 20:58:10 takeshi: Now Koji is fielding those requests, implement into CSS Text Level 4 or those levels, but most of Japanese publishers are agreed to go with this level of CSS support 20:58:13 takeshi: level 3 20:58:18 takeshi: ... 20:58:45 makoto: A group of Japanese publishers [... some document not available in English ... ] 20:58:52 makoto: I contacted that organization 20:59:02 makoto: One person said to me, if IDPF sends formal request to translate, it might happen 20:59:03 -cdougherty 20:59:10 makoto: Thinking to ask someone to do so 20:59:26 we have to wrap up 20:59:43 fantasai: Even submitting in Japanese would be helpful, because Koji at least can read it 20:59:57 tell us where to write and what! 21:00:15 glazou: Thank you for joining call, for giving your input. 21:00:32 glazou: Next few days, Thierry, Markus and I will browse the minutes and make a proposal 21:00:37 glazou: Then see if we need another conference call 21:00:56 rrsagent, draft minutes 21:00:56 I have made the request to generate http://www.w3.org/2013/03/22-ebook-minutes.html tmichel 21:00:58 glazou: In the meantime, if you want to share URLs, documents, etc. We have our mailing list and all addresses of participants of this call are in agenda from Thierry 21:01:03 glazou: Anything to add? 21:01:19 Luc: Will minutes be accessible? 21:01:27 glazou: We will send minutes to recipients of agenda 21:01:30 glazou: Anything else? 21:01:38 http://www.w3.org/TR/2012/NOTE-jlreq-20120403/ 21:01:54 ??: Link to Japanese document, be very very interested to look at that 21:02:03 http://www.w3.org/TR/jlreq/ 21:02:53 s/??/jdovey/ 21:03:01 glazou: Thank you everyone, will keep you posted. 21:03:04 Meeting closed. 21:03:05 -Jeff 21:03:06 rrsagent, draft minutes 21:03:06 I have made the request to generate http://www.w3.org/2013/03/22-ebook-minutes.html tmichel 21:03:06 -hober 21:03:08 -Janina 21:03:08 -Luc 21:03:09 -[IPcaller.a] 21:03:09 -Ivan 21:03:09 janina has left #ebook 21:03:09 jdovey has left #ebook 21:03:10 -glazou 21:03:10 -mgylling 21:03:10 -[IPcaller] 21:03:11 -[IPcaller.aa] 21:03:12 -Stearns 21:03:13 -Plh 21:03:14 -jdovey 21:03:15 -duga 21:03:15 -Bert_ 21:03:19 thanks mgylling ! 21:03:20 -plinss.a 21:03:28 -Liam 21:03:29 zakim, drop richard please 21:03:29 Richard is being disconnected 21:03:30 thanks glazou! 21:03:31 -Richard 21:03:33 good jobGlazou 21:04:00 thanks tmichel 21:04:20 have a good WE ... 21:06:16 Bert_ has left #ebook 21:08:30 disconnecting the lone participant, tmichel, in Styl_Ebook()4:00PM 21:08:31 Styl_Ebook()4:00PM has ended 21:08:31 Attendees were +81.46.647.aaaa, glazou, makoto-san, Janina, hober, Liam, Ivan, mgylling, plinss, Plh, +33.6.48.38.aabb, Luc, Stearns, +1.760.214.aacc, Jeff, duga, [IPcaller], 21:08:31 ... fantasai, takeshi-san, Richard, tmichel, Bert_, +1.303.475.aadd, +1.416.716.aaee, jdovey, cdougherty 21:10:53 fantasai, thanks for minuting ! 21:16:17 mgylling has joined #ebook 21:21:02