Return-Path: 
 <cocoon-users-return-51930-apmail-xml-cocoon-users-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-cocoon-users-archive@xml.apache.org
Received: (qmail 73235 invoked by uid 500); 11 Jun 2003 18:25:41 -0000
Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:cocoon-users-help@xml.apache.org>
list-unsubscribe: <mailto:cocoon-users-unsubscribe@xml.apache.org>
list-post: <mailto:cocoon-users@xml.apache.org>
Reply-To: cocoon-users@xml.apache.org
Delivered-To: mailing list cocoon-users@xml.apache.org
Received: (qmail 73211 invoked from network); 11 Jun 2003 18:25:41 -0000
Received: from warsl402pip3.highway.telekom.at (HELO email06.aon.at)
 (195.3.96.75)
  by daedalus.apache.org with SMTP; 11 Jun 2003 18:25:41 -0000
Received: (qmail 454158 invoked from network); 11 Jun 2003 18:25:43 -0000
Received: from n656p007.dipool.highway.telekom.at (HELO gmx.at)
 ([212.183.91.231]) (envelope-sender <alasan@gmx.at>)
          by qmail6rs.highway.telekom.at (qmail-ldap-1.03) with SMTP
          for <cocoon-users@xml.apache.org>; 11 Jun 2003 18:25:43 -0000
Message-ID: <3EE77488.6040301@gmx.at>
Date: Wed, 11 Jun 2003 20:27:21 +0200
From: Alexander Schatten <alasan@gmx.at>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: cocoon-users@xml.apache.org
Subject: Re: TeX to PDF serializator
References: <E03B309D-972B-11D7-A18C-000393A9DEF6@free.fr>
	 <00d601c32b3b$0af8d3d0$a501a8c0@computer2>  <3EE655B7.4010308@gmx.at>
 <1055284621.2107.43.camel@lughnasadh.silmaril.ie>
In-Reply-To: <1055284621.2107.43.camel@lughnasadh.silmaril.ie>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

Peter Flynn wrote:

>This has come up several times before. I agree completely: many people
>want to use LaTeX to create PDF because it does a vastly
>better job than any of the FOP systems.
>  
>
nevertheless it is imho the completly wrong attempt. because FOP is not 
ready for primetime, you suggest to put energy to integrate a legacy 
system, that does not fit into the XML publishing process?? this sounds 
weird to me. far better would be the idea to invest more energy in 
enhancing FOP.

>This is really a bad idea, I'm afraid, and the very last thing we 
>actually want or need.
>  
>
It is always great to be informed by others what *I* need.

thank you!

;-)

>TeX systems are for formatting: you use them to typeset something
>which was created/edited/stored/manipulated in (for example) XML.
>Because of the way history happened, TeX preceded XML, so we have
>a lot of legacy TeX. Sure it would be nice to have a tex2xml which
>would do the job (actually there are a few attempts) but if you stop
>for a moment to think of the ghastly mess which most authors make
>of TeX, you'll realise why there is no such animal right now. Yes,
>you could write a conversion from well-formed LaTeX to XML (I actually
>did one a long time ago, for SGML) but the instant an author starts
>to write her own macros or mess manually with the formatting, the model
>breaks and translation becomes virtually impossible. To effect it fully
>you'd need to rewrite TeX the program to output XML instead of DVI or
>PDF, and you'd *still* be in trouble because most of what TeX formats
>carries nothing with it which can be used to indicate markup, unless
>you want to go back to the days of <b>, <i>, and <u>.
>  
>
I really cannot see the point. the only thing I would need is a 
generator that 1:1 tries to move LaTeX into XML, if this is a user 
written command or not.

\begin{Citation}{1234}{456}
blabla
\end{Citation}

should become to something like

<comm arg1="Citation" arg2="1234" arg3="456">
blabla
</comm>

and \index{Test} to <index>Test</index>

you can then write your own stylesheets to process this to whatever 
needed. So really no need to rewrite the tex program. far away from this!

and such a generator would be fully sufficient to process available tex 
documents for some reasons.

>  
>
>>The next one will ask, why Cocoon cannot create WML from powerpoint or 
>>SVG from Postscript.
>>    
>>
>
>Because PowerPoint is not (yet) an XML format, nor is PostScript.
>What we need to to be able to go from XML to PDF via LaTeX.
>  
>
the same as LaTeX is no XML format? you seem to mix up a few things here.


Alex


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
For additional commands, e-mail: cocoon-users-help@xml.apache.org