Summary of Bug

      When a page is exported as PDF, special characters like Ω and µ are omitted.

      How to reproduce

      1. Create a page, and include special characters like Ω
      2. Save the page, and then 'Export as PDF'
      3. In the PDF file, the 'Ω' character is completely missing

      Findings

      I have tried this in Confluence 4.0.3, 4.0, 3.5.9, 3.4.9, 3.3.3, 3.1.2 and 3.0.0_01. All of these versions suffer from the same problem. Have tried disabling and re-enabling the PDF Export plugin, then restart Confluence instance, but problem persists.

      This is how it looks like in the editor :

      This is what happens after it is exported as PDF :

      Workaround

      Upload a font that contains these symbols to Confluence, as detailed in CONF-25887.

            [CONFSERVER-36371] PDF export omits special characters like µ and Ω

            My experience with this bug is somewhat different.

            I didn't have any problems with the export of special characters for as long as I didn't use any "font-family" definitions.
            Now, for the first time I had to use a specific font (my company's standard font). I uploaded it as an attachment and included it with "@font-face" and suddenly special characters were missing in PDF exports.

            I thought it was a problem of this specific font until I found out that as soon as I use any king of "font-family" definition the problem occured.

            In other words:

            To me it seems that special characters do work in exports as long as the standard Confluence font is used (whatever font that is).
            But as soon as you use any kind of "font-family" definition in your PDF export stylesheet, special characters are gone.

            For me this means that I can either use the right font or use special characters, but not both.

            Steffen Heller added a comment - My experience with this bug is somewhat different. I didn't have any problems with the export of special characters for as long as I didn't use any "font-family" definitions. Now, for the first time I had to use a specific font (my company's standard font). I uploaded it as an attachment and included it with "@font-face" and suddenly special characters were missing in PDF exports. I thought it was a problem of this specific font until I found out that as soon as I use any king of "font-family" definition the problem occured. In other words: To me it seems that special characters do work in exports as long as the standard Confluence font is used (whatever font that is). But as soon as you use any kind of "font-family" definition in your PDF export stylesheet, special characters are gone. For me this means that I can either use the right font or use special characters, but not both.

            I can't close the case, please be kind to do it for me. Thanks again for the help.

            Lionel CONFORTO added a comment - I can't close the case, please be kind to do it for me. Thanks again for the help.

            Yes it works, thanks !!

            Lionel CONFORTO added a comment - Yes it works, thanks !!

            Hi lionel.conforto

            Thanks for taking the time to raise this issue. It could be that you are experiencing a problem with the font used by default for PDFs. There is a resolution for this issue here: https://confluence.atlassian.com/display/DOC/Creating+PDF+in+Another+Language

            Are you able to confirm if this works for you?

            Regards
            Steve Haffenden
            Confluence Bugmaster

            Steve Haffenden (Inactive) added a comment - Hi lionel.conforto Thanks for taking the time to raise this issue. It could be that you are experiencing a problem with the font used by default for PDFs. There is a resolution for this issue here: https://confluence.atlassian.com/display/DOC/Creating+PDF+in+Another+Language Are you able to confirm if this works for you? Regards Steve Haffenden Confluence Bugmaster

            I've duplicated the issue as I also found the problem in release 5.5.3

            Lionel CONFORTO added a comment - I've duplicated the issue as I also found the problem in release 5.5.3

              shaffenden Steve Haffenden (Inactive)
              592725a8b6b0 Lionel CONFORTO
              Affected customers:
              0 This affects my team
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: