From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/22735 Path: news.gmane.org!not-for-mail From: Duncan Hothersall Newsgroups: gmane.comp.tex.context Subject: Re: DOC/RTF to ConTeXt via XML Date: Tue, 27 Sep 2005 09:05:43 +0100 Message-ID: <4338FD57.3040109@capdm.com> References: <20050927074229.9EF85127E2@ronja.ntg.nl> Reply-To: mailing list for ConTeXt users NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1127808448 14754 80.91.229.2 (27 Sep 2005 08:07:28 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 27 Sep 2005 08:07:28 +0000 (UTC) Original-X-From: ntg-context-bounces@ntg.nl Tue Sep 27 10:07:25 2005 Return-path: Original-Received: from ronja.vet.uu.nl ([131.211.172.88] helo=ronja.ntg.nl) by ciao.gmane.org with esmtp (Exim 4.43) id 1EKATx-0003E4-7r for gctc-ntg-context-518@m.gmane.org; Tue, 27 Sep 2005 10:06:33 +0200 Original-Received: from localhost (localhost [127.0.0.1]) by ronja.ntg.nl (Postfix) with ESMTP id 8A14912802; Tue, 27 Sep 2005 10:06:32 +0200 (CEST) Original-Received: from ronja.ntg.nl ([127.0.0.1]) by localhost (smtp.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 25313-08; Tue, 27 Sep 2005 10:06:30 +0200 (CEST) Original-Received: from ronja.vet.uu.nl (localhost [127.0.0.1]) by ronja.ntg.nl (Postfix) with ESMTP id B5328127CF; Tue, 27 Sep 2005 10:06:29 +0200 (CEST) Original-Received: from localhost (localhost [127.0.0.1]) by ronja.ntg.nl (Postfix) with ESMTP id C73DF127CF for ; Tue, 27 Sep 2005 10:06:27 +0200 (CEST) Original-Received: from ronja.ntg.nl ([127.0.0.1]) by localhost (smtp.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 25331-07-2 for ; Tue, 27 Sep 2005 10:06:26 +0200 (CEST) Original-Received: from liszt-04.ednet.co.uk (liszt-04.ednet.co.uk [212.20.226.25]) by ronja.ntg.nl (Postfix) with ESMTP id B3764127CD for ; Tue, 27 Sep 2005 10:06:26 +0200 (CEST) Original-Received: from [192.168.254.41] (unknown [212.20.255.162]) by liszt-04.ednet.co.uk (Postfix) with ESMTP id 2030714044 for ; Tue, 27 Sep 2005 09:06:26 +0100 (BST) User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en Original-To: ntg-context@ntg.nl In-Reply-To: <20050927074229.9EF85127E2@ronja.ntg.nl> X-Virus-Scanned: amavisd-new at ntg.nl X-BeenThere: ntg-context@ntg.nl X-Mailman-Version: 2.1.5 Precedence: list List-Id: mailing list for ConTeXt users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: ntg-context-bounces@ntg.nl Errors-To: ntg-context-bounces@ntg.nl X-Spam-Checker-Version: SpamAssassin 3.0.3 (2005-04-27) on smtp.ntg.nl X-Virus-Scanned: amavisd-new at ntg.nl Xref: news.gmane.org gmane.comp.tex.context:22735 Archived-At: > Question: Is it possible to design a doc or rtf template that Open Office can > convert to a sane, consistent xml format? OpenOffice.org does allow you to attach an XSLT stylesheet to an export process which therefore allows you to do a (limited) transformation from the visual markup which is its native format to a more structured one which you would need. But the biggest challenge is that all wordprocessors are designed for visual editing, meaning that there are, for example, 15 or so different ways to get a bulleted list in Word, creating 15 or so different RTF constructs, and coping with this can be a nightmare. > If the Tremblay approach is rich > enough, that would solve a lot of problems! Here is my idea: > > 1. Give each author a doc/rtf template for formatting their article; > 2. Use OpenOffice to convert to xml; > 3. Use the Tremblay method (have not tried it yet) to process this in Context. The FO approach (Paul Tremblay's focus) is one way to process XML to paginated output, but there are many others. Personally I don't like the FO approach, for a variety of reasons, but I'm sure others have had success with it. But you should also explore DocBook-in-ConTeXt, which uses ConTeXt's native XML processing capabilities. And don't rule out using a separate scripting language to convert XML into ConTeXt as a batch process, since that will give you the ultimate flexibility in accessing all of ConTeXt's abilities. > Question: Does the entire journal have to be in programmed in xml or can > ConTeXt process xml locally? For example, I may have my own article done in > COnTeXt mixed with other articles done in rtf=>xml. You can just put XML into \startXMLdata ... \stopXMLdata blocks. I do this for MathML processing within a larger ConTeXt document. > Any other advice (and/or pitfalls to watch for) would be appreciated. This > sounds very promising! Horses for courses. It's possible to get sucked into things like an FO implementation or an XML conversion and find that you have spent months perfecting it and it only shaves half an hour off your production time! Also, you do tend to have to make compromises in design if you want to be able to process directly from XML. But if you have sufficient throughput and an appropriate design, it can be a real boon. Hope that helps. Duncan