foray-support Mailing List for FOray

Hi K. Deepthi:

I finally was able to run a decent test here on the "float" issue that 
we have been discussing. I was quite wrong -- it looks like FOray does 
not support side floats at all right now. An examination of the code 
reveals that we have not even started to do so. My apologies for the 
confusion.

Victor Mote

Hi K Deepthi:

I don't see anything wrong in the way you are configuring FOray. The 
issue seems to generally be that the FOray parser is finding errors in 
the input file. Of course, some of these might be errors in the parser 
-- it is impossible for me to tell without the input fo file. If you can 
provide the fo file as an attachment that will help immensely.

Victor



k deepthi wrote:
> Hi Victor,
>  
> I am facing so many issues when using FOray formatter. May be I have 
> missed something in setting the environment. Please help me in this 
> regard. I am sending the process I have followed for converting .fo file 
> to .pdf using FOray jars. Please find the document attached.
> Same process we have to follow for integrating this with our own 
> application. Please suggest me if I made anything wrong.
>  
> I tried to generate pdfs for the .fo files which are there in the 
> downloaded version. For every file conversion I got different exceptions 
> for different files. Some of them are:
> 1) No such function url -- which you have suggested me to do in src 
> attribute.
> 2) org.axsl.fo.FoTreeException: No such function: abs
>   Context: null
>     (Line 43, Column 46)
>  at org.foray.fotree.FOTreeBuilder.startElement(FOTreeBuilder.java:257)
> 3) java.lang.NullPointerException
>  at 
> org.foray.fotree.PropertyList.getBorderSeparationIPD(PropertyList.java:879)
> 4) java.lang.UnsupportedOperationException
>  at java.util.AbstractList.add(Unknown Source)
>  at java.util.AbstractList.add(Unknown Source)
>  at org.foray.fotree.fo.obj.Character.setup(Character.java:101)
>  at org.foray.fotree.FOTreeBuilder.startElement(FOTreeBuilder.java:250)
> 5) org.axsl.fo.FoTreeException: May not contain non-whitespace text.
>   Context: null
>     (Line 142, Column 15)
>  at org.foray.fotree.FOTreeBuilder.characters(FOTreeBuilder.java:144)
>  at org.apache.xerces.parsers.AbstractSAXParser.characters(Unknown 
> Source). and so on...
>  
> Am I clear in explaining the things. If not please let me know.
>  
> Thanks,
> Deepthi.K.
> 
> --- On *Thu, 27/8/09, Victor Mote /<vi...@ou...>/* wrote:
> 
> 
>     From: Victor Mote <vi...@ou...>
>     Subject: Re: [FOray-support] Regarding FOray integration with our
>     own applications
>     To: "k deepthi" <kde...@ya...>, "FOray Support"
>     <for...@li...>
>     Date: Thursday, 27 August, 2009, 5:54 AM
> 
>     Hi K. Deepthi:
> 
>     See inline comments below.
> 
>     Victor
> 
>     k deepthi wrote:
>      > Hi Victor,
>      > I am very thankful to you for your quick response. I resolved the
>     problem of SAXParseException. When tried in some other way it has
>     shown me a nullpointer exception because of the nullpointer object
>     passed to the java code.
>      >  But many errors arised while running the foray converter. I
>     would like to know if any special handling of xsl-fo elements is
>     maintained for FOray converter. Meanwhile I would like to intimate
>     that the downloaded
> 
>     There are no known issues with /parsing/ of XSL-FO documents. (We
>     have many weaknesses in the processing, but I think we parse and
>     validate them pretty well).
> 
>      > zip file contains .afm related files for font base-14. But in the
>     code they are checking for .jbso files. I have changed the code and
>     reconstructed the jar file for foray font.
> 
>     The .jbso extension is our abbreviation for "java binary serialized
>     object". The needed base-14 jbso files are in a jar file
>     lib/foray-font-0.3-rsrc.jar, which should automatically be added to
>     the classpath if you use the standard scripts. If you use other
>     scripts, you will need to make sure that all of the jar files in the
>     lib directory are available in your classpath. Serializing the
>     parsed AFM files helps with performance by preventing us from
>     needing to parse them again at runtime.
> 
>      > One sample .fo file which I am triyng to convert is attached to
>     this mail and also the exception thrown by FOray is also attached.
>     Please find the attachments and give me the best solution. In case
>     of <fo:external-graphic> it is throwing exception related to src
>     attribute value.
> 
>     According to the XSL-FO 1.1 Recommendation, a "src" attribute takes
>     a type <uri-specification>. On page 73 of that recommendation, the
>     <uri-specification> must start with "url(" and end with "). So, in
>     the example FO file that you sent, it should look like this:
>     <fo:external-graphic src="url(D:\winter.jpeg)"/>
>     or perhaps:
>     <fo:external-graphic src="url(file://D:\winter.jpeg)"/>
> 
>     I have made a note to see that we make that Exception message more
>     explicit in the future.
> 
>     Now, if I substitute the "winter.jpeg" file reference with a file
>     that exists on my machine, I still get a failure with a
>     not-very-helpful message. I will check into this shortly to see if I
>     can find out what is going on.
> 
>     If you have the ability to get a copy of the source code from
>     Subversion and build it, a few problems go away with the current
>     repository code.
> 
>      > _Project Requirement_:-
>      > The main requirement for our project is we will get .fo file from
>     our application dynamically. We have to convert this .fo to .pdf
>     with text wrapping around an image.
>      >  Eg:- texttexttexttexttexttexttexttexttexttexttexttexttexttext
>      >        |          |texttexttexttexttexttexttexttexttexttexttexttext
>      >        | image|texttexttexttexttexttexttexttexttexttexttexttext
>      >        |_____ |texttexttexttexttexttexttexttexttexttexttexttext
>      >        texttexttexttexttexttexttexttexttexttexttexttexttexttext
>      >        texttexttexttexttexttexttexttexttexttexttexttexttexttext
>      >  I want to mention you a special case that text comes totally
>     from a separate template and images come from another template. Both
>     cannot happen at the same time. Previously we have tried with table
>     format. So that left side of the pdf page will be having text and
>     right will be having images. But it leads to wastage of page. Is
>     there any way to do this in writing XSL-FO by Foray and convert this
>     to PDF to attain the exact requirement. Please help me in this regard.
> 
>     If I understand you correctly, there should be no problem with
>     creating the text and images from two different sources. To get the
>     behavior you wish, use an fo:float object with a float attribute =
>     start | end | left | right | inside | outside.
> 
>     Now, whether FOray processes it correctly or not is another
>     question, although I think it should.
> 
>      >  Thanks
>      > Deepthi.K
> 
> 
> start: 2008-06-21 end: 0000-00-00
> ------------------------------------------------------------------------
> See the Web's breaking stories, chosen by people like you. Check out 
> Yahoo! Buzz 
> <http://in.rd.yahoo.com/tagline_buzz_1/*http://in.buzz.yahoo.com/>.

Hi K. Deepthi:

See inline comments below.

Victor

k deepthi wrote:
> Hi Victor,
> I am very thankful to you for your quick response. I resolved the 
> problem of SAXParseException. When tried in some other way it has shown 
> me a nullpointer exception because of the nullpointer object passed to 
> the java code.
>  
> But many errors arised while running the foray converter. I would like 
> to know if any special handling of xsl-fo elements is maintained for 
> FOray converter. Meanwhile I would like to intimate that the downloaded 

There are no known issues with /parsing/ of XSL-FO documents. (We have 
many weaknesses in the processing, but I think we parse and validate 
them pretty well).

> zip file contains .afm related files for font base-14. But in the code 
> they are checking for .jbso files. I have changed the code and 
> reconstructed the jar file for foray font.

The .jbso extension is our abbreviation for "java binary serialized 
object". The needed base-14 jbso files are in a jar file 
lib/foray-font-0.3-rsrc.jar, which should automatically be added to the 
classpath if you use the standard scripts. If you use other scripts, you 
will need to make sure that all of the jar files in the lib directory 
are available in your classpath. Serializing the parsed AFM files helps 
with performance by preventing us from needing to parse them again at 
runtime.

> One sample .fo file which I am triyng to convert is attached to this 
> mail and also the exception thrown by FOray is also attached. Please 
> find the attachments and give me the best solution. In case of 
> <fo:external-graphic> it is throwing exception related to src attribute 
> value.

According to the XSL-FO 1.1 Recommendation, a "src" attribute takes a 
type <uri-specification>. On page 73 of that recommendation, the 
<uri-specification> must start with "url(" and end with "). So, in the 
example FO file that you sent, it should look like this:
<fo:external-graphic src="url(D:\winter.jpeg)"/>
or perhaps:
<fo:external-graphic src="url(file://D:\winter.jpeg)"/>

I have made a note to see that we make that Exception message more 
explicit in the future.

Now, if I substitute the "winter.jpeg" file reference with a file that 
exists on my machine, I still get a failure with a not-very-helpful 
message. I will check into this shortly to see if I can find out what is 
going on.

If you have the ability to get a copy of the source code from Subversion 
and build it, a few problems go away with the current repository code.

> _Project Requirement_:-
> The main requirement for our project is we will get .fo file from our 
> application dynamically. We have to convert this .fo to .pdf with text 
> wrapping around an image.
>  
> Eg:- texttexttexttexttexttexttexttexttexttexttexttexttexttext
>        |          |texttexttexttexttexttexttexttexttexttexttexttext
>        | image|texttexttexttexttexttexttexttexttexttexttexttext
>        |_____ |texttexttexttexttexttexttexttexttexttexttexttext
>        texttexttexttexttexttexttexttexttexttexttexttexttexttext
>        texttexttexttexttexttexttexttexttexttexttexttexttexttext
>  
> I want to mention you a special case that text comes totally from a 
> separate template and images come from another template. Both cannot 
> happen at the same time. Previously we have tried with table format. So 
> that left side of the pdf page will be having text and right will be 
> having images. But it leads to wastage of page. Is there any way to do 
> this in writing XSL-FO by Foray and convert this to PDF to attain the 
> exact requirement. Please help me in this regard.

If I understand you correctly, there should be no problem with creating 
the text and images from two different sources. To get the behavior you 
wish, use an fo:float object with a float attribute = start | end | left 
| right | inside | outside.

Now, whether FOray processes it correctly or not is another question, 
although I think it should.

>  
> Thanks
> Deepthi.K

Hi K Deepthi:

With regard to wrapping text around an image: In general, I think this 
works properly, but it may not in some cases. I would certainly be glad 
to fix problems in any cases where it does not.

With regard to setting up an environment to run FOray: A 
SAXParseException might mean that the input is not well-formed. Can you 
send me the input file you are using? If so, I'll be glad to see if I 
can reproduce the problem here. If it is a problem with the environment, 
I'll be glad to help, and it may mean that our doc is not complete.

Victor Mote



k deepthi wrote:
> Hi Team,
> 
> This is K.N.B.Deepthi from an MNC. In our application there is a need 
> for XSL-FO to PDF conversion. In that there is a special requirement for 
> text wrapping round an image dynamically since FO file is generated 
> dynamically from our application. So I would like to know if there is 
> any possibility with Foray 0.3 XSL Formatter satisfies the need. Please 
> help me in this regard.
> 
>  
> 
> Note:- I have tried setting up environment for standalone application by 
> downloading jar files of Foray from sourceforge.net .But when using a 
> demo file in Java that converts FO to PDF I am getting SAXParseException 
> at the transformation. Please help in setting up the environment.
> 
>  
> 
> Thanks
> 
> Deepthi.K.N.B.
> 
> 
> ------------------------------------------------------------------------
> Looking for local information? Find it on Yahoo! Local 
> <http://in.rd.yahoo.com/tagline_local_1/*http://in.local.yahoo.com/>
> 
> 
> ------------------------------------------------------------------------
> 
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
> trial. Simplify your report design, integration and deployment - and focus on 
> what you do best, core application coding. Discover what's new with 
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> FOray-support mailing list
> FOr...@li...
> https://lists.sourceforge.net/lists/listinfo/foray-support

Hi Team,
This is K.N.B.Deepthi from an MNC. In our application there is a need for XSL-FO to PDF conversion. In that there is a special requirement for text wrapping round an image dynamically since FO file is generated dynamically from our application. So I would like to know if there is any possibility with Foray 0.3 XSL Formatter satisfies the need. Please help me in this regard. 
 
Note:- I have tried setting up environment for standalone application by downloading jar files of Foray from sourceforge.net .But when using a demo file in Java that converts FO to PDF I am getting SAXParseException at the transformation. Please help in setting up the environment.
 
Thanks
Deepthi.K.N.B.


      Love Cricket? Check out live scores, photos, video highlights and more. Click here http://cricket.yahoo.com

Dear Friends of FOray:

I am happy to announce the 0.3 release of FOray, available here:
http://www.foray.org/app/using/download.html

The release notes are here:
http://www.foray.org/00-release/notes-0_003.html

Much of the effort expended in this release related to changes related to
the upgrade to Java 5, javadoc improvements, API improvements, adding
testing infrastructure, and absorbing the XSL-FO 1.1 Recommendation. In
short, much of it benefits the developers and should make future development
easier. Many bugs were fixed, but there are several places where the product
needs serious improvement. I hope to address at least some of these in the
coming months. I hope that the next release will have more improvements for
users (rather than developers).

The future prospects for FOray are good. We have paid the infrastructure
bill and most of the API bill, and should be able to steadily improve the
product from this point forward. We have stronger-than-expected competition
from FOP but are glad for it. Their philosophy excludes use of our efforts,
but our philosophy allows us to benefit from the best of their improvements.

Your comments are welcome.

Victor Mote

Hi All:

I just committed a change that improves the integration between the FOray
configuration and the aXSL font configuration. The aXSL font configuration
scheme has the ability to set parameters from the java or system
environment. When used with FOray, the FOray parser now also treats the
special variable FONT_BASE_DIRECTORY (if not found in the environment) as
equal to the "font-base-directory" entry in the FOray configuration. Thus
there is no need to configure an environment variable for this value, as
long as it is configured in the FOray configuration. Details are here:
http://www.foray.org/app/features/fonts.html#config

Victor Mote

Hi All:

I am pleased to announce that FOray no longer has any dependencies on the
Java Advanced Imaging (JAI) system, which has been needed for PNG and TIFF
support. Because of licensing issues, JAI has been a separate download,
which has been an inconvenience for users. Current repository code uses and
future releases will use the Apache XML Graphics Commons library to achieve
the same general effect.

There is still much work to do to improve the FOray Graphics library, but
this step should put us in a better position to do so.

In addition, improvements have been made to the API to clarify the nature of
the image sample data that is returned. JPEG and TIFF formats return their
compressed values, while other formats are converted first to a standard
ordering. Previously these were handled in the same method, but are now
handled in separate methods, so that client applications can (theoretically)
use whichever they need, and to clean up the code behind that logic.

I have also added a suite of functional Graphics package tests into the
JUnit harness to help us manage changes to the Graphics package.
Contributions of non-working files that we can use for testing and
development purposes will be most welcome.

Victor Mote 

Based on the fact that no negative feedback has been received for upgrading
to Java 1.5, and based on the needs of aXSL, which wants to solidify its API
around typesafe enums where that is appropriate, FOray is in the process of
upgrading to Java 1.5. Some changes have already been made to use the new
features, and more will be forthcoming.

Please post a message to the support list
(mailto:for...@li...) if you have any problems with
the upgrade.

Victor Mote

Hi folks:

I am considering moving FOray to Java 1.5 for several good reasons. The main
reason I have not done so already is because I was trying to prevent us from
getting to a place where we were too far away from FOP's platform. Here are
the considerations:

1. Nobody has said so explicitly, but I am under the impression that FOP has
chosen not to write to the aXSL interfaces, nor to use any of the FOray
packages. So perhaps my concerns about maintaining code that was usable by
them were poorly placed. Can anyone shed light on this?

2. I am also under the impression that FOP may move to Java 1.4 in the near
future. It is my understanding that code compiled on Java 1.5 compilers runs
properly on Java 1.4 runtimes. This would mean that developers would need to
use 1.5 for development and builds, but that users would not be forced to
use it at runtime. If all of these are true, then FOray could move to 1.5
with no detriment to FOP anyway. Does anyone know what FOP's intentions are
in this matter, or care to comment on the assumptions I have made WRT
1.4/1.5 compatibility?

Also, if anyone other than FOP has concerns about moving to Java 1.5, now
would be a good time to raise them.

Victor Mote

inpost wrote: 

> I have unzipped foray 02 bin all to my pc at /usr/local/foray 
> (mandrake 92, gnome 24). Ibm java is installed at 
> /usr/local/java/ibm-java2-i386-50/jre/bin.
> 
> >From the location /usr/local/foray/foray-0.2-bin-all, I entered the
> following command in the gnome terminal:
> 
> java ./foray-0.2-all.jar
> 
> I received the following error
> 
> The jar file is missing the manifest entry for the main class:
> ./lib/foray-0.2-all.jar
> 
> How do I solve this problem please?

FOray isn't designed right now to be run as a self-executing jar file. I
recommend that you use or mimic the foray.sh script.

Victor Mote

Readers,

I have unzipped foray 02 bin all to my pc at /usr/local/foray
(mandrake 92, gnome 24). Ibm java is installed at
/usr/local/java/ibm-java2-i386-50/jre/bin.

>From the location /usr/local/foray/foray-0.2-bin-all, I entered the
following command in the gnome terminal:

java ./foray-0.2-all.jar

I received the following error

The jar file is missing the manifest entry for the main class:
./lib/foray-0.2-all.jar

How do I solve this problem please?

I am pleased to announce the release of FOray 0.2, which can now be
downloaded from SourceForge. Please visit the release notes:
http://www.foray.org/app/using/release.html#0_2
and download instructions:
http://www.foray.org/app/using/download.html
for more details.

Please note specifically that this release is more for the benefit of the
various developers that are using FOray modules than for end-users. We still
have significant work to do in FOTree and AreaTree before FOray will be
generally usable.

I will make an effort to release code in the future at or near the end of
each calendar quarter.

Many thanks to all who have contributed to this effort.

Victor Mote

(This message first sent Mon 7/4/2005 2:46 PM, but was rejected the
SourceForge server. Trying again. My apologies for the delay.)

Vincent Hennebert wrote:

> my very first mail to a FOray mailing list ;-)

Actually, you have the honor of being the first user to post any mail
message on any FOray mailing list.

> When I select a font with the FontServer.selectFont method, I must 
> provide a list of font families from which the best-fitting font is to be
selected.
> I guess that the getFontName method of the returned Font object will 
> correspond to one of the family names given to the previous call to
selectFont?

No, usually not. getFontName() returns the registered name of the font
itself, not the font family. In the configuration that you are now using,
the registered font name comes from the "name" attribute of the "font"
element in the font-configuration. The family name comes from the "family"
attribute of the "font-description" element.

Also, a font can be registered with more than one family. (You can't do this
in the old font-configuration scheme, but you can programmatically, and the
base-14 fonts especially tend to be registered with more than one
font-family name. The new font-configuration makes this relationship more
clear). Also, aliases can be registered for font-families. Both of these can
result in further differences between getFontName() and the font-family
passed to selectFont().

XSL-FO does not provide for direct specification of a font. Instead, you
pass it a font-family and other parameters (style, weight, etc.) and the
application needs to find the best font that it can to fit those parameters.
However, for purposes of embedding a font, a font-family is not enough --
there needs to be a unique font name that is used. So both concepts are
needed and must be kept separate. Clarification of the relationship between
the two is one of the reasons for the changes that I am making to the
font-configuration (which you and I have discussed off-line).

> It would perhaps be a litte bit more helpful to say it in the javadoc. 
> Or perhaps choose getFamilyName instead of getFontName?
 
1. The change you suggest would not be appropriate, but the javadoc does
need some work here, and I will try to make some appropriate changes in the
next day or two.
2. I should probably add a method getRegisteredFontName() and deprecate
getFontName(), but essentially have them do the same thing, for clarity.

Victor Mote

Hi,

my very first mail to a FOray mailing list ;-)

When I select a font with the FontServer.selectFont method, I must provide a 
list of font families from which the best-fitting font is to be selected.
I guess that the getFontName method of the returned Font object will correspond 
to one of the family names given to the previous call to selectFont?

It would perhaps be a litte bit more helpful to say it in the javadoc. Or 
perhaps choose getFamilyName instead of getFontName?

Cheers,
Vincent