To view parent comment, click here.
To read all comments associated with this story, please click here.
"Actually, it's good it's supported through a plug-in. It ought to be a part of system-wide plug-in structure akin to datatypes on Amiga or translators on the BeOS/Zeta/Haiku/Syllable/SkyOS systems or akin to the kits in *step.
Applications shouldn't worry about what elements they support natively - they should support virtually nothing natively, but support virtually everything through systemwide plug-ins. So no place for MS-bashing here.
Plug-ins are good."
You will all be pleased to know I found a way to get an SVG graphic into a Word document!
First I downloaded OpenOffice.org. Then I used OpenOffice.org writer to start a new document, and then I inserted a picture of the SVG graphics file. Then I saved the result in MS Word .doc format.
Mind you, once I have got the OpenOfffice.org suite on the system, I'm not at all sure exactly why I needed that last step. I could have just used Firefox to browse the web, and used the OpenOffice program for my document without involving MS Word at all, and save my documents in ISO standard ODF formats, and be standards compliant and integrated all along in the first place. Much easier, and way cheaper to boot.
This way, I don't need any half-baked plug-ins that run out of support and don't properly integrate with the whole desktop environment.






Member since:
2005-10-02
Actually, it's good it's supported through a plug-in. It ought to be a part of system-wide plug-in structure akin to datatypes on Amiga or translators on the BeOS/Zeta/Haiku/Syllable/SkyOS systems or akin to the kits in *step.
Applications shouldn't worry about what elements they support natively - they should support virtually nothing natively, but support virtually everything through systemwide plug-ins. So no place for MS-bashing here.
Plug-ins are good.