Re: Handling of text-align=justify when nesting blocks

2004-09-03 Thread Luca Furini
Arnd Beißner wrote:

 In the example, line 2 is neither the last nor the only line of a block,
 and it's also not a line ending in U+000A, so it should be justified.

Section 7.15.10 of the recommendation states that the property
text-align-last Specifies the alignment of the last line-area child of the
last block-area generated and returned by the formatting object, *and to any
line-area generated by the formatting object whose following sibling is a
block-area that is not a line-area*, and any lines in the block ending in
U+000A.

So, as a fo:block generates a block-area that is not a line-area (its
children are line-areas), I think line 2 should *not* be justified.

Regards
Luca






Re: DO NOT REPLY [Bug29124] - New line breaking algorithm

2004-09-03 Thread Luca Furini

Simon Pepping wrote:

 You mention that you have not implemented the Knuth algorithm for
 ContentLM. Would it be difficult to do that?

No, I have almost done.
I think I will be able to attach a patch including this fix this
afternoon.

Regards
Luca





Re: Handling of text-align=justify when nesting blocks

2004-09-03 Thread arnd . beissner
Luca Furini [EMAIL PROTECTED] schrieb am 03.09.2004 10:19:06:

 Section 7.15.10 of the recommendation states that the property
 text-align-last Specifies the alignment of the last line-area child of 
the
 last block-area generated and returned by the formatting object, *and to 
any
 line-area generated by the formatting object whose following sibling is 
a
 block-area that is not a line-area*, and any lines in the block ending 
in
 U+000A.

Thanks for digging this out. I will make a suggestion to the
xsl-editors to change the wording in 7.15.9 accordingly.

Thanks,

Arnd
-- 
Arnd Beißner
Cappelino Informationstechnologie GmbH


Handling of text-align=justify when nesting blocks

2004-09-03 Thread arnd . beissner
Editors,

please consider the following inconsistency in the recommendation:

Example:

fo:block text-align=justify
TEST TEST TEST TEST . ENOUGH TEXT TO FORMAT INTO MULTIPLE LINES 
 TEST ENDS A. 
fo:block
whatever
/fo:block
TEST TEST TEST TEST . ENOUGH TEXT TO FORMAT INTO MULTIPLE LINES 
 TEST ENDS B.
/fo:block

Now what would you expect:

Version A:

TEST TEST TEST TEST
TEST ENDS A.
whatever
TEST TEST TEST TEST
TEST ENDS B.

OR

Version B: (second line is justified)

TEST TEST TEST TEST
TEST   ENDS  A.
whatever
TEST TEST TEST TEST
TEST ENDS B.

Common sense would probably say A:

But, 7.15.9 of the rec says:

The last (or only) line of any block, and any lines in the block ending in 

U+000A, will be aligned in accordance with the text-align-last
property value. If such lines are to be justified specify
text-align-last='justify'.

In the example, line 2 is neither the last nor the only line of a block, 
and it's also not a line ending in U+000A, so it should be justified.

In contrast to this, 7.15.10 (text-align-last) says
(thanks to Luca Furini for the hint):

Specifies the alignment of the last line-area child of the last
block-area generated and returned by the formatting object, and to any
line-area generated by the formatting object whose following sibling is a
block-area that is not a line-area, and any lines in the block ending in 
U+000A.

If 7.15.9 were worded like 7.15.10, the example would be formatted like
in Version A, which is probably what the editors intended.

7.15.9 and 7.15.10 now clearly contradict each other, IMO.
My suggestion is to change the cited portion of 7.15.9 to the
following wording:

The last line-area child of the last block-area generated and returned
by the formatting object, and any line-area generated by the formatting
object whose following sibling is a block-area that is not a line-area,
and any lines in the block ending in U+000A, will be aligned in accordance
with the text-align-last property value. If such lines are to be
justified specify text-align-last='justify'.

Thanks for considering this,

Arnd
-- 
Arnd Beißner
Cappelino Informationstechnologie GmbH


DO NOT REPLY [Bug 31039] New: - URL in basic-link is scrambled by encryption

2004-09-03 Thread bugzilla
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

2004-09-03 Thread bugzilla
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

2004-09-03 Thread bugzilla
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

2004-09-03 Thread bugzilla
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

2004-09-03 Thread bugzilla
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)


Re: [Bug29124] - New line breaking algorithm

2004-09-03 Thread Simon Pepping
On Fri, Sep 03, 2004 at 10:23:27AM +0200, Luca Furini wrote:
 
 Simon Pepping wrote:
 
  You mention that you have not implemented the Knuth algorithm for
  ContentLM. Would it be difficult to do that?
 
 No, I have almost done.
 I think I will be able to attach a patch including this fix this
 afternoon.

I would rather commit the current patch, and then get a new patch
w.r.t. the committed code.

Regards, Simon

-- 
Simon Pepping
home page: http://www.leverkruid.nl