You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-dev@xmlgraphics.apache.org by Arved Sandstrom <Ar...@chebucto.ns.ca> on 2001/02/11 06:39:25 UTC
JPFOP in CVS
The JPFOP (Japanized FOP) distribution kindly provided by Satoshi Ishigami is
now in CVS.
It appears as a top-level source directory and top-level build files. Treat
this as a completely separate FOP build; do a 'clean' target after switching
from Western FOP to JPFOP, and vice versa. Bear in mind that the Java sources
in JPFOP include modified versions of standard FOP files; these must be kept in
sync.
The Readme indicates that a Japanese-localized JDK is required for running.
_And_ your machine must support the provided Japanese fonts.
The JPFOP distro compiles and builds, but I'd be surprised if it runs - yet.
Reason being, it was based on FOP 0.16.0; I did a fair amount of mungeing to
bring it in line with the latest CVS. In addition, I did the mods to bring it
in line with using TRAX under Xalan2. The modifications to several files were
extensive enough that I am dubious as to whether the JAR file will run properly
at the moment.
Please let me know how things turned out. You want to build with Xalan2 stuff;
add xalanj1compat.jar at the end of your classpath.
Effects on release: none. I wanted to get this into CVS. I very much doubt
whether I will include it in today's FOP 0.17.0 release, however. At such a
time as we get it working, whether today or in a week, I'll prepare a FOP
0.17.1 release and announce it as a JPFOP special release. Any thoughts on this?
Regards,
Arved
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: JPFOP in CVS
Posted by Arved Sandstrom <Ar...@chebucto.ns.ca>.
At 11:23 AM 2/12/01 +0100, FAGOT Alain wrote:
>Arved Sandstrom wrote:
>
>> I don't think there are any issues in the sense you mean. It's a
reasonably
>> complex extra chunk of code, and because it impacts on some of _our_
complex
>> code (LineArea, for example), and because I don't understand JPFOP that
>> well, I elected not to go for the fusion. But that would definitely be the
>> direction to go, probably for 0.18.
>
> I have spend almost one day trying to get JPFOP (btw, it should be
>ja-fop, because related to the Japanese language (ISO639), not the
>country (ISO3166) named Japan) into the current code tree. I definitely
>intend to acheive this within a few days. It could be also helpful for
>the further extensions about font support (anyway extended font support
>can't avoid CJK fonts;-).
>
> There remain two "hot spots": PDFRenderer.renderWordArea (formerly
>renderInlineAera) and generated code (using optional fields in the font
>descriptor).
Excellent. The current ja-fop (:-)) in CVS is primarily a mechanism for
getting the code up in CVS, conforming to FOP 0.17, and Xalan2. I know it
compiles but I sure don't know if it works. I considered a straight JaFOP
release based on FOP 0.16.0, and may still do that, depending on how things
go, but your efforts towards integrating into our existing codebase are the
right direction.
Did you also have problems with one of the XSLT stylesheets? I had to modify
one in order to get it to work. It strikes me that this was an XT->Xalan2
issue; the raw JPFOP code is based on the use of XT. Just curious.
I'll be standing by to help integrate your stuff into CVS. Thanks.
Regards,
Arved Sandstrom
Fairly Senior Software Type
e-plicity (http://www.e-plicity.com)
Wireless * B2B * J2EE * XML --- Halifax, Nova Scotia
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: JPFOP in CVS
Posted by FAGOT Alain <Al...@framfab.nl>.
Arved Sandstrom wrote:
> I don't think there are any issues in the sense you mean. It's a reasonably
> complex extra chunk of code, and because it impacts on some of _our_ complex
> code (LineArea, for example), and because I don't understand JPFOP that
> well, I elected not to go for the fusion. But that would definitely be the
> direction to go, probably for 0.18.
I have spend almost one day trying to get JPFOP (btw, it should be
ja-fop, because related to the Japanese language (ISO639), not the
country (ISO3166) named Japan) into the current code tree. I definitely
intend to acheive this within a few days. It could be also helpful for
the further extensions about font support (anyway extended font support
can't avoid CJK fonts;-).
There remain two "hot spots": PDFRenderer.renderWordArea (formerly
renderInlineAera) and generated code (using optional fields in the font
descriptor).
Hope to be back soon,
Alain.
--
FAGOT Alain
Alain.FAGOT@framfab.nl Senior Java Developer
Tel: +31 20 586 99 36 NetlinQ Framfab
Fax: +31 20 682 75 56 Arlandaweg 92
http://www.framfab.nl/ NL-1043 EX Amsterdam
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: JPFOP in CVS
Posted by Arved Sandstrom <Ar...@chebucto.ns.ca>.
Hi, Kelly
I don't think there are any issues in the sense you mean. It's a reasonably
complex extra chunk of code, and because it impacts on some of _our_ complex
code (LineArea, for example), and because I don't understand JPFOP that
well, I elected not to go for the fusion. But that would definitely be the
direction to go, probably for 0.18.
Arved
At 11:08 PM 2/10/01 -0700, Kelly Campbell wrote:
>Arved,
>
>What are the issues with integrating the differences between the
>versions into the mainline FOP code? It seems like that would be easier in
>the long run rather than doing double maintenance.
>
>-Kelly
>
>On Sun, Feb 11, 2001 at 01:39:25AM -0400, Arved Sandstrom wrote:
>> The JPFOP (Japanized FOP) distribution kindly provided by Satoshi
Ishigami is
>> now in CVS.
>>
>> It appears as a top-level source directory and top-level build files. Treat
>> this as a completely separate FOP build; do a 'clean' target after
switching
>> from Western FOP to JPFOP, and vice versa. Bear in mind that the Java
sources
>> in JPFOP include modified versions of standard FOP files; these must be
kept in
>> sync.
>>
>> The Readme indicates that a Japanese-localized JDK is required for running.
>> _And_ your machine must support the provided Japanese fonts.
>>
>> The JPFOP distro compiles and builds, but I'd be surprised if it runs -
yet.
>> Reason being, it was based on FOP 0.16.0; I did a fair amount of
mungeing to
>> bring it in line with the latest CVS. In addition, I did the mods to
bring it
>> in line with using TRAX under Xalan2. The modifications to several files
were
>> extensive enough that I am dubious as to whether the JAR file will run
properly
>> at the moment.
>>
>> Please let me know how things turned out. You want to build with Xalan2
stuff;
>> add xalanj1compat.jar at the end of your classpath.
>>
>> Effects on release: none. I wanted to get this into CVS. I very much doubt
>> whether I will include it in today's FOP 0.17.0 release, however. At such a
>> time as we get it working, whether today or in a week, I'll prepare a FOP
>> 0.17.1 release and announce it as a JPFOP special release. Any thoughts
on this?
>>
>> Regards,
>> Arved
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
>> For additional commands, email: fop-dev-help@xml.apache.org
>
>--
>Kelly A. Campbell Software Engineer
><ca...@merlotxml.org> ChannelPoint, Inc.
><ca...@channelpoint.com> Colorado Springs, Co.
>
>
Fairly Senior Software Type
e-plicity (http://www.e-plicity.com)
Wireless * B2B * J2EE * XML --- Halifax, Nova Scotia
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: JPFOP in CVS
Posted by Kelly Campbell <ca...@merlot.channelpoint.com>.
Arved,
What are the issues with integrating the differences between the
versions into the mainline FOP code? It seems like that would be easier in
the long run rather than doing double maintenance.
-Kelly
On Sun, Feb 11, 2001 at 01:39:25AM -0400, Arved Sandstrom wrote:
> The JPFOP (Japanized FOP) distribution kindly provided by Satoshi Ishigami is
> now in CVS.
>
> It appears as a top-level source directory and top-level build files. Treat
> this as a completely separate FOP build; do a 'clean' target after switching
> from Western FOP to JPFOP, and vice versa. Bear in mind that the Java sources
> in JPFOP include modified versions of standard FOP files; these must be kept in
> sync.
>
> The Readme indicates that a Japanese-localized JDK is required for running.
> _And_ your machine must support the provided Japanese fonts.
>
> The JPFOP distro compiles and builds, but I'd be surprised if it runs - yet.
> Reason being, it was based on FOP 0.16.0; I did a fair amount of mungeing to
> bring it in line with the latest CVS. In addition, I did the mods to bring it
> in line with using TRAX under Xalan2. The modifications to several files were
> extensive enough that I am dubious as to whether the JAR file will run properly
> at the moment.
>
> Please let me know how things turned out. You want to build with Xalan2 stuff;
> add xalanj1compat.jar at the end of your classpath.
>
> Effects on release: none. I wanted to get this into CVS. I very much doubt
> whether I will include it in today's FOP 0.17.0 release, however. At such a
> time as we get it working, whether today or in a week, I'll prepare a FOP
> 0.17.1 release and announce it as a JPFOP special release. Any thoughts on this?
>
> Regards,
> Arved
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
> For additional commands, email: fop-dev-help@xml.apache.org
--
Kelly A. Campbell Software Engineer
<ca...@merlotxml.org> ChannelPoint, Inc.
<ca...@channelpoint.com> Colorado Springs, Co.
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org