gt;
> Thank you
>
> ------
> *De :* Glenn Adams
> *Envoyé :* dimanche 7 mai 2023 06:19
> *À :* FOP Users ; FOP Developers <
> fop-...@xmlgraphics.apache.org>; Batik Developers <
> batik-...@xmlgraphics.apache.org>; XML Graphics Project <
&g
Hi All,
If you haven't yet heard, we are migrating the XMLGraphics project's issue
tracking from Jira to GitHub.
For the purpose of performing the migration from Jira to GitHub Issues, I
would like to have your GitHub User Identifier if you have previously
interacted with the XMLGraphics Jira
Pas de problème Jocelin. Juste une suggestion amicale.
G.
On Thu, Apr 27, 2023 at 9:27 AM Jocelin HEINEN (ext)
wrote:
> Yes sorry about that still don't have a Jira account but will do when I
> have and can create the issue
> --
> *De :* Glenn Adam
Also, please put any example XML into an attachment rather than inlined in
the problem description or a comment.
Thanks.
On Thu, Apr 27, 2023 at 5:12 AM Simon Steiner
wrote:
> Hi,
>
>
>
> You may need to open a bug in jira for us to check this.
>
>
>
> Thanks
>
>
>
> *From:* Jocelin HEINEN
entation (
> https://xmlgraphics.apache.org/fop/2.2/fonts.html) so users won't get
> false expectations when trying to find suitable fonts for characters that
> eventually are unsupported by FOP?
>
That's a reasonable request.
> Kind regards,
>
> Ron
>
> On 29/11/2017 18:41, Glen
Characters outside the BMP are not yet supported by FOP. See [1].
[1] https://issues.apache.org/jira/browse/FOP-1969
On Wed, Nov 29, 2017 at 7:29 AM, Ron Van den Branden <
ron.vandenbran...@kantl.be> wrote:
> Perhaps I should make clear that this is a general pattern: for all
> characters that
Since the XSLT front end functionality in FOP serves merely as a
convenience function for the user, you may choose to use alternative tools
not integrated into FOP as your front end. I suggest you do this in order
to transform from your input data set into XSL-FO input files which you can
feed
However, we are really keen to get the next release version of FOP so
>> we can
>> > use the fix for the PDF image plug-in.
>> >
>> >
>> >
>> > I appreciate the nature of these mainly volunteer led apache projects.
>> > However, I would
> mainly on bug nuking and feature implementation at the moment?
>
>
>
> *From:* Glenn Adams [mailto:gl...@skynav.com]
> *Sent:* 21 October 2016 02:08
> *To:* Jon Wu <j...@wuservices.com>
> *Cc:* FOP Users <fop-users@xmlgraphics.apache.org>; FOP Developers <
&
I've needed it for, but pointing to SNAPSHOT causes long daily dependency
> resolutions and it could break any time of course.
>
> On Thu, Oct 20, 2016 at 3:01 PM Glenn Adams <gl...@skynav.com> wrote:
>
>> Stand by. I will commit a fix to this configuration bug in a few
Stand by. I will commit a fix to this configuration bug in a few moments.
On Thu, Oct 20, 2016 at 2:38 PM, Jon Wu wrote:
> Can SNAPSHOT be republished?
>
> I've been using 2.2.0-SNAPSHOT for compatibility with the latest PDFBox,
> but my build broke this morning because I
There has been no discussion that I'm aware of. You are welcome to submit a
patch making the necessary changes.
On Thu, Aug 11, 2016 at 1:36 PM, jdebinder wrote:
> The last question on this topic was back in 2007. I also see a couple of
> more recent posts about the Maven
They aren't spurious. You need to find where you are using these fonts
(directly or indirectly). It seems you are using bold versions of Symbol
and ZapfDingbats.
On Thu, Jul 28, 2016 at 7:11 AM, Stefan Radermacher
wrote:
> Hello,
>
> FOP is generating a lot of warning about
OP developer.
>
>
>
> *From:* Glenn Adams [mailto:gl...@skynav.com]
> *Sent:* Thursday, July 14, 2016 1:48 PM
>
> *To:* FOP Users <fop-users@xmlgraphics.apache.org>
> *Subject:* Re: isolated high surrogate
>
>
>
> I'd suggest you test FOP by using an XSL-FO input
th-param **name*=*"data" **select*=*"$data"**/>*
>
> *<**xsl:with-param **name*=*"counter" **select*=*"$counter+1"**/>*
>
> **
>
> **
>
>
>
> So, not an FOP problem.
>
>
>
> Marc
&g
Non-BMP characters are not presently supported by FOP, see [1]. When they
are supported, you would best encode them in a file using a single (not
two) numeric character entities, e.g., , etc.
[1] https://issues.apache.org/jira/browse/FOP-1969
On Thu, Jul 14, 2016 at 12:51 PM, Marc Kaufman
You should check to make sure your VM is loading fontbox-2.0.0.jar from the
fop/lib directory.
On Tue, Jul 12, 2016 at 2:04 PM, Marc Kaufman wrote:
> I’m trying to use an Adobe CFF font (KozGoPr6N-Regular.otf). During the
> font loading I get to:
>
> OTFFile.readName() line
Please post a very short XSL-FO file containing a minimal example
demonstrating the problem.
On Thu, Jun 16, 2016 at 8:23 AM, Maxime Bégnis wrote:
> Hello,
>
> I'm using FOP 2.1 to generate PDF documents in Arabic. It seems that the
> letters that should be joined are not.
On Tue, May 24, 2016 at 9:45 AM, Mark Gibson <
mark.gib...@staff.bluematrix.com> wrote:
> Hi,
>
> There's a fix on trunk (https://issues.apache.org/jira/browse/FOP-2562)
> that we'd be very keen to see included in an official release ( we don't
> have the risk appetite for running production
renders
> properly everywhere else?
>
by default, the used subset will be be embedded in the PDF, so it does not
have to be present (externally) when rendering the PDF
>
>
> Thanks
>
>
>
> *From:* Glenn Adams-2 [via Apache FOP] [mailto:ml-node+[hidden email]
> <h
On Tue, Mar 8, 2016 at 6:53 PM, Puja wrote:
> I faced such issue with sigma character, I couldn't find worthwhile
> solution. Ended up using image of sigma character.
> On Mar 8, 2016 19:40, "gkaplan [via Apache FOP]" <[hidden email]
>
If you don't use non-latin scripts, such as Arabic, CJK, etc., and don't
care about ligatures, you can turn off complex script processing. See [1].
There may also be other performance affecting factors.
[1] https://xmlgraphics.apache.org/fop/2.1/complexscripts.html
On Tue, Feb 23, 2016 at 3:12
This is a known issue, see [1].
[1] https://issues.apache.org/jira/browse/FOP-1969
On Mon, Feb 22, 2016 at 7:19 AM, Chauhan Shubham <
chauhan.shubha...@gmail.com> wrote:
> Hello!
>
> I am currently facing issue with the CJK supplementary characters support.
> While processing the xml having
word spacing is zero, but
> when justifying left, there's always some interword spacing. I tried
> several values, but can't get it to zero.
> One complication I have is how to know the "normal" word space so I can
> adjust it to zero.
>
> Anyway to get word-spacing optimu
t
> it is a Microsoft encoded font.
>
> Carlos
>
>
> On 2/12/16 15:11, Glenn Adams wrote:
>
>
>
> On Thu, Feb 11, 2016 at 9:23 PM, Carlos Villegas < <c...@uniscope.jp>
> c...@uniscope.jp> wrote:
>
>> I'm trying to use FOP 2.0 to render
On Thu, Feb 11, 2016 at 9:23 PM, Carlos Villegas wrote:
> I'm trying to use FOP 2.0 to render Thai language. FOP doesn't really
> support Thai script
FOP does support Thai, at least glyph composition, though there appears to
be a few open issues (FOP-2092
The first thing you need to understand is that the input to FOP is XSL-FO
[1]. Although FOP provides a built-in utility mechanism to convert
arbitrary XML to XSL-FO by means of an XSLT transformation as a
pre-processing step, this mechanism is convenience function only, and
unrelated to FOP
Note that the team is discussing a possible bugfix release before the maven
transition work is complete. I will send an update on this subject if that
should transpire.
On Mon, Jan 4, 2016 at 10:54 AM, Glenn Adams <gl...@skynav.com> wrote:
> No fixed release schedule has been set. O
No fixed release schedule has been set. One gating factor is a transition
to maven build process which I expect to be put in place before a new
release, but this will depend also on doing the same transition for batik
and xmlgraphics-commons.
On Mon, Jan 4, 2016 at 7:20 AM, Radu Coravu
You need to use a font that has a glyph for each character. None of the
"base 14" fonts do so.
Also, FYI, please provide example input in terms of FO content, not XSL
input.
On Mon, Dec 14, 2015 at 9:14 PM, FOPUser wrote:
> We are currently using FOP 1.0 for PDF
No. But you are welcome to patch and build a local copy yourself.
On Thu, Jul 23, 2015 at 1:39 PM, jeya venkatesh M m.jeyavenkat...@gmail.com
wrote:
Hello,
We are migrating from FOP 1.0 to 1.1. I get NPE while generating a multi
language PDF. It usually worked in 1.0.
I verified that this
Yes, you are right. It also uses more memory. These are unavoidable side
effects of the ability to process complex scripts and font features.
If you don't need any complex script features, then you can disable that
processing as described in the documentation [1].
[1]
If you are using the built-in Times font, then it does not include a glyph
for that character.
On Tue, Jun 23, 2015 at 9:09 AM, mulos daniel.strackb...@mbi.de wrote:
Hi,
output format is PDF. Font type is TTF.
If I embedd another font (cambria), the character is found correctly. But
Firstly, I suggest you avoid using the term 4-byte Japanese characters,
since that has no meaning except in the context of some encoding, like
UTF-8, UTF-16, UTF-32, etc. In Java, all String objects are encoded in
UTF-16 as 16-bit code units. So BMP characters use one 16-bit code unit,
and non-BMP
Not sure what you mean by four byte characters unless you are referring
to non-BMP Unicode code points, i.e., those that require two 16-bit UTF-16
surrogates. FOP does not yet support non-BMP encoded characters.
On Mon, May 18, 2015 at 6:01 AM, mrunal28 loha...@gmail.com wrote:
Hi,
I am using
well, you will have to find a different solution for Arabic, as any
whitespace character between two nominally joining Arabic letters
effectively prevents their joining
On Wed, Apr 22, 2015 at 5:09 AM, kthangavel kumar.thanga...@gmail.com
wrote:
Hello Glenn,
If we remove the ZWSP , the
You cannot insert spaces between Arabic characters and expect them to join.
Remove the ZWSP characters you are inserting into the Arabic.
On Tue, Apr 21, 2015 at 12:22 PM, kthangavel kumar.thanga...@gmail.com
wrote:
Hi Glen,
I have attached the minified xsl-fo xml. There is only one table-row
I don't want to see the XSLT or the input XML to XLST. I need to see the
XSL-FO data (the output from performing XSLT).
The input to FOP is an XSL-FO file. Anything else is noise.
On Tue, Apr 21, 2015 at 7:45 AM, kthangavel kumar.thanga...@gmail.com
wrote:
Hi Glenn,
I am attaching the input
my apologies; now you can take the next step of simplifying the XSL-FO file
to the minimum content that demonstrates your problem; we call this a
maximally minimal test file
On Tue, Apr 21, 2015 at 10:08 AM, kthangavel kumar.thanga...@gmail.com
wrote:
Hi Glenn,
I have already attached that in
I need to see the FO input data, not XSLT.
On Mon, Apr 20, 2015 at 9:37 AM, kthangavel kumar.thanga...@gmail.com
wrote:
Hi All,
I am trying to generate a PDF report using Apache FOP in Arabic Language .
The report generation is working fine but I have used the following snippet
of xslt for
basically, relatively little effort has been spent on RTF support; we
always welcome patches submitted by interested parties
On Tue, Mar 24, 2015 at 4:56 AM, Simon Steiner simonsteiner1...@gmail.com
wrote:
Sending to mailing list
-Original Message-
From: Michele Zamparelli
it's on my (long) list
On Fri, Mar 13, 2015 at 1:20 PM, Claudius Teodorescu
claudius.teodore...@gmail.com wrote:
Hi, Glenn,
Any news on this issue?
Thanks,
Claudius
--
View this message in context:
well, at least the behavior is consistent ;) to proceed, please file an
issue [1] against FOP and include the input FO file (and your output PDF)
file, as well as a copy of the fop.xconf file you use and an indication of
the version of FOP you are using
[1]
Try FOP 1.1 or current trunk build.
On Fri, Feb 13, 2015 at 8:21 AM, Maxime Bégnis max...@neodoc.biz wrote:
Hi,
I'm trying to produce a PDF containing Chinese text using FOP 1.0. I tried
many TTF fonts but there is always some characters appearing as a #.
Does anyone recommend a specific
No released version yet. It is available in trunk.
On Wed, Jan 21, 2015 at 5:06 AM, kthangavel kumar.thanga...@gmail.com
wrote:
Hello All,
I am facing a similar issue in my project. I would love to know if this is
fixed. If yes , what is the version in which it is available?
I am currently
There is already a open issue for Mangal problems:
https://issues.apache.org/jira/browse/FOP-2437.
You should try a different font to see if the problem remains or not, e.g.,
Aparajita, Kokila, Utsaah.
On Mon, Jan 12, 2015 at 3:02 AM, Janaki Ramamurthy janaki...@gmail.com
wrote:
Good
I think there's a bug lurking, as I've seen this too. Please file a JIRA
issue and provide minimal input FO file that demonstrates problem as well
as PDF output and your configuration file.
On Wed, Dec 17, 2014 at 6:32 PM, Raymond Budd ray.b...@gmail.com wrote:
Hi,
I have a question about
On Sun, Nov 23, 2014 at 9:52 AM, Raj Singh rajoca2...@gmail.com wrote:
Dear team,
I am new to java,xml and fop,plz guide me in my urgent requirement,
below r d points for requirements
1. I've to print pdf files using socket in java.
2. I've to write such method which will
use a single font that has glyphs for both characters
On Mon, Oct 20, 2014 at 5:11 AM, Puja pujaag...@gmail.com wrote:
http://apache-fop.1065347.n5.nabble.com/file/n41322/FOP_AlignmentProblem.png
Hi,
I am using FOP 1.0 version for converting reports in PDF. Problem I am
facing is
Why aren't generating PDF directly from FOP?
On Sun, Oct 12, 2014 at 1:16 PM, Lembit Gerz lembit.g...@nortal.com wrote:
Hello,
I am using FOP 1.1 to generate postscript files with embedded fonts. Later
I’m using ps2pdf to convert the postscript files to pdfs. The text includes
Lithuanian
an awk
skript to the ps, that for example adds a watermark - convert the ps to
pdf.
I know it might be a hacky solution, but unfortunately changing this setup
is currently out of the question.
*From:* Glenn Adams [mailto:gl...@skynav.com]
*Sent:* 12. oktoober 2014. a. 22:31
*To:* FOP
...@nortal.com wrote:
No, if I generate the PDF directly using the same data and font file,
then all the letters are displayed correctly and copying from the PDF is
also possible.
*From:* Glenn Adams [mailto:gl...@skynav.com]
*Sent:* 12. oktoober 2014. a. 23:03
*To:* FOP Users
*Subject
On Tue, Sep 23, 2014 at 4:01 AM, MartinKl klapec.mar...@hotmail.com wrote:
Hello,
thank you for reaction.
I just wanted to explained why is not so easy to make automatic test. I´ve
decided to upgrade to fop 1.1 but I strugle the same problem.
As I believe has been mentioned before, any part of the process of
translating from arbitrary XML into XSL-FO proper is effectively out of
scope for this ML and group unless it is a real bug in the convenience
mechanism provided by FOP to invoke XSLT for you.
If there is a problem parsing or
On Sun, Aug 17, 2014 at 7:33 PM, pfuller pful...@callista.com.au wrote:
We have upgraded to FOP 1.1 and when trying to process an image we are
getting the following error:
SEVERE: Image not available. URI:
http://x.com:8281/contentServlet?id=70375422672598045316. Reason
:
You continue to fail to provide sufficient information to determine your
problem. Please supply the folllowing:
- your input FO file
- the output PDF file produced when formatting the above
- your FOP config file
- any relevant console output
On Tue, Jul 15, 2014 at 6:59 AM,
No.
On Thu, Jul 3, 2014 at 6:34 AM, Vijaya Raghavan.R
vijayaraghava...@solartis.net wrote:
Is it possible to merge pdf's using xsl-fo alone...?
Hi,
Now we are using Itext for merging pdf's.
Is there any solution to merge pdf's without using itext..
Note: Is it possible to merge pdf's
I recently added experimental support for PDF 1.5 Optional Content Groups
(OCGs), aka Layers. It is rather rudimentary and not yet documented (except
in the PDF spec), but you can find a couple of examples at [1][2].
The main hook for this is the use of an fox:layer property on a block class
FO
You do not need to specify the script property, unless the automatic
algorithm doesn't select the desired script. This latter would only be the
case if you are using an older font that supports only the pre-2005
OpenType Devanagari rendering rules ('deva'). The current automatic
algorithm maps to
Don't bother supplying XSL/XML input files. Preprocess them into an XSL-FO
file and then send it (and test with it), otherwise the XSL/XML files are
just noise.
Also, make sure you are using Unicode code points for the greek characters,
e.g., #x0370; through #x03ff;. Also, don't bother with FOP
Arabic is not presently supported in SVG when using FOP. For direct FOP use
(not SVG), then if you are using any version of FOP prior to FOP 1.1,
Arabic is not supported. If you are using 1.1 or current dev build, then
you are doing something wrong.
You need to provide more details.
On Wed, May
Personally, I support removing all XSLT functions from FOP, but I'm afraid
that would cause many users to find it less useful. I think it was a
serious architectural error to combine those functions in the first place,
but that horse left the gate long ago.
On Tue, May 13, 2014 at 4:18 AM, Peter
This is not an FOP problem, it is an XLST/Docbook problem. Before you run
FOP, use xsltproc or equivalent to verify the correctness of your XSLT
usage.
On Mon, May 12, 2014 at 6:18 AM, anmol gupta anmolgupta11...@gmail.comwrote:
Hi,
I am getting the following warning messages.
No
Since you reported a problem, how about reporting your fix?
On Mon, Apr 7, 2014 at 4:11 PM, edi4988 edi4...@gmail.com wrote:
Thank you for the replies, I solved the problem.
2014-04-03 16:32 GMT-06:00 Luis Bernardo [via Apache FOP] [hidden
the folks on this ML may be awesome, but keep in mind that the content of
your thread has little to do with FOP and mostly to do with XSLT; although
FOP provides a convenience function for ingesting XML along with an XSLT
stylesheet, that isn't the primary function of FOP, which is formatting
that you have to
make
the choice on the table as a whole.
(Refer May 2011 thread Complex Script, BIDI text supported?)
cheers .. Jason
On Wed, Mar 19, 2014 at 6:18 PM, Glenn Adams gl...@skynav.com wrote:
Per XSL-FO 1.1 [1]:
Property writing-mode applies to: fo:page
to block. However, we can write the text-align property on
table-cell since it is inherited by its children. This might be useful if
the cell contains multiple blocks and you don't want to specify text-align
on them individually.
On Fri, Mar 21, 2014 at 1:26 AM, Glenn Adams gl...@skynav.com wrote
Per XSL-FO 1.1 [1]:
Property writing-mode applies to: fo:page-sequence, fo:simple-page-master,
fo:region-body, fo:region-before, fo:region-after, fo:region-start,
fo:region-end, fo:block-container, fo:inline-container, and fo:table.
As you can, none of these is fo:block. You need to specify it
This is a task for XSLT or a pre-processor used in conjunction with FOP.
You need to process your incoming data to generate a ToC using FOP
primitives, and then FOP will do the formatting. XSLT gives you one way to
do that processing, but there are others. Best to think of FOP as simply a
On Wed, Mar 19, 2014 at 2:28 AM, Michael Wechner
michael.wech...@wyona.comwrote:
I think this is rather an XSL-FO question
http://en.wikipedia.org/wiki/XSL_Formatting_Objects
Not really. See my prior.
HTH
Michael
Am 17.03.14 07:52, schrieb Anastasia:
Good Day!
We are
.
(Refer May 2011 thread Complex Script, BIDI text supported?)
cheers .. Jason
On Wed, Mar 19, 2014 at 6:18 PM, Glenn Adams gl...@skynav.com wrote:
Per XSL-FO 1.1 [1]:
Property writing-mode applies to: fo:page-sequence,
fo:simple-page-master,
fo:region-body, fo:region-before, fo:region-after
We don't retroactively change release images. As Chris stated in his
previous email the avalon dependency will be fixed in the next release.
On Thu, Dec 26, 2013 at 9:52 AM, Carlos cper...@gmail.com wrote:
Hi,
Was this change commited? I'm using this dependecy:
dependency
On Tue, Dec 10, 2013 at 5:41 AM, Jan Tosovsky j.tosov...@email.cz wrote:
2. support for ligatures for non-english environments
https://issues.apache.org/jira/browse/FOP-2093
Ligatures do work in non-english environments. The bug you cite is a corner
case. If you have a specific (minimal)
j.tosov...@email.cz wrote:
On 2013-10-18 Glenn Adams wrote:
I will be visiting Basis Technology [1] in Cambridge, Massachusetts
during the week of Oct 28 through Nov 1, who has sponsored my work on
FOP, especially the Complex Script support. Basis has agreed to host an
informal meeting
I believe you are referring to the XSLT stylesheets used with the
convenience function of FOP to support XML to XSL-FO transformation as a
pre-processing step.
Formally, this step is incidental to the functionality of FOP, whose only
real task it transform XSL-FO documents into an output format.
Just a train ride away. :)
On Sun, Oct 20, 2013 at 9:58 AM, Bonekrusher djs...@yahoo.com wrote:
Too bad this is in Mass, and not NY. I would have loved to attend. Good
Luck!
--
View this message in context:
Dear FOP Users and Developers,
I will be visiting Basis Technology [1] in Cambridge, Massachusetts during
the week of Oct 28 through Nov 1, who has sponsored my work on FOP,
especially the Complex Script support. Basis has agreed to host an informal
meeting of parties interested in FOP, including
On Wed, Oct 16, 2013 at 4:41 AM, jsolutions j...@jsolutions.co.uk wrote:
http://apache-fop.1065347.n5.nabble.com/file/n39383/out.pdf
Thanks for this input. Please file a bug against FOP at [1], and be sure to
attach your test input and output pdf.
Feel free to submit a patch for the bug you will file, including a new test
case to add to the standard junit layout tests.
On Wed, Oct 16, 2013 at 10:45 AM, jsolutions j...@jsolutions.co.uk wrote:
Thanks Glenn,
I shall file a bug. For what it's worth, I believe it is due to the
text-indent
This question relates to XSLT, not XSL-FO or FOP, so this isn't really the
right ML to post this.
On Sun, Sep 29, 2013 at 12:23 AM, Bernard Giannetti
thebernmeis...@hotmail.com wrote:
Hi,
I'm using FOP, embedded in a desktop application, to create PDFs from a
single data XML file using an
change to a font that contains glyphs for the desired characters
On Thu, Sep 12, 2013 at 1:06 PM, Bonekrusher djs...@yahoo.com wrote:
Hi,
I want to output the Greater than or Equal (≥) and Less than or equal (≤)
to
symbols in Fop 1.0. But the output displays as #.
I have tried:
≥
≥
≥
P.S. In the future, don't bother sending the XSLT if your question is
related to formatting. Only the XSL-FO content is relevant.
P.S.S. Why do you use nested block containers for the first block?
On Tue, Aug 27, 2013 at 5:24 PM, Rob Sargent rsarg...@xmission.com wrote:
I cannot seem to push
I don't see any problem (attached). What version of FOP are you using? What
font type (ttf/otf) and version are you using?
On Mon, Aug 12, 2013 at 11:00 AM, Raphael Finkel raph...@cs.uky.edu wrote:
When fop renders Arabic, it uses isolated Arabic forms instead of
converting
them to the
On Sat, Aug 10, 2013 at 5:55 PM, Mahesh Rayudu mahesh.ray...@gmail.comwrote:
I noticed memory leak issue in font complex-scripts features with trunk
code. Not seen any memory issues with page numbers/totals. I tested my code
on Mac 10.7 and CentOS 6.4 with visualvm profiler.
Be specific.
Please provide the input FO file, not the input XML/XSLT files. FOP's
proper input is the FO file. The XML to FO translation is a preprocessor
convenience function unrelated to FO processing.
You can create the FO file (mini.fo.xml) as follows:
fop -c mini-fo.cfg -xml mini.xml -xsl mini.fo
support, output) files. Correct me
whether i configured all the things correctly or not and also refer or
share some example to use complex scripts to use correctly.
On Sun, Aug 4, 2013 at 2:56 AM, Glenn Adams gl...@skynav.com wrote:
There is preliminary support for some Indic scripts
There is preliminary support for some Indic scripts, but it is not fully
debugged or tested, so I expect there to be bugs. You should read the
description at [1] carefully If you encounter a specific problem, then
email me or this list, and provide a minimum FO test input file, the output
PDF
No special script processing should be required other than what is already
provided by the DefaultScriptProcessor, which enables 'ccmp', 'liga', and
'locl' features for GSUB and 'kern', 'mark', and 'mkmk' features for GPOS
for the Latin script.
Make sure you are using a font that contains
On Mon, Jun 3, 2013 at 11:09 PM, Ulrich Mayring u...@denic.de wrote:
sure, I agree if work is going on incorporating new features of
xmlgraphics-commons, then you wouldn't want to update its version every
week. However, the best practices I learned are to develop against official
APIs as soon
believe is
the
correct way.
Thanks a lot,
Ulrich
Glenn Adams wrote:
I would suggest you check the current trunk (you can use a nightly
build
if
you don't want to build yourself). There were some fixes in this are
since
1.1.
On Wed, May 29, 2013 at 6:56 AM, Ulrich Mayring u
I would suggest you check the current trunk (you can use a nightly build if
you don't want to build yourself). There were some fixes in this are since
1.1.
On Wed, May 29, 2013 at 6:56 AM, Ulrich Mayring u...@denic.de wrote:
Hi all,
please find attached an FO file and two PDFs, which were
for the pointer, your suspicion was correct. With the latest
nightly
build the page is rendered like it was in FOP 0.95, which I believe is
the
correct way.
Thanks a lot,
Ulrich
Glenn Adams wrote:
I would suggest you check the current trunk (you can use a nightly
build if
you don't want to build
What, am I supposed to guess your output? Come on now, how about an input
FO and output PDF file? Jeez.
Further, have you checked that this font actually contains a GSUB table
with a 'liga' feature that enables the mapping you wish?
On Wed, May 29, 2013 at 2:40 PM, honyk j.tosov...@email.cz
The addition of Complex Script support in FOP 1.1 is the cause. The font
actually controls whether ligatures are used or not.
The following features are enabled by default for all scripts which do not
otherwise override this feature set:
GSUB: {ccmp, liga, locl}
GPOS: {kern, mark, mkmk}
See
added a couple of New Feature issues on these items:
https://issues.apache.org/jira/browse/FOP-2256
https://issues.apache.org/jira/browse/FOP-2257
Kind regards,
Ulrich
Glenn Adams wrote:
The addition of Complex Script support in FOP 1.1 is the cause. The font
actually controls whether
Support for Advanced Typographic Tables (GSUB, GPOS, etc) [1] was added in
1.1 to support complex scripts [2]. You can also use these same complex
script features with non complex scripts, provided the font supports the
desired features [3].
At present, the default features enabled for all
You can start by filing a bug in JIRA, and supplying the following:
(1) input XSL-FO test file, in a maximally minimal form to show the problem
(2) sample output PDF from that input, showing the problem
(3) information about version and configuration
(4) any console output produced
See [1] for
Put each page-sequence in a separate XSL-FO file.
On Thu, Apr 18, 2013 at 5:09 AM, aemitic aemi...@hotmail.it wrote:
Hi,
I noticed that FOP (any version) uses a constantly growing amount of memory
when creating PDFs. Even if using very small page-sequence blocks and no
forward references.
use a separate tool to combine the PDFs
On Thu, Apr 18, 2013 at 8:31 AM, aemitic aemi...@hotmail.it wrote:
@Glenn Adams-2
Could you please elaborate more?
Transforming multiple XSL-FO files with FOP would mean to produce multiple
XSL-FO files, wouldn't it?
I need to produce a single PDF
It depends on what tool you use to combine them. In any case, I don't think
you will find an alternative any time soon. Just a heads up. If you care to
create a patch that solves this problem, then please post it and I'll make
sure it is applied ASAP.
On Thu, Apr 18, 2013 at 9:01 AM, aemitic
1 - 100 of 290 matches
Mail list logo