1
Automation Interface, Add-Ins and Tools / Re: Format of internal documentation when exportin
« on: July 15, 2006, 10:17:47 am »
Hello,
I mean the 'linked documentation' (new feature of V6 (?) I think).
The 'bunch of hex' is in reality a base64 coded zip file (you can try opening it by exporting XMI, copying the hex bytes to one of the free online base64 decoders, saving the result to foo.zip). Inside the zip file there is the linked documentation (I think the filename was 'str.dat' or something like that). But I don't know the file format of this file. I think its proprietary.
it would be wonderful to get a standalone program from sparx that converts this thing into RTF, or a function in the EA automation interface to save a 'linked document' into rtf directly...
I mean the 'linked documentation' (new feature of V6 (?) I think).
The 'bunch of hex' is in reality a base64 coded zip file (you can try opening it by exporting XMI, copying the hex bytes to one of the free online base64 decoders, saving the result to foo.zip). Inside the zip file there is the linked documentation (I think the filename was 'str.dat' or something like that). But I don't know the file format of this file. I think its proprietary.
it would be wonderful to get a standalone program from sparx that converts this thing into RTF, or a function in the EA automation interface to save a 'linked document' into rtf directly...