Pentaho Kettle 解决方案


I just received a copy of the Chinese translation of Pentaho Kettle Solutions.

Right off the bat when we made it open source over 8 years ago, Kettle became very popular in China.  Among the very first Chinese people who helped out with bug fixing and translation was Jason Chu , a Pentaho BI Consultant who lives in Beijing city.  Jason spent a few years of his life translating Pentaho Kettle Solutions, a book written by yours truly, Jos Van Dongen and of-course my colleage Roland Bouman.

The new book is called Pentaho Kettle解决方案 : 使用PDI构建开源ETL解决方案 and is available from

Matt holding Chinese Pentaho Kettle Solutions book

While I can’t read Chinese (at all) the look and feel of the book is excellent: graphics are great and for example screenshots were re-done in the Chinese localization setting of Spoon.  The book is published by Wiley and from what I learned from their method of publishing is that it is guaranteed to offer excellent results.  Congratulations to all involved in making this book possible!

It’s impossible to thanks Jason enough for all the hard work he has done, also now in translating our book and with this post I would like to recommend the end-result to all Chinese people!

Have fun with Kettle wherever you are!









  • Teruo Kawasaki

    Hi Matt, congratulation for the Chinese edition of Pentaho Kettle Solutions!

    BTW, no response to my pull request for over 2 months.

    Reading properties file without native2ascii. (use UTF8 characters)

    I want to write a property file with Japanese strings, not in native2ascii encoded strings.
    With multi-byte character languages such as Chinese, Korean and Japanese,
    it’s too much trouble with native2ascii encoded string.

    It was my first pull request.
    Please advise me how to go ahead with the problem.


  • Hello Kawasaki-san,

    I must admit that we have been overwhelmed with the amount of pull requests and contributions. At the same time Pentaho is hardening the code, as you might have seen, in the sense that we’re adamant about writing unit tests, code coverage and code formatting. In that sense it’s often hard to validate even a single line change such as yours. Please understand that we do this to protect our larger community from unexpected errors. So I left a comment to the pull request with the question to come up with a unit test to make sure old-style message bundles are read equally well as UTF-8 while being encoded in ISO-8859-1.

    I hope that soon we’ll be able to provide our community with exact contribution instructions and tips.

    Thank you for your time and contribution!


  • Teruo Kawasaki

    Thank you, Matt!
    I will try.