W3C home > Mailing lists > Public > public-digipub-ig@w3.org > February 2015

Re: Report on Houdini F2F from Simon Sapin

From: Ivan Herman <ivan@w3.org>
Date: Mon, 23 Feb 2015 09:10:23 +0100
Cc: Peter Krautzberger <peter.krautzberger@mathjax.org>, Dave Cramer <dauwhe@gmail.com>, W3C Digital Publishing IG <public-digipub-ig@w3.org>
Message-Id: <DA91C311-690F-49BE-9BA2-D5A4DA5BD34C@w3.org>
To: Toru Kawakubo <kwkbtr@vivliostyle.com>
Thanks a lot, Kawabuto-san. It is great for the DPUB IG to be informed of these evolutions.

Ivan



> On 23 Feb 2015, at 07:23 , Toru Kawakubo <kwkbtr@vivliostyle.com> wrote:
> 
>>> By the way, I wrote a brief report on Houdini (and CSSWG) F2F in Japanese.
>>> You can read it using Google Translate for now.
>>> I can translate it into English later if necessary.
>> I know it may be a lot to ask, but having this translated would be really helpful... The Google translate is, ehem, well, rudimentary:-)
> 
> I posted an English translation of the article (omitting some part of the original post).
> 
> CSS Houdini / CSS Working Group meeting report
> http://vivliostyle.com/2015/02/sydney/
> 
> Since my English is not fluent, please let me know if there are sentences incorrect or unclear. I will try to improve.
> 
>>>> However, will that API also allow for some sort of a fast search which, I presume, would be necessary (e.g., to answer to the question 'on which page is this image')? Do we know more?
>>> I think the idea of "break record", mentioned by Rossen in the F2F, could be used for implementing such kind of search.
>>> See IRC log: http://logs.csswg.org/irc.w3.org/houdini/2015-02-06/#e516631
>>> It was only briefly mentioned in the discussion and I am not sure if it is in the scope of the Fragment Tree API, though.
> 
> I summarized the idea of "break record" in the article as follows:
> 
>> If one can save information about positions of (page or column or any fragmentation) breaks after layout, it is possible to resume reading in the middle of the document efficiently, starting layout from that point. Without the break record, doing layout from the beginning of the document is necessary since one does not know page breaking positions.
> 
> With such information, one can identify the position of a page break nearest to the specified content (e.g. an image) without doing layout from the beginning of the document and answer the page number of the page on which the content is laid out.
> 
> --
> Toru Kawakubo
> Vivliostyle Inc.
> http://vivliostyle.com
> 
>> 2015/02/20 19:14, Ivan Herman <ivan@w3.org> wrote:
>> 
>> Thank you Kawakubo-san!
>> 
>> 
>> 
>>> On 20 Feb 2015, at 10:57 , Toru Kawakubo <kwkbtr@vivliostyle.com> wrote:
>>> 
>>> Hello,
>>> 
>>> I attended the Houdini F2F.
>>> 
>>>> However, will that API also allow for some sort of a fast search which, I presume, would be necessary (e.g., to answer to the question 'on which page is this image')? Do we know more?
>>> 
>>> 
>>> I think the idea of "break record", mentioned by Rossen in the F2F, could be used for implementing such kind of search.
>>> See IRC log: http://logs.csswg.org/irc.w3.org/houdini/2015-02-06/#e516631
>>> It was only briefly mentioned in the discussion and I am not sure if it is in the scope of the Fragment Tree API, though.
>> 
>> I would expect that this is some sort of a requirement we may have but, I must admit, it is a little bit difficult to follow and IRC minute...
>> 
>>> 
>>> By the way, I wrote a brief report on Houdini (and CSSWG) F2F in Japanese.
>>> You can read it using Google Translate for now.
>>> I can translate it into English later if necessary.
>> 
>> I know it may be a lot to ask, but having this translated would be really helpful... The Google translate is, ehem, well, rudimentary:-)
>> 
>> Thanks a lot
>> 
>> Ivan
>> 
>>> 
>>> Original (in Japanese): http://vivliostyle.co.jp/2015/02/sydney/
>>> English translation (Google Translate): https://translate.google.com/translate?sl=ja&tl=en&js=y&prev=_t&hl=ja&ie=UTF-8&u=http%3A%2F%2Fvivliostyle.co.jp%2F2015%2F02%2Fsydney%2F&edit-text=&act=url
>>> 
>>> --
>>> Toru Kawakubo
>>> Vivliostyle Inc.
>>> http://vivliostyle.com
>>> 
>>>> 2015/02/20 18:12, Ivan Herman <ivan@w3.org> wrote:
>>>> 
>>>> Thanks indeed.
>>>> 
>>>> How, technically, will this affect paging? I would expect that 'Fragment Tree' is the crucial one for us here, returning information on pages, ie, one could find out(?) where the page boundaries are. However, will that API also allow for some sort of a fast search which, I presume, would be necessary (e.g., to answer to the question 'on which page is this image')? Do we know more?
>>>> 
>>>> Thanks again!
>>>> 
>>>> Ivan
>>>> 
>>>>> On 19 Feb 2015, at 20:07 , Peter Krautzberger <peter.krautzberger@mathjax.org> wrote:
>>>>> 
>>>>> Thanks for that link, Dave.
>>>>> 
>>>>> On Thu, Feb 19, 2015 at 7:10 PM, Dave Cramer <dauwhe@gmail.com> wrote:
>>>>> I just found a first-hand report [1] from Mozilla's Simon Sapin on the recent inaugural meeting of Project Houdini. I found it quite helpful!
>>>>> 
>>>>> Dave
>>>>> 
>>>>> [1] http://www.mail-archive.com/dev-servo@lists.mozilla.org/msg01131.html
>>>>> 
> 
> 


----
Ivan Herman, W3C
Digital Publishing Activity Lead
Home: http://www.w3.org/People/Ivan/
mobile: +31-641044153
ORCID ID: http://orcid.org/0000-0003-0782-2704





Received on Monday, 23 February 2015 08:10:38 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:35:55 UTC