wkHTMLToPDF chinese/japanese/korean character support on Linux based systems

By -
This post will explain how to add support for Chinese or Japanese or Korean characters in wkHTMLToPDF - the famous tool that converts HTML pages to PDF documents seamlessly. By default, if you have Chinese characters in your HTML page and convert the page to PDF with wkHTMLToPDF, nothing comes out (blanks replace chinese characters). I doubt this subject will be helpful to a lot of people around the world, but I might need to use this trick again in the future so why not blog about it?

The trick is to install Chinese character support on your OS and rebuild the cache. Under Ubuntu, I ran this command to install Chinese fonts:
apt-get install fonts-wqy-microhei ttf-wqy-microhei fonts-wqy-zenhei ttf-wqy-zenhei 
Note: package names might be different if you aren't under Ubuntu (try apt-cache search ... to search for packages)
Then, run this command to update the font cache:
fc-cache -f -v

For Japanese and Korean please use those:
https://help.ubuntu.com/community/Fonts#Chinese.2C_Japanese.2C_and_Korean_Fonts

ttf-wqy-microhei - A droid derived Sans-Seri style CJK font
ttf-wqy-zenhei - "WenQuanYi Zen Hei" A Hei-Ti Style (sans-serif) Chinese font
ttf-dejima-mincho - antique-looking Japanese TrueType Mincho font
ttf-umefon - Japanese TrueType font, Ume-font
ttf-takao, ttf-takao-gothic, ttf-takao-mincho, and ttf-takao-pgothic - Japanese TrueType font set: Takao Fonts, Takao Gothic Fonts, Takao Mincho Fonts, and Takao P Gothic Fonts.
ttf-kochi-gothic and ttf-kochi-mincho - Kochi Subst Gothic and Mincho Japanese TrueType font without naga10
ttf-sazanami-gothic and ttf-sazanami-mincho - Sazanami Gothic and Mincho Japanese TrueType font (legacy)
ttf-nanum-coding - Nanum Coding fixed width Korean TrueType font
fonts-nanum and fonts-nanum-extra - Nanum and additional Nanum Korean fonts
ttf-baekmuk - Baekmuk series Korean fonts
After that, try generating a PDF again with wkHTMLToPDF: it works! Huge thanks to an anonymous user on StackOverflow for finding the solution.

Comments

descargar whatsapp gratis said…
This is a great article. It gave me a lot of useful information. thank you very much.
----
apply baixar facebook movel and descargar whatsapp gratis para android and apply baixar facebook gratis
Tue Jul 28, 12:43:00 PM
fnaf 3 said…
You know how to involve a reader and increase his curiosity to read more.
----
five nights at freddy's download | fnaf | five nights at freddy's
Mon Aug 10, 03:36:00 PM
Post a Comment

Popular posts from this blog

Nginx error 413: Request entity too large Quick Fix

By -
A quick article today about a common error people encounter with Nginx: the infamous 413 Request Entity Too Large HTTP error. I had the problem myself just yesterday on one of my newly configured servers, so I thought I'd make a blog post about it to make sure I don't forget this next time. Error 413: what does it mean? This error shows up when a visitor sends too much data in the HTTP request. This is normally caused by: • an overy large file being uploaded by the visitor • more generally too much POST data being sent by the client The fix is as simple as setting a directive in your Nginx configuration, read on below. How to fix it? client_max_body_size To fix this, you need to increase the value of the client_max_body_size directive. This directive defines the maximum amount of data Nginx will accept in an HTTP request. By default this value is set to 1 megabyte, meaning if you attempt to upload a file larger than 1 megabyte you'll be getting an  Error ...
Read more

Dealing with Nginx 400 Bad Request HTTP errors

By -
Today I'll write about something I experienced personally, on my websites. Some visitors reported that they were getting a "400 Bad Request" Nginx error randomly when visiting pages. And when they start getting that error, they can't access the site anymore: it'll output the same error no matter the page, until you "clear your cache and cookies". The error is easily understandable and is likely to be caused by... too much cookie data. Every time a visitor loads *any* page/content/file of your website, it sends the cookie data to the server. Cookie data is sent under the form of 1 header line starting with "Cookie: ". Basically, Nginx by default is configured to accept header lines of a maximum size of 4 kilobytes. When a line in the headers exceeds 4 kilobytes, Nginx returns the '400 Bad Request' error. Cookie data sometimes gets big, so it causes the error. It particularly happens on forums like vBulletin, Invision and others...
Read more

Affiliate module for Interspire Shopping Cart

By -
Image
Hello, I have already implemented this module on two shops rather successfully. The concept is quite simple: websites that want to get rewarded through affiliation must link to your website using an identifier in the URL. If your website is http://website.com/, then your links must be of the form http://website.com/?ref=123 where 123 is the affiliate ID. when a visitor clicks the link, the affiliate ID will be placed in a cookie that will expire after 15 days (this can be configured) when the visitor purchases an item: if the affiliate ID cookie is still enabled, the affiliate will be credited of a certain amount, it can be a share of the sale or a fixed amount. affiliate accounts are simple customer accounts, there is no modification to make regarding accounts. When a sale is made, they receive store credit. They can either spend the store credit to purchase items on the store, or they can manually request for a withdrawal (managing withdrawals is up to you). I will detail the i...
Read more