[
Lists Home |
Date Index |
Thread Index
]
This sort of conversion can be done very nicely in XSLT 2.0: I showed a very
similar example in my tutorial at XML Europe.
1. read the file using the unparsed-text() function
2. split it into lines using the tokenize() function
3. analyze each line using the <xsl:analyze-string> instruction
4. group the resulting lines hierarchically using the <xsl:for-each-group>
instruction, within a recursive template so you do the grouping repeatedly
at each level of hierarchy.
Michael Kay
> -----Original Message-----
> From: Igor [mailto:logastellus@yahoo.com]
> Sent: 12 May 2004 14:15
> To: xml-dev@lists.xml.org
> Subject: [xml-dev] converting a proprietary config file to XML
>
> Perhaps someone here can help me? I've posted this on
> newsgroups and thru IRC and no responses so far.
>
> I have a "*"-delimited config file for our internal
> app. The syntax is as follows:
>
> param1*param2*value=3
> param1*param2*param3*value=4
> param1*value=1
> param2*value=3
>
> etc..
>
> What's the best way of doing this? As seen from the
> example above, this lends itself to a very nice
> tree-based representation. So I tried using an
> acyclic graph but got bogged down converting it to
> tree, the
> original idea was to first convert it to a tree, then
> traverse the tree xml-tagging it along the way. Is
> that a good idea?
>
> Are there better ideas? Thanks for your help.
>
>
>
>
> __________________________________
> Do you Yahoo!?
> Yahoo! Movies - Buy advance tickets for 'Shrek 2'
> http://movies.yahoo.com/showtimes/movie?mid=1808405861
>
> -----------------------------------------------------------------
> The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
> initiative of OASIS <http://www.oasis-open.org>
>
> The list archives are at http://lists.xml.org/archives/xml-dev/
>
> To subscribe or unsubscribe from this list use the subscription
> manager: <http://www.oasis-open.org/mlmanage/index.php>
>
>
|
