|
Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
| Summary: | double quote " become || | ||
|---|---|---|---|
| Product: | gsl | Reporter: | utomo99 <utomo.prawiro> |
| Component: | code | Assignee: | ulf.stroehler |
| Status: | CLOSED FIXED | QA Contact: | issues@gsl <issues> |
| Severity: | Trivial | ||
| Priority: | P5 (lowest) | CC: | issues |
| Version: | OOo 1.1 RC5 | Keywords: | oooqa |
| Target Milestone: | OOo 2.0 | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Issue Type: | DEFECT | Latest Confirmation in: | --- |
| Developer Difficulty: | --- | ||
| Attachments: | |||
|
Description
utomo99
2003-10-18 06:54:24 UTC
Created attachment 10429 [details]
double quote not correctly displayed
add ms_interoperability, oooqa keyword 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. closing. OK, look at attachements. It has relation with ms_interoperability. open the new doc, and you will not able to see " correctly Created attachment 10463 [details]
New doc, can see more easier double quote is not correctly displayed
Created attachment 10464 [details]
screenshot
Created attachment 10465 [details]
this is screenshot in ooo, look at the different
Utomo > CL: Now you can see that at least in 3 font, it is not correctly showed MS san serief System MS Serif no problem on linux, maybe a windows-only problem. Created attachment 10502 [details]
what the doc looks like on linux...
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 Reassigned to MRU 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 ;-) SBA: Target set to OOo 2.0. 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? 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...
reopening for reassignment. reopening for reassignment. reassigning HDU->US: please see my comment above, verify the fix for truetype fonts and split up a separate issue for the obsolete bitmap fonts... (@HDU: sorry I missed that the second bugdoc used Win 'fon' bitmap fonts.) Verified. |