|
Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
| Summary: | fonts displayed are thin, weak, malformed | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Writer | Reporter: | vgivanovic <vladimir> | ||||||||
| Component: | ui | Assignee: | eric.savary | ||||||||
| Status: | CLOSED NOT_AN_OOO_ISSUE | QA Contact: | issues@sw <issues> | ||||||||
| Severity: | Trivial | ||||||||||
| Priority: | P2 | CC: | caolanm, fonts-bugs, hdu, issues, stefan.baltzer | ||||||||
| Version: | DEV300m19 | Keywords: | needmoreinfo, oooqa | ||||||||
| Target Milestone: | --- | ||||||||||
| Hardware: | PC (x86_64) | ||||||||||
| OS: | Linux, all | ||||||||||
| Issue Type: | DEFECT | Latest Confirmation in: | --- | ||||||||
| Developer Difficulty: | --- | ||||||||||
| Attachments: |
|
||||||||||
|
Description
vgivanovic
2008-06-14 15:46:18 UTC
Created attachment 54479 [details]
Screenshot of oowriter-2.4.1 (fonts OK)
Created attachment 54480 [details]
Screenshot of oowriter-3.0m19 (fonts not OK)
Just in case it's thought that I have a Fedora system, I do not. I'm running a fully updated Gentoo AMD 64 laptop: uname -a -> Linux scarlatti 2.6.24-gentoo-r8 #2 PREEMPT Sat Jun 7 13:29:30 PDT 2008 x86_64 AMD Turion(tm) 64 Mobile Technology MT-32 AuthenticAMD GNU/Linux Please also attach a smple document. Created attachment 54498 [details]
source document for both images
Can't confirm (no fonts or Gentoo, so I may be completely off-mark) but I can say that although the fonts on the two screenshots appear different, the relative spacing is identical, so visual differences in glyph outlines appear to be the result of rendering/hinting (the oowriter-2.4.1 version is properly hinted, either either grayscale or whatever the Gentoo equivalent to ClearType is, whilst the 3.0 version isn't). My guess is something up with Freetype 2.3.6. This is not a P2. No crash, no loss of data. No discussion on this please. If all submitters could set their "personal priority", then ALL issues would be a P1 and show stoppers. Makes no sense as then there would NEVER ever be a final version. Does not work withour rules that everybody follows. See http://www.openoffice.org/scdocs/ddIssues_EnterModify.html#priority Set to P3. Thanks for your comprehension. I spoke to hdu on this. We believe that cairo text rendering in involved in your problem. Set CMC on cc. See issue 85470 for details of the cairo integration. Please try the following: Quit office and all its processes, set the environment variable SAL_ENABLE_CAIROTEXT to 0 (Default is 1), Then restart the office (from the shell you set the variable of course :-=) and look at the document. Please comment, thx. Set CCs. Its always a possibility. What I also like to see are the font settings, a screenshot of the fonts tab in gnome-appearance-properties should suffice to see what they are, and the output of fc-list. Are these fonts available anywhere for download ? (or does it happen with easier to get fonts like "Liberation" or "DejaVu") Where does it say that P2's HAVE to involve crashes or loss of data??? It is a bug that HAS NO WORKAROUND. It is a bug that makes one NOT USE the product. A major feature, DISPLAY OF TEXT, is broken. It is a MAJOR usability problem. It HAS TO BE FIXED for the next release. Seems like a P2 to me. I used to work in SQE, for Sun as a matter of fact, and I get really, really upset when I see cases where people play with priority or severity just to get around fixing a bug for a release. It is dishonest as well. At this point I'm so disgusted with the behavior of 'sga' that I'm simply going to close the bug. I want no further association with this issue. @vgivanovic: Please calm down. I can understand you are upset but let people who fix the issues set the priority according to rules AND ressources. In the end, the priority is not that important if the bug is fixed, right? ;) Now your bug has the correct - on your opinion - prio but is closed. That's neither what you wanted. So please reconsider, do what SBA and CMC asked/adviced you to do and comment. Thanx! Reopening @es I re-reviewed the criteria for priority, and I did not see any mention of resources. I understand that resources are alway finite, but that should only affect the order in which the bugs are fixed. What's happening here is a P2 is being swept under the rug in order to make a release, rather than shipping with open P2's. In both cases, the product is the same, the bug is not fixed, but one case is honest, the other dishonest. Since I have seen no reason (yet) to change my mind about these issues, and since I suspect that you folks are equally unmoved, perhaps we should just drop the discussion and get on with our lives. @vgivanovic: the purpose of my comment was not to discuss about prio but to make you focus on the bug, the things CMS/SBA asked you, in order to make this issue move further. Apparently you're stucked on that prio argument and don't want to give us more valuable info. Up to you. I'll then close as "invalid" for we cannot get all the info we need. Feel free to reopen if you change your mind and can provide this info. closed Yes, I am stuck on the "priority issue". I think the stated criteria should be followed, or the criteria should be changed. If you'd like me to or you want to reopen this bug as a P2, I'll follow up with the requested information. |