To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=52786
User cmc changed the following:
What |Old value |New value
================================================================================
Issue type|DEFECT |PATCH
--------------------------------------------------------------------------------
------- Additional comments from [EMAIL PROTECTED] Thu Aug 4 04:22:49 -0700
2005 -------
When resaved in wordXP back to the word95/6 format then the font "Times New
Roman CE" which is used in the document has its "chs" field set to "238" which
is the correct encoding for CP1250. In the original document it is set to 0,
which is ANSI which is correctly set to CP1252. A chs field of 0 gets converted
to CP1252 as the equivalent to ANSI
So I believe that the filter is basically doing the right thing. So my suspicion
is that word is doing something like the following patch, i.e. assuming that 0
is not "ANSI" per-se, but set to default to the using the language of the text.
issue 22206 is relevent here. There the assumption was only to do this type of
guesswork if no default font was set, so this would be a superset of that
technique. So for testing, regression checks of the samples in issue 22206 is
indicated
---------------------------------------------------------------------
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]
