EZ xslt

[fmsavey]

Is anyone using Chapparelle Software's XSLT Stylesheet builder for FileMaker? This piece of software will convert a "marked up" Word document into an xslt stylesheet which then can be used to create Word documents from exported xml data from FileMaker. I was wondering if it could create stylesheets that would mimic FileMaker reports that had subsummary parts.

[fabriceN]

EZxslt now has a feature for repeating sections, so that you can mimic the list view or a portal.

But sub totals and other calculations must be calculated in FM and exported.

Also, only one section of Word document is repeating.

Still, EZxslt is a BIG time saver.

Edited May 3, 2007 by Guest

[Stickybeak]

Not any more it wont - its power pc software and it wont work if you upgrade to Lion which I, foolishly, did.

Any comparable solution out there?

Help....

[beverly]

What's not compatible now? is it the version of MS office that is used?

[Stickybeak]

No its the EZXslt thats not compatible

[beverly]

OK, thanks, Stickybeak! I'd forgotten that it was "compiled". There are ways to do the same thing, you just have to create your XSLT manually...

Beverly

[Stickybeak]

That's beyond me

[beverly]

The Word document can be saved as RTF format and opened with a text editor. Try to see if you can use the same "format" with calculated fields to "merge" the field data. No XML or XSLT required. Save the text (export) with the .rtf extension and see what happens.

Beverly

[comment]

Save the text (export) with the .rtf extension

I think you'll run into a problem with the UTF-16 encoding (assuming you meant export field contents).

[beverly]

I think you'll run into a problem with the UTF-16 encoding (assuming you meant export field contents).

what problem?

[comment]

When Export Field Contents is used with a Text field, the resulting file is always encoded in UTF-16. Such .rtf file is either rejected or read as gibberish by target applications. Here is a simple test you can try for yourself.

RTF.zip

[beverly]

It could be the "LIttle Endian" BOM (byte order mark) at the beginning of the text content (also in the Export Field Contents). This is invisible, but if your RTF can't handle it, It can't handle it.

Beverly