Issue 15642 - Symbol incorrectly imported in 1.1b2 from 1.0.1
Summary: Symbol incorrectly imported in 1.1b2 from 1.0.1
Status: CLOSED FIXED
Alias: None
Product: Impress
Classification: Application
Component: code (show other issues)
Version: OOo 1.1 Beta2
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: ulf.stroehler
QA Contact: issues@graphics
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-06-15 18:33 UTC by pierrechanial
Modified: 2013-08-07 15:20 UTC (History)
1 user (show)

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

Attachments
1.0.1 file with a capitalized sigma (6.99 KB, application/octet-stream)
2003-06-15 18:36 UTC, pierrechanial 		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 pierrechanial 2003-06-15 18:33:23 UTC 
Symbols are incorrectly imported in 1.1b2 from 1.0.1

Steps to reproduce:
- open a new presentation OO 1.0.1
- insert a text using the Symbol font
- save
- open the file with OO 1.1b2

Expected behavior: see the greek symbols
Current behavior: instead of the greek symbols, we see roman letters.
Comment 1 pierrechanial 2003-06-15 18:36:11 UTC 
Created attachment 6901 [details]
1.0.1 file with a capitalized sigma
Comment 2 pierrechanial 2003-06-15 18:41:52 UTC 
Update: the bug is more serious than I thought:
If you open a new presentation in OO 1.1b2, insert a text with the
Symbol font (in linux), then typing letters in the keyboard will not
bring the greek letters, but the roman ones instead.

Inserting greek letters via the Special character dialog works for the
Symbol font, however.

IMO, it should be a 1.1 blocker.
Comment 3 wolframgarten 2003-06-19 12:13:44 UTC 
This is reproduceable on Linux but not on Windows. US suggested that
this might be a glyph fallback problem and that symbol fonts should be
excluded... Please contact him for further information.
Reassigned to Herbert.
Comment 4 hdu@apache.org 2003-06-20 10:14:33 UTC 
To me this all sounds like a charset mapping problem since 
the characters are there when the insert special character 
dialog is used. But I have to analyze it anyway to get an idea 
whom to forwar it to...
Comment 5 hdu@apache.org 2003-06-25 14:26:02 UTC 
What happens is that the unicode character U+0053 'Capital 
S' is used and this character is a postscript symbol font. For 
the display there is only an X11 symbol font which theoretically 
only has codes in the U+F020..U+F0FF range. So a fallback to 
a font which has a good Capital S is done. 
 
Fix is to allow aliasing of the symbol unicodes 
U+F020..U+F0FF to there "highbyte stripped counterparts" at 
U+0020..U+00FF. <rant> I still don't like this kind of symbol 
aliasing though. Originally it was used by programs with 
unicode as a hack to have better backwards compatibility with 
their 8bit ancestors but this hack has outlived its expiry date 
many times. </rant>
Comment 6 hdu@apache.org 2003-06-30 07:20:12 UTC 
Reassigning for verification in CWS VCL14.
Comment 7 ulf.stroehler 2003-06-30 10:24:35 UTC 
verified in workspace vcl14.
Setting to fixed in order to mark it verified.
Comment 8 ulf.stroehler 2003-06-30 10:25:22 UTC 
.
Comment 9 oc 2003-07-16 09:58:37 UTC 
Doesn't make it in OOo1.1RC, but will be integrated in OOo1.1Final
Comment 10 ulf.stroehler 2003-07-21 11:42:53 UTC 
OK in OOo RC2 (srx645_m13s2.8662).
Closing Issue.