Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-9831

non-english (international characters) in code and noformat macros render as # on pdf export

XMLWordPrintable

      It appears that at least some international characters render as # signs when exported to pdf. This has been reported and replicated in environments in which encoding tests pass.

      The following string:
      я хочу видеть этот текст отформатированным

      Yielded the attached PDF (ds-589825-20071026-12_10_38.pdf)

        1. Picture 12.png
          Picture 12.png
          79 kB
        2. ds-589825-20071026-12_22_43.pdf
          171 kB
        3. ds-589825-20071026-12_10_38.pdf
          171 kB

            [CONFSERVER-9831] non-english (international characters) in code and noformat macros render as # on pdf export

            Chris Kiehl added a comment -

            I think the code is fine as it is. Although we need to keep in mind that code/pre formatted text will no longer be displayed using a monospace font. To be able to do that we would have to enable the user to upload a monospace font for PDF export which is able to render all of the required characters next to the normal font. But this will be a special case only covering the code/pre macro. To properly solve that issue we would need to add the ability for macros to provide their own XSL and fonts which is out of the scope of this issue.

            Chris Kiehl added a comment - I think the code is fine as it is. Although we need to keep in mind that code/pre formatted text will no longer be displayed using a monospace font. To be able to do that we would have to enable the user to upload a monospace font for PDF export which is able to render all of the required characters next to the normal font. But this will be a special case only covering the code/pre macro. To properly solve that issue we would need to add the ability for macros to provide their own XSL and fonts which is out of the scope of this issue.

            Brian Nguyen (Inactive) added a comment -

            It turns out the problem was because the noformat and code macros explicitly used the the monospace font, which does not support the unicode characters.

            I've removed the font but that made the macros look exactly the same as standard text. So I've added some extra styling (indentation and font color) as well.

            Brian Nguyen (Inactive) added a comment - It turns out the problem was because the noformat and code macros explicitly used the the monospace font, which does not support the unicode characters. I've removed the font but that made the macros look exactly the same as standard text. So I've added some extra styling (indentation and font color) as well.

            Sandy James added a comment -

            I have found a temporary work around. First convert the wiki page to a Word document - than convert the Word document to a PDF. This is inconvenient but at least is doable.

            Sandy James added a comment - I have found a temporary work around. First convert the wiki page to a Word document - than convert the Word document to a PDF. This is inconvenient but at least is doable.

            Luke Yang added a comment -

            Hi, guys

            This is Luke from Korean partner, Goldpitcher.
            This issue is same with Korean characters.

            One of our customer reported this and we confirmed it.
            Please check as soon as possible.

            Thanks in advance.

            Cheers.

            Luke Yang added a comment - Hi, guys This is Luke from Korean partner, Goldpitcher. This issue is same with Korean characters. One of our customer reported this and we confirmed it. Please check as soon as possible. Thanks in advance. Cheers.

            Neeraj Jhanji added a comment -

            I confirm the same problem with Japanese characters: CONF-10109

            Neeraj Jhanji added a comment - I confirm the same problem with Japanese characters: CONF-10109

            Igor Minar added a comment - - edited

            I can confirm this bug on our system with installed UTF8 fonts, see the attached screenshot.

            Igor Minar added a comment - - edited I can confirm this bug on our system with installed UTF8 fonts, see the attached screenshot.

            Igor Minar added a comment -

            HTML page on the left and PDF with ### on the right

            Igor Minar added a comment - HTML page on the left and PDF with ### on the right

            Choy Li Tham [Atlassian] added a comment -

            Hi there,

            This instruction doesn't heal the ###-problem with macros code and noformat

            It appears that the special characters are output as the '#' symbol too if the string is wrapped with the monospace macro. For example:

            {{ÁRVÍZTŰRŐ TÜKÖRFÚRÓGÉP}}

            Cheers,
            Choy Li

            Choy Li Tham [Atlassian] added a comment - Hi there, This instruction doesn't heal the ###-problem with macros code and noformat It appears that the special characters are output as the '#' symbol too if the string is wrapped with the monospace macro. For example: {{ÁRVÍZTŰRŐ TÜKÖRFÚRÓGÉP}} Cheers, Choy Li

            Jeremy Largman added a comment -

            Reopening issue per Alexander's comment above.

            Jeremy Largman added a comment - Reopening issue per Alexander's comment above.

            Alexander Korolev added a comment -

            Hi, Matt!

            This instruction doesn't heal the ###-problem with macros code and noformat!
            It's affect only on common text.

            See how people comment this here:
            http://confluence.atlassian.com/display/DOC/Create+PDF+in+another+language?showComments=true#comments

            Alexander Korolev added a comment - Hi, Matt! This instruction doesn't heal the ###-problem with macros code and noformat ! It's affect only on common text. See how people comment this here: http://confluence.atlassian.com/display/DOC/Create+PDF+in+another+language?showComments=true#comments

            Jeremy Largman added a comment -

            Thanks Matt, I missed that! Resolving the issue.

            Jeremy Largman added a comment - Thanks Matt, I missed that! Resolving the issue.

            Matt Ryall added a comment -

            You need to install a Unicode font to produce PDFs with non-Latin characters, as documented here:

            http://confluence.atlassian.com/display/DOC/Create+PDF+in+another+language

            Has this been done?

            Matt Ryall added a comment - You need to install a Unicode font to produce PDFs with non-Latin characters, as documented here: http://confluence.atlassian.com/display/DOC/Create+PDF+in+another+language Has this been done?

            Jeremy Largman added a comment -

            The following string fails to export as well:

            大陆新移民刘怡欣女士当选珀斯市议员

            Jeremy Largman added a comment - The following string fails to export as well: 大陆新移民刘怡欣女士当选珀斯市议员

              bnguyen Brian Nguyen (Inactive)
              jlargman Jeremy Largman
              Affected customers:
              9 This affects my team
              Watchers:
              11 Start watching this issue

                Created:
                Updated:
                Resolved: