[jira] [Commented] (FOP-2587) Acrobat Reader error with Google Noto Sans CJK fonts

2016-03-07 Thread Hua Lan (JIRA)

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

Hua Lan commented on FOP-2587:
--

Hi Chunlinyao, it worked. Great work.



> Acrobat Reader error with Google Noto Sans CJK fonts
> 
>
> Key: FOP-2587
> URL: https://issues.apache.org/jira/browse/FOP-2587
> Project: FOP
>  Issue Type: Bug
>  Components: font/opentype
>Affects Versions: 2.1
> Environment: Operating Systems: Windows
> Platform: PC
>Reporter: Hua Lan
>Assignee: simon steiner
> Attachments: testNoto.fo, testNoto_Black.pdf, testNoto_Bold.pdf, 
> testNoto_DemiLight.pdf, testNoto_Light.pdf, testNoto_Medium.pdf, 
> testNoto_Regular.pdf, testNoto_Thin.pdf
>
>   Original Estimate: 336h
>  Remaining Estimate: 336h
>
> This is a followup to https://issues.apache.org/jira/browse/FOP-2491
> Symptom: when opening the PDF file generated by FOP 2.1, depending on the 
> font weight, the Acrobat Reader has the following issues:
> 1. some characters are not well aligned with others in the same line 
> horizontally
> 2. it reports "cannot extract the embedded font 'EB+NotoSansCJKSC'. Some 
> characters may not display or print correctly". Some characters are missing 
> on the PDF.
> How to repeat:
> 1. Get FOP 2.1 library.
> 2. Get Google-Noto-Sans from 
> https://noto-website.storage.googleapis.com/pkgs/NotoSansCJKTC-hinted.zip.
> 3. Set the fop.xconf as following:
>  
>  . 
>   embed-url="Noto_Sans/NotoSansCJKsc-Black.otf" >
>   style="normal" weight="normal" />
>  
>   embed-url="Noto_Sans/NotoSansCJKsc-Bold.otf" >
>   style="normal" weight="normal" />
>  
>   embed-url="Noto_Sans/NotoSansCJKsc-DemiLight.otf" >
>   style="normal" weight="normal" />
>  
>   embed-url="Noto_Sans/NotoSansCJKsc-Light.otf" >
>   style="normal" weight="normal" />
>  
>   embed-url="Noto_Sans/NotoSansCJKsc-Medium.otf" >
>   style="normal" weight="normal" />
>  
>   embed-url="Noto_Sans/NotoSansCJKsc-Regular.otf" >
>  style="normal" weight="normal" />
>  
>   embed-url="Noto_Sans/NotoSansCJKsc-Thin.otf" >
>   style="normal" weight="normal" />
>  
>   embed-url="Noto_Sans/NotoSansCJKtc-Black.otf" >
>   style="normal" weight="normal" />
>  
>   embed-url="Noto_Sans/NotoSansCJKtc-Bold.otf" >
>   style="normal" weight="normal" />
>  
>   embed-url="Noto_Sans/NotoSansCJKtc-DemiLight.otf" >
>   style="normal" weight="normal" />
>  
>   embed-url="Noto_Sans/NotoSansCJKtc-Light.otf" >
>   style="normal" weight="normal" />
>  
>   embed-url="Noto_Sans/NotoSansCJKtc-Medium.otf" >
>   style="normal" weight="normal" />
>  
>   embed-url="Noto_Sans/NotoSansCJKtc-Regular.otf" >
>  style="normal" weight="normal" />
>  
>   embed-url="Noto_Sans/NotoSansCJKtc-Thin.otf" >
>   style="normal" weight="normal" />
>  
>   embed-url="Noto_Sans/NotoSansCJKjp-Black.otf" >
>   style="normal" weight="normal" />
>  
>   embed-url="Noto_Sans/NotoSansCJKjp-Bold.otf" >
>   style="normal" weight="normal" />
>  
>   embed-url="Noto_Sans/NotoSansCJKjp-DemiLight.otf" >
>   style="normal" weight="normal" />
>  
>   embed-url="Noto_Sans/NotoSansCJKjp-Light.otf" >
>   style="normal" weight="normal" />
>  
>   embed-url="Noto_Sans/NotoSansCJKjp-Medium.otf" >
>   style="normal" weight="normal" />
>  
>   embed-url="Noto_Sans/NotoSansCJKjp-Regular.otf" >
>  style="normal" weight="normal" />
>   
>   embed-url="Noto_Sans/NotoSansCJKjp-Thin.otf" >
>   style="normal" weight="normal" />
>  
>   embed-url="Noto_Sans/NotoSansCJKkr-Black.otf" >
>   style="normal" weight="normal" />
>  
>   embed-url="Noto_Sans/NotoSansCJKkr-Bold.otf" >
>

[jira] [Commented] (FOP-2524) FOP 2.0: target-resolution not set in FoUserAgent

2016-03-07 Thread simon steiner (JIRA)

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

simon steiner commented on FOP-2524:


This works for me:
{code}
String fopxconf = "\n"
+ "288"
+ "";

FopFactoryBuilder confBuilder = new FopConfParser(
new ByteArrayInputStream(fopxconf.getBytes()),
new URI(".")).getFopFactoryBuilder();
FopFactory fopFactory = confBuilder.build();
FOUserAgent foUserAgent = fopFactory.newFOUserAgent();
foUserAgent.getTargetResolution();
{code}

> FOP 2.0: target-resolution not set in FoUserAgent
> -
>
> Key: FOP-2524
> URL: https://issues.apache.org/jira/browse/FOP-2524
> Project: FOP
>  Issue Type: Bug
>  Components: renderer/png
>Affects Versions: 2.0
> Environment: Java 1.8.0_51, 64 Bit, Windows 7, Windows 2008 R2
>Reporter: MH
> Attachments: screenshot-FOP-PNG-Renderer.png
>
>
> We upgraded from FOP 1.0 to FOP 2.0 (as we had to skip FOP 1.1 due to a 
> blocker bug in 1.1). After converting all Java embedding code, we are now in 
> test phase. Almost everything looks good, but our PNG rendered documents 
> suddenly all look very blurry (see atachement). We had the same problem with 
> FOP 1.0 but "solved" it by setting the target resolution to 288:
> 288
> We still have this setting in the fop user config XML file, but it seems that 
> it has no effect anymore!



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (FOP-2523) Behavior change in include path handling breaks existing 1.1 docs

2016-03-07 Thread simon steiner (JIRA)

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

simon steiner commented on FOP-2523:


Related to FOP-2306 maybe

> Behavior change in include path handling breaks existing 1.1 docs
> -
>
> Key: FOP-2523
> URL: https://issues.apache.org/jira/browse/FOP-2523
> Project: FOP
>  Issue Type: Bug
>  Components: image/jpeg, image/png
>Affects Versions: 2.0
> Environment: OS X , Linux
>Reporter: Johan Persson
>Priority: Minor
>  Labels: path
>
> When transforming a document with included files (images) there is a 
> different behavior between 1.1 and 2.x.
> Transformation that works with fop 1.1 no longer works with 2.0
> I suspect that this is not so much a bug as a change that breaks existing 
> build schemas due to fop making different assumption on relative paths in 1.1 
> compared with 2.x. but I have to yet figure out what the assumption is.
> If the generated .fo includes say, 
> {{}}
> If all files (both images and .fo) are in a flat directory this works well 
> with 1.1. Running the same source through 2.0 will generate an error saying 
> that FOP cannot find the referred file (myimage.jpg)
> I suspect this is a common enough pattern to warrant some notice on how to 
> handle this situation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Closed] (FOP-2571) display is not correct

2016-03-07 Thread simon steiner (JIRA)

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

simon steiner closed FOP-2571.
--
Resolution: Cannot Reproduce

>  display is not correct
> -
>
> Key: FOP-2571
> URL: https://issues.apache.org/jira/browse/FOP-2571
> Project: FOP
>  Issue Type: Bug
>Affects Versions: 1.1
>Reporter: LiuChuanming
> Attachments: 1.fo, 1.pdf
>
>
> Using FOP1.1, generatedPDF by fo.
>  within the  tag, not break page, 
> some data is not displayed.
> Referenceļ¼š 1.fo and 1.pdf



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (FOP-2557) [PATCH] Adobe Reader report corrupt embedded font

2016-03-07 Thread simon steiner (JIRA)

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

simon steiner commented on FOP-2557:


Thanks for contribution

> [PATCH] Adobe Reader report corrupt embedded font 
> --
>
> Key: FOP-2557
> URL: https://issues.apache.org/jira/browse/FOP-2557
> Project: FOP
>  Issue Type: Bug
>  Components: fo/block
>Affects Versions: trunk
> Environment: Mac OSX 10.10, JDK 1.8
>Reporter: chunlinyao
>Assignee: simon steiner
>  Labels: patch
> Attachments: fop.xconf, patch.txt, patch20160104.txt, 
> patch_20160102.txt, patch_with_fixed_test_case-20160304.txt, test_fail.xml, 
> test_fail2.pdf, test_fail2.xml, test_good.pdf, test_good.xml, testbigset.pdf, 
> testbigset.xml, testbigset_full.pdf
>
>
> When use NotoSansCJKSc regular font, If I don't include any number the 
> embedded subset is corrupt.
> How to repeat
> 1. Get FOP from trunk@1720811
> 2. Get Font from 
> https://github.com/googlei18n/noto-cjk/blob/40d9f5b179a59a06b98373c76bdc3e2119e4e6b2/NotoSansCJKsc-Regular.otf
> 3. Use my config file and transform my fo files.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Closed] (FOP-2587) Acrobat Reader error with Google Noto Sans CJK fonts

2016-03-07 Thread simon steiner (JIRA)

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

simon steiner closed FOP-2587.
--
Resolution: Duplicate

> Acrobat Reader error with Google Noto Sans CJK fonts
> 
>
> Key: FOP-2587
> URL: https://issues.apache.org/jira/browse/FOP-2587
> Project: FOP
>  Issue Type: Bug
>  Components: font/opentype
>Affects Versions: 2.1
> Environment: Operating Systems: Windows
> Platform: PC
>Reporter: Hua Lan
>Assignee: simon steiner
> Attachments: testNoto.fo, testNoto_Black.pdf, testNoto_Bold.pdf, 
> testNoto_DemiLight.pdf, testNoto_Light.pdf, testNoto_Medium.pdf, 
> testNoto_Regular.pdf, testNoto_Thin.pdf
>
>   Original Estimate: 336h
>  Remaining Estimate: 336h
>
> This is a followup to https://issues.apache.org/jira/browse/FOP-2491
> Symptom: when opening the PDF file generated by FOP 2.1, depending on the 
> font weight, the Acrobat Reader has the following issues:
> 1. some characters are not well aligned with others in the same line 
> horizontally
> 2. it reports "cannot extract the embedded font 'EB+NotoSansCJKSC'. Some 
> characters may not display or print correctly". Some characters are missing 
> on the PDF.
> How to repeat:
> 1. Get FOP 2.1 library.
> 2. Get Google-Noto-Sans from 
> https://noto-website.storage.googleapis.com/pkgs/NotoSansCJKTC-hinted.zip.
> 3. Set the fop.xconf as following:
>  
>  . 
>   embed-url="Noto_Sans/NotoSansCJKsc-Black.otf" >
>   style="normal" weight="normal" />
>  
>   embed-url="Noto_Sans/NotoSansCJKsc-Bold.otf" >
>   style="normal" weight="normal" />
>  
>   embed-url="Noto_Sans/NotoSansCJKsc-DemiLight.otf" >
>   style="normal" weight="normal" />
>  
>   embed-url="Noto_Sans/NotoSansCJKsc-Light.otf" >
>   style="normal" weight="normal" />
>  
>   embed-url="Noto_Sans/NotoSansCJKsc-Medium.otf" >
>   style="normal" weight="normal" />
>  
>   embed-url="Noto_Sans/NotoSansCJKsc-Regular.otf" >
>  style="normal" weight="normal" />
>  
>   embed-url="Noto_Sans/NotoSansCJKsc-Thin.otf" >
>   style="normal" weight="normal" />
>  
>   embed-url="Noto_Sans/NotoSansCJKtc-Black.otf" >
>   style="normal" weight="normal" />
>  
>   embed-url="Noto_Sans/NotoSansCJKtc-Bold.otf" >
>   style="normal" weight="normal" />
>  
>   embed-url="Noto_Sans/NotoSansCJKtc-DemiLight.otf" >
>   style="normal" weight="normal" />
>  
>   embed-url="Noto_Sans/NotoSansCJKtc-Light.otf" >
>   style="normal" weight="normal" />
>  
>   embed-url="Noto_Sans/NotoSansCJKtc-Medium.otf" >
>   style="normal" weight="normal" />
>  
>   embed-url="Noto_Sans/NotoSansCJKtc-Regular.otf" >
>  style="normal" weight="normal" />
>  
>   embed-url="Noto_Sans/NotoSansCJKtc-Thin.otf" >
>   style="normal" weight="normal" />
>  
>   embed-url="Noto_Sans/NotoSansCJKjp-Black.otf" >
>   style="normal" weight="normal" />
>  
>   embed-url="Noto_Sans/NotoSansCJKjp-Bold.otf" >
>   style="normal" weight="normal" />
>  
>   embed-url="Noto_Sans/NotoSansCJKjp-DemiLight.otf" >
>   style="normal" weight="normal" />
>  
>   embed-url="Noto_Sans/NotoSansCJKjp-Light.otf" >
>   style="normal" weight="normal" />
>  
>   embed-url="Noto_Sans/NotoSansCJKjp-Medium.otf" >
>   style="normal" weight="normal" />
>  
>   embed-url="Noto_Sans/NotoSansCJKjp-Regular.otf" >
>  style="normal" weight="normal" />
>   
>   embed-url="Noto_Sans/NotoSansCJKjp-Thin.otf" >
>   style="normal" weight="normal" />
>  
>   embed-url="Noto_Sans/NotoSansCJKkr-Black.otf" >
>   style="normal" weight="normal" />
>  
>   embed-url="Noto_Sans/NotoSansCJKkr-Bold.otf" >
>   style="normal" weight="normal" />

[jira] [Assigned] (FOP-2587) Acrobat Reader error with Google Noto Sans CJK fonts

2016-03-07 Thread simon steiner (JIRA)

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

simon steiner reassigned FOP-2587:
--

Assignee: simon steiner

> Acrobat Reader error with Google Noto Sans CJK fonts
> 
>
> Key: FOP-2587
> URL: https://issues.apache.org/jira/browse/FOP-2587
> Project: FOP
>  Issue Type: Bug
>  Components: font/opentype
>Affects Versions: 2.1
> Environment: Operating Systems: Windows
> Platform: PC
>Reporter: Hua Lan
>Assignee: simon steiner
> Attachments: testNoto.fo, testNoto_Black.pdf, testNoto_Bold.pdf, 
> testNoto_DemiLight.pdf, testNoto_Light.pdf, testNoto_Medium.pdf, 
> testNoto_Regular.pdf, testNoto_Thin.pdf
>
>   Original Estimate: 336h
>  Remaining Estimate: 336h
>
> This is a followup to https://issues.apache.org/jira/browse/FOP-2491
> Symptom: when opening the PDF file generated by FOP 2.1, depending on the 
> font weight, the Acrobat Reader has the following issues:
> 1. some characters are not well aligned with others in the same line 
> horizontally
> 2. it reports "cannot extract the embedded font 'EB+NotoSansCJKSC'. Some 
> characters may not display or print correctly". Some characters are missing 
> on the PDF.
> How to repeat:
> 1. Get FOP 2.1 library.
> 2. Get Google-Noto-Sans from 
> https://noto-website.storage.googleapis.com/pkgs/NotoSansCJKTC-hinted.zip.
> 3. Set the fop.xconf as following:
>  
>  . 
>   embed-url="Noto_Sans/NotoSansCJKsc-Black.otf" >
>   style="normal" weight="normal" />
>  
>   embed-url="Noto_Sans/NotoSansCJKsc-Bold.otf" >
>   style="normal" weight="normal" />
>  
>   embed-url="Noto_Sans/NotoSansCJKsc-DemiLight.otf" >
>   style="normal" weight="normal" />
>  
>   embed-url="Noto_Sans/NotoSansCJKsc-Light.otf" >
>   style="normal" weight="normal" />
>  
>   embed-url="Noto_Sans/NotoSansCJKsc-Medium.otf" >
>   style="normal" weight="normal" />
>  
>   embed-url="Noto_Sans/NotoSansCJKsc-Regular.otf" >
>  style="normal" weight="normal" />
>  
>   embed-url="Noto_Sans/NotoSansCJKsc-Thin.otf" >
>   style="normal" weight="normal" />
>  
>   embed-url="Noto_Sans/NotoSansCJKtc-Black.otf" >
>   style="normal" weight="normal" />
>  
>   embed-url="Noto_Sans/NotoSansCJKtc-Bold.otf" >
>   style="normal" weight="normal" />
>  
>   embed-url="Noto_Sans/NotoSansCJKtc-DemiLight.otf" >
>   style="normal" weight="normal" />
>  
>   embed-url="Noto_Sans/NotoSansCJKtc-Light.otf" >
>   style="normal" weight="normal" />
>  
>   embed-url="Noto_Sans/NotoSansCJKtc-Medium.otf" >
>   style="normal" weight="normal" />
>  
>   embed-url="Noto_Sans/NotoSansCJKtc-Regular.otf" >
>  style="normal" weight="normal" />
>  
>   embed-url="Noto_Sans/NotoSansCJKtc-Thin.otf" >
>   style="normal" weight="normal" />
>  
>   embed-url="Noto_Sans/NotoSansCJKjp-Black.otf" >
>   style="normal" weight="normal" />
>  
>   embed-url="Noto_Sans/NotoSansCJKjp-Bold.otf" >
>   style="normal" weight="normal" />
>  
>   embed-url="Noto_Sans/NotoSansCJKjp-DemiLight.otf" >
>   style="normal" weight="normal" />
>  
>   embed-url="Noto_Sans/NotoSansCJKjp-Light.otf" >
>   style="normal" weight="normal" />
>  
>   embed-url="Noto_Sans/NotoSansCJKjp-Medium.otf" >
>   style="normal" weight="normal" />
>  
>   embed-url="Noto_Sans/NotoSansCJKjp-Regular.otf" >
>  style="normal" weight="normal" />
>   
>   embed-url="Noto_Sans/NotoSansCJKjp-Thin.otf" >
>   style="normal" weight="normal" />
>  
>   embed-url="Noto_Sans/NotoSansCJKkr-Black.otf" >
>   style="normal" weight="normal" />
>  
>   embed-url="Noto_Sans/NotoSansCJKkr-Bold.otf" >
>   style="normal" 

[jira] [Commented] (FOP-2557) [PATCH] Adobe Reader report corrupt embedded font

2016-03-07 Thread simon steiner (JIRA)

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

simon steiner commented on FOP-2557:


Added http://svn.apache.org/viewvc?view=revision=1733922

> [PATCH] Adobe Reader report corrupt embedded font 
> --
>
> Key: FOP-2557
> URL: https://issues.apache.org/jira/browse/FOP-2557
> Project: FOP
>  Issue Type: Bug
>  Components: fo/block
>Affects Versions: trunk
> Environment: Mac OSX 10.10, JDK 1.8
>Reporter: chunlinyao
>Assignee: simon steiner
>  Labels: patch
> Attachments: fop.xconf, patch.txt, patch20160104.txt, 
> patch_20160102.txt, patch_with_fixed_test_case-20160304.txt, test_fail.xml, 
> test_fail2.pdf, test_fail2.xml, test_good.pdf, test_good.xml, testbigset.pdf, 
> testbigset.xml, testbigset_full.pdf
>
>
> When use NotoSansCJKSc regular font, If I don't include any number the 
> embedded subset is corrupt.
> How to repeat
> 1. Get FOP from trunk@1720811
> 2. Get Font from 
> https://github.com/googlei18n/noto-cjk/blob/40d9f5b179a59a06b98373c76bdc3e2119e4e6b2/NotoSansCJKsc-Regular.otf
> 3. Use my config file and transform my fo files.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Closed] (FOP-2557) [PATCH] Adobe Reader report corrupt embedded font

2016-03-07 Thread simon steiner (JIRA)

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

simon steiner closed FOP-2557.
--
Resolution: Fixed

> [PATCH] Adobe Reader report corrupt embedded font 
> --
>
> Key: FOP-2557
> URL: https://issues.apache.org/jira/browse/FOP-2557
> Project: FOP
>  Issue Type: Bug
>  Components: fo/block
>Affects Versions: trunk
> Environment: Mac OSX 10.10, JDK 1.8
>Reporter: chunlinyao
>Assignee: simon steiner
>  Labels: patch
> Attachments: fop.xconf, patch.txt, patch20160104.txt, 
> patch_20160102.txt, patch_with_fixed_test_case-20160304.txt, test_fail.xml, 
> test_fail2.pdf, test_fail2.xml, test_good.pdf, test_good.xml, testbigset.pdf, 
> testbigset.xml, testbigset_full.pdf
>
>
> When use NotoSansCJKSc regular font, If I don't include any number the 
> embedded subset is corrupt.
> How to repeat
> 1. Get FOP from trunk@1720811
> 2. Get Font from 
> https://github.com/googlei18n/noto-cjk/blob/40d9f5b179a59a06b98373c76bdc3e2119e4e6b2/NotoSansCJKsc-Regular.otf
> 3. Use my config file and transform my fo files.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Closed] (FOP-2460) Subsetting OTF font leads to PDF errors when viewing / incorrect characters

2016-03-07 Thread simon steiner (JIRA)

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

simon steiner closed FOP-2460.
--
Resolution: Duplicate

> Subsetting OTF font leads to PDF errors when viewing / incorrect characters
> ---
>
> Key: FOP-2460
> URL: https://issues.apache.org/jira/browse/FOP-2460
> Project: FOP
>  Issue Type: Bug
>  Components: font/opentype
>Affects Versions: trunk
>Reporter: Robert Meyer
>Assignee: simon steiner
>
> When attempting to generate a document whilst subsetting the 
> VilleroyBoch-Regular.otf font, different viewers will either show errors, no 
> text or lead to incorrect or corrupt characters being drawn.
> I currentlty believe this is down to either a subroutine not being copied 
> from the original font leading to a invalid reference, or the subroutine does 
> not contain valid data. When looking at this font in FontForge, 3 characters 
> in a "hello world" example I used were missing which backs up this hypothesis.
> [EDIT] I've removed the font as I did not check if there were copyright 
> issues by making it public domain. I will work when I am able to do so but 
> keep the font privately unless I hear otherwise from the user who originally 
> posted the problem



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Assigned] (FOP-2460) Subsetting OTF font leads to PDF errors when viewing / incorrect characters

2016-03-07 Thread simon steiner (JIRA)

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

simon steiner reassigned FOP-2460:
--

Assignee: simon steiner

> Subsetting OTF font leads to PDF errors when viewing / incorrect characters
> ---
>
> Key: FOP-2460
> URL: https://issues.apache.org/jira/browse/FOP-2460
> Project: FOP
>  Issue Type: Bug
>  Components: font/opentype
>Affects Versions: trunk
>Reporter: Robert Meyer
>Assignee: simon steiner
>
> When attempting to generate a document whilst subsetting the 
> VilleroyBoch-Regular.otf font, different viewers will either show errors, no 
> text or lead to incorrect or corrupt characters being drawn.
> I currentlty believe this is down to either a subroutine not being copied 
> from the original font leading to a invalid reference, or the subroutine does 
> not contain valid data. When looking at this font in FontForge, 3 characters 
> in a "hello world" example I used were missing which backs up this hypothesis.
> [EDIT] I've removed the font as I did not check if there were copyright 
> issues by making it public domain. I will work when I am able to do so but 
> keep the font privately unless I hear otherwise from the user who originally 
> posted the problem



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Assigned] (FOP-2557) [PATCH] Adobe Reader report corrupt embedded font

2016-03-07 Thread simon steiner (JIRA)

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

simon steiner reassigned FOP-2557:
--

Assignee: simon steiner

> [PATCH] Adobe Reader report corrupt embedded font 
> --
>
> Key: FOP-2557
> URL: https://issues.apache.org/jira/browse/FOP-2557
> Project: FOP
>  Issue Type: Bug
>  Components: fo/block
>Affects Versions: trunk
> Environment: Mac OSX 10.10, JDK 1.8
>Reporter: chunlinyao
>Assignee: simon steiner
>  Labels: patch
> Attachments: fop.xconf, patch.txt, patch20160104.txt, 
> patch_20160102.txt, patch_with_fixed_test_case-20160304.txt, test_fail.xml, 
> test_fail2.pdf, test_fail2.xml, test_good.pdf, test_good.xml, testbigset.pdf, 
> testbigset.xml, testbigset_full.pdf
>
>
> When use NotoSansCJKSc regular font, If I don't include any number the 
> embedded subset is corrupt.
> How to repeat
> 1. Get FOP from trunk@1720811
> 2. Get Font from 
> https://github.com/googlei18n/noto-cjk/blob/40d9f5b179a59a06b98373c76bdc3e2119e4e6b2/NotoSansCJKsc-Regular.otf
> 3. Use my config file and transform my fo files.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (FOP-2588) Conserve Memory strips NOP from AFP output

2016-03-07 Thread Jerome O'Flaherty (JIRA)

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

Jerome O'Flaherty updated FOP-2588:
---
Attachment: ConserveMemoryTestCase.java
CachedRenderPagesModel.java

These files are the Unit test to replicated the issue and an updated version of 
the CacheRenderPagesModel which fixes the issue.

> Conserve Memory strips NOP from AFP output
> --
>
> Key: FOP-2588
> URL: https://issues.apache.org/jira/browse/FOP-2588
> Project: FOP
>  Issue Type: Bug
>  Components: layout/page
>Affects Versions: 2.0, trunk, 2.1
>Reporter: Jerome O'Flaherty
> Attachments: CachedRenderPagesModel.java, ConserveMemoryTestCase.java
>
>
> When the conserve memory flag is enabled, the CachedRenderPagesModel is 
> enabled, but unfortunately it is missing some code compared to the 
> RenderPagesModel and misses (i.e. doesn't write out) the NOP values when AFP 
> is the output format.
> I have attached a simple Unit Tests and an updated version of the 
> CachedRenderPagesModel which fixes the issue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Created] (FOP-2588) Conserve Memory strips NOP from AFP output

2016-03-07 Thread Jerome O'Flaherty (JIRA)
Jerome O'Flaherty created FOP-2588:
--

 Summary: Conserve Memory strips NOP from AFP output
 Key: FOP-2588
 URL: https://issues.apache.org/jira/browse/FOP-2588
 Project: FOP
  Issue Type: Bug
  Components: layout/page
Affects Versions: 2.0, trunk, 2.1
Reporter: Jerome O'Flaherty


When the conserve memory flag is enabled, the CachedRenderPagesModel is 
enabled, but unfortunately it is missing some code compared to the 
RenderPagesModel and misses (i.e. doesn't write out) the NOP values when AFP is 
the output format.

I have attached a simple Unit Tests and an updated version of the 
CachedRenderPagesModel which fixes the issue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Comment Edited] (FOP-2557) [PATCH] Adobe Reader report corrupt embedded font

2016-03-07 Thread simon steiner (JIRA)

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

simon steiner edited comment on FOP-2557 at 3/7/16 9:19 AM:


Fop works ok with 
https://sourceforge.net/p/itext/sandbox/ci/8cc448b68ccb0d567d1b6f716c904a6e8581f38f/tree/resources/fonts/NotoSansCJKsc-Regular.otf


was (Author: ssteiner1):
Try using 
https://sourceforge.net/p/itext/sandbox/ci/8cc448b68ccb0d567d1b6f716c904a6e8581f38f/tree/resources/fonts/NotoSansCJKsc-Regular.otf

> [PATCH] Adobe Reader report corrupt embedded font 
> --
>
> Key: FOP-2557
> URL: https://issues.apache.org/jira/browse/FOP-2557
> Project: FOP
>  Issue Type: Bug
>  Components: fo/block
>Affects Versions: trunk
> Environment: Mac OSX 10.10, JDK 1.8
>Reporter: chunlinyao
>  Labels: patch
> Attachments: fop.xconf, patch.txt, patch20160104.txt, 
> patch_20160102.txt, patch_with_fixed_test_case-20160304.txt, test_fail.xml, 
> test_fail2.pdf, test_fail2.xml, test_good.pdf, test_good.xml, testbigset.pdf, 
> testbigset.xml, testbigset_full.pdf
>
>
> When use NotoSansCJKSc regular font, If I don't include any number the 
> embedded subset is corrupt.
> How to repeat
> 1. Get FOP from trunk@1720811
> 2. Get Font from 
> https://github.com/googlei18n/noto-cjk/blob/40d9f5b179a59a06b98373c76bdc3e2119e4e6b2/NotoSansCJKsc-Regular.otf
> 3. Use my config file and transform my fo files.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (FOP-2557) [PATCH] Adobe Reader report corrupt embedded font

2016-03-07 Thread simon steiner (JIRA)

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

simon steiner commented on FOP-2557:


Try using 
https://sourceforge.net/p/itext/sandbox/ci/8cc448b68ccb0d567d1b6f716c904a6e8581f38f/tree/resources/fonts/NotoSansCJKsc-Regular.otf

> [PATCH] Adobe Reader report corrupt embedded font 
> --
>
> Key: FOP-2557
> URL: https://issues.apache.org/jira/browse/FOP-2557
> Project: FOP
>  Issue Type: Bug
>  Components: fo/block
>Affects Versions: trunk
> Environment: Mac OSX 10.10, JDK 1.8
>Reporter: chunlinyao
>  Labels: patch
> Attachments: fop.xconf, patch.txt, patch20160104.txt, 
> patch_20160102.txt, patch_with_fixed_test_case-20160304.txt, test_fail.xml, 
> test_fail2.pdf, test_fail2.xml, test_good.pdf, test_good.xml, testbigset.pdf, 
> testbigset.xml, testbigset_full.pdf
>
>
> When use NotoSansCJKSc regular font, If I don't include any number the 
> embedded subset is corrupt.
> How to repeat
> 1. Get FOP from trunk@1720811
> 2. Get Font from 
> https://github.com/googlei18n/noto-cjk/blob/40d9f5b179a59a06b98373c76bdc3e2119e4e6b2/NotoSansCJKsc-Regular.otf
> 3. Use my config file and transform my fo files.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)