c2c-oerpscenario team mailing list archive

["Olivier Dony \(OpenERP\)" <633991@xxxxxxxxxxxxxxxxxx>]

(Sorry for the status spam, was trying to convert to a question but
Launchpad crashes.. happens for bugs with a too long history = bug
438116)

@digitalsatori: I understand why you marked this bug a duplicate of bug 625019, but I would like to make them separate, just to be sure that people find this one easily as well.
Indeed the issue in comment #1 is just a bad encoding in the old l10n_chart_cn modules in extra-addons (5.0 and 6.0), and people can instead use the modules on your googlecode project, or simply the new chart of accounts "l10n_cn" that was merged and is directly included in OpenERP 6.0 official addons.

But this bug also discusses the issue of chinese characters in PDF
reports, which is really just a problem of fonts. Basically for chinese-
speaking countries, you need to tell the report engine to use chinese
fonts in the PDFs, as the default international fonts do not have
support for chinese characters. A possible solution is to install the
base_report_cn module that you created, similar to the
base_report_unicode module from Gábor Dukai: http://bit.ly/g5vIPp

Perhaps you could also add your base_report_cn module in the extra-
addons if it is correctly tested now, to help others find it more
easily?

** Changed in: openobject-server
       Status: Confirmed => Invalid

** Changed in: openobject-server
     Assignee: OpenERP's Framework R&D (openerp-dev-framework) => (unassigned)

-- 
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.
https://bugs.launchpad.net/bugs/633991

Title:
  How to display Chinese characters properly in PDF reports?

Status in OpenObject GTK Client:
  Invalid
Status in OpenObject GTK Client 5.0 series:
  Invalid
Status in OpenObject GTK Client trunk series:
  Invalid
Status in OpenObject Server:
  Invalid

Bug description:
  Hi all,

  We have a problem with the Chinese characters.

  Could you check and fix this bug in 5.0 and 6.0.

  Thank you,

  Regards,