- From: tey tag <teytag@gmail.com>
- Date: Tue, 17 Oct 2017 16:53:04 +0300
- To: W3C EPUB3 Community Group <public-epub3@w3.org>
- Cc: Laurent Le Meur <laurent.lemeur@edrlab.org>, Jiminy Panoz <jiminy@chapalpanoz.com>, Dave Cramer <dauwhe@gmail.com>, Rachel Comerford <rachel.comerford@macmillan.com>
- Message-Id: <F4434919-CB14-4FA7-80A2-867CF86D3A11@gmail.com>
Hello to everyone, Any work done for EPUB3 should be supported. Because the results of these studies will cause other ideas to be triggered. Best Regards N. Erhan Uzumcu Art Director and EPUB Developer W3C EPUB Community Group Member TEYTAG Founder (Turkish Electronic Publishing Desing and Research Group - Istanbul, Turkey) https://independent.academia.edu/NErhanÜzümc http://teytagblog.blogspot.com.tr http://www.teyid.org/ePub3Lib/ @ePub3Lib #teytag > On Oct 17, 2017, at 4:40 PM, Rachel Comerford <rachel.comerford@macmillan.com> wrote: > > Thanks Laurent, > > Having witnessed Jiminy's magic at ebookcraft I am 100% convinced of his status as a senior epub developer however, my comment was not about Jiminy's ability to contribute any more than it was about RS's ability to contribute. Please don't misconstrue a comment about process as ad hominem attack. > > I believe it is important for these best practices to be developed and it is important that they come out of the CG as a community with contributions from it's varied and valuable members. I say this out of my own, non-technical, experience attempting to apply epub3.1 to the ebooks that we produce at a higher ed company. > > R > > Rachel Comerford | Director of Content Standards | T 212.576.9433 > > Macmillan Learning > > On Mon, Oct 16, 2017 at 4:36 PM, Laurent Le Meur <laurent.lemeur@edrlab.org <mailto:laurent.lemeur@edrlab.org>> wrote: > HI Rachel, > > Note that the links provided by Jiminy hare not directly related to the Readium CSS effort. > Note also that Jiminy is part of the Readium team, as developer of Readium CSS. > Last note: most EPUB 3 best practices will not come from RS developers but from senior EPUB authors IMO. Jiminy is a senior EPUB author. > > The Readium CSS project (a sub-project of the overall Readium initiative) is an aiming at displaying correctly EPUB 3 files coming from very different sources, therefore not directly related to the other Readium sub-projects (Readium JS, Readium SDK, Readium 2 SDK or Readium Desktop). > > I'm personally convinced that the EPUB 3 CG should release a "best of" of EPUB (3) best practices; or write its own maybe. EPUB 3 offers so much HTML/CSS freedom that many EPUB authors, no sufficiently versed in HTML/CSS wizardry, create markup that plays badly in most RSes (even if they play well in their unique test RS, often iCloud or Readium Chrome app). > > Bien Cordialement, > > Laurent Le Meur > CTO, EDRLab > >> Le 16 oct. 2017 à 21:56, Rachel Comerford <rachel.comerford@macmillan.com <mailto:rachel.comerford@macmillan.com>> a écrit : >> >> Jiminy - I think the Readium team is doing great work but I am hesitant to have a single reading system determine best practices. I'm sure there is plenty that we can cull from the work that they have done in order to start the conversation though and I am looking forward to digging into it in detail as we start documenting this. >> >> Rachel Comerford | Director of Content Standards | T 212.576.9433 <tel:(212)%20576-9433> >> >> Macmillan Learning >> >> On Mon, Oct 16, 2017 at 1:11 PM, Jiminy Panoz <jiminy@chapalpanoz.com <mailto:jiminy@chapalpanoz.com>> wrote: >> Regrets, prior engagement. >> >> As regards “[4] Should the CG be involved in documenting best practices for EPUB?” though, a quick feedback: authoring docs/best practices have been a constant issue we could read between the lines of the Readium CSS Project, to be honest. And I’m not seeing anyone else doing this work. >> >> To sum things up, we’ve had requests about layouts which are already possible with CSS in EPUB 3.1, scattered knowledge of progressive enhancement techniques and the latest CSS modules/proposals, and quite significant issues related to deprecated practices (e.g. Mobi7). >> >> Consequently, evangelization has been a regular concern when analyzing feedback/requests. I’d be happy to put the following into public domain if you decide to document best practices, should it help: >> >> https://dauwhe.github.io/reflow/ <https://dauwhe.github.io/reflow/> (which is a translation of https://jaypanoz.github.io/reflow/ <https://jaypanoz.github.io/reflow/>) >> https://friendsofepub.github.io/eBookDesignChecklist/ <https://friendsofepub.github.io/eBookDesignChecklist/> >> https://friendsofepub.github.io/eBookPerfChecklist/ <https://friendsofepub.github.io/eBookPerfChecklist/> >> https://friendsofepub.github.io/eBookTricks/ <https://friendsofepub.github.io/eBookTricks/> >> related slides and materials for https://jaypanoz.github.io/ebookcraft2017/#/ <https://jaypanoz.github.io/ebookcraft2017/#/> >> It’s just impossible to manage all of this on my own anyway, and could help start some collective effort more quickly. >> >> Best, >> >> Jiminy >> >> Le 16.10.2017 16:10, Dave Cramer a écrit : >> >>> Hi Everyone, >>> >>> We will have a virtual meeting of the EPUB 3 Community Group on Thursday, October 19 at 1600 UTC, which is: >>> >>> 9AM in San Francisco >>> 12 Noon in New York and Toronto >>> 5PM in London >>> 6PM in Paris and Amsterdam >>> 9:30PM in Chennai >>> 1AM Thursday in Tokyo (sorry!) >>> >>> The meeting will be one hour. >>> >>> ========== >>> DRAFT AGENDA >>> ========== >>> >>> [1] Accessibility task force update (Avneesh?) >>> >>> [2] reminder of beta testing for the ACE accessibility checker >>> >>> [3] Should some parts of EPUB for Education be merged into the main EPUB spec? (Rachel) >>> >>> [4] Should the CG be involved in documenting best practices for EPUB? (Dave) >>> >>> >>> ============================ >>> TELECONFERENCE INFORMATION >>> ============================ >>> >>> JOIN WEBEX MEETING >>> https://mit.webex.com/mit/j.php?MTID=m57513dcab244d32d626741269004303b <https://mit.webex.com/mit/j.php?MTID=m57513dcab244d32d626741269004303b> >>> Meeting number (access code): 319 436 071 >>> Meeting password: email dauwhe@gmail.com <mailto:dauwhe@gmail.com> for the password, or ask privately in IRC. >>> >>> >>> JOIN FROM A VIDEO SYSTEM OR APPLICATION >>> Dial sip:319436071@mit.webex.com <mailto:sip%3A319436071@mit.webex.com> >>> >>> >>> JOIN BY PHONE >>> +1-617-324-0000 <tel:(617)%20324-0000> US Toll Number >>> >>> >>> >>> Can't join the meeting? >>> https://help.webex.com/docs/DOC-5412 <https://help.webex.com/docs/DOC-5412> >>> >>> >>> ========================================= >>> OTHER USEFUL (AND IMPORTANT) INFORMATION >>> ========================================= >>> ------ >>> IRC >>> ------ >>> >>> W3C groups use IRC (Internet Relay Chat) during meetings to take >>> minutes, manage the queue of people wishing to ask questions or make >>> comments, providing useful links, etc. >>> >>> We will use the IRC channel #epub3cg: >>> >>> channel: #epub3cg >>> server: irc.w3.org <http://irc.w3.org/> >>> port: 6665 or 6667 >>> >>> General information on IRC at W3C can be found at >>> https://www.w3.org/Project/IRC/ <https://www.w3.org/Project/IRC/> >>> >>> ------------ >>> GITHUB >>> ------------- >>> >>> We have a general repository for the community group at: >>> >>> https://github.com/w3c/pub-cg <https://github.com/w3c/pub-cg> >>> >>> Ivan Herman has written up a helpful guide for newcomers to GitHub at >>> >>> https://github.com/iherman/misc-notes/blob/master/docs/BasicGitHubContributionIntro.md <https://github.com/iherman/misc-notes/blob/master/docs/BasicGitHubContributionIntro.md> >>> >>> If you don't already have a GitHub account, you might want to set one >>> up before the call. >>> >>> >>> Thanks very much, and please let us know if you have any questions. >>> >>> >>> Rachel Comerford >>> Dave Cramer >>> co-chairs >>> >>> >>> >> >> > >
Received on Tuesday, 17 October 2017 13:53:32 UTC