Arabic font issue in PDF - FOP

[Neeraj <ne...@gmail.com>]

Hi,

I download the NFOP project from sourceforge.com and implemented it working
fine.

http://sourceforge.net/projects/nfop/

However it is not working fine with Arabic language in PDF(font is
appearing disjoint and not in reverse order, however it is working fine for
HTML). The fix is available for JAVA platform, but does not mention
anything about porting the same fix for .NET Framework.

It solves the reverse character issue and disjointed font also by using
nonstandard FOP.

http://people.apache.org/~spepping/
http://osdir.com/ml/fop-users-xmlgraphics.apache.org/2011-10/msg00043.html

I would like to apply this fix in my nFOP(.NET version of FOP), It will be
very helpful if you can provide me list of changes for this fix.

Looking forward for your reply.

Thanks in advance for your support.

Thanks
Neeraj Chaurasia

Re: Arabic font issue in PDF - FOP

[Pascal Sancho <ps...@gmail.com>]

Hi,
NFOP seems to be a dead project, last commit occurred on may 2008, and
was based on FOP 0.20.5, witch is a *very* old FOP version, based on
an abandoned design.

On the other hand, FOP has now integrated the cited patch and either
current 1.1RC1 version or TRUNK version.

Giving you the list of changes introduced by the cited patch will not
help, since it was an unstable, incomplete development, and it was
mainly based on recent design of FOP, witch is quite different from
the one on witch NFOP is based.

That said, you can try a solution based on IKVM (see [1]).
In such solution, there is some difficulties to work with SVG, but I
know that there is an ANT option to build Xmlgraphics.commons (see
[2]) against IKVM. Never tried.

[1] http://www.ikvm.net/

2012/7/24 Neeraj <ne...@gmail.com>:
> Hi,
>
> I download the NFOP project from sourceforge.com and implemented it working
> fine.
>
> http://sourceforge.net/projects/nfop/
>
> However it is not working fine with Arabic language in PDF(font is appearing
> disjoint and not in reverse order, however it is working fine for HTML). The
> fix is available for JAVA platform, but does not mention anything about
> porting the same fix for .NET Framework.
>
> It solves the reverse character issue and disjointed font also by using
> nonstandard FOP.
>
> http://people.apache.org/~spepping/
> http://osdir.com/ml/fop-users-xmlgraphics.apache.org/2011-10/msg00043.html
>
> I would like to apply this fix in my nFOP(.NET version of FOP), It will be
> very helpful if you can provide me list of changes for this fix.
>
> Looking forward for your reply.
>
> Thanks in advance for your support.
>
> Thanks
> Neeraj Chaurasia



-- 
pascal

---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org

Re: Arabic font issue in PDF - FOP

[Glenn Adams <gl...@skynav.com>]

On Tue, Jul 24, 2012 at 3:57 AM, Neeraj <ne...@gmail.com> wrote:

> Hi,
>
> I download the NFOP project from sourceforge.com and implemented it
> working fine.
>
> http://sourceforge.net/projects/nfop/
>
> However it is not working fine with Arabic language in PDF(font is
> appearing disjoint and not in reverse order, however it is working fine for
> HTML). The fix is available for JAVA platform, but does not mention
> anything about porting the same fix for .NET Framework.
>
> It solves the reverse character issue and disjointed font also by using
> nonstandard FOP.
>
> http://people.apache.org/~spepping/
> http://osdir.com/ml/fop-users-xmlgraphics.apache.org/2011-10/msg00043.html
>
> I would like to apply this fix in my nFOP(.NET version of FOP), It will be
> very helpful if you can provide me list of changes for this fix.
>

I'm not familiar with the NFOP project. Why don't you just use FOP directly
and create a shim between .NET and FOP Java APIs? I'm afraid you are now
encountering one of the downsides of forking a technology then
porting/retargeting it to another environment.

In any case, the changes to FOP to add support for a complex text path were
fairly extensive. You will have to read FOP code and evaluate SVN change
logs to understand the changes. However, for convenience sake, I attempted
to put the new code into its own package and sub-packages under
org.apache.fop.complexscripts.

Good Luck,
Glenn