Yuriko N. wrote:
We are having trouble using pdf add-on.
I am not sure how much support I can ask from you for this but please help if
possible.
We have Japanese and English characters mixed paragraph.
My guess is that this is quite common in the context of a large
corporation like yours.
For such case, pdf output do not go to next line at the right hand side end of
page
and keeps on printing on the same line even if it goes past the end of paper
range.
When it is a paragraph of ALL Japanese characters there is no problem. (as
checked with the first two paragraphs).
We see no trouble for word output. (As attached)
MS-Word output is created by our own XMLmind XSL-FO Converter (packaged
as an add-on), a commercial product: http://www.xmlmind.com/foconverter/
But the text justification is of course performed by MS-Word itself.
By default, PDF output is created using free, open source, Apache FOP
(packaged as an add-on): https://xmlgraphics.apache.org/fop/
There is no problem with RenderX XEP (packaged as an add-on), a
commercial product: http://www.renderx.com/tools/xep.html
See attached test01_xep.pdf (using Simplified Chinese fonts because I
already had these ready in my test environment, sorry!).
Therefore the culprit is Apache FOP. Mixing Japanese and English in the
same paragraph seems to defeat its word wrap algorithm.
Can you suggest if we need to announce some kind of character sequence
limitation
to users when writing Japanese data docs on XXE,
The suggested restriction "do not mix Japanese and English in the same
paragraph" would not be sustainable.
or if we can solve by adding parameters or properties when starting up XXE.
A) I've tested document conversion parameter justified=no (see attached
screenshot) and this does NOT solve the problem.
B) I've tested document conversion parameter hyphenate=no and this does
NOT solve the problem.
C) I've tested document conversion parameters justified=no and
hyphenate=no and this does NOT solve the problem.
D) I've tested wrapping every English text run in <ph xml:lang="en">
elements and this does NOT solve the problem.
E) I've tested this with an old but usable version of FOP, v1.1 (the
version before the implementation of "Improved support for complex
scripts") and this does NOT solve the problem.
I'm out of ideas.
This seems to be a quite ancient limitation of Apache FOP, for which
there is no workaround.
--
XMLmind XML Editor Support List
xmleditor-support@xmlmind.com
http://www.xmlmind.com/mailman/listinfo/xmleditor-support
