We have no idea what you hacked into your customized version. You'd better try to work with standard XSL-FO than to coerce FOP into doing what you expect. Maybe you should start by explaining the problem you'd like solved in the first place. It could be that you simply don't know about some funny little detail that would have solved your problem easily. Attach a (preferably small) FO file that demonstrates the problem. That's the easiest way to get us to look into a problem. Otherwise, you just get some not really helpful answers like mine here. :-)
BTW, I've explained it once before last week: It's generally a bad/risky idea to hack some private functionality into FOP and not publish it. Mainstream FOP development goes on and you may lose your investment in your code because suddenly, you can't easily upgrade anymore. Please work with us and we'll find the best solution together. That way you can protect your investments. I know, sometimes way may not be as responsive as one might wish. But if that happens, just keep bugging us. An issue may simply have slipped through the cracks. And yes, please upgrade from 0.92beta. ;-) Especially, since we have full support for internal destinations now. Jeremias Maerki On 19.11.2007 04:35:32 william wrote: > Hi, > > We're currently using 0.92beta. We have done some customization to the > fop version (in case you offer me to upgrade) > > The problem that I have currently is that: > For the purpose of the pdf output, I used initial-page-number = 1 to > reset the page number and start from 1 somewhere within the file. > As a result, some basic-link internal-destination does not point to the > right place even though the id has already been specified to the right > position. > > Suggestions are welcome. > > Thanks a lot, > wliem --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
