Hi, Jeongkyu Kim wrote:
> Hello, > > A Korean user posted a complaint that he lost his work after saving > the document into MS Word format. Later, it was found that he chose MS > Word 6.0 format which does not support unicode to save the document. > The result was critical. When he opened the document again, all Korean > characters turned into question mark. > > I understand the warning message for non-native filter could be one > way to prevent this kind of situation. However, the issue should be > addressed in better way because it is possible to cause data loss. > Before going to issuezilla, I'd like to discuss here on what is the > best way to handle the issue. > > A suggestion came up to me so far is to have different filter list for > each language version. For instance, MS Word 6.0 and 95 format filters > are almost useless and even dangerous for Korean users (unless we > implement application-level character set handling). Considering the > fact, I believe it is safe to hide those filters in Korean version. > However, I am not sure how practical the suggestion is. How do you > think? That's not easy. Even Koreans might want to write english documents, so removing all filters for formats that don't support UniCode might be a little bit too much. And think further: there are other missing features in certain formats that can render documents useless if you export it to them. As an example, think about a document containing a lot of complicated table structures and formattings that is stored into the "pure text" format or a document containing OLE objects stored as HTML document. So there are a lot of different possible losses to consider. To plan for every possible situation you have to analyze the document content before you can advise users about filters - not doable! So for the time being I think we are doing something acceptable - warn the users that they are writing to a lossy format and leave it up them to check what the documents contain that they have created. We could think about not clearing the "modified" flag of a document that was stored in an alien format, thus making this an "export", not a "save" operation - but that could be considered as annoying. Can we have "good" (those a user can "save" into) and "bad" (those users can only "export" to) alien formats? And which one is "good"? Only the latest Microsoft formats, so storing to all other alien formats will be considered as an export, not a "save" operation? Or should we allow to "save" in an alien format if the document was loaded in that format? All in all this is more a "user experience" than a developer question. Perhaps repeating it on the [EMAIL PROTECTED] list can give more insight. Regards, Mathias -- Mathias Bauer (mba) - Project Lead OpenOffice.org Writer OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS Please don't reply to "[EMAIL PROTECTED]". I use it for the OOo lists and only rarely read other mails sent to it. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
