The subject of this thread is misleading: the FOP 1.x plug-in which is a available as an add-on of XXE v4.7 works *very* *well*, either with the stock PDF fonts or with a custom set of fonts.
The problem occurs only when you create a customized FOP add-on including a custom set of fonts. This problem is almost certainly caused by something new to FOP 1.0 because on our side, we didn't change the plug-in code and this plug-in code used to work fine with FOP 0.95. Yes, we didn't take the time to test your very specific use case, but we have carefully tested all the other use cases. Therefore, we have no urge to fix this problem. We'll try to fix it for next release of XXE. May be before that if we have some time. Meanwhile, you are not stuck because you have 3 possible solutions: [1] Do not upgrade to XXE v4.7. [2] OR upgrade to XXE v4.7 but keep using your custom FOP add-on based on FOP 0.95. [3] OR pay us 4 xe-su units because you need a fixed FOP 1.0 plug-in urgently. See http://www.xmlmind.com/xmleditor/customization_service.html Philippe Nobili wrote: > On 11/04/2010 05:49 PM, Hussein Shafie wrote: >> >> Sorry for the misunderstanding, but I need the Java stack trace and not >> XXE's log of the process command execution. >> >> The Java stack trace consists in everything which follows >> "java.lang.StringIndexOutOfBoundsException: String index out of range". >> This Java stack trace may be a few dozen lines long in the case of >> nested exceptions. >> >> This Java stack trace will tell me in which part of the code (.java >> filename, linenumber) FOP's or XXE's, the problem occurred. > This is very clear; however, how do I get the Java stack trace ? all I > have is the message I sent yesterday at first, which is the following: > > Command execution has failed: > FOP XSL-FO processor error: > java.lang.StringIndex.OutOfBoundsException: String index out of range: 10 > > Nothing on the terminal apart from the message: > "Making portrait pages on A4 paper (210mmx297mm)" > > I understand this might be not sufficient to sort out the problem; is > there something else we can do to help you find out what went wrong ? > -- XMLmind XML Editor Support List [email protected] http://www.xmlmind.com/mailman/listinfo/xmleditor-support
