Luis Bernardo (JIRA | 19 May 2013 00:39
Picon
Favicon

[jira] [Resolved] (FOP-2248) add support for AES 256 PDF encryption


     [
https://issues.apache.org/jira/browse/FOP-2248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luis Bernardo resolved FOP-2248.
--------------------------------

       Resolution: Implemented
    Fix Version/s: trunk

> add support for AES 256 PDF encryption
> --------------------------------------
>
>                 Key: FOP-2248
>                 URL: https://issues.apache.org/jira/browse/FOP-2248
>             Project: Fop
>          Issue Type: New Feature
>            Reporter: Luis Bernardo
>            Priority: Minor
>             Fix For: trunk
>
>         Attachments: fop.xconf, test.pdf
>
>
> AES 256 PDF encryption is described in PDF 1.7 Extension Level 3.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
(Continue reading)

Luis Bernardo (JIRA | 19 May 2013 00:39
Picon
Favicon

[jira] [Updated] (FOP-2248) add support for AES 256 PDF encryption


     [
https://issues.apache.org/jira/browse/FOP-2248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luis Bernardo updated FOP-2248:
-------------------------------

    Attachment: test.pdf
                fop.xconf

attached an example fop.xconf to use the new encryption. also attached a sample document encrypted. the
password is "userpassword".

> add support for AES 256 PDF encryption
> --------------------------------------
>
>                 Key: FOP-2248
>                 URL: https://issues.apache.org/jira/browse/FOP-2248
>             Project: Fop
>          Issue Type: New Feature
>            Reporter: Luis Bernardo
>            Priority: Minor
>         Attachments: fop.xconf, test.pdf
>
>
> AES 256 PDF encryption is described in PDF 1.7 Extension Level 3.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
(Continue reading)

Luis Bernardo (JIRA | 19 May 2013 00:35
Picon
Favicon

[jira] [Commented] (FOP-2248) add support for AES 256 PDF encryption


    [
https://issues.apache.org/jira/browse/FOP-2248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13661439#comment-13661439
] 

Luis Bernardo commented on FOP-2248:
------------------------------------

committed: http://svn.apache.org/viewvc?view=revision&revision=1484190.

Note: The above commit implements AES 256 PDF encryption as described in PDF 1.7 Extension Level 3 and
supported by Adobe Acrobat/Reader 9 (and higher). This first proposal for AES 256 encryption was shown to
have some shortcomings and was not accepted by the ISO committee that oversees the PDF spec. A second
proposal described in PDF 1.7 Extension Level 8, and which will be part of PDF 2.0 exists but the spec is not
publicly available. The first Adobe product to support this second implementation of AES 256 is
Acrobat/Reader 10. The current commit only implements the first proposal.

> add support for AES 256 PDF encryption
> --------------------------------------
>
>                 Key: FOP-2248
>                 URL: https://issues.apache.org/jira/browse/FOP-2248
>             Project: Fop
>          Issue Type: New Feature
>            Reporter: Luis Bernardo
>            Priority: Minor
>
> AES 256 PDF encryption is described in PDF 1.7 Extension Level 3.

--
(Continue reading)

Luis Bernardo (JIRA | 19 May 2013 00:21
Picon
Favicon

[jira] [Created] (FOP-2248) add support for AES 256 PDF encryption

Luis Bernardo created FOP-2248:
----------------------------------

             Summary: add support for AES 256 PDF encryption
                 Key: FOP-2248
                 URL: https://issues.apache.org/jira/browse/FOP-2248
             Project: Fop
          Issue Type: New Feature
            Reporter: Luis Bernardo
            Priority: Minor

AES 256 PDF encryption is described in PDF 1.7 Extension Level 3.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Pascal Sancho (JIRA | 16 May 2013 14:51
Picon
Favicon

[jira] [Updated] (FOP-1124) percent in table-cell width are not correctly handled


     [
https://issues.apache.org/jira/browse/FOP-1124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pascal Sancho updated FOP-1124:
-------------------------------

          Component/s:     (was: general)
                       page-master/layout
             Priority: Minor
    Affects Version/s: trunk
              Summary: percent in table-cell width are not correctly handled  (was: border-separation disturbs table layout)

After deeper analyse, the behaviour is caused by using percent values on table-cell, witch causes the
following error:

[ERROR] AbstractBaseLayoutManager - Cannot find LM to handle given FO for LengthBase. (fo:table-cell,
location: 13:63)

                
> percent in table-cell width are not correctly handled
> -----------------------------------------------------
>
>                 Key: FOP-1124
>                 URL: https://issues.apache.org/jira/browse/FOP-1124
>             Project: Fop
>          Issue Type: Bug
>          Components: page-master/layout
>    Affects Versions: 0.91, trunk
>         Environment: Operating System: Windows XP
(Continue reading)

Pascal Sancho (JIRA | 16 May 2013 14:51
Picon
Favicon

[jira] [Updated] (FOP-1124) percent in table-cell width are not correctly handled


     [
https://issues.apache.org/jira/browse/FOP-1124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pascal Sancho updated FOP-1124:
-------------------------------

    Attachment: _test.fo

reviewed test case

> percent in table-cell width are not correctly handled
> -----------------------------------------------------
>
>                 Key: FOP-1124
>                 URL: https://issues.apache.org/jira/browse/FOP-1124
>             Project: Fop
>          Issue Type: Bug
>          Components: page-master/layout
>    Affects Versions: 0.91, trunk
>         Environment: Operating System: Windows XP
> Platform: PC
>            Reporter: Pascal Sancho
>            Priority: Minor
>         Attachments: go_ex.fo, _test.fo
>
>
> When the table property border-separation.b-p-d is greater than 0:
> 1. the table header is not layed out if the table overflows the first page;
> 2. in Awt renderer, the vertical space between 2 cells seems to be ignored.
(Continue reading)

Guest User (JIRA | 16 May 2013 12:27
Picon
Favicon

[jira] [Created] (FOP-2247) Vertical table border differs width, when horizontal border is omitted

Guest User created FOP-2247:
-------------------------------

             Summary: Vertical table border differs width, when horizontal border is omitted
                 Key: FOP-2247
                 URL: https://issues.apache.org/jira/browse/FOP-2247
             Project: Fop
          Issue Type: Bug
          Components: pdf
    Affects Versions: 1.1
         Environment: Windows 7, JRE1.6
            Reporter: Guest User
            Priority: Minor

Following description applies to PDF view.

When using a table grid to place contents on a page, the border width of the cell borders differ in their
width. This happens when both, top and bottom border, are omitted. Here is an example, which nicely
demonstrates the effect. See the comment in the code to know, which borders will be painted wrong:

<?xml version="1.0"?>
<fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format">
  <fo:layout-master-set>
    <fo:simple-page-master master-name="content"
        page-width="210mm" page-height="297mm" margin="1cm">
      <fo:region-body/>
    </fo:simple-page-master>
  </fo:layout-master-set>
  <fo:page-sequence master-reference="content">
    <fo:flow flow-name="xsl-region-body">
(Continue reading)

Luis Bernardo (JIRA | 14 May 2013 00:51
Picon
Favicon

[jira] [Commented] (FOP-2221) [PATCH] Make overflow messages easier to read and fix wrong/ missing messages


    [
https://issues.apache.org/jira/browse/FOP-2221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13656487#comment-13656487
] 

Luis Bernardo commented on FOP-2221:
------------------------------------

patch overflowsmsg8svn.patch applied: http://svn.apache.org/viewvc?view=revision&revision=1482140.

> [PATCH] Make overflow messages easier to read and fix wrong/ missing messages
> -----------------------------------------------------------------------------
>
>                 Key: FOP-2221
>                 URL: https://issues.apache.org/jira/browse/FOP-2221
>             Project: Fop
>          Issue Type: Bug
>            Reporter: simon steiner
>             Fix For: trunk
>
>         Attachments: overflow-message-0.fo, overflow-message.fo, overflowsmessage2.patch,
overflowsmessage5.patch, overflowsmsg8svn.patch
>
>
> Users find it difficult to read over flow messages, patch shows element name and easier to read message.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
(Continue reading)

Luis Bernardo (JIRA | 14 May 2013 00:41
Picon
Favicon

[jira] [Updated] (FOP-2221) [PATCH] Make overflow messages easier to read and fix wrong/ missing messages


     [
https://issues.apache.org/jira/browse/FOP-2221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Luis Bernardo updated FOP-2221:
-------------------------------

    Attachment: overflow-message-0.fo

attached sample fo with many examples of overflow in static regions.

> [PATCH] Make overflow messages easier to read and fix wrong/ missing messages
> -----------------------------------------------------------------------------
>
>                 Key: FOP-2221
>                 URL: https://issues.apache.org/jira/browse/FOP-2221
>             Project: Fop
>          Issue Type: Bug
>            Reporter: simon steiner
>             Fix For: trunk
>
>         Attachments: overflow-message-0.fo, overflow-message.fo, overflowsmessage2.patch,
overflowsmessage5.patch, overflowsmsg8svn.patch
>
>
> Users find it difficult to read over flow messages, patch shows element name and easier to read message.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
(Continue reading)

simon steiner (JIRA | 13 May 2013 17:29
Picon
Favicon

[jira] [Commented] (FOP-2221) [PATCH] Make overflow messages easier to read and fix wrong/ missing messages


    [
https://issues.apache.org/jira/browse/FOP-2221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13656046#comment-13656046
] 

simon steiner commented on FOP-2221:
------------------------------------

Version 2 and 5 were committed to trunk, version 8 overflowsmsg8svn.patch is not.
I completed the CLA and emailed it.

> [PATCH] Make overflow messages easier to read and fix wrong/ missing messages
> -----------------------------------------------------------------------------
>
>                 Key: FOP-2221
>                 URL: https://issues.apache.org/jira/browse/FOP-2221
>             Project: Fop
>          Issue Type: Bug
>            Reporter: simon steiner
>             Fix For: trunk
>
>         Attachments: overflow-message.fo, overflowsmessage2.patch, overflowsmessage5.patch, overflowsmsg8svn.patch
>
>
> Users find it difficult to read over flow messages, patch shows element name and easier to read message.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
(Continue reading)

Chris Bowditch (JIRA | 13 May 2013 17:03
Picon
Favicon

[jira] [Commented] (FOP-2221) [PATCH] Make overflow messages easier to read and fix wrong/ missing messages


    [
https://issues.apache.org/jira/browse/FOP-2221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13656026#comment-13656026
] 

Chris Bowditch commented on FOP-2221:
-------------------------------------

Hi Simon,

Its not clear to me, which of the 3 patch files attached a committer is supposed to apply? Are they all
cummaltive? It so it would be better if you could combine them. If not, could you delete the ones that are no
longer relevant?

Furthermore, I notice that you don't yet have an ICLA file at [1] Since you've submitted a few patches now you
really ought to file one, see [2] on how to do that.

Thanks,

Chris

[1] http://people.apache.org/committer-index.html
[2] http://www.apache.org/licenses/#clas

> [PATCH] Make overflow messages easier to read and fix wrong/ missing messages
> -----------------------------------------------------------------------------
>
>                 Key: FOP-2221
>                 URL: https://issues.apache.org/jira/browse/FOP-2221
>             Project: Fop
(Continue reading)


Gmane