Subject:Working with FO in Source and then WYSIWYG closes tags improperly Author:Anna Marie van Vliet Date:31 Aug 2005 12:18 PM
I am new to both Stylus Studio and XSL, so it is possible that I am doing something incorrectly, but here is what's happening:
I have created an xsl document using formatting objects and it all renders properly and properly generates a PDF. I then went to the WYSIWYG tab to see what it looked like, and when I went back to the source window again, it was all messed up. My open table tags were closed right away (<fo:table/>) and the closing tags from where they had originally been no longer existed. This occurred with most of the table-type tags, and the block tags that were contained within the table cells. It would no longer generate, with the error indicating that my document was not properly formed.
I am using the demo version of Stylus Studio Professional Edition version 3.
I know that WYSIWYG editing for FO is not a supported feature, but I did not expect it to actually change my source code.
Also, in playing with the sample fo catalogue, when I first installed Stylus Studio, it rendered properly, but after a while it quit working. I can't really say "when" it quit working. I was generating it and others while learning how it worked and wasn't always watching the preview. I was watching the output to see if error were generated, which they were not. It still rendered HTML. I saw in another post that you said to change the output back to XML when that happens. I did that and it still didn't work. When I reinstalled Stylus Studio, it worked again. Any suggestions?
Subject:Working with FO in Source and then WYSIWYG closes tags improperly Author:Tony Lavinio Date:31 Aug 2005 11:06 PM
For the first part, the WYSIWYG tab is for HTML, and switching to it
will cause Stylus Studio to try to make your XSL generate HTML, which
is definitely not what you want.
For the second part, I'm not sure what broke. FO is sensitive to the
Java settings, since Apache FOP is a Java-based product. It could be
that somehow the settings from Tools|Options were changed. But nothing
done in ordinary operation should break the install.