Issue 13255 - showing nonprinting characters in a RTL paragraph wreaks havoc
Summary: showing nonprinting characters in a RTL paragraph wreaks havoc
Status: CLOSED FIXED
Alias: None
Product: gsl
Classification: Code
Component: code (show other issues)
Version: OOo 1.1 Beta2
Hardware: PC Windows 2000
: P3 Trivial (vote)
Target Milestone: OOo 1.1.1
Assignee: ulf.stroehler
QA Contact: issues@l10n
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-04-10 13:49 UTC by mehlng
Modified: 2004-01-09 11:19 UTC (History)
2 users (show)

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


Attachments
a document in which (apparently the comma causes) non-printing characters to destroy document. (7.83 KB, image/png)
2003-06-26 15:51 UTC, mehlng
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description mehlng 2003-04-10 13:49:08 UTC
When one shows the nonprinting characters of a RTL text it goes kaboom nothing's
clear.
Many concatenated spaces are being attached and all words are getting close
together with space-for-dots in between without the space.
Maybe the problem is that the inserted spaces are English LTR spaces.
Comment 1 Dieter.Loeschky 2003-04-22 11:31:30 UTC
DL->HDU: Would you please takeover?
Comment 2 hdu@apache.org 2003-04-30 07:12:10 UTC
HDU->US: Fixed in SRX644m12. 
Comment 3 hdu@apache.org 2003-04-30 07:13:49 UTC
Reopening to get it reassigned for verification. 
Comment 4 hdu@apache.org 2003-04-30 07:14:33 UTC
HDU->US: Please verify in >=SRX644m12 
Comment 5 hdu@apache.org 2003-04-30 07:15:22 UTC
Changing resolution back to FIXED after reassgning. 
Comment 6 thorsten.ziehm 2003-05-20 16:12:29 UTC
This task is fixed or worked in OOo 1.1 beta2.
Comment 7 mehlng 2003-06-26 15:46:51 UTC
this task simply doesn't work, the words order is reversed.
I just can't understand why do you think it's fixed.
Comment 8 mehlng 2003-06-26 15:51:01 UTC
Created attachment 7160 [details]
a document in which (apparently the comma causes) non-printing characters to destroy document.
Comment 9 ulf.stroehler 2003-08-05 11:35:12 UTC
us: again the old story: multiple problems in one task.
Submitter now seems to concentrate on full-stop and comma (a bugdoc
would have helped).
us->mehlng: pls. provide a simple "bugdoc" that shows the error. Thx.
us->hdu: I guess you already own a similar task but AFAIK in a
different bug tracking system.
Comment 10 hdu@apache.org 2003-08-05 12:00:58 UTC
It is very important to know which OOo version was used. 
 
As US already mentioned a bugdoc is very also important if only to know which 
font is being used. E.g. if the font does contain the "middle dot" U+00B7 and the 
"paragraph sign" U+00B6 the range of possible core reasons for the problem you 
are seeing is greatly reduced. 
Comment 11 mehlng 2003-08-06 11:11:10 UTC
It has been fixed apparently with the RC version general fixes. I
can't   remake it now
Comment 12 hdu@apache.org 2003-08-08 09:46:34 UTC
Great to hear this. There is so much going on and the issues 
in basetech are often so subtly related that "collateral fixes" 
are quite common. 
 
HDU->US: please verify and close. 
Comment 13 ulf.stroehler 2003-08-27 18:12:47 UTC
us->mehlng: if not reproducible any more, pls. close this issue. Thx.
Comment 14 mehlng 2003-08-27 22:17:20 UTC
issue closed.
Comment 15 ulf.stroehler 2004-01-09 11:19:25 UTC
Closing issue.