RE: [office-comment] Requirement: page and line break indicators

["Alex Brown" <alexb@griffinbrown.co.uk>]

Patrick, Sean,

I'd certainly agree there is a use case for recording line-breaking
decisions (for UK legislation, for example, there is a requirement that
the HTML versions of documents have identical line numbering to print,
to prevent divergent referencing).

(Call me old-fashioned, but I quite using PIs for these things, since
they are incidental to the application, rather than innate to the
content. It also means you don't have to mess up your content models by
allowing an element everywhere...)

- Alex.

> -----Original Message-----
> From: Patrick Durusau [mailto:patrick@durusau.net]
> Sent: 23 February 2009 15:06
> To: Sean McGrath
> Cc: office-comment@lists.oasis-open.org
> Subject: Re: [office-comment] Requirement: page and line break
> indicators
> 
> Sean,
> 
> In what way does the use of <text:soft-page-break> not meet your
> requirement?
> 
> Granted that different applications will have varying support for that
> element, resulting is as you note below, different presentations, but
> what more can a format do other than allow the specification of the
> page
> breaks?
> 
> That some application chooses to ignore them or doesn't support
> <text:soft-page-break>, I am not real sure what the format can do to
> assist.
> 
> Am I missing the problem?
> 
> Granted I would really like to see a robust solution, given my
interest
> in ancient texts where line breaks, etc. are essential to
understanding
> dittography and other features of ancient texts. But, other than
> recording the presence of such breaks, what do you see a format as
> being
> able to offer?
> 
> Thanks for writing!
> 
> Hope you are having a great day!
> 
> Patrick
> 
> Sean McGrath wrote:
> > +NAME
> > Sean McGrath
> >
> > +CONTACT
> > seanmcgrath@propylon.com
> >
> > +CATEGORY (select one or more from below)
> > import-export
> >
> > +SCOPE (select one or more from below)
> > text
> >
> > +USE CASE
> > I have a set of ODT documents to batch process into a report. The
> > report needs to cite locations in the ODT documents
> > using page and line number.
> >
> > +DESCRIPTION
> > Unlike some "high end" wordprocessor/DTP packages such as
FrameMaker,
> ODT
> > provides no way to access hard/soft page breaks or hard/soft line
> breaks.
> >
> > Obviously, the soft line/page break information is volatile -
opening
> > up the same
> > ODT in another ODT processor will most likely result in new soft
> > line/page breaks.
> >
> > However, there are many high-volume usage scenarios where having
> > access to line/page
> > number information of the last rendering is very useful. Examples
> > include citation of line/page info
> > in reports, back-linking from HTML to PDF on a page-by-page basis,
> > pre-flight checks etc.
> >
> > This problem of page/line view on one side and content-oriented
> object
> > flow view is as old as the hills.
> > I'm a big fan of designing around the latter but facilitating the
> > former. I.e. allowing
> > ODT implementations to optionally record soft page/line break
> > information in point elements
> > or perhaps processing instructions.
> >
> > Sean
> >
> >
> >
> 
> --
> Patrick Durusau
> patrick@durusau.net
> Chair, V1 - US TAG to JTC 1/SC 34
> Convener, JTC 1/SC 34/WG 3 (Topic Maps)
> Editor, OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300
> Co-Editor, ISO/IEC 13250-1, 13250-5 (Topic Maps)
> 
> 
> --
> This publicly archived list offers a means to provide input to the
> OASIS Open Document Format for Office Applications (OpenDocument) TC.
> 
> In order to verify user consent to the Feedback License terms and
> to minimize spam in the list archive, subscription is required
> before posting.
> 
> Subscribe: office-comment-subscribe@lists.oasis-open.org
> Unsubscribe: office-comment-unsubscribe@lists.oasis-open.org
> List help: office-comment-help@lists.oasis-open.org
> List archive: http://lists.oasis-open.org/archives/office-comment/
> Feedback License: http://www.oasis-
> open.org/who/ipr/feedback_license.pdf
> List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
> Committee: http://www.oasis-
> open.org/committees/tc_home.php?wg_abbrev=office