|
Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
| Summary: | Asian characters in WMF displayed extremely condensed | ||
|---|---|---|---|
| Product: | gsl | Reporter: | zhipengzhang <zhipeng.zhang> |
| Component: | code | Assignee: | AOO issues mailing list <issues> |
| Status: | ACCEPTED --- | QA Contact: | |
| Severity: | Trivial | ||
| Priority: | P4 | CC: | hdu, issues, ooo, sven.jacobi |
| Version: | OOo 2.0.1 | Keywords: | oooqa, regression |
| Target Milestone: | OOo 3.x | ||
| Hardware: | All | ||
| OS: | All | ||
| Issue Type: | DEFECT | Latest Confirmation in: | --- |
| Developer Difficulty: | --- | ||
| Attachments: | |||
|
Description
zhipengzhang
2005-12-10 08:58:47 UTC
Created attachment 32262 [details]
the example
m142 is wrong, but m130 is right confirming issue. 2.0 does a better job than 2.0.1, OOo 1.1.5 does a better job than 2.0 a continous regression. Since the wmf-picture doesn't seem to be fully standard-compliant, I lower the prio. see the screenshots for comparison. Created attachment 32277 [details]
word viewer vs OOo 2.0.1 vs OOo 2.0
Created attachment 32278 [details]
word viewer compared to OOo 1.1.5 - as it should be.
MRU->SJ: the characters in the graphic seem to be too large, thus they are partly covering each other. In 1.1.x this looked better. sj->hd: The problem seems to be the font width that is given by the VDev in
svtools/source/filter.vcl/wmf/winmtf.cxx line ~300. There we use following code
to determine the font width:
if ( !rFont.lfWidth )
{
VirtualDevice aVDev;
aFont.SetSize( aFontSize );
aVDev.SetFont( aFont );
FontMetric aMetric( aVDev.GetFontMetric() );
aFontSize.Width() = aMetric.GetWidth();
}
If you skip the code everything looks all right. Please have a look and change
the target if you have a proper solution for OOo2.03.
Created attachment 34233 [details]
I can not see the words under the red circle, but MSWord can see it.
@SJ: for the font width calculation you are using a virtual device. Make sure you set the map mode for it to match the map mode of the device you are targeting at. This will avoid such funny problems like rounding issues and problems with asymmetric mappings. changed target target 3.0 changed target setting fix priority for 3.4 to P4. |