RE: Language is not markup and markup is not language.

The point Paul raises below was the chief justification, I believe, in the
creation of PDF out of Postscript. Postscript has a Halting Problem (you
don't know if it will), while PDF doesn't. An important distinction in the
print industry. The lesson for XSL is to never start down this path in the
FO vocabulary.
Cheers,
David vun Kannon

> -----Original Message-----
> From:	Paul Prescod [SMTP:paul@xxxxxxxxxxx]
> Sent:	Monday, May 10, 1999 4:01 PM
> To:	xsl-list@xxxxxxxxxxxxxxxx
> Subject:	Re: Language is not markup and markup is not language.
> 
	<snipped>
> For instance imagine you are serving documents through a script to publish
> them to the Web. Wouldn't it be nice to be able to check if the documents
> and the script are "compatible" before you put them on your website? A
> "compatible" document would be one that wouldn't cause the script to go
> into an infinite loop or crash. Well with a scripting language the only
> way to check is to run the script. If it seems to go into an infinite loop
> then you could wait for half an hour and say: "well, I guess it is in an
> infinite loop"-- but unless you know the details of the code you are just
> guessing. You don't know for sure.
> 
> 
*****************************************************************************
The information in this email is confidential and may be legally privileged.
It is intended solely for the addressee. Access to this email by anyone else
is unauthorized. 

If you are not the intended recipient, any disclosure, copying, distribution
or any action taken or omitted to be taken in reliance on it, is prohibited
and may be unlawful. When addressed to our clients any opinions or advice
contained in this email are subject to the terms and conditions expressed in
the governing KPMG client engagement letter.         
*****************************************************************************


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list