Gary Schnabl wrote:
Is there really any value in a broad-brush listing of the thousands of functions of one suite, say, MSO that can be done on OOo or not?
I wasn't suggesting anything like that (or were you talking in more general terms than the tables in Ch1 of GS?). Those tables (repeated in Ch1 of the Migration Guide) are fairly high-level. The Marketing document I mentioned may be more extensive, but all I suggested was that someone could extract from it the info needed to update the existing tables.
Your comment does bring up a related, and important, question, though: are the tables in the current GS valuable? Should we delete the comparisons and focus solely upon OOo? I don't have a strong opinion either way. (And I didn't do the original tables in GS, so I don't have any personal stake in retaining them.)
I believe that the Migration Guide should revolve upon the usual authoring/editing functions that pose problems going in direction or the other. [...] it would be advantageous to know in advance what to avoid with one application that won't work with another application. These are typically only learned through experience: either one's personal experience or one derived from reading about them. The Migration Guide should serve this latter function, in addition to whatever else it does.
I agree, that is something that very much needs to be in the Migration Guide. It's one of the many items we wanted to include several years ago, but no one was available to do the necessary research and writing. I'm very glad to see someone interested in taking on this task.
--Jean --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
