Re: Difference between fop 1.0 and trunk in font-base URL

2012-05-04 Thread Vincent Hennebert
Hi Alexios,

On 03/05/12 17:23, Alexios Giotis wrote:
 Hi,
 
 I noticed a difference to the way the font-base works in FOP configuration 
 file, when I upgrade from 1.0 to trunk. In 1.0, relative paths (for example 
 font-basesrc/test/data/fonts/font-base) are resolved against the current 
 working directory (of the java process), while in trunk relative paths are 
 resolved against the location of the fop.xconf file.
 
 Is it a bug or is this intentional ? In the latter case, what are the reasons 
 for this change ?

This is intentional and actually fixes the buggy previous behaviour.
A relative URI should be resolved against the URI of the containing
document, not the current directory in which the process is running.

See http://svn.apache.org/viewvc?revision=1058945view=revision
See also section 5.1 of the URI RFC: http://www.ietf.org/rfc/rfc3986.txt


 Alex Giotis

HTH,
Vincent

-
To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org



Re: Difference between fop 1.0 and trunk in font-base URL

2012-05-04 Thread Alexios Giotis
Helpful and in depth answer, 
Thanks Vincent


On May 4, 2012, at 11:31 AM, Vincent Hennebert wrote:

 Hi Alexios,
 
 On 03/05/12 17:23, Alexios Giotis wrote:
 Hi,
 
 I noticed a difference to the way the font-base works in FOP configuration 
 file, when I upgrade from 1.0 to trunk. In 1.0, relative paths (for example 
 font-basesrc/test/data/fonts/font-base) are resolved against the current 
 working directory (of the java process), while in trunk relative paths are 
 resolved against the location of the fop.xconf file.
 
 Is it a bug or is this intentional ? In the latter case, what are the 
 reasons for this change ?
 
 This is intentional and actually fixes the buggy previous behaviour.
 A relative URI should be resolved against the URI of the containing
 document, not the current directory in which the process is running.
 
 See http://svn.apache.org/viewvc?revision=1058945view=revision
 See also section 5.1 of the URI RFC: http://www.ietf.org/rfc/rfc3986.txt
 
 
 Alex Giotis
 
 HTH,
 Vincent
 
 -
 To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
 For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
 


-
To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org



Difference between fop 1.0 and trunk in font-base URL

2012-05-03 Thread Alexios Giotis
Hi,

I noticed a difference to the way the font-base works in FOP configuration 
file, when I upgrade from 1.0 to trunk. In 1.0, relative paths (for example 
font-basesrc/test/data/fonts/font-base) are resolved against the current 
working directory (of the java process), while in trunk relative paths are 
resolved against the location of the fop.xconf file.

Is it a bug or is this intentional ? In the latter case, what are the reasons 
for this change ?

Alex Giotis


-
To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org