Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | Incorrect Handling of Surrogate Pair | ||||||
---|---|---|---|---|---|---|---|
Product: | Writer | Reporter: | xieqian <xieqian02> | ||||
Component: | code | Assignee: | AOO issues mailing list <issues> | ||||
Status: | CONFIRMED --- | QA Contact: | |||||
Severity: | Trivial | ||||||
Priority: | P3 | CC: | hdu, issues, khirano | ||||
Version: | OOo 1.1.2 | Keywords: | oooqa | ||||
Target Milestone: | --- | ||||||
Hardware: | PC | ||||||
OS: | Linux, all | ||||||
Issue Type: | DEFECT | Latest Confirmation in: | --- | ||||
Developer Difficulty: | --- | ||||||
Issue Depends on: | 40391, 45983, 105571, 105901 | ||||||
Issue Blocks: | 102943 | ||||||
Attachments: |
|
Description
xieqian
2005-02-01 11:46:00 UTC
looks like a writer issue (the issue with displaying the characters is handled in i40391) us->dvo: not sure whether this issue is already covered by issue 40391. Also I don't know if it's gsl or Writer. Could you pls. dispatch if not you and set an appropriate target. Thanks, Ulf. I have seen that this issue is OOo 1.1.2 related (which is rather old) and that the last entry was in February ... :( Have you tried this with OOo 1.1.3, 1.1.4 or some 1.9.xxx builds? Does your problem occur there, too? No, I didn't try these newer versions, because they are not handy. The reason cause the bugs is quite profound, I believe the phenomena will be there as long as OOo uses UTF-16 as internal coding format while some upper layer components calculate string length by counting 16-bit units rather than using some unified APIs. Redistributing dvo's issues. For me, It is covered with issue 45983 and issue 40391 (feel free to mark it duplicate) But anyway: This issue is already confirmed by different people but still unconfirmed → confirming. To get the relation to the other two surrogate issues (win & linux) I set those in the depends-on field. Retargeted to OOo later tra->mba: You might want to distribute this one insight your team Stephan can you help me distributing this issue to the right developer? @ama: As discussed with mba: The code in Writer that determines what has been selected appears to not take care of surrogate pairs. This issue has probably fixed indirectly via issues 105901 and issue 105571. If testing confirms that all is fine now I'd close it as a duplicate to 105901. Looking at issue 105571's desc15 the problem here can still occur because the fix I suggested in desc14 was not fully implemented there but only for scripts classified as CTL. Examples to reproduce it should use e.g. codepoints from the math symbols in U+1D400..U+1D7FF. Created attachment 71027 [details]
sample document using the non-BMP codepoints for the Phaistos disc
|