Menu

#5 Encoding support Traditional Chinese?

open
GUI (1)
5
2011-10-20
2011-10-20
Anonymous
No

I have many ebooks are written with traditional chinese. It seems that I can't find the encoding supporting traditional chinese. current version support only simplified chinese? if yes, hope can add traditional chinese encoding.

Discussion

  • Martin Schröder

    This feature request is on my ToDo list for v0.9.14, so I'll take a look at it in the coming days and weeks.

    But do be aware that this might not actually lead somewhere if the fonts installed on the device by Palm/HP do not contain traditional chinese characters. In that case, you will have to install a custom font capable of displaying these glyphs. As the UTF-8 support is complete in the pReader, you can test this by loading an UTF-8 document with traditional chinese glyphs and see if they show up correctly in the default fonts.

     
  • Martin Schröder

    • labels: --> GUI
    • assigned_to: nobody --> jappus
     
  • rayfu

    rayfu - 2011-10-21

    Thanks. Actually I am using touchpad to run your app. I tried to set UTF8 and different fonts, but it can't display the chinese correctly. However, after converting them to simplified chinese, it can display the simplified chinese in your app.

     
  • rayfu

    rayfu - 2011-11-01

    I just download the new version today. Thanks, but I found that sometimes it hung during loading. There is still no big 5 traditional Chinese encoding. Planning to add the feature later?

    Thanks

     
  • Martin Schröder

    The TouchPad issue was already reported by other users. It is not strictly a pReader-bug, but rather an issue introduced in the update to WebOS 3.0.4. I will receive a TouchPad soon, so I can hopefully fix that issue.

    As for Big5 support, the truth is that the pReader already supports pretty much every encoding in existence, thanks to using the ICU Framework in the C++ back-end. Unfortunately, I have not yet actually found the time to support this flexibility in the JavaScript front-end, due to me mostly being busy with bug fixes.

    The issue is on my ToDo for v0.9.14 though, as the actual support is pretty simple, just time-consuming.