>
>> 4. The credit above mentions Sun, but I don't see Sun mentioned here <
>>
http://odf-converter.sourceforge.net/>. Is all the OpenOffice.org
>> development for OdfConverter, including Sun's work, going back into the
>> SF.net project?
>>
>
> Here you are confusing the "native" OOXML filters with odf-converter. The native filter code is in C++ and written by people at Sun and Novell. odf-converter is in C# with the majority of the actual "business logic" in XSLT, and written by people at Clever Age and their subcontractors (or whatever).
>
Yes, I was not clear on the distinction until it was pointed out today.
>
>> 5. The OdfConverter version from Sourceforge requires .Net framework
>> 2.0, but the version from download.go-oo.org seems not to.
>>
>
> Do you mean the OOo build with the "native" OOXML filters included in the GoOo build of OOo in their work-in-progress state, or the odf-converter builds for Linux and Windows?
I mostly meant GoOo (which I didn't know had native filters until
today), but I also meant odf-converter too. :)
> The former have nothing to do with .NET at all. The latter don't require the .NET framework even if they are C# code as they are built as Mono "bundled" executables (i.e. include the Mono runtime and class libraries).
>
> As such it is possible to use the upstream command-line odf-converter with OOo on Windows instead of the Mono-built executable.
>
Andrew
_______________________________________________
Dev mailing list
Dev@...
http://lists.go-oo.org/listinfo.cgi/dev-go-oo.org
