Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | Unicode Surrogate Characters do not display | ||
---|---|---|---|
Product: | gsl | Reporter: | openoffice |
Component: | code | Assignee: | hdu <hdu> |
Status: | CLOSED IRREPRODUCIBLE | QA Contact: | issues@gsl <issues> |
Severity: | Trivial | ||
Priority: | P3 | CC: | issues, khirano, lohmaier, naoyuki.ishimura, stephan.bergmann.secondary |
Version: | 680m72 | Keywords: | oooqa |
Target Milestone: | AOO PleaseHelp | ||
Hardware: | All | ||
OS: | Windows, all | ||
Issue Type: | DEFECT | Latest Confirmation in: | --- |
Developer Difficulty: | --- | ||
Issue Depends on: | |||
Issue Blocks: | 41792 |
Description
openoffice
2005-01-11 14:55:52 UTC
dvo: On re-reading issue 31168: According to reinerg61, this also worked in OOo 1.1.4. He wrote additional info into that issue on details. . Seems to be introduced by the workaround against XP SP2's automatic ligatures in issue 27336, which got integrated in 680m64. please have a look at issue 45983 as well. This is a similar problem on linux, but without the surrogate-part (but I'm not sure what a surrogate-character should be, so maybe these two are the same). . In CWS vcl69 a crash when working with surrogate pairs on WIN platforms was fixed (#138843#). With the fix the display of surrogate pairs on WIN works. Since CWS vcl69 got into SRC680_m196 it will be in OOo 2.2 So the most approriate status for this issue is WORKSFORME then. Hi Hubert, Does this issue depend on Windows version? I've tried SRC680m9 with HG 明朝L Sun on XP and 2000, and found m9 works fine on XP, but not on 2000 (it does not show surrogate pair glyphs). Could you please clarify system requirement for this, if there are any? Thanks Naoyuki Confirming that OOo on Win2K has display problems with unicode surrogate pairs. I submitted issue 75450 for the Win2K specific aspect, since this issue is already overloaded (it started as "problem on all platforms" to "windows all" and now to win2K and older). The Issue you raised has been marked as 'Resolved' and not updated within the last 1 year+. I am therefore setting this issue to 'Verified' as the first step towards Closing it. If you feel this is incorrect, please re-open the issue and add any comments. Many thanks, Andrew Cleaning-up and Closing old Issues ~ The Grand Bug Squash, pre v3 ~ http://marketing.openoffice.org/3.0/announcementbeta.html As per previous posting: Verified -> Closed. A Closed Issue is a Happy Issue (TM). Regards, Andrew |