Created attachment 17110 [details]
bugdoc

The bugdoc works perfectly fine here on unxlngi5.pro SRC680m50_9.en-US on Suse91...
HDU->JW: please isolate the the problem to make it reproducable reliably

Other useful bug reporting hints:
- Setting the "OS where the problem occurred" to ALL, when the problem was only
seen for the unxlngi5.pro SRC680m50_8 build on a linux distribution (which one?)
creates a lot of unnecessary work...

- There usually is more than one "current" release (e.g. current end user build,
current  development build, current alpha release, etc.) and multiple people in-
and outside of Sun work on issues. More often than not there is a delay between
a problem is reported to the time people work on the issue, so
=> setting the "Version where the bug occurred" to "current" in the issue
tracker is not a good idea
=> I also requested that the "current" and obsolete versions get removed from
the Version listbox in issuetracker

.

this happens on a jds with a 680_m50-5 and 680_m50-9. if you like you can come 
an take a look on this again. the text looks good in an 680_m49 on the same 
system.

we can also confirm this on redhat system of us. in his opinion this depends on the 
fonts. 
reopend set target to OOlater.
this is not only a 680_m50 problem we can also confirm this on a 680_m49
the systems we tested it on have no tahoma font installed and the document 
default font is unknown

retested an still a bug

Reset assigne to the default "issues@openoffice.apache.org".