Altova Mailing List Archives

Re: generating XML from ini-file

From: Rick Geimer <rick.geimer@------->
Date: 4/26/1999 2:03:00 AM

Since your initial document is not XML, I don't think you could use XSL for
this transformation.

The typical way to do this kind of up-translation is to use a pattern
matching language to process the ini-file,  write out your XML as best you
can to match the structure required by the DTD, then parse the result to
make sure the output is error-free.

I typically use OmniMark, since it has a powerful pattern matching language
and a built-in XML parser, but you could do this with Perl as well,
especially with the XML module.

Hope this helps.

Rick Geimer
National Semiconductor

"Bruening, Oliver" wrote:

> i have to generate a xml-document with a given dtd from data which has
> an ini-file structure (best case; the data comes from an ibm host ...).
> how can this to done in an elegant way ? my first idea was to traverse
> through the dtd and to add the fitting elements to the xml-file. is this
> the right way ? any examples or hints around ?
> regards
>   oliver bruening
>  XSL-List info and archive:

 XSL-List info and archive:


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 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.