Jump to content
You must now use your email address to sign in [click for more info] ×

Search the Community

Showing results for tags 'afb-3865'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Affinity Support
    • News and Information
    • Frequently Asked Questions
    • Affinity Support & Questions
    • Feedback & Suggestions
  • Learn and Share
    • Tutorials (Staff and Customer Created Tutorials)
    • Share your work
    • Resources
  • Bug Reporting
    • V2 Bugs found on macOS
    • V2 Bugs found on Windows
    • V2 Bugs found on iPad
    • Reports of Bugs in Affinity Version 1 applications
  • Beta Software Forums
    • 2.5 Beta New Features and Improvements
    • Other New Bugs and Issues in the Betas
    • Beta Software Program Members Area
    • [ARCHIVE] Reports from earlier Affinity betas

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Location


Interests


Member Title

Found 2 results

  1. Operating system: Windows 10 Home | Affinity Publisher version: 1.8.3.641 When using a full charset version of the pan-CJK typeface, Source Han Sans (SHS), .pdf files can be exported when there is text rendered using Chinese glyphs, Japanese glyphs, or a combination of both. However, when using any number of Korean hangul glyphs (minimum of 1) with the same font (either alone or with Chinese/Japanese glyphs), the export fails to complete. All glyphs render properly within the application. An indication of the problem can be seen before exporting, as in the export settings window, the application will calculate the estimated filesize indefinitely if any pan-CJK SHS Korean glyphs are present in the document. The error message displayed afterwards is: "An error occurred while exporting to [filepath]." It is not a problem with the font files, as Chinese/Japanese glyphs from the same font work, other programs' .pdf export features work with Source Han Sans' Korean glyphs, and the font files were downloaded directly from the official repository: https://github.com/adobe-fonts/source-han-sans/tree/release. When the Korean glyphs are rendered using other Korean-language fonts, they can be exported. This problem can be reproduced in new documents. Using various export presets failed to resolve the issue. Not electing to embed fonts failed to resolve the issue. Changing font subsetting settings failed to resolve the issue. Changing various language-tagging options failed to resolve the issue. The workaround that I found was to use the Korean "Region-Specific OTF" (within the Github repository) which only contained Korean glyphs. When I used the SHS KR version to render Korean text, and the pan-CJK version to render the Chinese/Japanese text, the .pdf export was successful. As such, I suspect that the issue may be tied to the way that Affinity Publisher reads large pan-CJK font files (the full charset version of SHS contains an extremely large number of glyphs—over 65,000), and particularly Korean glyphs, since Korean characters are individually constructed from component glyphs, while one Chinese/Japanese character is equivalent to 1 glyph. On my machine, steps taken to isolate the issue were as follows: 1. Create three text boxes—one with Chinese text, one with Japanese text, and one with Korean text. 2. Apply Source Han Sans (any weight) to all text. 3. Export the document as a .pdf. The export should fail to complete. 4. Delete the box with Korean text. 5. Export the document as a .pdf. The export should complete successfully. The issue can also be reproduced by only adding Korean text to a new document, applying the typeface, and attempting to export the document as a .pdf.
  2. Hello, I get the enclosed error message when exporting PDF/X4 The export is aborted. I had a similar problem in one of the beta versions last year. At that time an old Adobe postscript font was responsible. When I export the document as PDF/X3 the export works fine. I have a similar problem when exporting from AD when a PDF is placed in the document. What could be the reason for this? Regards Kai-Uwe
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.