To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=40919
                  Issue #:|40919
                  Summary:|Anti Aliased fonts are illegible
                Component:|Word processor
                  Version:|OOo 1.1.4
                 Platform:|PC
                      URL:|
               OS/Version:|FreeBSD
                   Status:|UNCONFIRMED
        Status whiteboard:|
                 Keywords:|
               Resolution:|
               Issue type:|DEFECT
                 Priority:|P3
             Subcomponent:|ui
              Assigned to:|mru
              Reported by:|nbco





------- Additional comments from [EMAIL PROTECTED] Tue Jan 18 11:04:22 -0800 
2005 -------
I have the same problem with OO-1.1.3 and 1.1.4 package and source version. 
 
I am running freebsd 5.3-RELEASE with xorg 6.8.1.  
 
Fonts appear to overlap in both the OO interface and documents rendering 
certain letters illegible.   
 
I have a screenshot which I will happily send. 
 
I have tried the following fixes, none of which has helped at all: 
freetype2 
pango 
 
 - OpenOffice ships with own freetype library 
 libfreetype.so.9 
  - How built? 
   - Not built, it's in LIB_DEPENDS;  
     so where does it end up in the package? during build phase? 
  Referenced in setup log, but copied from package 
 
 Not in any sonames except: 
   libvcl645fi.so 
 
 elfdump it, check DT_NEEDED hints 
 
 - grep reports ref. strings does not. strings not looking in 
   all sections? 
 
 - elfdump reports refs in dynamic sections. 
ft_glyphslot_free_bitmap 
 
references ft symbols but does not appear to depend on it directly 
 (no DT_NEEDED) 
  -- assume that it's pulled in indirectly, walk DT_NEEDEDS 
ldd donut werk here 
 
persuade it to work: 
env LD_LIBRARY_PATH=`pwd` ldd libvcl645fi.so 
Throw an -a in to indirect 
 
 
fontconfig 
 
This points the finger at X... 
 
use lsof to inspect vm objects 
 -> freetype does not appear to be referenced in ANY WAY!! 
 
--> leads me to believe that X is where the truetype rasterization 
is coming from (using RENDER extension) 
 -> double check symbols (to be sure) 
  -> freetype was compiled STATICALLY!!! 
 
Xrender is referenced dynamically, but indirectly 
  interesting symbols? 
 
   -> so the finger indeed points to X. 
 
 
 -> Check xorg.conf font rendering modules in use. 
 
Leaving out fonts for now 
 
Load module confs: 
freetype 
xtt 
type1 
speedo 
 
Font paths: default. 
 
Check x startup logs 
 
[1]  +  2895 Suspended                     sudo view Xorg.0.log 
 - grep for 'Loading fontXXXX' 
Check font path, fonts.dir errors, etc 
 
 - Have there been backend changes? 
 
Theories 
 
 - font path problems, missing font.dir, metrics etc -> further research 
   may be needed 
 - corrupt glyphs -> file corruption of .ttfs 
 - wrong charset for ttf file 
 - fonts shadowed in path, ie kosher fonts present, but above behaviour 
   preventing good render 
 
 - rendering has changed - xtt has been depracated in 6.8.0 
 
check xorg-fonts-encodings port is present 
  - yes, files are present, except for encodings.dir 
    which is zero length 
 
 - double check, perform 'locate encodings.dir | xargs ls -l" 
   last updated dec 23, many of the encodings.dir files on the 
   affected system are *actually* symlinks pointing to the 
   zero length main encodings.dir file. 
 
suggest rerunning mkfontdir appropriately 
 
date Dec 23 of zero length encodings.dir 
 
 - Attempt to resolve encodings.dir issue by: 
   1. running mkfontdir -e in main encodings dir 
   2. xset fp rehash 
 
  - Does not resolve OO problem 
  - Can't confirm it fixes the freetype encodings errors in Xorg.log 
 
  - No encodings file specified in xorg.conf 
   - Is there such a directive? 
   - No. Font encodings are looked for in one central compiled-in 
     path, and each individual font directory. 
 
 
font path elements reorganized, did not resolve. 
 
many invalid font path elements. 
 
try removing user font paths et cetera, trim the fat down. 
 xset fp default && xset fp rehash --> does not resolve 
 
trimming font path on startup, after eliminating bad font path 
elements 
 -- no resolve 
 
try flip to default to lose kde added user defaults, rehash, 
and rerun 
 -- no resolve 
 
force *all* fontconfig cache files to be rebuilt in the system 
like we really mean it -- 
 -- does not resolve 
 
force all encodings.dir files in the system to be regenerated, 
including the removal of symlinks 
bounce x/kde 
check x error log 
 -- startup ok, no failure mode as known introduced 
resolution? 
 -- does not resolve 
 
truetype font files in a bitmap directory 
 - looks odd. 
 
latin2 element may be bunk, try removing it 
 -- no resolve 
 
futz with /usr/X11R6/etc/fonts/local.conf to tweak freetype/fontconfig 
rendering settings, specifically disabling autohinting 
 -- no resolve 
 
creating a symlink to encodings.dir in openoffice's fonts directory 
 -- no resolve 
 
finally, check freetype and pango versions installed 
pango-1.6.0 
freetype2-2.1.7_4 
 
check for any legacy libraries 
 no freetype version 1 in sight, mine has, unused apparently 
freetype versions in sync with mine 
 
deleted and reinstalled truetype fonts 
re-installed openoffice 
no resolve

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to