Issue 23202 - Reversed Hebrew brackets/prentasis on printing when using type1 fonts
Summary: Reversed Hebrew brackets/prentasis on printing when using type1 fonts
Status: CLOSED FIXED
Alias: None
Product: gsl
Classification: Code
Component: code (show other issues)
Version: OOo 1.1
Hardware: All Linux, all
: P3 Trivial (vote)
Target Milestone: OOo 1.1.1
Assignee: ulf.stroehler
QA Contact: issues@gsl
URL:
Keywords: oooqa
Depends on:
Blocks:
 
Reported: 2003-12-04 16:07 UTC by eyalbens
Modified: 2004-01-29 17:50 UTC (History)
2 users (show)

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

Attachments
testcase (5.90 KB, application/octet-stream)
2003-12-10 13:56 UTC, sforbes 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description eyalbens 2003-12-04 16:07:02 UTC 
Writing with Hebrew (and maybe other bi-di langs), is working fine, and when you
writing brackets it's also working fine.
But when sending to printer the brackets are reversed so that:
'(' will became ')'
and ')' will transform into '('
but only on hebrew text.

This bug is tested and find to be exist in Ximian OO, OO1.1.0 in Debian, OO1.1.0
on Mandrake, Gentoo, Fedora.
Comment 1 sforbes 2003-12-08 09:47:50 UTC 
Can't repro with 1.1.0 on MDK 8.2 and HP Laserjet 4L printer.

Can you please give more information:
* Are you using the final 1.1.0 or one of the RC versions?
* What printer where you printing to?
* In OO, what are your local setting? Is CTL support enabled?
* In spadmin, in the printer properties, is the font replacement option enabled
or disabled?

Thanks
Comment 2 sforbes 2003-12-08 09:52:13 UTC 
adding myself as CC.

Also, can you please attach an example file?

THanks
Comment 3 eyalbens 2003-12-08 13:19:33 UTC 
Well if I dont wrong i have already told you that problem.

It's happend everywhere (execpt windows and mac?).
Im using the Final and not RC, im using Debian with CULMUS fonts that have been
detected automaticaly so i didnt need to use spadmin to config them.

Im printing using LPR and ivve tried using CUPS, but no different.
Altrough exporting to a PDF is working correctly, so all im doing right now is
exporting to PDF and then printing.. and I dont like this trick.

Ofcourse that CTL is enabled, and its happend wehn my locale is UTF8 and also
when it's he_IL.

The font replacemnt is enabled but not affected or replacing ny of my hebrew fonts.
I even diabled it.. no affect.
Comment 4 sforbes 2003-12-08 13:43:47 UTC 
Well, I am adding the needmoreinfo keyword, as I am unable to reproduce your
problem (OpenOffice prints Hebrew perfectly from my mandrake linux), and I don't
have enugh information here to pin down the diffrense between our setups (that
would help us isolate the problem).
Comment 5 sforbes 2003-12-10 13:55:35 UTC 
Confirming.
This happens only with the Culmus ( http://culmus.sourceforge.net/ ) fonts
(which are type 1).

True type fonts with Hebrew (like the MS core fonts) print correctly.

I am attaching a testcase file- compare the printed results of the MS core fonts
and the Culmus fonts.
Comment 6 sforbes 2003-12-10 13:56:37 UTC 
Created attachment 11865 [details]
testcase
Comment 7 hdu@apache.org 2003-12-10 15:19:02 UTC 
I'll take it.
Comment 8 hdu@apache.org 2003-12-10 16:57:07 UTC 
.
Comment 9 hdu@apache.org 2003-12-10 17:04:52 UTC 
Fixed in CWS vcl7pp1r4 for target OOo 1.1.1 and CWS vcl17 for target OOo2.
(Unsuspicious ASCII printer font subsets also have to be able to do mirroring)
Comment 10 hdu@apache.org 2003-12-18 15:06:40 UTC 
HDU->US: Please verify in CWS vcl7pp1r4.
Comment 11 ulf.stroehler 2004-01-06 18:27:52 UTC 
Changing resolution to FIXED in order to mark issue as VERIFIED.
Comment 12 ulf.stroehler 2004-01-06 18:29:01 UTC 
Issue VERIFIED in cws vcl7pp1r4.
Comment 13 ulf.stroehler 2004-01-22 16:30:02 UTC 
Re-verified on resynced cws vcl7pp1r4 with Type1 culmus fonts.
Comment 14 ulf.stroehler 2004-01-29 17:50:57 UTC 
ok in (internal) master workspace srx645_m27s1-1.8738.
Fix will be in forthcoming OOo 1.1.1.
Closing Resolved/Verified issue.