Many thanks for your answer.
It seems that we have the same issue with other PDF readers; so this is
unlikely to be a bug in Acroread.
We are left with the two other possibilitie (might also be a combination of
both...), that is either a bug in FOP 1 or in Docbook FO XSL.
For the later, I gues
>> and if not, is there anything that could be done
>> to restore the correct FOP behavior in XXE 4.8 or later ?
> If it's really a bug in FOP v1[*], that is, a regression from FOP v0.9,
> then the only solutions are:
>
> [a] Report the bug to the FOP dev team and wait for the next release of FOP.
Philippe Nobili wrote:
>>> and if not, is there anything that could be done
>>> to restore the correct FOP behavior in XXE 4.8 or later ?
>> If it's really a bug in FOP v1[*], that is, a regression from FOP v0.9,
>> then the only solutions are:
>>
>> [a] Report the bug to the FOP dev team and wait
On 06/08/2011 12:24 PM, Hussein Shafie wrote:
>
> We'll try to fix this DocBook XSL 1.76.1 bug in the next few days and
> we'll submit the patch to the DocBook XSL dev team.
>
> If we succeed in doing so, then the bug fix will be found in v4.9.1 (to
> be released next week).
>
That would be great;
L. H. Silli wrote:
>
> I was testing your product again. And in all the tests I made, I found
> that it deletes the Byte-Order Mark (BOM).
That's right.
> It also does not use the BOM
> to interpret the encoding.
XXE uses the Xerces XML parser and to my knowledge Xerces uses the BOM
to in
5 matches
Mail list logo
