From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/22687 Path: news.gmane.org!not-for-mail From: Christopher Creutzig Newsgroups: gmane.comp.tex.context Subject: Re: ConTeXt to RTF Conversion Date: Fri, 23 Sep 2005 22:13:45 +0200 Message-ID: <433461F9.8030205@creutzig.de> References: <20050922100002.E15A2127F0@ronja.ntg.nl> <43328617.30205@capdm.com> <2DF694F1-C55F-47D5-95E2-1D889971836F@ensta.fr> <43331A17.1020100@creutzig.de> Reply-To: mailing list for ConTeXt users NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Trace: sea.gmane.org 1127506682 2233 80.91.229.2 (23 Sep 2005 20:18:02 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 23 Sep 2005 20:18:02 +0000 (UTC) Original-X-From: ntg-context-bounces@ntg.nl Fri Sep 23 22:17:51 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 1EItxU-00052Z-An for gctc-ntg-context-518@m.gmane.org; Fri, 23 Sep 2005 22:15:48 +0200 Original-Received: from localhost (localhost [127.0.0.1]) by ronja.ntg.nl (Postfix) with ESMTP id CF415127A2; Fri, 23 Sep 2005 22:15:47 +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 12108-04; Fri, 23 Sep 2005 22:15:47 +0200 (CEST) Original-Received: from ronja.vet.uu.nl (localhost [127.0.0.1]) by ronja.ntg.nl (Postfix) with ESMTP id 60A6812778; Fri, 23 Sep 2005 22:13:51 +0200 (CEST) Original-Received: from localhost (localhost [127.0.0.1]) by ronja.ntg.nl (Postfix) with ESMTP id 278FD12778 for ; Fri, 23 Sep 2005 22:13:50 +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 12093-10 for ; Fri, 23 Sep 2005 22:13:49 +0200 (CEST) Original-Received: from mailgate.uni-paderborn.de (mailgate.uni-paderborn.de [131.234.22.32]) by ronja.ntg.nl (Postfix) with ESMTP id 00A7A12775 for ; Fri, 23 Sep 2005 22:13:48 +0200 (CEST) Original-Received: from p548b0e69.dip0.t-ipconnect.de ([84.139.14.105] helo=[192.168.1.2]) by mailgate.uni-paderborn.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.43) id 1EItwX-0005nA-6K for ntg-context@ntg.nl; Fri, 23 Sep 2005 22:14:49 +0200 User-Agent: Mozilla Thunderbird 1.0.6 (Macintosh/20050716) X-Accept-Language: en-us, en Original-To: mailing list for ConTeXt users In-Reply-To: X-Enigmail-Version: 0.92.0.0 X-UNI-PB_FAK-EIM-MailScanner-Information: Please see http://imap.uni-paderborn.de for details X-UNI-PB_FAK-EIM-MailScanner: Found to be clean X-UNI-PB_FAK-EIM-MailScanner-SpamCheck: not spam, SpamAssassin (score=-3.208, required 4, AUTH_EIM_USER -5.00, RCVD_IN_NJABL_DUL 1.66, RCVD_IN_SORBS_DUL 0.14) X-MailScanner-From: christopher@creutzig.de 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:22687 Archived-At: Idris Samawi Hamid wrote: > Would it be possible to define an xml format for the journal so that I > could more easily process both ConTeXt/LaTeX articles as well as the > docs and rtfs I generally receive? Is this more work than it's worth? > It's a humanities journal, so little-to-no math. Math is, in my experience, the worst part of it, so you an consider yourself happy that you don't need it. The question is, what problems of the current process are you trying to improve/solve with a possible move to xml? If your most pressing problem is the variety of data formats you receive articles in, then no, xml won't help. You'd still need some way of transforming the articles to the format of your choice. That being said, XML may be a very good intermediate step from Word or rtf to ConTeXt, if only because OpenOffice has pretty advanced import filters and stores its data in a straightforward xml format that should be easy to transform, assuming you start with a sufficiently rich set of predefined formats and somehow get people to either use them (fat chance, I know) or have them be sufficiently different that you can automatically or at least semi-automatically classify the author's formatting to your presets. In really simple cases (e.g., pure prose) you may get away with accepting HTML and converting that. If your most serious problem is a variety of output formats you want to support (print/pdf, html, some eBook variants, ...), xml is a perfect technique to develop a solution. If getting lots of different encodings is a problem of yours, xml solves that nicely as well. But just for that, there are simpler and less intrusive ways. Other things xml may solve well: - archivability (although your ConTeXt files are probably no worse) - reusability: Almost everything in a file following a well-designed xml format is local and you can simply copy a (complete) block of text + markup and insert it into another file. - consistency, enforcing rules: While it is possible to enforce things like =93every article must start with an abstract containing one to three paragraphs=94 in TeX, it is way easier in xml. - all sorts of conversions, including shuffling around or extracting data of interest Things xml won't do any magic for: - layout. You'd need to write a conversion to ConTeXt or whatever. Depending on your needs, this can be anything from trivial (say, two hours) to almost undoable (although this would mean the xml format is particularly badly designed for your journal). Both lists are certainly incomplete. I hope you will get other answers as well. regards, Christopher