Re: Can not check out Trunk with SVN
Thank you J.Pietschmann, That works and brings me to my next question. Sorry for all the questions, but I am trying to learn :) When the check out starts I receive this message: svn: 'trunk' is already a working copy for a different URL; run 'svn update' to complete it So I run: svn update c:\fop_Home and get this message: Skipped 'C:\fop_Home' What am I doing wrong? Thanks, Bones bonekrusher wrote: Hi, please see related post: http://www.nabble.com/Setting-up-FOP-Trunk-in-Netbeans-6.1-td17338581.html The SVN repository is unavailable. http://svn.apache.org/repos/asf/xmlgraphics/fop/trunk/ Receiving the following error from SVN command line: C:\fop_Homesvn co http://svn.apache.org/repos/asf/xmlgraphics/fop/trunk/ svn: PROPFIND request failed on '/repos/asf/xmlgraphics/fop/trunk' svn: PROPFIND of '/repos/asf/xmlgraphics/fop/trunk': Could not read status line: An existing connection was forcibly closed by the remote host. (http://svn.apache.org) -- View this message in context: http://www.nabble.com/Can-not-check-out-Trunk-with-SVN-tp17404672p17423508.html Sent from the FOP - Dev mailing list archive at Nabble.com.
Re: Can not check out Trunk with SVN
Hi bonekrusher, It sounds like you have already checked out (partially or otherwise) http://svn.apache.org/repos/asf/xmlgraphics/fop/trunk. Its probably best to start again by deleting your c:\fop_Home directory and make a fresh clean checkout as J.Pietschmann suggested :- svn co https://svn.apache.org/repos/asf/xmlgraphics/fop/trunk Good luck! Adrian. bonekrusher wrote: Thank you J.Pietschmann, That works and brings me to my next question. Sorry for all the questions, but I am trying to learn :) When the check out starts I receive this message: svn: 'trunk' is already a working copy for a different URL; run 'svn update' to complete it So I run: svn update c:\fop_Home and get this message: Skipped 'C:\fop_Home' What am I doing wrong? Thanks, Bones bonekrusher wrote: Hi, please see related post: http://www.nabble.com/Setting-up-FOP-Trunk-in-Netbeans-6.1-td17338581.html The SVN repository is unavailable. http://svn.apache.org/repos/asf/xmlgraphics/fop/trunk/ Receiving the following error from SVN command line: C:\fop_Homesvn co http://svn.apache.org/repos/asf/xmlgraphics/fop/trunk/ svn: PROPFIND request failed on '/repos/asf/xmlgraphics/fop/trunk' svn: PROPFIND of '/repos/asf/xmlgraphics/fop/trunk': Could not read status line: An existing connection was forcibly closed by the remote host. (http://svn.apache.org)
DO NOT REPLY [Bug 45070] New: Spurious WARNING on span=inherit
https://issues.apache.org/bugzilla/show_bug.cgi?id=45070 Summary: Spurious WARNING on span=inherit Product: Fop Version: 0.94 Platform: PC URL: http://lists.oasis-open.org/archives/docbook- apps/200805/msg00094.html OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: general AssignedTo: fop-dev@xmlgraphics.apache.org ReportedBy: [EMAIL PROTECTED] When I transform the attached file to XSL-FO and process the resulting FO with FOP, I get this warning: WARNING: span=inherit on fo:block, but no explicit value found on the parent FO. I'm using the 1.73.2 DocBook XSL. I get this problem with both FOP 0.94 and FOP 0.95beta. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
DO NOT REPLY [Bug 45070] Spurious WARNING on span=inherit
https://issues.apache.org/bugzilla/show_bug.cgi?id=45070 --- Comment #1 from Andrew McFarland [EMAIL PROTECTED] 2008-05-23 05:44:40 PST --- Created an attachment (id=21991) -- (https://issues.apache.org/bugzilla/attachment.cgi?id=21991) simple docbook file that demonstrates the problem -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
Re: Can not check out Trunk with SVN
Thanks Adrian! Perfect Adrian Cumiskey wrote: Hi bonekrusher, It sounds like you have already checked out (partially or otherwise) http://svn.apache.org/repos/asf/xmlgraphics/fop/trunk. Its probably best to start again by deleting your c:\fop_Home directory and make a fresh clean checkout as J.Pietschmann suggested :- svn co https://svn.apache.org/repos/asf/xmlgraphics/fop/trunk Good luck! Adrian. bonekrusher wrote: Thank you J.Pietschmann, That works and brings me to my next question. Sorry for all the questions, but I am trying to learn :) When the check out starts I receive this message: svn: 'trunk' is already a working copy for a different URL; run 'svn update' to complete it So I run: svn update c:\fop_Home and get this message: Skipped 'C:\fop_Home' What am I doing wrong? Thanks, Bones bonekrusher wrote: Hi, please see related post: http://www.nabble.com/Setting-up-FOP-Trunk-in-Netbeans-6.1-td17338581.html The SVN repository is unavailable. http://svn.apache.org/repos/asf/xmlgraphics/fop/trunk/ Receiving the following error from SVN command line: C:\fop_Homesvn co http://svn.apache.org/repos/asf/xmlgraphics/fop/trunk/ svn: PROPFIND request failed on '/repos/asf/xmlgraphics/fop/trunk' svn: PROPFIND of '/repos/asf/xmlgraphics/fop/trunk': Could not read status line: An existing connection was forcibly closed by the remote host. (http://svn.apache.org) -- View this message in context: http://www.nabble.com/Can-not-check-out-Trunk-with-SVN-tp17404672p17425029.html Sent from the FOP - Dev mailing list archive at Nabble.com.
DO NOT REPLY [Bug 45070] Spurious WARNING on span=inherit
https://issues.apache.org/bugzilla/show_bug.cgi?id=45070 Vincent Hennebert [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |ASSIGNED --- Comment #2 from Vincent Hennebert [EMAIL PROTECTED] 2008-05-23 07:02:19 PST --- (This issue came up on the docbook-apps mailing list.) There are two problems IMO: - I don't see why FOP should issue a warning while such a construct is perfectly legal. I realize that this may help debugging stylesheets, but this will also annoy most users. - The code in PropertyMaker.make(PropertyList, String, FObj) looks suspicious. It tries to get the explicit value set on the parent, whereas it should get its /computed/ value. Granted, the end result is probably the same, still. Leaving it over to property specialists... Vincent -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
AUTO: Bradley Harrington/Austin/IBM is out of the office. (returning 05/27/2008)
I am out of the office until 05/27/2008. Please work with John Oustalett and Phil Hardy for Insight for SAP issues in my absense. I will respond to TPC Reporter issues when I return. If you have any questions, please contact my manager Jim Dilley. Thanks very much, Brad Note: This is an automated response to your message Re: Can not check out Trunk with SVN sent on 5/23/08 5:10:23. This is the only notification you will receive while this person is away.
DO NOT REPLY [Bug 45070] Spurious WARNING on span=inherit
https://issues.apache.org/bugzilla/show_bug.cgi?id=45070 --- Comment #3 from Andreas L. Delmelle [EMAIL PROTECTED] 2008-05-23 08:08:32 PST --- (In reply to comment #2) (This issue came up on the docbook-apps mailing list.) There are two problems IMO: - I don't see why FOP should issue a warning while such a construct is perfectly legal. I realize that this may help debugging stylesheets, but this will also annoy most users. Granted... Question in this particular case, however, is what the stylesheet authors hope to achieve by adding 'span=inherit' anyway. The property only has effect for areas returned by a flow-child. Although the property is not inherited, further descendants automatically take on the characteristics of their parent (see: http://www.w3.org/TR/xsl/#span) - The code in PropertyMaker.make(PropertyList, String, FObj) looks suspicious. It tries to get the explicit value set on the parent, whereas it should get its /computed/ value. Granted, the end result is probably the same, still. I think the reason behind the warning is indeed stylesheet debugging, in the sense that one would expect a value on the parent for a specified value of 'inherit' on the child (?) The keyword is permitted as a value for inherited properties, but hardly useful there... If used for non-inherited properties, then it should indeed evaluate to the computed value. The explicit value obtained in PropertyMaker is used /only/ to check whether there was a value specified on the parent. If this is not the case, then the computed value will evaluate to the initial value, and so could just as well have been omitted... All the same for me to have FOP shut up in those cases, or reduce it to debug-level. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
