Marco Fioretti wrote:
Laurent Godard wrote.
IMHO, macros (developepd in StarBasic, python, beanshell,
whateverlanguage) do not deal with openDocument at all
It only deals with the layer the software (OOo) that render an
OpenDocument gives the script through its API. It is implementation
specific
OpenDocment is /only/ the description of the xml files (eg
content.xml), and not a specification of the api of the
implementation
The only answer I have to this is the same I gave to the KOffice
developers when they made the very same remark a few days ago:
1) technically, you are 100% right, and I even agree, but
2) after years of advertising what is now OpenDocument as THE
one, application-independent, truly open, durable solution
etc... that frees your data from lock-in to any single SW
provider (including "free as in freedom" ones)...
...end users are going to be mightily pissed when they start
exchanging .odt files from/to OO.o and KOffice or whatever else
and they don't always work in the same way.
Perhaps I am too learned, but I'd NEVER expect interoperability on
OpenDocument to extend to macros or any programming function.
OpenDocument attaches to its title: a document, a piece of paper.
If you go to macros you are talking about an _application_ standarising
on that has been much more difficult ever. For that several software
makers MUST agree in a common API.
Even within single companies like Microsoft or Adobe, different products
use difefrent APIs, just because they were created by different people.
It is rather impossible that an .odt file may contain a macro functional
at OOo, KOffice or whatever. This is not the same as saying that a
CONVERTER cannot be build. But that is a different approach.
- Enrique -
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
