Issue 71631 - Asian only: exported objects changes in size.
Summary: Asian only: exported objects changes in size.
Status: ACCEPTED
Alias: None
Product: Draw
Classification: Application
Component: code (show other issues)
Version: recent-trunk
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-11-16 15:54 UTC by fredrik.haegg
Modified: 2013-08-07 15:40 UTC (History)
1 user (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description fredrik.haegg 2006-11-16 15:54:28 UTC 
This is a StarSuite-only -bug: 
(Affected filetypes: BMP, EMF, MET, PCT, SVM, and WMF)

Example: when exporting a BMP-object which is 9 x 9 cm, 
the resulting file contains a BMP-object which is 90 x 90 cm. 

From the testlog: 
" Width is different expected: '9.00センãƒ' is: '90.00センãƒ' "

With other words: while the distance-Unit remains the same, 
the value for the size has multiplied with 10. 

= BUG.
Comment 1 fredrik.haegg 2006-11-17 11:28:17 UTC 
Ok, duno if you can read the signs after the 9.00 and 90.00, 
or if the browser only shows some questionmarks or similar, 
but it was the same Japanese signs. (=the same unit)
Comment 2 clippka 2006-11-17 11:36:18 UTC 
reassign
Comment 3 fredrik.haegg 2006-11-20 16:47:07 UTC 
A _very_ similar scenario happens when doing the same with a m4 on Linux, 
but then with English as language. (The size changes when exporting using 
the same formats, but the object shrinks instead of getting bigger)

= This is more important than 2.x. I therefore set it to 2.2.
Comment 4 pavel 2007-01-26 13:42:29 UTC 
Is this really StarSuite only? If so, can you please migrate this now-OOo-2.2 targeted bug into Sun private 
database?

fredrikh: how do you know this is StarSuite only relevant?

As the last comment is from Nov 20, reset target to 2.x.

Please set target when you know, it will be fixed in that version.
Comment 5 fredrik.haegg 2007-01-26 16:08:44 UTC 
I targeted this issue to 2.2 because two of my tests failed on machines where
Asian languages were installed. The same tests worked fine on the same machines
when Western languages were tested. And since those test were my export-tests
(eg i_export_graphics.bas and d_export_graphics.bas), which tests the complete
set of exporting-capabilities for the office regarding Graphics, I saw this as a
rather serious bug. (Asia is an important market) Which I really wished to have
seen fixed in 2.2.
Comment 6 sven.jacobi 2007-07-20 16:21:04 UTC 
I do not have enough time to fix this issue for OOo2.3, so I change the target.
Comment 7 sven.jacobi 2008-01-21 15:32:04 UTC 
changed target
Comment 8 sven.jacobi 2008-06-02 17:12:04 UTC 
changed target