[austechwriter] Re: OT: Footers in Word: Is look-ahead possible?

  • From: Mike Buckler <mbuckler@xxxxxxxxxxxxxxxxxx>
  • To: austechwriter@xxxxxxxxxxxxx
  • Date: Fri, 16 May 2003 13:33:10 +0800

Friday, May 16, 2003, 11:20:17 AM, Elizabeth wrote:

FE> I'm not sure how well a strict XML structure would work in the real =
FE> world. It sounds like a great idea, but there's always life, sitting in =
FE> the wings, waiting to take centre stage - you know, when almost =
FE> everything fits, but some things simply won't... Has anyone used =
FE> structure-oriented tools like XML successfully? Has it required vastly =
FE> more effort than the output was worth?

Authoring XML/SGML is definitely slower. There are several reasons.

1) Using a DTD as complex as Docbook requires many hours of study.

2) The current crop of XML/SGML aware tools are not particularly user friendly.

3) If the DTD doesn't fit the type of document exactly, then you can
spend as much time revising the DTD and style rules as actually
writing the document.

4) Things like tables do not fit into the classic XML/SGML model. This
is where presentation (column and row layout) comes into play and
messes up the whole point of using XML/SGML in the first place.

The current hype around XML is mainly to do with data interchange
between application that do data processing. For example an insurance
claim form where a set number of fields must be completed in order to
create a "valid document".


Best regards,
 Mike Buckler     

**************************************************
To post a message to austechwriter, send the message to 
austechwriter@xxxxxxxxxxxxxx

To subscribe to austechwriter, send a message to 
austechwriter-request@xxxxxxxxxxxxx with "subscribe" in the Subject field.

To unsubscribe, send a message to austechwriter-request@xxxxxxxxxxxxx with 
"unsubscribe" in the Subject field.

To search the austechwriter archives, go to 
www.freelist.org/archives/austechwriter

To contact the list administrator, send a message to 
austechwriter-admins@xxxxxxxxxxxxx
**************************************************

Other related posts: