| astir |
| Newbie |
|
| India |
|
|
| None Specified |
|
| Tuesday, May 13, 2008 |
| Wednesday, May 21, 2008 4:04:12 AM |
5
[0.03% of all post / 0.00 posts per day] |
|
Thanks for the reply.
I tried the "Save Generated XSLT-RTF" feature, we are able to generate word 2007 file but the file is not opening in a machine having word 2007 installed (The error message is given below). It is opening only in word 2003.
"The Office Open XML file Altova cannot be opened because there are problems with the contents."
|
Is it possible to convert an existing xslt to sps, so that we can maintain existing reports (created using wordml tags in xslt) using stylevision. Please clarify.
Thanks,
Karthik
|
Does stylevision support the following section breaks in word,
next
continous
even
odd
If yes, please let us know the approach.
Thanks.
|
Requirement: We want to create a word document 2007 version on the fly from .NET windows application.
Steps Done:
The source XML file has been created using visual studio 2005
The source XML file was opened in style vision and SPS was created.
The required content was placed in SPS and saved. The previews are coming correctly in preview word 2007
Using the "Save Generated XSLT-Word 2007" menu item, we created the xslt file
Then Altova.AltovaXML dll was referenced in .NET project and Excecute method was used to generate the docx.
Result:
The docx file is not getting created, only [Content_Types].xml, word and _rels folders are getting created.
If I repeat the above mentioned steps for html by doing "Save Generated XSLT-HTML" it is wordking fine.
I do not have word 2007 in my machine, is it the reason for not generating word 2007 file through application.
As per the link https://www.altova.com/manual2008/StyleVision/stylevisionenterprise/index.html?svintro_settingup.htm it says,
"Microsoft Word 2000 or later, for RTF Preview. Microsoft Word 2003 or later is recommended."
Please let us know whether word 2007 needs to be installed for this operation.
|
We are creating word documents (2003) using the wordml approach. Following are the steps carried out,
1• Create an xml file to create the report template
2• Open this xml file in word and apply the formatting for the static part of the document which does not involve any business logic (like adding header, footer, page number etc)
3• Save the xml file after unselecting "Save data only" option
4• Run the inference tool(for word 2003) to convert the xml to xsl file
5• Open the xsl file generated by the inference tool and add all the business logic (like dynamic generation of tables) at appropriate places of the xsl document. This business logic will be used to fetch the data from the xml file (which acts as the data store).
6• Then finally in the C# code the Transform method is applied using the xsl and xml files to get the final report in word 2003. To get the output report in doc format, the extension of the output file is mentioned as doc.
Step 5 is very difficult in the above approach because the xsl file generated by the inference tool generates a lot of code and it becomes very difficult to identify approprite places for writing the business logic. The maintainability of the code becomes very poor.
Does xmlspy make the xsl edting easy in the xsl generated by the inference tool?
|
|
