[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: The problem with typography (with or without flow objects)

• From: Marcus Carr <mrc@a...>
• To: xml-dev@x...
• Date: Thu, 15 Jun 2000 09:55:25 +1000

Sebastian Rahtz wrote:

> no, the human inserts them in the source. we ran the book, viewed the
> pages, and corrected the bad breaks with PIs in the XML file, and
> reran the formatting.

So if you wanted to use a different FO application to render that book, you would
likely have to go back to the source document and redo your page breaks, right?
If the two applications used different hyphenation dictionaries, there is a
distinct possibility that the page breaks would change in a 300 page book.
Restricting the formatting abstraction to the FO layer has failed - aspects of
format have crept straight past it and back into the source data. (Please don't
take this as criticism of your approach Sebastian - it's pragmatic and effective
and under the circumstances, I would likely have done the same sort of thing.)
The point is, rendering is and will remain specific to the application, so the
syntax behind it will have limited impact on the end product. I accept that there
are benefits in everyone using the same terminology, but I believe that FOs are
intended to fulfill a much bigger role than that. My understanding is that
they're supposed to "free us from the shackles of formatting applications", but
I've yet to be convinced that they can deliver this.


--
Regards,

Marcus Carr                      email:  mrc@a...
___________________________________________________________________
Allette Systems (Australia)      www:    http://www.allette.com.au
___________________________________________________________________
"Everything should be made as simple as possible, but not simpler."
       - Einstein



***************************************************************************
This is xml-dev, the mailing list for XML developers.
To unsubscribe, mailto:majordomo@x...&BODY=unsubscribe%20xml-dev
List archives are available at http://xml.org/archives/xml-dev/
***************************************************************************

• Follow-Ups:
  • Re: The problem with typography (with or without flow objects)
    • From: Sebastian Rahtz <sebastian.rahtz@c...>

• References:
  • Re: The problem with typography (with or without flow objects)
    • From: "Eve L. Maler" <Eve.Maler@e...>
  • Re: The problem with typography (with or without flow objects)
    • From: "Eve L. Maler" <Eve.Maler@e...>
  • The problem with typography (with or without flow objects)
    • From: David Megginson <david@m...>
  • Future of Formatting Objects (XSL/FO)
    • From: Thierry Hanser <thanser@c...>
  • Re: Future of Formatting Objects (XSL/FO)
    • From: Peter Murray-Rust <peter@u...>
  • Re: Future of Formatting Objects (XSL/FO)
    • From: Marcus Carr <mrc@a...>
  • Re: Future of Formatting Objects (XSL/FO)
    • From: Sebastian Rahtz <sebastian.rahtz@c...>
  • Re: The problem with typography (with or without flow objects)
    • From: "Eve L. Maler" <Eve.Maler@e...>
  • Re: The problem with typography (with or without flow objects)
    • From: "Sebastian Rahtz" <sebastian.rahtz@c...>

• Prev by Date: Re: The problem with typography (with or without flow objects)
• Next by Date: acronym => trademark
• Previous by thread: Re: The problem with typography (with or without flow objects)
• Next by thread: Re: The problem with typography (with or without flow objects)
• Index(es):
  • Date
  • Thread