Hi Jonathan,

Arabic script is not trivial...
- text pads (or more generally file viewers) can have different behavior, depending on how Arabic script is managed:
   - either Arabic script is recognized correctly:
       - it is displayed in right-to-left mode,
       - Arabic character shaping (IOW: inner word ligatures) is OK
       - ex: Firefox, IE, Win notepad, babelpad, etc.
- (try to select a part of Arabic script, this is funny when Arabic and Latin scripts are mixed)
   - or Arabic script is not recognized:
       - Arabic script is displayed char-by-char
       - default writing mode is used (left-to-right for latin scripts)
       - ex: Jedit

- FOP doesn't implement writing-mode (see [1])
- however, you can apply the patch #42307 (see [2]) and rebuild FOP from source, it gives acceptable result.

- FOP doesn't manage Arabic character shaping

For further information, there are some Unicode materials:
- bidirectional algorithm: see [3]
- Arabic character shaping: see [4] (PDF file)

[1] http://xmlgraphics.apache.org/fop/compliance.html#fo-property-writingmode-section
[2] https://issues.apache.org/bugzilla/show_bug.cgi?id=42307
[3] http://unicode.org/reports/tr9/
[4] http://www.unicode.org/versions/Unicode5.2.0/ch08.pdf#G20596

Note that developpers that have good knowledge about Arabic layout will be welcome to help FOP team.

Pascal


Jonathan Levinson a écrit :

Attached is an fo file which shows a problem we have printing Arabic text. The text is printed in the wrong order, the opposite of the order it occurs in the file. It renders right to left but the order in the file is left to right.

The file is UTF-8 and we are using FOP-0.95. In the fop.xconf file, in the fonts section, we have <auto-detect/>. This allows FOP on Windows XP to auto-detect the Arabic font.

Does anyone know a solution to this problem in rendering Arabic text?

Best Regards,

Jonathan Levinson



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to