Issue 119692 - the fontwork shape:ring outside is not imported correctly.
Summary: the fontwork shape:ring outside is not imported correctly.
Status: CONFIRMED
Alias: None
Product: Calc
Classification: Application
Component: open-import (show other issues)
Version: 3.4.0
Hardware: PC All
: P3 Normal (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks: 120823
  Show dependency tree
 
Reported: 2012-06-04 05:26 UTC by Du Jing
Modified: 2012-09-06 13:20 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments
sample file (40.00 KB, application/vnd.ms-excel)
2012-06-04 05:26 UTC, Du Jing
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description Du Jing 2012-06-04 05:26:40 UTC
Created attachment 77903 [details]
sample file

build info:AOO3.4_1327774

Steps:
1.open the sample in the AOO3.4
2.check the fontwork shape

defect:
it display incorrectly,when open the sample in MS office,it can display correctly.
Comment 1 binguo 2012-06-12 05:26:46 UTC
This bug can repros on AOO3.4.O Rev. 1327774,
and I change the status from Unconfirmed to confirmed.
Comment 2 Armin Le Grand 2012-09-06 13:20:46 UTC
ALG: The difference is that the filling looks different.

- in MS, all character-polyPolygons are put into a single PolyPolygon, thus e.g. the 'o' and 'u' overlapping is transparent (see better when copying object to PPT and choosing a fill style).
- In AOO, each single charater is a filled PolyPolygon, so the overlappings depend on the order in which these are painted.

In principle I would guess that's it an error in MS that a single PolyPolygon is used (and not a group of one PolyPolygon per character). Thus it is questionable to call this the 'correct' viszualisation.

On the other hand it is an error on our side that the ordering of the shapes makes it look wrong, e.g. the 'u' should be painted first so that the 'o' overlaps it. The order of painting seems to rely simply on character order. This could evtl. be fixed by sorting 'mirrored' characters to the back.