Thanks to Simon for committing this patch. Let me provide some additional information that will help evaluators or reviewers:
- this work is being developed in the Temp_ComplexScripts branch of the FOP SVN repository, and, when appropriate, will be merged into the main development trunk; however, that will not occur until the new features in this branch are completed, new test suites are created and verified, and sufficient time has passed to ensure appropriate evaluation and verification by the FOP community; - the present state of this work is PRE-ALPHA; as such, it is not yet feature complete; therefore, anyone attempting to use this work should expect to find incomplete or incorrect results as well as programming errors resulting in abnormal termination, etc; so, caveat emptor please! - some preliminary documentation of this work is available at https://skynav.trac.cvsdude.com/fop/wiki; as work progresses, this documentation will be better organized and transferred to the FOP Wiki and Documentation pages; - during the development of this branch, known issues on this work are being tracked at https://skynav.trac.cvsdude.com/fop/report; after this branch is merged into the development trunk, new bugs and issues will be tracked in the Apache bugzilla database; - initial support is focused on Arabic script support, which entails the support of complex character to glyph mapping (sometimes referred to as 'glyph shape selection' or 'glyph substitution') and bidirectional processing; - currently supported fonts (that I have tested to some extent, but not completely) are documented at https://skynav.trac.cvsdude.com/fop/wiki/SupportedFonts; this list will be expanded over time; - no use is made of external libraries or platform specific libraries; e.g., ICU4J is not used; the platform fonts are used directly to provide advanced typographic table support (about which see https://skynav.trac.cvsdude.com/fop/wiki/ComplexScriptFeatures); - no testing on output renderers other than PDF and AT (XML area tree) has taken place yet; so please restrict your usage to PDF in the near term; Now, here are some additional useful points to make about current limitations or known issues that apply. Please read the Active Issues report in the above referenced TRAC site for further details: - non-spacing marks are not yet supported, and their use in content will cause noticeable problems; this is the current top priority issue, since support for a number of such NSMs is mandatory even in non-vowelized (non-pointed) Arabic; - use of text-align='justify' does not produce correctly justified lines when Arabic is present; - correct semantic support for "writing mode relative corresponding properties" is not yet present, and, as a result text-align='right' is not implied for blocks that have a default bidi level of 1 (right to left), so you will need to explicitly add text-align='right' to achieve correct alignment; - support for inline FOs in bidi contexts is presently limited to fo:inline, fo:bidi-override, and fo:character; support for the remaining inline FOs will be added in an upcoming update to this branch; - full testing of bidi level assignment and reordering has not yet occurred, so some errors should be expected; the same applies for arabic shaping rules (i.e., presentation glyph selection); Keeping the above in mind, please do try out this preliminary work and report to me or to this list any issues that you find. When you do find an issue, try to isolate the input FO file to the absolute minimum amount of content that causes the problem. If I have to look through a long input file (and output PDF) for a small problem I am more likely to put that on the bottom of my queue, and not on the top. In other words, if you are going to take the trouble to report something, then please help me out by reducing the problem to its bare minimum form. Furthermore, when posting issues, please provide the output PDF file as well as. Regards, Glenn On Fri, Aug 20, 2010 at 4:35 AM, Simon Pepping <spepp...@leverkruid.eu>wrote: > We are happy to let you know that Complex Script Support for FOP is > under development. Glenn Adams is developing this functionality on > behalf of Basis Technologies. > > To make this development efficient and successful, we need your > contribution as well. Does your native language use complex scripts > and perhaps right-to-left writing mode (Arabic, Hebrew, Indic > scripts)? Then install this version of FOP and test it with some of > your XML or FO files. Report your findings on this mailing list. > > We will announce updates of this work on this mailing list. > > You can download the binary distribution or the fop jar file from > http://people.apache.org/~spepping/. > > You can check out the source code from FOP's subversion repository, > > http://svn.apache.org/repos/asf/xmlgraphics/fop/branches/Temp_ComplexScripts > . > > You can follow the work at FOP's Bugzilla, bug nr. 49687, > https://issues.apache.org/bugzilla/show_bug.cgi?id=49687. > > Simon > > -- > Simon Pepping > home page: http://www.leverkruid.eu > > --------------------------------------------------------------------- > To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org > For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org > >
