Issue 21393 - double quote " become ||
Summary: double quote " become ||
Alias: None
Product: gsl
Classification: Code
Component: code (show other issues)
Version: OOo 1.1 RC5
Hardware: PC Windows XP
: P5 (lowest) Trivial (vote)
Target Milestone: OOo 2.0
Assignee: ulf.stroehler
QA Contact: issues@gsl
Keywords: oooqa
Depends on:
Reported: 2003-10-18 06:54 UTC by utomo99
Modified: 2004-08-26 17:11 UTC (History)
1 user (show)

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

double quote not correctly displayed (22.50 KB, application/octet-stream)
2003-10-18 06:55 UTC, utomo99
no flags Details
New doc, can see more easier double quote is not correctly displayed (19.50 KB, application/octet-stream)
2003-10-20 04:18 UTC, utomo99
no flags Details
screenshot (19.34 KB, image/gif)
2003-10-20 04:20 UTC, utomo99
no flags Details
this is screenshot in ooo, look at the different (16.28 KB, image/gif)
2003-10-20 04:21 UTC, utomo99
no flags Details
what the doc looks like on linux... (50.04 KB, image/png)
2003-10-20 21:28 UTC, lohmaier
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description utomo99 2003-10-18 06:54:24 UTC
If we open doc file, in some Font, double quote" is not shown correctly, it is
shown as ||

look at attachements
Comment 1 utomo99 2003-10-18 06:55:42 UTC
Created attachment 10429 [details]
double quote not correctly displayed
Comment 2 utomo99 2003-10-18 06:56:23 UTC
add ms_interoperability, oooqa keyword
Comment 3 lohmaier 2003-10-18 12:04:00 UTC
closing as worksforme. Has nothing to do with ms_interoperability.

The only font where " is not displayed is the "Symbol" font wich
doesn't contain the quote character.. This is a symbol-font where a
replacement by characters of another (text-)font is not possible. If
Symbol-Font would contain the quotes-glyph it would be displayed.

I see no errror. This report is btw. not very clear "somewhere in the
document" is not very precise. Maybe you supplied the wrong
attachment. If so, please reopen.
Comment 4 lohmaier 2003-10-18 12:04:21 UTC
Comment 5 utomo99 2003-10-20 04:18:01 UTC
OK, look at attachements. It has relation with ms_interoperability. 
open the new doc, and you will not able to see " correctly
Comment 6 utomo99 2003-10-20 04:18:56 UTC
Created attachment 10463 [details]
New doc, can see more easier double quote is not correctly displayed
Comment 7 utomo99 2003-10-20 04:20:09 UTC
Created attachment 10464 [details]
Comment 8 utomo99 2003-10-20 04:21:06 UTC
Created attachment 10465 [details]
this is screenshot in ooo, look at the different
Comment 9 utomo99 2003-10-20 04:22:59 UTC
Utomo > CL:
Now you can see that at least in 3 font, it is not correctly showed
MS san serief
MS Serif
Comment 10 lohmaier 2003-10-20 21:27:23 UTC
no problem on linux, maybe a windows-only problem.
Comment 11 lohmaier 2003-10-20 21:28:34 UTC
Created attachment 10502 [details]
what the doc looks like on linux...
Comment 12 utomo99 2003-10-21 06:23:33 UTC
If we see screenshot on Linux, it is OK. 
But if we see screenshot on Windows it is problem. 
I think I agree with you that it maybe a windows problem. I tested on
win XP
Comment 13 h.ilter 2003-10-21 10:55:04 UTC
Reassigned to MRU
Comment 14 michael.ruess 2003-10-21 16:25:50 UTC
Christian is right, it is not an interoperability issue. It is to be
found in the font replacement. Some fonts do not have these quote
symbols, and SO seems not to choose a proper font when such
"undefined" symbols are displayed. You can see, that the characters
are correctly imported, when you choose e.g. "MS Serif" to be replaced
by "Courier" on the screen.

MRU->US: are there already any issues regardig this problem? I guess,
it is not new to you ;-)
Comment 15 stefan.baltzer 2003-10-23 15:19:23 UTC
SBA: Target set to OOo 2.0.
Comment 16 ulf.stroehler 2004-07-29 13:42:48 UTC
us->hdu: unfortunately the problem persists; even in 680s fontlist02 cws.
Windows only. Pls. try utomo's latest bugdoc.
Is this the famous glyphfallback issue on Win32 systems?
Comment 17 2004-08-02 16:40:58 UTC
The fonts in the bugdoc are bitmap fonts. The improved glyph fallback feature
only works when the glyph availability of the selected font can be determined.
Currently this only works for truetype fonts but not for bitmap fonts (ugh!).
AFAIK there is no way to determine the unicode coverage of bitmap fonts on all
supported Win32 platforms without direct access to the font files. Even if the
font files could be accessed the gain of support these obsolete font formats is
not worth the effort... especially since we cannot print or embedd them anyway...

HDU->US: Nowadays truetype fonts are by far the most important font format on
Win32 platforms. I suggest to verify the fix for truetype fonts in a milestone
>= SRC680m48 (which contain the famous CWS fontlists02). Then split up an issue
for the obsolete bitmap fonts with an appropriate target...
Comment 18 2004-08-02 16:41:33 UTC
reopening for reassignment.
Comment 19 2004-08-02 16:42:09 UTC
reopening for reassignment.
Comment 20 2004-08-02 16:42:39 UTC
Comment 21 2004-08-02 16:44:47 UTC
HDU->US: please see my comment above, verify the fix for truetype fonts and
split up a separate issue for the obsolete bitmap fonts...
Comment 22 ulf.stroehler 2004-08-26 17:11:46 UTC
(@HDU: sorry I missed that the second bugdoc used Win 'fon' bitmap fonts.)