Issue 55068 - Font for CTL text incorrect after import from Excel
Summary: Font for CTL text incorrect after import from Excel
Status: CLOSED FIXED
Alias: None
Product: Calc
Classification: Application
Component: open-import (show other issues)
Version: OOO 2.0 Beta2
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: oc
QA Contact: issues@sc
URL:
Keywords:
: 57010 (view as issue list)
Depends on:
Blocks: 41707
  Show dependency tree
 
Reported: 2005-09-25 18:13 UTC by jjc
Modified: 2013-08-07 15:13 UTC (History)
2 users (show)

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

Attachments
Example of spreadsheet with CTL text whose font is not correct after import (13.50 KB, application/vnd.ms-excel)
2005-09-25 18:14 UTC, jjc 		no flags Details
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 jjc 2005-09-25 18:13:38 UTC 
CTL text in Calc has the wrong font after import from Excel 2003 (Thai edition).

Excel has a single font rather than distinct Western/CTL fonts.  The Excel font
gets mapped on import onto the OpenOffice Western font, so Thai (or other CTL)
characters get the default OpenOffice CTL font.
Comment 1 jjc 2005-09-25 18:14:50 UTC 
Created attachment 29887 [details]
Example of spreadsheet with CTL text whose font is not correct after import
Comment 2 frank 2005-09-26 11:25:24 UTC 
Hi Daniel,

you told me that Thai isn't in a special CTL table. So it's yours.

Frank
Comment 3 daniel.rentz 2005-09-26 12:26:20 UTC 
fixed in SRC680/dr41 (OOo 2.0.1)
Comment 4 daniel.rentz 2005-10-07 14:27:08 UTC 
back to QA

re-open issue and reassign to oc@openoffice.org
Comment 5 daniel.rentz 2005-10-07 14:28:13 UTC 
reassign to oc@openoffice.org
Comment 6 daniel.rentz 2005-10-07 14:28:36 UTC 
reset resolution to FIXED
Comment 7 frank 2005-10-19 14:16:42 UTC 
found fixed on cws dr41 on Linux, Solaris and Windows build
Comment 8 frank 2005-10-31 10:33:19 UTC 
*** Issue 57010 has been marked as a duplicate of this issue. ***
Comment 9 oc 2005-12-08 14:32:42 UTC 
closed because fix available in OOo2.0m145