To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=51525 Issue #:|51525 Summary:|Ability to select code page on import of non-Unicode |text/document Component:|framework Version:|680m109 Platform:|PC URL:| OS/Version:|All Status:|UNCONFIRMED Status whiteboard:| Keywords:| Resolution:| Issue type:|FEATURE Priority:|P2 Subcomponent:|code Assigned to:|tm Reported by:|pmike
------- Additional comments from [EMAIL PROTECTED] Mon Jul 4 02:02:28 -0700 2005 ------- When importing a text in "native" encoding and there is no info about valid code page, OO defaults to ANSI code page. Plain text is a good example. This lead to corruption of any non-ANSI chars. A dialog with manual selection of code page for import would help a lot. Also, some "invalid" MSWord docs might be Unicode, but contain emedded objects with non-Unicode text. So, recoding ANSI->Unicode->Native for selected text_range/ objects will be also very useful. --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
