DO NOT REPLY [Bug 33729] New: - basic-link external-destination (.pdf#dest=) only open pdf file not destination
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=33729. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=33729 Summary: basic-link external-destination (.pdf#dest=) only open pdf file not destination Product: Fop Version: all Platform: PC OS/Version: Windows XP Status: NEW Severity: normal Priority: P2 Component: pdf renderer AssignedTo: fop-dev@xml.apache.org ReportedBy: [EMAIL PROTECTED] If I have this: fo:basic-link external-destination=url(destdoc.pdf#dest=destlinkend)some text/fo:basic-link and when I click to link some text then is open pdf file at first page not on page where is destlinkend. In destdoc.pdf basic-link internal-destination work OK: fo:basic-link internal-destination=destlinkendsome text/fo:basic-link -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
DO NOT REPLY [Bug 32327] - Basic-link w/ 'mailto:' URL behave improperly
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=32327. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=32327 --- Additional Comments From [EMAIL PROTECTED] 2004-11-23 18:58 --- Follow-up on fop-user leads to the conclusion that PDF form fields should be used for this. Consider possibility of incorporating the required code from Florian Hecht's PDF Forms FO extension: http://wwwstud.ira.uka.de/~s_hecht/ -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
DO NOT REPLY [Bug 32327] New: - Basic-link w/ 'mailto:' URL behave improperly
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=32327. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=32327 Summary: Basic-link w/ 'mailto:' URL behave improperly Product: Fop Version: 1.0dev Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: pdf renderer AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] (moved here from fop-user) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] I'm putting an email link into my pdf using teh following fop syntax in my xsl... E-mail: fo:basic-link external-destination=mailto:[EMAIL PROTECTED] [EMAIL PROTECTED]/fo:basic-link Clicking on the link in the created PDF brings up an email client ok but it also brings up a browser which tries to access the url 'mailto:[EMAIL PROTECTED]'. I have verified this. Indeed 0.20.5 opens up a browser, and so does HEAD. I can't seem to find *any* reference to this in the PDF Specification, but apparently iText succeeds in adding 'mailto:' links that perform the correct action. We'll definitely have to have a look at how iText handles these (when we have some spare-time) -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
DO NOT REPLY [Bug 31039] New: - URL in basic-link is scrambled by encryption
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=31039. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=31039 URL in basic-link is scrambled by encryption Summary: URL in basic-link is scrambled by encryption Product: Fop Version: 0.20.5 Platform: PC OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: pdf renderer AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] When I process a document with a tag fo:basic-link external-destination=whateversometext/fo:basic-link the link in the resulting pdf points to something that I presume is the *encrypted* URL. This of course doesn't work. I am using JDK 1.4.2 on linux and the Bouncy Castle crypto provider version 1.24.
DO NOT REPLY [Bug 31039] - URL in basic-link is scrambled by encryption
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=31039. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=31039 URL in basic-link is scrambled by encryption --- Additional Comments From [EMAIL PROTECTED] 2004-09-03 13:56 --- Created an attachment (id=12629) example xml
DO NOT REPLY [Bug 31039] - URL in basic-link is scrambled by encryption
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=31039. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=31039 URL in basic-link is scrambled by encryption --- Additional Comments From [EMAIL PROTECTED] 2004-09-03 13:56 --- Created an attachment (id=12630) example xsl
DO NOT REPLY [Bug 31039] - URL in basic-link is scrambled by encryption
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=31039. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=31039 URL in basic-link is scrambled by encryption --- Additional Comments From [EMAIL PROTECTED] 2004-09-03 13:57 --- Created an attachment (id=12631) example pdf with no encryption (link works)
DO NOT REPLY [Bug 31039] - URL in basic-link is scrambled by encryption
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=31039. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=31039 URL in basic-link is scrambled by encryption --- Additional Comments From [EMAIL PROTECTED] 2004-09-03 13:58 --- Created an attachment (id=12632) example pdf with printing disabled (link doesn't work)
DO NOT REPLY [Bug 27111] New: - basic-link after some elements/attributes does not render hyperlink in output PDF
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27111.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27111
basic-link after some elements/attributes does not render hyperlink in output PDF
Summary: basic-link after some elements/attributes does not
render hyperlink in output PDF
Product: Fop
Version: 0.20.5
Platform: PC
OS/Version: Windows XP
Status: NEW
Severity: Normal
Priority: Other
Component: pdf renderer
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
A) normal example (under flow):
fo:block-container border-color=#E0F0E0 background-color=#F0F0F0 border-
style=solid/
fo:block
fo:basic-link color=green external-destination=url
('http://xml.apache.org/fop')http://xml.apache.org/fop/fo:basic-link
/fo:block
...in output PDF is all OK - WEB link is working.
B) problem example modification (under flow):
I add only one attribute padding=1cm to fo:block-container element...
fo:block-container border-color=#E0F0E0 background-color=#F0F0F0 border-
style=solid padding=1cm/
fo:block
fo:basic-link color=green external-destination=url
('http://xml.apache.org/fop')http://xml.apache.org/fop/fo:basic-link
/fo:block
...and the link in output PDF not work now!
Leos
DO NOT REPLY [Bug 25467] - basic-link external-destination to http://site/document.pdf broken
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25467.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25467
basic-link external-destination to http://site/document.pdf broken
--- Additional Comments From [EMAIL PROTECTED] 2003-12-22 11:45 ---
Hello community,
Not knowing if this is a bug or a feature
I solved this for me patching the file
org.apache.fop.pdf.PDFDocument.java
with the following
1080a1081
if (!destination.startsWith(http://;)) {
1103a1105,1108
} else { // URI
PDFUri uri = new PDFUri(destination);
link.setAction(uri);
}
HTH someone with the same problems.
Regards,
Claus
DO NOT REPLY [Bug 25467] New: - basic-link external-destination to http://site/document.pdf broken
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25467. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25467 basic-link external-destination to http://site/document.pdf broken Summary: basic-link external-destination to http://site/document.pdf broken Product: Fop Version: 0.20.4 Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: Other Component: pdf renderer AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Hello, FOP works fine ... almost ;-) I get a strange thing when rendering basic-links to PDF files. I render all external links using xsl:element name=fo:basic-link xsl:attribute name=colorblue/xsl:attribute xsl:attribute name=external-destination xsl:value-of select=$target/ /xsl:attribute xsl:value-of select=$text/ /xsl:element Some are ordinary URLs like http://www1.etad.com/signon.xml?url=document_detail.xml%3Fser_no%3D30036 they come out fine. others are http://www.etad.com/Abstract/2003/12140.pdf They do not work in Acrobat 5.0 I get a FILE not found error. If I look in the binary file I see that the first translates in somthing like: /URI (http://www1.etad.com/document_detail.xml?ser_no= 30036) /S /URI This works perfectly. But the second becomes: /Type /FileSpec /F (http://www.etad.com/Abstracts/2003/12140.pdf) And this thing does not work. I guess this a bug? I would like to get it translated the same. Best regards, Claus
Re: PDF meta properties (was Re: basic-link)
Clay Leeds wrote: I was unaware that FOP has the ability to add Producer, Author and Title properties It can be set via the PDF renderer API, at least for HEAD. Maybe the producer is hardcoded to FOP or something (look into the source for details). It's not accessible on the command line yet. J.Pietschmann
RE: PDF meta properties (was Re: basic-link)
-Original Message- From: Clay Leeds [mailto:[EMAIL PROTECTED] I was unaware that FOP has the ability to add Producer, Author and Title properties to FOP. In fact, the web site still shows FOP does not currently support several desirable PDF features: document properties (title, author, etc.), and watermarks.: http://xml.apache.org/fop/output.html#pdf Maestro, Hold yer horses here... I had to do a bit of browsing around in the code to find out that support for these is already implemented. Once I saw this, it was merely a question of calling the appropriate method(s) in the Driver. (In fact, the producer field was already being used. At first I added the other properties to the code myself, after reading a bit through the pdf spec based upon what was already there... Only to find out later on that these were also added by dev... :) ) If support for these have been added, I think it would be great to add this info to the web site. If it's been added to 1.0Dev then, as Emily Litella would say... never mind. Hmmm... I doubt the way it works right now deserves to be put on the site somewhere, but still it's probably nice for some users to know that these features are already available under the surface somewhere. Greetz, Andreas
DO NOT REPLY [Bug 23099] New: - Computed contents inside of basic-link doesn't create a link
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23099.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23099
Computed contents inside of basic-link doesn't create a link
Summary: Computed contents inside of basic-link doesn't create a
link
Product: Fop
Version: 0.20.5
Platform: Sun
OS/Version: Solaris
Status: NEW
Severity: Normal
Priority: Other
Component: pdf renderer
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
It seems that computed contents of a fo:basic-link element does not create
a link in the rendered output. This happens at least with fo:leader and
fo:page-number-citation.
I want to generate an index, linking the page numbers with the occurences
of the keywords like this:
fo:basic-link internal-destination={generate-id()}
fo:page-number-citation ref-id={generate-id()} /
/fo:basic-link
No success.
If static text occurs within the link, only this text acts as the link anchor,
for examples in a table of contents (simplified):
fo:basic-link internal-destination={generate-id()}
xsl:value-of select=. / !-- ok --
fo:leader ... / !-- not ok, i.e. not linked --
fo:page-number-citation ref-id={generate-id()} / !-- dito --
/fo:basic-link
DO NOT REPLY [Bug 22053] New: - basic-link off by footer height in table
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22053. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22053 basic-link off by footer height in table Summary: basic-link off by footer height in table Product: Fop Version: 0.20.5 Platform: PC OS/Version: Windows XP Status: NEW Severity: Normal Priority: Other Component: pdf renderer AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] When adding a table-footer the hotspot for a basic-length appears to be offset toward the bottom by the height of the footer. Is the position incorrectly taking into account the table rows in the footer? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 14569] - basic-link problem
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14569. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14569 basic-link problem [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2002-12-02 21:22 --- Please, provide *reproducible* example of the problem. Your 450+Kb document screwed up and is useless, sorry. Please, always *attach* such a big documents, don't paste half of mega Kb into a bug description. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 14569] - basic-link problem
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14569. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14569 basic-link problem --- Additional Comments From [EMAIL PROTECTED] 2002-12-02 21:37 --- Oleg, I appreciate the advice, but I was actually creating an attachment to #14248 when Mozilla went down in a screaming heap. This mess is presumably the result. I'll try again. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 14569] - basic-link problem
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14569. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14569 basic-link problem --- Additional Comments From [EMAIL PROTECTED] 2002-12-02 21:51 --- Does anyone have any idea of how to clean this up? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 14569] - basic-link problem
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14569. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14569 basic-link problem --- Additional Comments From [EMAIL PROTECTED] 2002-11-19 08:32 --- Please, provide you fo document as *attachment*, not as plain text within a description. Your example was screwed up by hyphenations, I'm unable to fix 22 page document by hands. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: basic-link brocken (maintenance branch)
Hi guys, If the problem is that the link rectangles are now merged by default, I am the one that changed it. There was a bug: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9335 and I was doing a bunch of improvements to the positioning of the link rectangles. However, in this case, all I did was change the default merge behavior to yes. Is there something else broken? Regards, Karen Jeremias Maerki wrote: I fixed a bug there, but this obviously brought another. I'll have a look at it. On Wed, 13 Nov 2002 12:17:59 +0100 Christian Geisert wrote: Hi, I just discoverd that basic-link isn't working as expected in the maintenance branch (docs/example/fo/links.fo for example) It seems that mergelinks() is the problem so I'll change the default links.merge to no if there are no objections. (IIRC there has been some discussion about this but a quick search on the mailing list did not find anything) Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
BASIC-LINK
Hí again I'm going crazy with this kind of problems... I'm rendering a pdf file of 22 pages. at the first of the file, I have the following basic links: fo:block hyphenate='false' text-align='justify' text-align-last='start' line-height='12pt' font-size='9pt' space-before.optimum='1.5pt' space-after.optimum='1.5pt' keep-together='always' color='gray' fo:inline white-space-collapse='false'tarariiislkjalskjdflksjdflkasjdlfkasjdlfkasjldfkjasldfjl fo:basic-link color='#ff' text-decoration='underline' internal-destination='subprin3B'3B/fo:basic-link ,fo:basic-link color='#ff' text-decoration='underline' internal-destination='subprin3D'3D/fo:basic-link ,fo:basic-link color='#ff' text-decoration='underline' internal-destination='subprin6D'6D/fo:basic-link ,fo:basic-link color='#ff' text-decoration='underline' internal-destination='subprin6H'6H/fo:basic-link. /fo:inline/fo:block- after of this, the rest o the fo file, with some blocks fo:block id='subprin3A' t... page n fo:block id='subprin3B' t... page k ... fo:block id='subprin3D' t... Well, the problem is with the basic link named: subprin3D. When fop render the fo file, the only message i get is: [INFO] [11] [INFO] [12] [INFO] [13] - and the render crashes... If I make different the name of the basic-link or the name of the block id, the pdf is well rendered. I have anothers .fo files with many more links that are well rendered, but this file no. Why ? Thanks at all, Sergio.
Re: BASIC-LINK
Sergio wrote: and the render crashes... If I make different the name of the basic-link or the name of the block id, the pdf is well rendered. I have anothers .fo files with many more links that are well rendered, but this file no. Why ? Looks too bizarre, open a bug in bugzilla and attach full fo document illustrating the problem. -- Oleg Tkachenko eXperanto team Multiconn Technologies, Israel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
basic-link brocken (maintenance branch)
Hi, I just discoverd that basic-link isn't working as expected in the maintenance branch (docs/example/fo/links.fo for example) It seems that mergelinks() is the problem so I'll change the default links.merge to no if there are no objections. (IIRC there has been some discussion about this but a quick search on the mailing list did not find anything) Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: basic-link brocken (maintenance branch)
I fixed a bug there, but this obviously brought another. I'll have a look at it. On Wed, 13 Nov 2002 12:17:59 +0100 Christian Geisert wrote: Hi, I just discoverd that basic-link isn't working as expected in the maintenance branch (docs/example/fo/links.fo for example) It seems that mergelinks() is the problem so I'll change the default links.merge to no if there are no objections. (IIRC there has been some discussion about this but a quick search on the mailing list did not find anything) Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 13406] - Using padding displaces basic-link
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13406. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13406 Using padding displaces basic-link [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2002-11-13 23:18 --- This is fixed in CVS (and therefore in the forthcoming 0.20.5 release) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 664] - Basic-Link does not move with its content, when using absolute postitioned block containers
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=664. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=664 Basic-Link does not move with its content, when using absolute postitioned block containers [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2002-11-11 23:46 --- Works with current CVS (maintenance branch) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 13406] - Using padding displaces basic-link
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13406. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13406 Using padding displaces basic-link --- Additional Comments From [EMAIL PROTECTED] 2002-11-06 09:18 --- I found the same problem within a table. As a workaround I added 'space' blocks in the cell fo:table-cell border-width=0.1pt border-style=solid !-- padding-top=5pt padding-bottom=5pt -- fo:block space-before.optimum=5pt/fo:block fo:block fo:basic-link color=blue xsl:attribute name=internal-destination xsl:value-of select=BusinessObject/Row/GLOBAL_ID/ /xsl:attribute xsl:value-of select=BusinessObject/Row/GLOBAL_ID/ /fo:basic-link /fo:block fo:block space-after=5pt/fo:block /fo:table-cell David Gilby [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 13406] New: - Using padding displaces basic-link
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13406. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13406 Using padding displaces basic-link Summary: Using padding displaces basic-link Product: Fop Version: 0.20.4 Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Normal Priority: Other Component: page-master/layout AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Overview Description: Consider a page with 2 blocks. The first contains some text and has the padding attribute set (for example, padding=5mm). The second contains an external basic-link. The resulting PDF file shows the two blocks correctly, but the active area of the basic-link (the area over which it's possible to follow the link) is set 10mm above the corresponding text. This bug is always reproducible. Steps to Reproduce: See the attached file Actual Results: The active area is 10mm above the corresponding text Expected Results: The active area must be over the corresponding text - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 13406] - Using padding displaces basic-link
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13406. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13406 Using padding displaces basic-link --- Additional Comments From [EMAIL PROTECTED] 2002-10-08 13:23 --- Created an attachment (id=3388) Test case - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 3462] - basic-link does not work in list-items inside tables other than 1st column
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3462. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3462 basic-link does not work in list-items inside tables other than 1st column [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2002-09-26 21:24 --- Should be in 0.20.5 on the maintenance branch. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 8968] - basic-link with internal-destination attribute doesn't work inside static-content element
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8968. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8968 basic-link with internal-destination attribute doesn't work inside static-content element [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2002-09-26 21:24 --- Should be in 0.20.5 on the maintenance branch. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Maintenance release: improvements to basic-link
Hi all, I haven't seen anything about the next maintenance release for about a week now, but I noticed that there had been some discussion about basic-link problems. In the meantime, I have improved the basic-link positioning and also made it work for external-graphic and foreign-inline-object, since I needed it for a project at work. It now works correctly when links are inside blocks and tables with before and/or after padding and borders; it also works inside list items in tables. The X positioning is corrected. Nothing else seems to be broken. :-) I've also changed the default behavior to make all the words into a single link rectangle; the current behavior can be forced by defining the system property links.merge to no. If there are no objections, I will commit this to the maintenance branch. -Karen J.Pietschmann wrote: Hi all, we should think about getting 0.20.5 out of the door. Yes, I know I'm behind with the doc, I really promise to get it ready this weekend... As for the Bugs to be fixed, what should get in? Choices: SNIP/ 3. Harder stuff - Links for non-text inlines(tried and failed: the link was misplaced, I think I know why but may still need some time) - Links in static content (no idea) SNIP/ J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 8968] - basic-link with internal-destination attribute doesn't work inside static-content element
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8968. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8968 basic-link with internal-destination attribute doesn't work inside static-content element [EMAIL PROTECTED] changed: What|Removed |Added Summary|basic-link with internal- |basic-link with internal- |destination atribute doesn't|destination attribute |work inside static-content |doesn't work inside static- |element |content element --- Additional Comments From [EMAIL PROTECTED] 2002-06-25 08:11 --- Duplicate bug #10179 observed that an external-destination basic-link did work in the fo:static-content flow-name=xsl-region-before region. But did not in the fo:static-content flow-name=xsl-region-after region. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 8968] - basic-link with internal-destination atribute doesn't work inside static-content element
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8968. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8968 basic-link with internal-destination atribute doesn't work inside static-content element [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Additional Comments From [EMAIL PROTECTED] 2002-06-24 20:13 --- *** Bug 10179 has been marked as a duplicate of this bug. *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 8968] New: - basic-link with internal-destination atribute doesn't work inside static-content element
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8968. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8968 basic-link with internal-destination atribute doesn't work inside static-content element Summary: basic-link with internal-destination atribute doesn't work inside static-content element Product: Fop Version: all Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Normal Priority: Other Component: page-master/layout AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] The basic-link element refering to an internal destination seems not to work inside static-contet (doesn't matter wich region it's inside). There's no warning or error message during rendering, but the link doesn't appear in the final result. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 3007] - broken basic-link when referencing a following page
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3007. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3007 broken basic-link when referencing a following page [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2002-05-06 16:13 --- The test case works in 0.20.3. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 964] - FOP 0.17 throws exception with basic-link in xsl-region-before/after
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=964. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=964 FOP 0.17 throws exception with basic-link in xsl-region-before/after [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Priority||High Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2002-05-03 15:45 --- Works with 0.20.3 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 1231] - basic-link can't link to a page-sequence element
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1231. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1231 basic-link can't link to a page-sequence element [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||DUPLICATE --- Additional Comments From [EMAIL PROTECTED] 2002-05-03 16:02 --- *** This bug has been marked as a duplicate of 635 *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 964] - FOP 0.17 throws exception with basic-link in xsl-region-before/after
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=964. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=964 FOP 0.17 throws exception with basic-link in xsl-region-before/after [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Additional Comments From [EMAIL PROTECTED] 2002-04-22 10:38 --- *** Bug 2331 has been marked as a duplicate of this bug. *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 3204] - basic link mouse sensitive area wrongly positioned
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3204. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3204 basic link mouse sensitive area wrongly positioned [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||DUPLICATE --- Additional Comments From [EMAIL PROTECTED] 2002-04-22 10:47 --- *** This bug has been marked as a duplicate of 3061 *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 3007] - broken basic-link when referencing a following page
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3007. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3007 broken basic-link when referencing a following page [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] ||rostock.de --- Additional Comments From [EMAIL PROTECTED] 2002-04-22 10:49 --- *** Bug 3354 has been marked as a duplicate of this bug. *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 3007] - broken basic-link when referencing a following page
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3007. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3007 broken basic-link when referencing a following page [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] ||aachen.de --- Additional Comments From [EMAIL PROTECTED] 2002-04-22 10:50 --- *** Bug 3379 has been marked as a duplicate of this bug. *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 3462] - basic-link does not work in list-items inside tables other than 1st column
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3462. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3462 basic-link does not work in list-items inside tables other than 1st column --- Additional Comments From [EMAIL PROTECTED] 2002-04-22 11:14 --- The links are there, the areas are shifted to the upper left corner of the table. Another example that link area calculation is still seriously broken in 0.20.3. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 3007] - broken basic-link when referencing a following page
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3007. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3007 broken basic-link when referencing a following page [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Additional Comments From [EMAIL PROTECTED] 2002-04-22 11:17 --- *** Bug 5718 has been marked as a duplicate of this bug. *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 5888] - basic-link gets wrong coordinates when using padding-top somewhere above
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5888. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5888 basic-link gets wrong coordinates when using padding-top somewhere above [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||DUPLICATE --- Additional Comments From [EMAIL PROTECTED] 2002-04-22 11:19 --- *** This bug has been marked as a duplicate of 3061 *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 3007] - broken basic-link when referencing a following page
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3007.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3007
broken basic-link when referencing a following page
--- Additional Comments From [EMAIL PROTECTED] 2002-02-25 14:01 ---
The same patch should also be applied in org/apache/fop/fo/flow/Block.java:
if (area.getIDReferences() != null)
{
// area.getIDReferences().createID(id);
area.getIDReferences().createUnvalidatedID(id);
area.getIDReferences().addToIdValidationList(id);
}
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
RE: basic-link internal-destination
the id has to be unique.. possibly ur assigning the same id at more than one location in your document.. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Monday, November 26, 2001 12:15 PM To: [EMAIL PROTECTED] Subject: fo:basic-link internal-destination Hi, I'm facing a problem in basic-link internal-destination. The problem is, when my document in first page contain internal-destination attribute then in second page contains the id attribute (which refer to internal-destination). When I run fop.0.20.1 the fop given me an error The 'id' already exists in the document. If my document contain internal-destination attribute and id attribute on same page then the fop can produce pdf file for me. So, I hope that anyone can tell how to solved the problem. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 4373] - Cannot use xslt:attribute inside basic-link
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4373. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4373 Cannot use xslt:attribute inside basic-link [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2001-10-23 12:48 --- Sorry it's my fault. It has been just an xslt error. Making as INVALID - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: [DO NOT REPLY: Bug 3007] broken basic-link when referencing a following page
It is commited into the current CVS-tree but not in the recent release 0.20.1. Enrico 01:50 --- + Am also experiencing similar difficulties. + I see there is a work around supplied but not added to the product. When is it + likely that the fix will be applied to the core product? Unfortunately I am not + competent enough in OpenSource development projects to achieve this myself yet, + otherwise obviously I would do so. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Basic Link
Basic links that have a destination that will be on a following page are broken. The changes involving the stream renderer do not check to make sure that the links are resolved before rendering the page, or more correctly, the id references don't care about basic links. To fix this someone will need to implement something so that the IDReference's know that there are unresolved links on a page. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Basic Link
Basic links that have a destination that will be on a following page are
broken.
The changes involving the stream renderer do not check to make sure that
the links are resolved before rendering the page, or more correctly, the id
references don't care about basic links.
You have just found the reason for Bug #3354 which I've searched for
several hours. Thank you very much! That explains that when copying the
lines where the link is into an new file no error happens, because the
link and the destination are on the same page.
MfG, Daniel
--
Daniel Knapp [EMAIL PROTECTED]
int a=1,b,c=2800,d,e,f[2801],g;main(){for(;b-c;)f[b++]=a/5;for(;d=0,
g=c*2;c-=14,printf(%.4d,e+d/a),e=d%a)for(b=c;d+=f[b]*a,f[b]=d%--g,d/=
g--,--b;d*=b);} berechnet Pi auf 800 Stellen genau. :-)
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
Re: Basic Link
Basic links that have a destination that will be on a following page are
broken.
The changes involving the stream renderer do not check to make sure that
the links are resolved before rendering the page, or more correctly, the id
references don't care about basic links.
Unfortunately that's not always correct, I've found an example against
your theory. The basic-link is on page 2, the referenced link is on page
1. Have a look at the attached .fo and .pdf-file (don't be confused, the
links are invisible).
MfG, Daniel
--
Daniel Knapp [EMAIL PROTECTED]
int a=1,b,c=2800,d,e,f[2801],g;main(){for(;b-c;)f[b++]=a/5;for(;d=0,
g=c*2;c-=14,printf(%.4d,e+d/a),e=d%a)for(b=c;d+=f[b]*a,f[b]=d%--g,d/=
g--,--b;d*=b);} berechnet Pi auf 800 Stellen genau. :-)
?xml version=1.0 encoding=ISO-8859-1?
!-- edited with XML Spy v3.5 NT (http://www.xmlspy.com) by Daniel Knapp (Universität
Rostock) --
fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format;
fo:layout-master-set
fo:simple-page-master master-name=A4 page-width=210mm
page-height=297mm margin-top=15mm margin-bottom=15mm margin-left=25mm
margin-right=25mm
fo:region-before extent=15mm/
fo:region-body margin-top=15mm margin-bottom=15mm/
fo:region-after extent=15mm/
/fo:simple-page-master
/fo:layout-master-set
fo:page-sequence master-name=A4
fo:static-content flow-name=xsl-region-before
fo:block font-size=9pt
text-align=centertest_blockfo:block/
fo:leader leader-length=160mm leader-pattern=rule
rule-thickness=2pt/
/fo:block
/fo:static-content
fo:static-content flow-name=xsl-region-after
fo:block
fo:leader leader-length=160mm leader-pattern=rule
rule-thickness=2pt/
/fo:block
fo:block font-size=9pt
fo:table
fo:table-column column-width=150mm/
fo:table-column column-width=10mm/
fo:table-body
fo:table-row
fo:table-cell
fo:block
font-size=9ptH.-R. Vatterrott
(Universität Rostock)
/fo:block
/fo:table-cell
fo:table-cell
fo:block
font-size=9pt text-align=end
fo:page-number/
/fo:block
/fo:table-cell
/fo:table-row
/fo:table-body
/fo:table
/fo:block
/fo:static-content
fo:flow flow-name=xsl-region-body
fo:block
fo:table
fo:table-column column-width=160mm/
fo:table-body
fo:table-row
fo:table-cell
fo:block
fo:external-graphic src=image_common/abstandu.gif/
/fo:block
/fo:table-cell
/fo:table-row
fo:table-row
fo:table-cell
fo:block
font-weight=bold font-size=20pt text-align=start line-height=36pt
id=testtest/fo:block
/fo:table-cell
/fo:table-row
/fo:table-body
/fo:table
/fo:block
fo:block font-size=12pt text-align=justify
line
RE: Basic Link
I applied the patch, which seemed to solve the problem, but I would like someone to examine it and change a bit. 1. the idValidation vs. idUnvalidated names are very confusing without comments that explain what's what. 2. the createID method needs better commenting. I'm not entirely sure I correctly understand it, so I didn't do so. Thanks for the patch L. McKenzie (?), but please send patches to the list so we won't miss them. We don't mind the full files if you don't have access to CVS, either, but we'll include them faster if you do: diff -u MyJava.java.orig MyJava.java patchfile.diff Enrico, thanks for pointing this patch as it was languishing. -Steve -Original Message- From: Enrico Schnepel [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 30, 2001 4:34 PM To: [EMAIL PROTECTED] Subject: Re: Basic Link Hello Keiron, I had the same problem a few weeks ago and the bug is in the buglist as bug 3007. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3007 The bug was resolved by [EMAIL PROTECTED] but is not merged yet I've attached the corresponding files which resolves the problem. Enrico - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
[DO NOT REPLY: Bug 1231] basic-link can't link to a page-sequence element
PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL BE LOST SOMEWHERE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1231 *** shadow/1231 Sun May 20 17:24:39 2001 --- shadow/1231.tmp.7007Tue Aug 28 06:00:17 2001 *** *** 1,19 ! Bug#: 1231 ! Product: Fop ! Version: all ! Platform: All ! OS/Version: All ! Status: NEW ! Resolution: ! Severity: Normal ! Priority: ! Component: general ! AssignedTo: [EMAIL PROTECTED] ! ReportedBy: [EMAIL PROTECTED] ! URL: ! Cc: ! Summary: basic-link can't link to a page-sequence element ! It seems that when a basic-link element has got an internal-destination attribute that points to a page-sequence element, FOP won't find the ID, and complains that an ID was referenced but not found. --- 1,18 ! ++ ! | basic-link can't link to a page-sequence element | ! ++ ! |Bug #: 1231Product: Fop | ! | Status: NEW Version: all | ! | Resolution:Platform: All | ! | Severity: Normal OS/Version: All | ! | Priority: High Component: general | ! ++ ! | Assigned To: [EMAIL PROTECTED] | ! | Reported By: [EMAIL PROTECTED] | ! ++ ! | URL: | ! ++ ! | DESCRIPTION | It seems that when a basic-link element has got an internal-destination attribute that points to a page-sequence element, FOP won't find the ID, and complains that an ID was referenced but not found. *** *** 38,41 (this can be reproduced with the DocBook DTD and associated style sheets : page number is not set in TOC for chapters and other top-level components) ! Sylvain --- 37,40 (this can be reproduced with the DocBook DTD and associated style sheets : page number is not set in TOC for chapters and other top-level components) ! Sylvain - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
[DO NOT REPLY: Bug 3204] basic link mouse sensitive area wrongly positioned
PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL BE LOST SOMEWHERE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3204 *** shadow/3204 Tue Aug 21 06:16:46 2001 --- shadow/3204.tmp.3201Tue Aug 21 06:21:23 2001 *** *** 17,20 (For 0.20.1, PDF) basic-link mouse sensitive area is to the north-east of the basic-link text, making it rather difficult to click the link. ! See TOC in attached PDF. --- 17,24 (For 0.20.1, PDF) basic-link mouse sensitive area is to the north-east of the basic-link text, making it rather difficult to click the link. ! See TOC in attached PDF. ! ! --- Additional Comments From [EMAIL PROTECTED] 2001-08-21 06:21 --- ! Created an attachment (id=432) ! PDF where TOC links are off - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
[DO NOT REPLY: Bug 3204] basic link mouse sensitive area wrongly positioned
PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL BE LOST SOMEWHERE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3204 *** shadow/3204 Tue Aug 21 06:21:23 2001 --- shadow/3204.tmp.3212Tue Aug 21 06:21:59 2001 *** *** 22,24 --- 22,29 --- Additional Comments From [EMAIL PROTECTED] 2001-08-21 06:21 --- Created an attachment (id=432) PDF where TOC links are off + + + --- Additional Comments From [EMAIL PROTECTED] 2001-08-21 06:21 --- + Created an attachment (id=433) + source attached PDF file - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: [Bug 3007] - broken basic-link when referencing a following page
Hi, thank you for resolving the problem. Your files are working fine. I am running into another problem now but I am still trying to locate and separate it. Regards Enrico -- Aufgepasst - jetzt viele 11 New WebHosting Pakete ohne Einrichtungsgebuehr + 1 Monat Grundgebuehrbefreiung! http://puretec.de/index.html?ac=OM.PU.PU003K00736T0492a - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
[Bug 3007] - broken basic-link when referencing a following page
PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL BE LOST SOMEWHERE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3007 *** shadow/3007 Wed Aug 8 14:33:35 2001 --- shadow/3007.tmp.9409Wed Aug 8 14:35:21 2001 *** *** 131,133 --- 131,166 --- Additional Comments From [EMAIL PROTECTED] 2001-08-08 14:33 --- Created an attachment (id=401) Modified PDFDocmument.java + + + --- Additional Comments From [EMAIL PROTECTED] 2001-08-08 14:35 --- + I ran into the same problem and did some digging. I believe I've located the + problem. The problem is that the PDFDocument class sometimes creates an IDNode + for an ID before the IDReferences.createID gets called. When createID gets + called a bit later, it sees that the ID already exists and things it's a + duplicate. + + I made the following modifications to IDReferences, and that seemed to clear up + the problem: + + 1. Created a new attribute 'unvalidatedIds' to track IDs that have been created, + but not validated. + + 2. Created methods to add to, remove from and search for an ID in the + unvalidatedIds list. Modified constructor to initialize the list. + + 3. Modified createID to check if the Id is in the unvalidatedIds. If so, it + removes it from the list (as well as from the idValidation list). It does NOT + raise a dup error : + + 4. Added a CreateUnvalidatedID(ID as String) method that calls createNewId, AND + adds the new id to the unvalidateIds list. + + 5. Modified PDFDocument.getGoToReference to call CreateUnvalidatedID instead of + createNewId + + I've attached the modified java files. (Hope it's ok this way. Didn't have + time to pursue installing/using CVS) You may wish to consider a different name + than unvalidatedId (the similarity with idValidation may cause confusion). I + couldn't come up with anything better in the 5 minutes I spent thinking about it + : - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
