Peter Hillier-Brook wrote: > I think the confusion is with the term, "copy". I appreciate that the > converter is implemented via the "Save as" function, and that is where > the problem lies, but when converting a document to a new file format I > would expect to convert the complete document and not to view it as a > copy. Using "Save as" seems to have been a mis-judgement of the true > requirement: either that or a short cut that went wrong.
You named the problem exactly, there is no "Convert" API, so the converter uses "SaveAs" and this creates a problem because the semantics of the APIs don't match completely. So the bug was "built in" already, but it didn't show up until now (at least not in its full "beauty"). This also shows the direction where I'm searching for a workaround: give the "SaveAs" call a "Convert" instead of "Copy" semantics by applying a new parameter. > Accepting the foregoing, is my issue now an RFE, or do I have to start > again and make a specific request? The issue is still an RFE and you don't need to create a new one. I'm very thankful that you showed us this problem. :-) > Upgrading to a new software version with a new file format - guess who - > could have been difficult if the versions had been discarded during the > upgrade process. Obviously it was an internal discipline for us to > create a new transmittable copy of the document without the versioning > data and this did not prove to be a problem. Understood, you don't need to convince me that a document converter should keep all versions, the problem lies in a different area as you already described by yourself. > I would urge the development of a work around, for the corporate market > requirements mentioned earlier, if at all possible, but in any case I > would hope that you accept my reasoning? Yes, definitely, I never wanted to play down the problem itself. I'm still thinking that the "SaveAs" feature needs a redesign because the same use case as in the document converter might happen at runtime also: You load an sxw, modify and save it. OOo asks you to store as odt, you agree - and loose all your versions (because it is also done as a "SaveAs")! This makes me say: it's an RFE and we need more time. The document converter can possibly be fixed by the mentioned workaround (extending API call). Best regards, Mathias -- Mathias Bauer - OpenOffice.org Application Framework Project Lead Please reply to the list only, [EMAIL PROTECTED] is a spam sink. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
