Re: [pagination] Draft pagination document now in GitHub and online

On Oct 27, 2013, at 22:26 , "Cramer, Dave" <Dave.Cramer@hbgusa.com> wrote:

> On 10/27/13 4:35 PM, "Liam R E Quin" <liam@w3.org> wrote:
> 
> 
>> On Sun, 2013-10-27 at 09:05 +0100, Ivan Herman wrote:
>> 
>>> I must admit I am uneasy about putting anything out of scope at this
>>> moment. For example, call me naïve, but my hope is that, aside from
>>> terminology, Arabic, Hebrew, and other rtl writing systems may not be
>>> all that different apart from a carefully chosen terminology.
>> 
>> They aren't, although the definition of a baseline has to be made
>> carefully, maths (even simple numbers) need special handling, and of
>> course whitespace is treated very differently with the Arabic script. So
>> there are a lot of details to consider. Typography is about attention to
>> detail.
>> 
>> RenderX, as I understand it, is quite widely used for formatting (using
>> XSL-FO with of course embedded CSS properties) of Arabic and Chinese,
>> and mixed Arabic, Chinese and English such as you might find in
>> Malaysia. I remember a question to the XSL-FO WG at one point about
>> where to put the underline on a right-to-left quotation embedded in
>> vertical text. There's also stuff in XSL-FO for mixing e.g. Hindi and
>> Arabic. So there's expertise floating around not too far away, and
>> documents for Arabic and Hebrew typesetting would share a lot with those
>> for Latin script Western languages, kashida and cantillation
>> notwithstanding :)
> 
> A pragmatic approach to the scope of the document would be to cover
> everything people are willing to write about!
> 
> Do we still want to cover Japanese-language issues in depth, given the
> existence of JLREQ?

I think we should separate two issues. First, whether we want to make a detailed description of the Japanese pagination issues: of course not. JLREQ is referred to from within the document, and we are fine. But I believe it would be good if somebody from this IG looked at the various CSS features to see whether the JLREQ requirements are indeed covered; also, whether what this document would come up with as requirements are at least in line with JLREQ. Although I realize that, for example, Koji is both on the IG and on the CSS WG, but he may not have the energy to check and look at all CSS documents, and he may well welcome some assistance on that. And, of course, we have other languages, too...

One possibility is that we plan this work by concentrating on ltr languages first and we plan to issue a second release of the document with more I18N features later. (I am not sure that is optimal, but we may consider this.) 

But I do have a question that Hachette may very well know (being present in different countries already): how different are the pagination habits from one country, one culture to the other even if we stay, say, in European languages? The small discussion on the side on the French punctuation show that there might be local specificities... We have to be careful of covering those, too...

Sigh. This is complicated:-)... but fun!

Ivan


> 
> Dave
> 
> 
> 
> This may contain confidential material. If you are not an intended recipient, please notify the sender, delete immediately, and understand that no disclosure or reliance on the information herein is permitted. Hachette Book Group may monitor email to and from our network.
> 
> 


----
Ivan Herman, W3C 
Home: http://www.w3.org/People/Ivan/
mobile: +31-641044153
FOAF: http://www.ivan-herman.net/foaf.rdf