Pascal Sancho (JIRA | 15 Apr 12:02 2014
Picon

[jira] [Commented] (FOP-2365) pdf's name contains chinese character


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

Pascal Sancho commented on FOP-2365:
------------------------------------

After changing codepage, you should restart Windows and check in a shell environment that your change is effective.

Guessing you are invoking fop.bat through a java process:
JVM config can differ between your 2 machines, including java version.
Perhaps the ProcessBuilder() contructor set some default values

Or maybe a Windows bugfix...

Or... googleing:
http://www.coderanch.com/t/279253/java-io/java/Unicode-cmd-parameters-main-args

This seems to be definitively related to your machine configuration, in such case FOP has nothing to do with
this issue.

> pdf's name contains chinese character
> -------------------------------------
>
>                 Key: FOP-2365
>                 URL: https://issues.apache.org/jira/browse/FOP-2365
>             Project: Fop
>          Issue Type: Bug
>          Components: pdf
(Continue reading)

zhangcui (JIRA | 15 Apr 11:29 2014
Picon

[jira] [Commented] (FOP-2365) pdf's name contains chinese character


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

zhangcui commented on FOP-2365:
-------------------------------

Hi,Pascal Sancho
Thanks for your response.
Windows 7 Ultimate 64bit and  windows 2008 JP have the same FS,NTFS.
And i generate a UTF8 file by "new File()" on Windows 7 Ultimate 64bit,so i can say it support UTF8,right?

Another cause could be the codepage used by the Windows shell.
->means change regedit.exe's HKEY_LOCAL_MACHINE\Software\Microsoft\Command Processor\Autorun to
 <at> chcp 65001?
i changed it,not work

Is there any other possible reasons?

> pdf's name contains chinese character
> -------------------------------------
>
>                 Key: FOP-2365
>                 URL: https://issues.apache.org/jira/browse/FOP-2365
>             Project: Fop
>          Issue Type: Bug
>          Components: pdf
>    Affects Versions: 1.0
>         Environment: Windows 7 Ultimate 64bit
(Continue reading)

Pascal Sancho (JIRA | 15 Apr 09:41 2014
Picon

[jira] [Commented] (FOP-2365) pdf's name contains chinese character


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

Pascal Sancho commented on FOP-2365:
------------------------------------

Hi,
I'm pretty sure that the cause is how File system handle filenames.
Not all FS used by Windows support UTF8 filenames (Cf. [1]).
Another cause could be the codepage used by the Windows shell.

Another thing: I guess you are calling fop.bat from Java app; it's not a common way to run FOP from Java... it
would be benefit to directly embed FOP calls in your app (see [2]), so you will not be facing to Shell limitations.

I expect some feedback before I close this issue as Invalid.

[1] http://msdn.microsoft.com/en-us/library/windows/desktop/dd317748%28v=vs.85%29.aspx
[2] http://xmlgraphics.apache.org/fop/1.0/embedding.html

> pdf's name contains chinese character
> -------------------------------------
>
>                 Key: FOP-2365
>                 URL: https://issues.apache.org/jira/browse/FOP-2365
>             Project: Fop
>          Issue Type: Bug
>          Components: pdf
>    Affects Versions: 1.0
(Continue reading)

zhangcui (JIRA | 15 Apr 03:37 2014
Picon

[jira] [Updated] (FOP-2365) pdf's name contains chinese character


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

zhangcui updated FOP-2365:
--------------------------

    Description: 
use fop1.0,i create a pdf,if the pdf's name contains chinese character,it will fail.
but use the same code,if the server OS is windows 2008 JP,it works fine.
my server OS is windows 7 ultimate JP.

List<String> cmdList = new ArrayList<String>();
cmdList.add("fop.bat");
cmdList.add("c:\\logfile.log");
cmdList.add("-xsl");
cmdList.add("c:\\myxsl.xsl");
cmdList.add("-param");
cmdList.add("pp");
cmdList.add("c:\\param.txt");
cmdList.add("-xml");
cmdList.add("c:\\myxml.xml");
cmdList.add("-pdf");
cmdList.add("c:\\mypdf.pdf");
ProcessBuilder pb = new ProcessBuilder(command);
p = pb.start();

sorry for my english.......

  was:
(Continue reading)

zhangcui (JIRA | 14 Apr 12:08 2014
Picon

[jira] [Created] (FOP-2365) pdf's name contains chinese character

zhangcui created FOP-2365:
-----------------------------

             Summary: pdf's name contains chinese character
                 Key: FOP-2365
                 URL: https://issues.apache.org/jira/browse/FOP-2365
             Project: Fop
          Issue Type: Bug
          Components: pdf
    Affects Versions: 1.0
         Environment: Windows 7 Ultimate 64bit
            Reporter: zhangcui

use fop1.0,i create a pdf,if the pdf's name contains chinese character,it will fail.
i use this code
List<String> cmdList = new ArrayList<String>();
cmdList.add("fop.bat");
cmdList.add("c:\\logfile.log");
cmdList.add("-xsl");
cmdList.add("c:\\myxsl.xsl");
cmdList.add("-param");
cmdList.add("pp");
cmdList.add("c:\\param.txt");
cmdList.add("-xml");
cmdList.add("c:\\myxml.xml");
cmdList.add("-pdf");
cmdList.add("c:\\mypdf.pdf");
ProcessBuilder pb = new ProcessBuilder(command);
p = pb.start();

(Continue reading)

inferyes | 13 Apr 18:51 2014
Picon

FOP can not create a special table?

Hi all,

I am using FOP 1.1 to create a special table as follow:
<http://apache-fop.1065347.n5.nabble.com/file/n40479/table.png> 

As you seen, the table header is at right, and the table content(Asian
characters) is displayed vertically. 
I have tried to use /writing-mode="rl-tb"/ in <fo:table>, but it is not work
as follow. 
<http://apache-fop.1065347.n5.nabble.com/file/n40479/table-1.png> 

My questions:
1. Does FOP support to use "rl-tb" writing-mode in fo:table to create table
like this? 
2. How to display the Asian characters in the vertical line?(Not just
rotate)

My code:

<?xml version="1.0" encoding="UTF-8" ?>
<fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format">
  <fo:layout-master-set>
	<fo:simple-page-master master-name="content" page-height="29.7cm"
page-width="21cm" margin-top="0.5cm" margin-bottom="0.5cm"
margin-left="1.5cm" margin-right="1.5cm">
	  <fo:region-body margin-top="1.5cm" margin-bottom="2cm" column-count="2"
column-gap="0.25in"/>
	  <fo:region-before extent="2.5cm"/>
	  <fo:region-after extent="1.5cm"/>
	</fo:simple-page-master>
(Continue reading)

Picon

[jira] [Created] (FOP-2364) Keep-with-next integer value: Illegal value for breakClass: 75

Matthias Reischenbacher created FOP-2364:
--------------------------------------------

             Summary: Keep-with-next integer value: Illegal value for breakClass: 75
                 Key: FOP-2364
                 URL: https://issues.apache.org/jira/browse/FOP-2364
             Project: Fop
          Issue Type: Bug
          Components: page-master/layout
    Affects Versions: trunk
            Reporter: Matthias Reischenbacher
         Attachments: illegal_break_class_75.xml

The attached sample FO file causes an IllegalArgumentException: Illegal value for breakClass: 75.

It seems to be related to the integer value within the keep-with-next property.

--
This message was sent by Atlassian JIRA
(v6.2#6252)

Picon

[jira] [Updated] (FOP-2364) Keep-with-next integer value: Illegal value for breakClass: 75


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

Matthias Reischenbacher updated FOP-2364:
-----------------------------------------

    Attachment: illegal_break_class_75.xml

Test case

> Keep-with-next integer value: Illegal value for breakClass: 75
> --------------------------------------------------------------
>
>                 Key: FOP-2364
>                 URL: https://issues.apache.org/jira/browse/FOP-2364
>             Project: Fop
>          Issue Type: Bug
>          Components: page-master/layout
>    Affects Versions: trunk
>            Reporter: Matthias Reischenbacher
>         Attachments: illegal_break_class_75.xml
>
>
> The attached sample FO file causes an IllegalArgumentException: Illegal value for breakClass: 75.
> It seems to be related to the integer value within the keep-with-next property.

--
This message was sent by Atlassian JIRA
(v6.2#6252)
(Continue reading)

Seifeddine Dridi (JIRA | 11 Apr 11:17 2014
Picon

[jira] [Updated] (FOP-2293) Whitespace management extension


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

Seifeddine Dridi updated FOP-2293:
----------------------------------

    Attachment: FO_multi-switch_best-fit_ext_rev13.patch

Hello,

I have added a couple of layoutengine tests and made minor changes to the code. It's kind of reassuring to
know that everything is still working as expected.

{quote}
If having this extension work with changing IPD is not a priority for you, I suggest you leave the code as is.
{quote}

I prefer to leave that for another time...

> Whitespace management extension
> -------------------------------
>
>                 Key: FOP-2293
>                 URL: https://issues.apache.org/jira/browse/FOP-2293
>             Project: Fop
>          Issue Type: New Feature
>          Components: general
>    Affects Versions: trunk
>            Reporter: Seifeddine Dridi
(Continue reading)

Vincent Hennebert (JIRA | 9 Apr 21:40 2014
Picon

[jira] [Commented] (FOP-2293) Whitespace management extension


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

Vincent Hennebert commented on FOP-2293:
----------------------------------------

Hmmm. I suspect it works because then the algorithm breaks at the 'normal' penalty that follows the
WhitespaceManagementPenalty, and it knows how to restart at such a penalty. Given the way the
implementation has evolved (storing on the active node the selected variant), I guess it will always be
possible to break at this penalty that follows the WMPenalty. In fact, you could probably turn the
WMPenalty into an infinite penalty and always break at the penalty that would follow it. It might make
easier to implement keeps and breaks (which BTW don't work properly on the example you uploaded since it
shouldn't break at the WMPenalty). And if not, at least you have a cheap way to support changing IPD.

Note that in order to have changing IPD properly working, you also need to make the MultiSwitchLM
restartable and implement the 5-parameter getNextKnuthElements method.

If having this extension work with changing IPD is not a priority for you, I suggest you leave the code as is.

HTH,
Vincent

> Whitespace management extension
> -------------------------------
>
>                 Key: FOP-2293
>                 URL: https://issues.apache.org/jira/browse/FOP-2293
>             Project: Fop
(Continue reading)

Seifeddine Dridi (JIRA | 9 Apr 16:40 2014
Picon

[jira] [Commented] (FOP-2293) Whitespace management extension


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

Seifeddine Dridi commented on FOP-2293:
---------------------------------------

{quote}
What do you mean by this? When it restarts at a too short/long node because no feasible break has been found,
or when it restarts the whole page layout because changing IPD has been detected?
{quote}

Page-restart due to changing IPD (see bug_page_ipd_change.fo). This is probably related to space
resolution, since FOP expects the restarting position to be instance of SpaceHandlingBreakPosition.
I've been able to suppress this issue by adding a BreakElement at the end of the Knuth list, but I'm not quite
sure if it's right way to deal with this.

> Whitespace management extension
> -------------------------------
>
>                 Key: FOP-2293
>                 URL: https://issues.apache.org/jira/browse/FOP-2293
>             Project: Fop
>          Issue Type: New Feature
>          Components: general
>    Affects Versions: trunk
>            Reporter: Seifeddine Dridi
>            Priority: Minor
>              Labels: XSL-FO
(Continue reading)


Gmane