- From: Daniel Weck <daniel.weck@gmail.com>
- Date: Tue, 6 Jun 2017 15:35:48 +0100
- To: "Gribben, Andrew" <Andrew.Gribben@hmhco.com>
- Cc: "public-epub3@w3.org" <public-epub3@w3.org>
- Message-ID: <CA+FkZ9GQC6y-RhTh_gOwZeU5mAqHBhAdbxzsOuoTUXuchJDSFw@mail.gmail.com>
Hello all, during the EPUB 3.1 revision cycle there was a discussion about some kind of "leave me alone" (aka LMA) property that would somehow instruct reading systems to forego custom layout and styling in reflowable documents, much like how fixed-layout documents are rendered. Bearing in mind though, such broadly-scoped functionality would interfere with (take precedence over?) user preferences, and would therefore likely impede on accessibility (e.g. font overrides, colour schemes). Full-bleed is mostly impacted by reading system margins, so I can see how a margin-focused property would address this particular use-case. But there are other presentational and interactional aspects where the author's intent is bound to conflict with user preferences and default reading system rendering rules. Just to name a few examples: pagination (content sectioning), navigation / visualisation aids (e.g. zoomable images), media overlay playback (synchronised highlights), selections / annotations, text justification, line spacing, font family and size overrides, etc. Regards, Daniel On 6 June 2017 at 15:06, Gribben, Andrew <Andrew.Gribben@hmhco.com> wrote: > Hi Elie > > That's a great idea. > > ———————————— > > *Andrew Gribben* > > Technical Product Owner > > Engineering > > > > *Houghton Mifflin Harcourt* > > Office: +353 1 514 7759 > > Mobile: +44 7411 923951 > > > On 6 June 2017 at 14:30:56, Elie Mietkiewicz (mietkiewicz@gutenberg- > technology.net) wrote: > > *This message originated from outside your organization* > ------------------------------ > Hi Andrew, > > Thanks for sharing these samples. Full bleed images indeed allow nice > layout :) > > I have a more generic suggestion: why don't we create an "advanced author" > attribute which simply remove the automatic margin and let the author > decide to apply margin (or not!) for text, images but also videos or custom > JS interactivities. Applying this automatic margin limit the reflowable > epub to very basic layout whereas HTML5 & CSS3 allow incredible things! > > Regards, > > Elie > > Elie Mietkiewicz > Product Manager, in charge of epub standard > > Inscrivez-vous <https://www.myecontentfactory.com/fr/#newsletter> à notre > newsletter mensuelle ! > LinkedIn <https://www.linkedin.com/company-beta/2481694/> | Facebook > <https://www.facebook.com/GutenbergTechnology/> | Twitter > <https://twitter.com/GutenbergTech> | Blog > <http://gutenberg-technology.com/blog/> > > Monthly Newsletter: Subscribe Today! > <https://www.myecontentfactory.com/en/#newsletter> > LinkedIn <https://www.linkedin.com/company-beta/2481694/> | Facebook > <https://www.facebook.com/GutenbergTechnology/> | Twitter > <https://twitter.com/GutenbergTech> | Blog > <http://gutenberg-technology.com/blog/en/> > > 2017-06-01 19:15 GMT+02:00 Gribben, Andrew <Andrew.Gribben@hmhco.com>: > >> Rather than wait until the next call, I figured I'd share this out now in >> the hope that it gives some talking points if nothing else. >> >> I've uploaded a few single page samples of (non-HMH) content that >> required support for full bleed images and backgrounds and where we ended >> up using our own fork of Readium to support it. I find lot of digital >> textbook designers want to do the same and without a way to do so their >> designs tend to be a bit more bland than they otherwise could be. (That's >> not always a bad thing). >> >> https://andrewgribben.github.io/publ-cg >> >> ———————————— >> >> *Andrew Gribben* >> >> >> >> On 30 May 2017 at 16:09:58, Dave Cramer (dauwhe@gmail.com) wrote: >> >> *This message originated from outside your organization* >> ------------------------------ >> Hi Everyone, >> >> We will have the second virtual meeting of the EPUB 3 Community Group on >> Thursday, June 1 at 1600 UTC, which is: >> >> 9AM in San Francisco >> 12 Noon in New York and Toronto >> 4PM 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] Update on recent and future events (Dave) >> >> [2] Education task force. Call for volunteers to organize and lead this >> work. What are the next steps? >> >> [3] A11y task force. Call for volunteers to organize and lead this work. >> What are the next steps? >> >> [4] Rendering and image bleeds. See https://github.com/w3c/pub >> l-cg/wiki/Rendering and https://github.com/w3c/publ-cg/issues/3. How >> might such a feature be designed? How can we work with reading system >> developers on this? >> >> >> ============================ >> TELECONFERENCE INFORMATION >> ============================ >> >> Meeting Number: 319 436 071 >> Meeting Password: [ask on IRC, or use the name of the irc channel without >> the hash character] >> >> >> >> ------------------------------------------------------- >> To join the online meeting (Now from mobile devices!) >> ------------------------------------------------------- >> 1. Go to https://mit.webex.com/mit/j.php?MTID=me9b9a0fe10fe9072be3 >> be63ce160da16 >> 2. If requested, enter your name and email address. >> 3. If a password is required, enter the meeting password: [which is the >> same as the IRC channel name, without the #] >> 4. Click "Join". >> >> To view in other time zones or languages, please click the link: >> https://mit.webex.com/mit/j.php?MTID=mc4e0e4fcf4fe84a3f03489b4be126646 >> >> ------------------------------------------------------- >> To join the audio conference only >> ------------------------------------------------------- >> To receive a call back, provide your phone number when you join the >> meeting, or call the number below and enter the access code. >> US Toll Number: +1-617-324-0000 <(617)%20324-0000> >> >> Access code:319 436 071 >> Mobile Auto Dial:+1-617-324-0000 <(617)%20324-0000>,,,319436071# >> >> ------------------------------------------------------- >> For assistance >> ------------------------------------------------------- >> 1. Go to https://mit.webex.com/mit/mc >> 2. On the left navigation bar, click "Support". >> >> You can contact me at: >> iherman@mit.edu >> 1-951563749 >> >> Add this meeting to your calendar (Cannot add from mobile devices): >> https://mit.webex.com/mit/j.php?MTID=ma5c75a948df7ab7d064d140bddd7a3b6 >> >> >> >> >> ========================================= >> 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 >> port: 6665 or 6667 >> >> General information on IRC at W3C can be found at >> https://www.w3.org/Project/IRC/ >> >> ------------ >> GITHUB >> ------------- >> >> We have a general repository for the community group at: >> >> 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/Basic >> GitHubContributionIntro.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. >> >> Dave Cramer >> Rachel Comerford >> co-chairs >> >> >
Received on Tuesday, 6 June 2017 14:37:12 UTC