Issue 32911 - thai text is missformated; words are wronge drawn and font is to big
Summary: thai text is missformated; words are wronge drawn and font is to big
Alias: None
Product: gsl
Classification: Code
Component: code (show other issues)
Version: 680m50
Hardware: All Linux, all
: P3 Trivial (vote)
Target Milestone: AOO PleaseHelp
Assignee: AOO issues mailing list
QA Contact:
Depends on: 41671
  Show dependency tree
Reported: 2004-08-12 16:29 UTC by jack.warchold
Modified: 2017-05-20 11:30 UTC (History)
4 users (show)

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

bugdoc (11.05 KB, application/vnd.sun.xml.writer)
2004-08-12 16:29 UTC, jack.warchold
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description jack.warchold 2004-08-12 16:29:05 UTC
as shown you today
take a look on the attached bugdoc
Comment 1 jack.warchold 2004-08-12 16:29:37 UTC
Created attachment 17110 [details]
Comment 2 2004-08-13 10:16:36 UTC
The bugdoc works perfectly fine here on 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 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
Comment 3 2004-08-13 10:17:03 UTC
Comment 4 jack.warchold 2004-08-13 11:03:18 UTC
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 
Comment 5 jack.warchold 2004-08-13 11:56:36 UTC
we can also confirm this on redhat system of us. in his opinion this depends on the 
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
Comment 6 jack.warchold 2004-08-24 12:01:29 UTC
retested an still a bug
Comment 7 Marcus 2017-05-20 11:30:03 UTC
Reset assigne to the default "".