You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-users@xmlgraphics.apache.org by william <wl...@allette.com.au> on 2007/11/19 04:35:32 UTC
basic-link internal-destination wrong page
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: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
Re: basic-link internal-destination wrong page
Posted by william <wl...@allette.com.au>.
Thanks for looking at it with me. Not meaning to be rude, but I won't be
sending you any FO file. Please follow my reasoning below:
I've tried the fo with 0.20.5 and it's working fine as well.
And as you've also checked with 0.92beta and 0.93, so now I'll try to
have a look at the modified version of our 0.92beta.
I'll keep you posted if any findings might have caused this, for your
information.
Thank you,
William
Jeremias Maerki wrote:
> I've done a quick test shows that this should work just fine in 0.93,
> but it also works fine for me in 0.92beta.
>
> Maybe you've made a mistake somewhere. So again, please attach a
> (preferably small) FO file that demonstrates your problem.
>
> Jeremias Maerki
>
>
>
> On 19.11.2007 11:15:58 wliem wrote:
>
>> Thanks Jeremias,
>>
>> It happens that the basic-link points to page 1 in the next page-sequence
>> rather than the first page.
>>
>> Table of Content
>> Introduction .... 1
>> Content ...........2
>>
>> #######################
>> Actual Content of Page 1
>> abcdef
>>
>> Actual Content of Page 2
>> ghijkl
>>
>> Another Content with Page number set to 1
>> mnopqrs
>> ########################
>>
>> It happens when I click Introduction, it links to 'mnopqrs' instead of
>> 'abcdef' even though the block id links to 'abcdef'.
>> I know that I have to follow on the version upgrade to find the best
>> solution. But do you have any idea which version has
>> started to accommodate this?
>>
>> Many thanks,
>> wliem
>>
>>
>>> 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: fop-users-unsubscribe@xmlgraphics.apache.org
> For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
>
>
--
William Liem Email: wliem@allette.com.au
Allette Systems Pty Ltd.
Level 2, 73 Union St
Pyrmont NSW 2009 Australia
Tel: +61 2 9660 8866
Fax: +61 2 9660 8869
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
Re: basic-link internal-destination wrong page
Posted by Jeremias Maerki <de...@jeremias-maerki.ch>.
I've done a quick test shows that this should work just fine in 0.93,
but it also works fine for me in 0.92beta.
Maybe you've made a mistake somewhere. So again, please attach a
(preferably small) FO file that demonstrates your problem.
Jeremias Maerki
On 19.11.2007 11:15:58 wliem wrote:
> Thanks Jeremias,
>
> It happens that the basic-link points to page 1 in the next page-sequence
> rather than the first page.
>
> Table of Content
> Introduction .... 1
> Content ...........2
>
> #######################
> Actual Content of Page 1
> abcdef
>
> Actual Content of Page 2
> ghijkl
>
> Another Content with Page number set to 1
> mnopqrs
> ########################
>
> It happens when I click Introduction, it links to 'mnopqrs' instead of
> 'abcdef' even though the block id links to 'abcdef'.
> I know that I have to follow on the version upgrade to find the best
> solution. But do you have any idea which version has
> started to accommodate this?
>
> Many thanks,
> wliem
>
> > 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: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
Re: basic-link internal-destination wrong page
Posted by wl...@allette.com.au.
Thanks Jeremias,
It happens that the basic-link points to page 1 in the next page-sequence
rather than the first page.
Table of Content
Introduction .... 1
Content ...........2
#######################
Actual Content of Page 1
abcdef
Actual Content of Page 2
ghijkl
Another Content with Page number set to 1
mnopqrs
########################
It happens when I click Introduction, it links to 'mnopqrs' instead of
'abcdef' even though the block id links to 'abcdef'.
I know that I have to follow on the version upgrade to find the best
solution. But do you have any idea which version has
started to accommodate this?
Many thanks,
wliem
> 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: fop-users-unsubscribe@xmlgraphics.apache.org
> For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
Re: basic-link internal-destination wrong page
Posted by Jeremias Maerki <de...@jeremias-maerki.ch>.
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: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org