D. Carrera wrote: > But this addon would not be embedded in an .odt paragraph (at > least, not in the current and near-future OOo releases).
Why not, if I may ask? > May I ask... is there a reason why a .odt file is needed but > an addon won't work for you? (provided that the add-on works > whenever OOo is installed). Fair question, but you partly answered it yourself. OpenDocument is one thing, OO.o another. Who can assume that the latter *will* be installed wherever the former is used? Especially in 2/4 years, if OpenDocument is to become the truly universal that we keep saying etc etc... Before answering "gee, that's so far in the future, why bother?", keep in mind that OpenDocument is being advertised as *the* long term solution for governments, multinationals and so on. All organizations that have a huge inertia to switch, and before "buying" the whole FOSS thing still need to see or be told that there *is* a coherent, long term strategy behind. Back to my training class example: a portable macro embedded into an .odt file is what you could use to distribute tutorials or any other interactive educational material where there is scarce bandwidth and/or PCs not powerful enough to run OO.o. Ditto for CDs attached to magazines or books. Teacher writes on OO.o, students learn on KOffice. Or vice-versa. That's why I said "embedded into the .odt file". Of course, if (in the conditions above) there is any other solution which has the same end result for the student/user is OK, but is there? Ciao, Marco F. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
