Open
Bug 990997
Opened 12 years ago
Updated 3 years ago
hebrew encoding (ISO8859-8) missing spaces while start the line (not render well) in plain/text mode
Categories
(Core :: Layout: Text and Fonts, defect)
Tracking
()
UNCONFIRMED
People
(Reporter: queency3, Unassigned)
Details
(Keywords: testcase)
Attachments
(2 files)
User Agent: Mozilla/5.0 (Windows NT 5.1; rv:27.0) Gecko/20100101 Firefox/27.0 (Beta/Release)
Build ID: 20140212131424
Steps to reproduce:
legacy system produce report in cp862 and firefox (in the past) could encode / render it well.
after firefox dropped support for cp862 i reencode it with bidi library to iso8859-8.
when render it again in firefox i noticed the whenever my lines ended with spaces
those spaces should be represented in the start of the line.
is seems that firefox (text/plain mode) forget to render those spaces in the start of the line
and then all my lines lost their margins
Actual results:
whenever using the old cp862 firefox encoding , i use the sign "_" as a space in this example
i get my report well aligned :
_874__eli______alelov____18/03/2014
__64__moshe___stakalov__18/04/2014
now whenever i use the iso8859-8 encoding i loose spaces and my alignment as well:
874__eli______alelov____18/03/2014
64__moshe___stakalov__18/04/2014
altough my hex code contains the spaces (code 20) !
Expected results:
the expected result is to be similar to the cp862 encoding
bring the spaces back !
| Reporter | ||
Comment 1•12 years ago
|
||
Comment 2•12 years ago
|
||
Please attach example files.
QA Whiteboard: [bugday-20140414]
Component: Untriaged → Layout: Text
Flags: needinfo?(queency3)
Keywords: testcase-wanted
Product: Firefox → Core
Comment 3•12 years ago
|
||
Code page 862 stands for Visual Hebrew, while ISO-8859-8 (ISO-8859-8-I) and (Windows-1255) stands for Logical Hebrew.
Given that said, please also note that plain text isn't well supported in Right-to-left texts, as the text will still flow from left to right, and you don't set your text direction to RTL.
My best idea would be to not only re-encode the outputs to ISO-8859-8, but also convert the output to an HTML output. If you don't like the idea of converting everything, you can keep it as plain text but add the following code snippet before the output "<pre dir='rtl'>" and "</pre>" after your content. Not the best solution and I recommend doing better job in converting to HTML, but it could serve as a quick workaround and a proof-of-concept for a better solution.
I'm attaching an example file. Please let me know if it is not exactly the problem you are facing.
Comment 4•10 years ago
|
||
Removing the testcase-wanted keyword as one was provided in comment 3.
Thanks,
Cipri
Keywords: testcase-wanted → testcase
Updated•3 years ago
|
Severity: normal → S3
Comment 5•3 years ago
|
||
Clear a needinfo that is pending on an inactive user.
Inactive users most likely will not respond; if the missing information is essential and cannot be collected another way, the bug maybe should be closed as INCOMPLETE.
For more information, please visit auto_nag documentation.
Flags: needinfo?(queency3)
You need to log in
before you can comment on or make changes to this bug.
Description
•