On Wed, 2004-03-17 at 20:54, Joerg Heinicke wrote: > On 17.03.2004 19:11, Bruno Dumon wrote: > > >>Ok, asking the list: in which way shall we handle the update in the > >>repeater syntax? > > > e) Use a text-based search and replace. This preserves the layout of the > > XML (which I consider to be rather important since these files are > > mostly hand-edited). > > I saw how easy this was for replacing the namespaces, but how shall this > work for replacing attributes with child elements? Have a look at the > stylesheet tools/src/cforms-repeater-syntax.xsl for the logic I use at > the moment. Even if you remove the handling of the short time > intermediate wb:unique-row: is this really doable through search and > replace?
Didn't know about that, that won't work indeed. > > The layout of the XML is also preserved by the stylesheet as everything > in the source is copied to the output. Xalan only removes whitespaces > outside of the root element. I would be suprised if Xalan keeps the order of attributes, let alone the whitespace between them. But no XML parsing solution I know of keeps that information, so the users will just have to live with it. Either they choose for the automated conversion with the annoyance that some things might be rearranged, or they do the conversion manually. > > Try it yourself by just hitting 'Enter' on all questions, the replacing > is tested on the Woody block sources and copied to > build/woody2cforms_timestamp. > > Joerg -- Bruno Dumon http://outerthought.org/ Outerthought - Open Source, Java & XML Competence Support Center [EMAIL PROTECTED] [EMAIL PROTECTED]
