Forum Replies Created
-
AuthorPosts
-
in reply to: Deployment / Configuration issues August 29, 2017 at 22:15#27163
Hi,
We are facing a very strange behavior with PD4ML and JBOSS App server in our production environment. We are using custom fonts embedded within a jar file which is part of the app war deployable.
We have configured the below fonts in the pd4fonts.properties which is called by the java class using pd4ml.useTTF(“java:defaultfonts”, true);
Arial=arial.ttf
Arial Bold=arialbd.ttf
Arial Bold Italic=arialbi.ttf
Arial Italic=ariali.ttf
Courier New=cour.ttf
Courier New Bold=courbd.ttf
Courier New Bold Italic=courbi.ttf
Courier New Italic=couri.ttf
Times New Roman=times.ttf
Times New Roman Bold=timesbd.ttf
Times New Roman Bold Italic=timesbi.ttf
Times New Roman Italic=timesi.ttf
Calibri Bold=calibribd.ttf
Calibri=calibri.ttf
Calibri Italic=Calibrii.ttf
MingLiU=mingliu.ttc_0
Gill Sans=GillSansMT.ttf
Gill Sans Bold=GillSansMTBold.ttf
Gill Sans Bold Italic=GillSansMTBoldItalic.ttf
Gill Sans Italic=GillSansMTItalic.ttf
Gill Sans Light=GillSansMTLight.ttf
Gill Sans Semi Bold=GillSans-SemiBold.ttf
Gill Sans Condensed=GillSansMT-condensed.ttf
AdobeSongStd=AdobeSongStd.ttf
SharpSong=SharpSong.ttfThe issue is that we are seeing, in Production the fonts in the PDF generated are switching to AdobeSongStd.ttf instead of times.ttf. Once we restart the jboss by clearing the cache files (tmp and work folders in unix) the times.ttf is being used again which is the expected fonts. After a few random days, the fonts are going back to AdobeSongStd. Every time the jboss is restarted the fonts switch back to times.ttf.
I can see that Jboss is extracting these jar files having the fonts on to the tmp cache folder and I am assuming it then uses the fonts from there. However we are not able to understand why jboss/pd4ml is not using the times.ttf font and why it is using AdobeSongStd.ttf file instead. Also we do not know why the times.ttf is fetched properly when we do a jboss restart after clearing cache.
Can anyone please help me on this?
in reply to: General questions / FAQ August 30, 2017 at 08:39#27162Hi,
We are facing a very strange behavior with PD4ML and JBOSS App server in our production environment. We are using custom fonts embedded within a jar file which is part of the app war deployable.
We have configured the below fonts in the pd4fonts.properties which is called by the java class using pd4ml.useTTF(“java:defaultfonts”, true);
Arial=arial.ttf
Arial Bold=arialbd.ttf
Arial Bold Italic=arialbi.ttf
Arial Italic=ariali.ttf
Courier New=cour.ttf
Courier New Bold=courbd.ttf
Courier New Bold Italic=courbi.ttf
Courier New Italic=couri.ttf
Times New Roman=times.ttf
Times New Roman Bold=timesbd.ttf
Times New Roman Bold Italic=timesbi.ttf
Times New Roman Italic=timesi.ttf
Calibri Bold=calibribd.ttf
Calibri=calibri.ttf
Calibri Italic=Calibrii.ttf
MingLiU=mingliu.ttc_0
Gill Sans=GillSansMT.ttf
Gill Sans Bold=GillSansMTBold.ttf
Gill Sans Bold Italic=GillSansMTBoldItalic.ttf
Gill Sans Italic=GillSansMTItalic.ttf
Gill Sans Light=GillSansMTLight.ttf
Gill Sans Semi Bold=GillSans-SemiBold.ttf
Gill Sans Condensed=GillSansMT-condensed.ttf
AdobeSongStd=AdobeSongStd.ttf
SharpSong=SharpSong.ttfThe issue is that we are seeing, in Production the fonts in the PDF generated are switching to AdobeSongStd.ttf instead of times.ttf. Once we restart the jboss by clearing the cache files (tmp and work folders in unix) the times.ttf is being used again which is the expected fonts. After a few random days, the fonts are going back to AdobeSongStd. Every time the jboss is restarted the fonts switch back to times.ttf.
I can see that Jboss is extracting these jar files having the fonts on to the tmp cache folder and I am assuming it then uses the fonts from there. However we are not able to understand why jboss/pd4ml is not using the times.ttf font and why it is using AdobeSongStd.ttf file instead. Also we do not know why the times.ttf is fetched properly when we do a jboss restart after clearing cache.
Can anyone please help me on this?
in reply to: Troubleshooting August 30, 2017 at 08:40#27151Hi,
We are facing a very strange behavior with PD4ML and JBOSS App server in our production environment. We are using custom fonts embedded within a jar file which is part of the app war deployable.
We have configured the below fonts in the pd4fonts.properties which is called by the java class using pd4ml.useTTF(“java:defaultfonts”, true);
Arial=arial.ttf
Arial Bold=arialbd.ttf
Arial Bold Italic=arialbi.ttf
Arial Italic=ariali.ttf
Courier New=cour.ttf
Courier New Bold=courbd.ttf
Courier New Bold Italic=courbi.ttf
Courier New Italic=couri.ttf
Times New Roman=times.ttf
Times New Roman Bold=timesbd.ttf
Times New Roman Bold Italic=timesbi.ttf
Times New Roman Italic=timesi.ttf
Calibri Bold=calibribd.ttf
Calibri=calibri.ttf
Calibri Italic=Calibrii.ttf
MingLiU=mingliu.ttc_0
Gill Sans=GillSansMT.ttf
Gill Sans Bold=GillSansMTBold.ttf
Gill Sans Bold Italic=GillSansMTBoldItalic.ttf
Gill Sans Italic=GillSansMTItalic.ttf
Gill Sans Light=GillSansMTLight.ttf
Gill Sans Semi Bold=GillSans-SemiBold.ttf
Gill Sans Condensed=GillSansMT-condensed.ttf
AdobeSongStd=AdobeSongStd.ttf
SharpSong=SharpSong.ttfThe issue is that we are seeing, in Production the fonts in the PDF generated are switching to AdobeSongStd.ttf instead of times.ttf. Once we restart the jboss by clearing the cache files (tmp and work folders in unix) the times.ttf is being used again which is the expected fonts. After a few random days, the fonts are going back to AdobeSongStd. Every time the jboss is restarted the fonts switch back to times.ttf.
I can see that Jboss is extracting these jar files having the fonts on to the tmp cache folder and I am assuming it then uses the fonts from there. However we are not able to understand why jboss/pd4ml is not using the times.ttf font and why it is using AdobeSongStd.ttf file instead. Also we do not know why the times.ttf is fetched properly when we do a jboss restart after clearing cache.
Can anyone please help me on this?
in reply to: General questions / FAQ September 2, 2017 at 22:56#27152Hello,
we are trying to merge a pre-existing pdf with the pdf we generated using pd4ml(recently purchased a volume license – .net version)
We are receiving following exception while doing so… can you please help.. this is high priority for our release next week.. hence would be great if we could get the response as soon as possible.
Error message : “PDF Merge: Parsing of PDF failed: Parse error at
. Encountered: > 7676″ Stack trace : ” at org.zefer.pd4ml.PD4ML.e()rn at org.zefer.pd4ml.PD4ML.f()rn at org.zefer.pd4ml.PD4ML.render(Uri url, StreamWriter os)rn at org.zefer.pd4ml.PD4ML.render(String textUrl, Stream os)rn at SpecDeck.Helpers.Utilities.GeneratePDF(String presentationId, String orientation, Boolean customise, String presentationRoomId, String pageNumber) in D:\Projects\Sprint3-ManageRoomsProducts\SpecDeck\Helpers\Utilities.cs:line 660″
-Ganesh M.
in reply to: PDF merge failing with .net library September 4, 2017 at 01:35#30062Also in .Net library we couldn’t find a type called pd4document.. but looks like this is available in the java library, as shown here
http://www.pd4ml.com/cookbook/pd4ml_pdf_merge.htmPD4Document doc1 = new PD4Document(new URL(“file:c:/pdfs/doc1.pdf”), null);
int pagenum = doc1.getNumberOfPages();
…
PD4Document doc2 = new PD4Document(new URL(“file:c:/pdfs/doc2.pdf”), null);
pagenum = doc2.getNumberOfPages();
…
doc2.append(doc1);
pagenum = doc2.getNumberOfPages();
…
File f = new File(“c:/pdfs/result.pdf”);
FileOutputStream fos = new FileOutputStream(f);
doc2.write(fos);in reply to: Free CJK Fonts September 6, 2017 at 08:19#30047If the fonts are not listed in the .properties file, it seems they are still not in a compatible format. Did you try to convert them with a mentioned above Python script?
Q2 more debug info will be available in forthcoming PD4ML v4
Q3, Q4 it is possible. http://pd4ml.com/examples.zip contains chinese_ttf sample, which illustrates how to do that.See also http://pd4ml.com/cookbook/pd4ml_pdf_true_type_fonts.htm
in reply to: PD4ML cannot access Times New Roman Font September 6, 2017 at 11:13#30093Hi Team,
Can you please help us on this issue? I have been looking at the issue posted at the below link and our issue somewhat resembles the one posted here.
But we still cannot figure out why restarting the JBOSS server brings the fonts back to Times New Roman.
html-css-to-pdf-rendering-issues-f3/issue-with-font-family-on-chinese-characters-t921.html
in reply to: PD4ML cannot access Times New Roman Font September 6, 2017 at 11:13#30085Hi Team,
Can you please help us on this issue? I have been looking at the issue posted at the below link and our issue somewhat resembles the one posted here.
But we still cannot figure out why restarting the JBOSS server brings the fonts back to Times New Roman.
html-css-to-pdf-rendering-issues-f3/issue-with-font-family-on-chinese-characters-t921.html
in reply to: PD4ML cannot access Times New Roman Font September 6, 2017 at 11:27#30086What does it print (to STDOUT or server’s log) if you switch debug mode on with pd4ml.enableDebugInfo()?
in reply to: PD4ML cannot access Times New Roman Font September 6, 2017 at 12:13#30087Unfortunately since this is a PROD system, we do not have an option to do a enableDebugInfo() and cannot replicate the same in Dev or UAT
We have 3 servers with the same war file deployed and we see that this issue does not happen with all the 3 servers at the same time.
Can you please let us know if Jboss extracts the PD4ML font files from the war to any temp files?
Also why PD4ML is not fetching times font even though it is available and also why it is happening only sometimes and restarting jboss resolves it?
in reply to: PDF merge failing with .net library September 6, 2017 at 17:20in reply to: Free CJK Fonts September 6, 2017 at 17:26#30048following link does not work
http://pd4ml.com/examples.zipPage is throwing Error
No such file: /examples.zip
in reply to: Free CJK Fonts September 6, 2017 at 20:21#30049The correct link: http://pd4ml.com/examples.2017.05.zip
in reply to: PDF merge failing with .net library September 7, 2017 at 10:30#30064As PD4Document interface is not ported to .NET yet, for the time being the only solution is to use Java API for doc merging.
We’ll start porting of the doc merging functionality to .NET only after PD4ML v4 Java is released (in 2-4 weeks)
in reply to: PDF merge failing with .net library September 7, 2017 at 12:16#30065What would be the timeline for this porting? can I assume by end of this month?
-
AuthorPosts