down12
wrote on 2013-07-18:
I tried to use PHP class to cover my html to pdf, but there was an error below:
Pdfcrowd Error: [510] Timed out. Can't load the specified URL.
List of the resources that can't be loaded:
http://***/test/book/fonts/fzltqh.TTF
http://***/book/fonts/hiraginosansgbw3.otf
http://***/test/book/fonts/fzltzh.TTF
http://***/test/book/fonts/FZKT.TTF
the three .ttf files and one .otf file is existed, so I guessed that pdfcrowd cat support cunstom font. Is it?
and then the font file is in a large size , because it's not english language.
support
wrote on 2013-07-18:
Hello,
Yes, Pdfcrowd supports custom fonts.
The error message you are getting indicates that Pdfcrowd failed to download the fonts from the server.
If you can post here a full URLs of the fonts (or send them to info@pdfcrowd.com), we will take a look at what exactly the problem is.
down12
wrote on 2013-07-23:
I have sent a mail to info@pdfcrowd.com, thank you
support
wrote on 2013-07-24:
Hello,
The problem is the size and the download speed of the font files. For example, hiraginosansgbw3.otf (12.5MB) takes more than 80 seconds to download (at 153kB/s). Pdfcrowd aborts a conversion if takes more than 40 seconds. That is why you are getting the timeout error.
The solution is to serve the font files from a faster server or does not use the custom fonts.
down12
wrote on 2013-07-26:
Thank you for your reply, I wanna know another question. If pdfcrowd got a cunstom font file, will pdfcrowd save this font file?
support
wrote on 2013-07-29:
Hello,
No, Pdfcrowd does not cache any files between conversions.
stvogdn
wrote on 2013-08-09:
I am having a similar problem using web fonts with a large font file. Trying to convert this page:http://jp.flukenetworks.com/print/content/managing-byod-and-consumerization-it I get an error message, "Sorry, we can't process your request". This happens if I try to convert the html using the api or if I just enter it on your web page. The font file is hosted on our CDN and loads very quickly from where I am sitting. Is this a timeout or some other problem?
support
wrote on 2013-08-12:
Hello,
I have just tried to convert the page and it works me. Did you make any changes on your end in the meantime?
stvogdn
wrote on 2013-08-13:
I had in fact changed the page to remove the webfont. I have now replaced the webfont with another(somewhat smaller) font and I am once again getting the error. I would appreciate it if you would take another look.
The page is http://jp.flukenetworks.com/print/content/managing-byod-and-consumerization-it
support
wrote on 2013-08-14:
Hello,
The download speed is ok but it seems there is a bug in our software which causes that it fails to process this particular font file.
We will look into what can be done about it.
stvogdn
wrote on 2013-08-14:
I did not make it clear in my original post but my actual usage is with the API using the PHP sdk. The page that we normally use is http://jp.flukenetworks.com/content/managing-byod-and-consumerization-it. The PDF link on the page submits the content html via the api and then serves the pdf to the user.
If you have enough information to proceed without it, I am going to revert to the non-webfont version. Even though the end users don't like the default font, it is better than no font at all. If you need me to create a page for you to test with, let me know and I'll create a page to test with.
Steve
support
wrote on 2013-08-14:
Hello Steve,
Thanks for the info and your willingness to help. The font file itself is enough for us to reproduce the issue in our environment.
stvogdn
wrote on 2013-08-28:
Can you let me know if any progress has been made on this issue?
Thanks.
support
wrote on 2013-08-30:
Hello,
No progress on this issue yet. We will post an update here once the issue is resolved.
stvogdn
wrote on 2013-09-17:
I know you said you would post when the issue was resolved, but I was wondering if there was any way to predict when this might be. This is also an open ticket on my queue and I am getting pressure from Japan.
Thanks for your help.
Steve
support
wrote on 2013-09-18:
Hello Steve,
Unfortunately, this turned out to be more complicated than we initially expected so we are not really able to give an ETA for this at the moment.