Hi,
RTF support is a bit broken in 1.1, see also
https://issues.apache.org/jira/browse/FOP-2182
You can workaround by not using a PageSequenceMaster, so use your simple
page master's name first as master-reference on the fo:page-sequence
element and it should process again without errors.
Hi Glenn,
I am trying to understand if Katakana japanese language is a BMP unicode as
per below link:
http://www.sttmedia.com/unicode-basiclingualplane
http://www.sttmedia.com/unicode-basiclingualplane
If I assume that Katakana is a 4-byte japanese language. As per your reply
if Katakana is
I just tried to upgrade from FOP 1.0 to 1.1 and while most things work, one RTF
document doesn't.
It worked smoothly with the 1.0 version, but now produces an empty zero-byte
OutputStream (ByteArrayOutputStream in my case).
No errors in the log, nothing.
The upgrade notes
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
