Altova Mailing List Archives
>xml-dev Archive Home
>Recent entries
>Thread Prev - Re: [xml-dev] Remembering the original XML vision
>Thread Next - Re: [xml-dev] Remembering the original XML vision
Re: [xml-dev] Remembering the original XML vision
To: <xml-dev@-----.---.--->
Date: 2/18/2003 7:09:00 PM
Gavin Thomas Nicol writes: > This is part of it, but conversion tools from Word/Frame/etc. have > existed for a fairly long time... as have forms-based authoring > solutions. The former have not been all that successful anywhere I've seen them used, despite the fact that I used to work at a company that made one of them. Using Word styles is tempting up front, but the conversion systems generally fall apart under heavy use (if they even survive the initial testing). Perhaps they'd be OK for a very small operation with one or two writers and a lot of patience. I did see one non-profit project succeed in using the built-in SGML support in WordPerfect for a large authoring team, but that was as close as I've seen anyone come. All the best, David -- David Megginson, david@m..., http://www.megginson.com/
Disclaimer
These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

