To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=61927





------- Additional comments from [EMAIL PROTECTED] Tue Apr 29 11:14:09 +0000 
2008 -------
FWIW, on export we use "GetPseudoCharRuns" in writerwordglue.cxx to split the
text of a paragraph into character runs, and for a WW6 we break those runs down
so that they comprise of characters that can all be rendered with the same 8bit
font with a mapping like..

... { UnicodeScript_kLatin1Supplement, 
UnicodeScript_kLatin1Supplement,
RTL_TEXTENCODING_MS_1252}, ...

So you can check if the exported characters are getting an appropiate export
TEXTENCODING as the meCharSet member of a CharRun in there.

For each WW8_SwAttrIter::OutAttr we force a "if not WW8 force the font encoding
to the run's charset" which should set the font for that range correctly for
ww6/95 if it is different from the underlying style

Meanwhile in importing we have SwWW8ImplReader::ReadPlainChars where for WW6 we
call GetCurrentCharSet to figure out the charset that the 8bit text is in. So if
e.g. the export is working but not the import then the right font *should* have
shown up during import in SwWW8ImplReader::SetNewFontAttr with the same
eSrcCharSet that we exported and should be at the top of maFontSrcCharSets and
available for use by ReadPlainChars

---------------------------------------------------------------------
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]

Reply via email to