Issue 27293 - Arabic Support is severely borken
Summary: Arabic Support is severely borken
Status: CLOSED DUPLICATE of issue 28567
Alias: None
Product: Internationalization
Classification: Code
Component: code (show other issues)
Version: OOo 1.1.1
Hardware: PC Linux, all
: P2 Trivial with 2 votes (vote)
Target Milestone: ---
Assignee: hdu@apache.org
QA Contact: issues@l10n
URL:
Keywords: oooqa
Depends on:
Blocks:
 
Reported: 2004-04-01 11:08 UTC by kefah
Modified: 2013-08-07 15:00 UTC (History)
2 users (show)

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


Attachments
1.1.0 with correct font / text display (94.72 KB, image/jpeg)
2004-04-01 11:09 UTC, kefah
no flags Details
The broken text in 1.1.1 :-( (89.71 KB, image/jpeg)
2004-04-01 11:10 UTC, kefah
no flags Details
Different fonts and sizes. Red is bad, green is ok. (5.56 KB, application/vnd.sun.xml.writer)
2004-04-01 18:23 UTC, kefah
no flags Details
The problems also changes per page-size-view. This one is at 100% (59.18 KB, image/png)
2004-04-01 18:32 UTC, kefah
no flags Details
This is how it looks just by chaning the view size to page width (63.57 KB, image/png)
2004-04-01 18:32 UTC, kefah
no flags Details
OO 1.1.1 in Debian not having this issue (68.07 KB, image/png)
2004-04-08 17:21 UTC, bayazidi
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description kefah 2004-04-01 11:08:11 UTC
I was lazy to file this in the early 1.1.1 RC's, but I thought it would 
automatically be fixed.  
 
Anyway, the problem is arabic characters are severely broken, they get 
condensed to each other leaving the text totally unreadable.  
 
Please find the two attached screen shots for 1.1.0 and 1.1.1. Strange enough 
choosing certain sizes of the font would make it readable (but still 
improper). 
 
Steps to reproduce are straight forward: with OOo 1.1.1 and using any 
avaliable arabic font (you can make use of arabeyes.org if missing the last 
piece) , configure your keyboard for arabic, or cut and paste from an arabic 
website (bbcarabic.com makes a good source). 
 
This problem did not exist in 1.1.0. 1.1.0 had rendering issues that we could 
live with, I understand that most of those rendering issues have been resolved 
in 1.1.1 thank you for the awesome work. 
 
But still, this one is really really big. I would like to grap your strong 
attention to it and further more offer any kind of help you might find useful. 
I shall respond to you promptly for any requests. I shall not rest until OOo 
is useable for arab users again :-) 
 
Regards, 
- Kefah.
Comment 1 kefah 2004-04-01 11:09:56 UTC
Created attachment 14241 [details]
1.1.0 with correct font / text display
Comment 2 kefah 2004-04-01 11:10:57 UTC
Created attachment 14242 [details]
The broken text in 1.1.1 :-(
Comment 3 thorsten.ziehm 2004-04-01 11:45:06 UTC
Ulf could you have a look. This looks like a regression to OOo1.1.1 which has to
be fixed in OOo1.1.2. thx
Comment 4 ulf.stroehler 2004-04-01 14:33:04 UTC
us@kefah: think I got the point.
To be sure pls. attach a bugdoc (*.sxw) that demonstrates the error. Thx.
Comment 5 ulf.stroehler 2004-04-01 14:34:49 UTC
.
Comment 6 kefah 2004-04-01 18:23:52 UTC
Created attachment 14256 [details]
Different fonts and sizes. Red is bad, green is ok.
Comment 7 kefah 2004-04-01 18:24:43 UTC
I use Fedora Core 1 
Comment 8 kefah 2004-04-01 18:32:01 UTC
Created attachment 14257 [details]
The problems also changes per page-size-view. This one is at 100%
Comment 9 kefah 2004-04-01 18:32:56 UTC
Created attachment 14258 [details]
This is how it looks just by chaning the view size to page width
Comment 10 kefah 2004-04-01 18:34:29 UTC
The problem also manfestes when chainging the view zoom size. 
at 100% it would fix some and break others, at page width it would break the 
first, keep some as it, and keep others as is. see the related attachements 
for screen shots. 
Comment 11 ulf.stroehler 2004-04-06 19:45:13 UTC
US->HDU: broken glyphfallback for arabic (best reproduction on Linux) and hebrew
(best reproduction on Win2k). Pls. contact me for details and bugdocs.
Comment 12 bayazidi 2004-04-08 17:20:23 UTC
I use Debian, and the OpenOffice Debian Packages. I am currently using the
openoffice-1.1.1-1 packages from Debain sid (unstable) repositories. when I
tried to Open the sxw file attached with this bug it opened fine, without any
problem. I suppose that the Debian Patched with a fix to this issue. Or it could
be non-related to OpenOffice it self, and caused by some libs that Fedora have,
and OpenOffice use. Attached is a snapshot of how it looks in my OO 1.1.1
Comment 13 bayazidi 2004-04-08 17:21:57 UTC
Created attachment 14421 [details]
OO 1.1.1 in Debian not having this issue
Comment 14 bulbul 2004-04-11 21:58:23 UTC
See also issue 25565. Are these the same issue?
Comment 15 bulbul 2004-04-11 21:58:41 UTC
See also issue 25565. Are these the same issue?
Comment 16 bayazidi 2004-04-20 13:28:08 UTC
it turned out to be a bug in the freetype package that comes with Fedora. Once
freetype was build with certain patches, the problem disapeared. The OpenOffice
direct calls to FreeType, and not using XFT system, made issue hard to trace.
Luckily it is not an OO issue.
Comment 17 hdu@apache.org 2004-04-20 14:02:06 UTC
Very interesting. Do you know which version of freetype showed the problem and
which patches were applied to make it work? Was this discussed in another
(Fedora?) mailing list?

Anyway, since it is not an OOo problem I changing the status to INVALID.
Comment 18 hdu@apache.org 2004-05-06 09:35:48 UTC
HDU->bayazidi: do you know more details of the Fedora/Freetype problem or do you
have a link for these problems?
Comment 19 hdu@apache.org 2004-08-20 15:02:27 UTC
reopening for statsus change
Comment 20 hdu@apache.org 2004-08-20 15:03:41 UTC
Now understood that this is a duplicate to issue 28567.

*** This issue has been marked as a duplicate of 28567 ***
Comment 21 ace_dent 2008-05-17 21:34:24 UTC
The Issue you raised has been marked as 'Resolved' and not updated within the
last 1 year+. I am therefore setting this issue to 'Verified' as the first step
towards Closing it. If you feel this is incorrect, please re-open the issue and
add any comments.

Many thanks,
Andrew
 
Cleaning-up and Closing old Issues
~ The Grand Bug Squash, pre v3 ~
http://marketing.openoffice.org/3.0/announcementbeta.html
Comment 22 ace_dent 2008-05-17 23:37:42 UTC
As per previous posting: Verified -> Closed.
A Closed Issue is a Happy Issue (TM).

Regards,
Andrew