Re: Question about status of Bidi support, and Arabic/Persian shaping!
Hi all, Jeremias Maerki <[EMAIL PROTECTED]> wrote on 05/05/2006 02:43:26 AM: > I think it is preferrable to reuse code from the Java class library if > it covers our requirements (among them: maintain JDK 1.3 compatibility). > Sadly that means that java.text.Bidi is a little problematic, except if > we say that Bidi support is only available under JDK 1.4 but that might > complicate the implementation additionally. java.awt.Font.TextLayout does Bidi layout. This is how Batik gets it's display order information. > If we can reuse code from our sister project Batik, that's probably > better. Introducing an external library will take careful consideration. > We have to make sure, among other things, that the licensing situation is ok. You are more than welcome to use Batik code. However all of Batik's text handling is built around the JDK's AttributedString class, which may not be that compatible with FOP's text handling. > Please also look through the fop-dev mailing list archives for any > discussions around Bidi and UAX#14. I think the two aspects may be closely > related. The two are mostly independent in Batik's implementation. > On 05.05.2006 01:00:04 Kia Teymourian wrote: > > Dear developers, > > > > I’m interested to use FOP for creating Documentation with complex text > > layout languages such as Arabic/Persian. > > I would like to offer my help for the implementation of Bidi Algorithm > > (Bug 32789) > > > > I search on the FOP-User mailing list and found, this discussion. > > http://www.mail-archive.com/fop-users@xmlgraphics.apache.org/msg01575.html > > > > I’ve done the initial steps and establish myself a development environment, > > and could render a Unicode String for the Arabic Unicode shaping > > here is the PDF output and the fo file: > > > > http://user.cs.tu-berlin.de/~kiat/fop/simple.pdf > > http://user.cs.tu-berlin.de/~kiat/fop/simple.fo > > > > This test PDF output shows that the words in Arabic/Persian should be > > rendered for ligature glyphs characters Unicode Arabic Presentation form. > > And there is no problem with the Arabic shaping for Text, RTF output. > > > > Is there anyone who works on Bidi implementation? > > > > Should the Bidi Implementation be an awt independent solution? > > Could we use jdk 1.4 and classes like java.text.Bidi or > > java.awt.font.TextLayout? > > > > I looked around for Bidi implementation and found Fribid, > > http://fribidi.org/wiki/ which is implemented in C. > > > > iText project has also some Bidi classes like > > class com.lowagie.text.pdf.ArabicLigaturizer > > class com.lowagie.text.pdf.BidiLine > > class com.lowagie.text.pdf.BidiOrder > > > > Or we can use Batik classes like > > org.apache.batik.gvt.text.ArabicTextHandler.java > > > > I think the first point should be the implementation of > > > > org.apache.fop.fo.flow.BidiOverride.java > > org.apache.fop.layoutmgr.inline.BidiLayoutManager.java > > > > And then add some classes for the Arabic character shaping like > > ArabicLigaturizer. > > The bidi-Override implementation is very useful for some other projects > > to be able to > > create Persian/Arabic Documentation with PDF output from DocBook files. > > > > Regards, > > Kia Teymourian > > > > > > > > > > Jeremias Maerki >
Re: Question about status of Bidi support, and Arabic/Persian shaping!
On Fri, 2006-05-05 at 10:59 +0200, Jeremias Maerki wrote: > On 05.05.2006 10:51:35 Peter B. West wrote: > > On Fri, 2006-05-05 at 08:43 +0200, Jeremias Maerki wrote: > > > This is good news. I did not study the problems around non-LTR texts so > > > I can't say anything useful about this. > > > > > > I think it is preferrable to reuse code from the Java class library if > > > it covers our requirements (among them: maintain JDK 1.3 compatibility). > > > Sadly that means that java.text.Bidi is a little problematic, except if > > > we say that Bidi support is only available under JDK 1.4 but that might > > > complicate the implementation additionally. If we can reuse code from > > > our sister project Batik, that's probably better. Introducing an > > > external library will take careful consideration. We have to make sure, > > > among other things, that the licensing situation is ok. > > > > > > I don't know of anyone currently working on a Bidi impementation. If > > > someone does, I expect that person to speak up. > > > > > I am. Using Java 1.5 for the basics, and Java 1.6 for kerning and > > ligatures. I suppose you were aware of that though. > > Well, the requirement for 1.5 or even 1.6 pretty much rules out your > implementation for us. > > > Jeremias Maerki :) Peter
Re: Question about status of Bidi support, and Arabic/Persian shaping!
On 05.05.2006 10:51:35 Peter B. West wrote: > On Fri, 2006-05-05 at 08:43 +0200, Jeremias Maerki wrote: > > This is good news. I did not study the problems around non-LTR texts so > > I can't say anything useful about this. > > > > I think it is preferrable to reuse code from the Java class library if > > it covers our requirements (among them: maintain JDK 1.3 compatibility). > > Sadly that means that java.text.Bidi is a little problematic, except if > > we say that Bidi support is only available under JDK 1.4 but that might > > complicate the implementation additionally. If we can reuse code from > > our sister project Batik, that's probably better. Introducing an > > external library will take careful consideration. We have to make sure, > > among other things, that the licensing situation is ok. > > > > I don't know of anyone currently working on a Bidi impementation. If > > someone does, I expect that person to speak up. > > > I am. Using Java 1.5 for the basics, and Java 1.6 for kerning and > ligatures. I suppose you were aware of that though. Well, the requirement for 1.5 or even 1.6 pretty much rules out your implementation for us. Jeremias Maerki
Re: Question about status of Bidi support, and Arabic/Persian shaping!
On Fri, 2006-05-05 at 08:43 +0200, Jeremias Maerki wrote: > This is good news. I did not study the problems around non-LTR texts so > I can't say anything useful about this. > > I think it is preferrable to reuse code from the Java class library if > it covers our requirements (among them: maintain JDK 1.3 compatibility). > Sadly that means that java.text.Bidi is a little problematic, except if > we say that Bidi support is only available under JDK 1.4 but that might > complicate the implementation additionally. If we can reuse code from > our sister project Batik, that's probably better. Introducing an > external library will take careful consideration. We have to make sure, > among other things, that the licensing situation is ok. > > I don't know of anyone currently working on a Bidi impementation. If > someone does, I expect that person to speak up. > I am. Using Java 1.5 for the basics, and Java 1.6 for kerning and ligatures. I suppose you were aware of that though. Peter
Re: Question about status of Bidi support, and Arabic/Persian shaping!
This is good news. I did not study the problems around non-LTR texts so I can't say anything useful about this. I think it is preferrable to reuse code from the Java class library if it covers our requirements (among them: maintain JDK 1.3 compatibility). Sadly that means that java.text.Bidi is a little problematic, except if we say that Bidi support is only available under JDK 1.4 but that might complicate the implementation additionally. If we can reuse code from our sister project Batik, that's probably better. Introducing an external library will take careful consideration. We have to make sure, among other things, that the licensing situation is ok. I don't know of anyone currently working on a Bidi impementation. If someone does, I expect that person to speak up. Please also look through the fop-dev mailing list archives for any discussions around Bidi and UAX#14. I think the two aspects may be closely related. On 05.05.2006 01:00:04 Kia Teymourian wrote: > Dear developers, > > Im interested to use FOP for creating Documentation with complex text > layout languages such as Arabic/Persian. > I would like to offer my help for the implementation of Bidi Algorithm > (Bug 32789) > > I search on the FOP-User mailing list and found, this discussion. > http://www.mail-archive.com/fop-users@xmlgraphics.apache.org/msg01575.html > > Ive done the initial steps and establish myself a development environment, > and could render a Unicode String for the Arabic Unicode shaping > here is the PDF output and the fo file: > > http://user.cs.tu-berlin.de/~kiat/fop/simple.pdf > http://user.cs.tu-berlin.de/~kiat/fop/simple.fo > > This test PDF output shows that the words in Arabic/Persian should be > rendered for ligature glyphs characters Unicode Arabic Presentation form. > And there is no problem with the Arabic shaping for Text, RTF output. > > Is there anyone who works on Bidi implementation? > > Should the Bidi Implementation be an awt independent solution? > Could we use jdk 1.4 and classes like java.text.Bidi or > java.awt.font.TextLayout? > > I looked around for Bidi implementation and found Fribid, > http://fribidi.org/wiki/ which is implemented in C. > > iText project has also some Bidi classes like > class com.lowagie.text.pdf.ArabicLigaturizer > class com.lowagie.text.pdf.BidiLine > class com.lowagie.text.pdf.BidiOrder > > Or we can use Batik classes like > org.apache.batik.gvt.text.ArabicTextHandler.java > > I think the first point should be the implementation of > > org.apache.fop.fo.flow.BidiOverride.java > org.apache.fop.layoutmgr.inline.BidiLayoutManager.java > > And then add some classes for the Arabic character shaping like > ArabicLigaturizer. > The bidi-Override implementation is very useful for some other projects > to be able to > create Persian/Arabic Documentation with PDF output from DocBook files. > > Regards, > Kia Teymourian > > > Jeremias Maerki
