Jump to content

Recommended Posts

Posted

I found a bug after crating a document with some characters of the font "Winding" in a new document. After exporting the publisher file to pdf and reimport this PDF File in Publisher the characters of the Windings font are not visible. the characters of Windings are often used as Textboxes in formulars to choose an option.

The behavior is reproduceable.

Regards

erdi12

Posted
12 hours ago, LibreTraining said:

@erdi12

Where can this "Winding" font be found?

Can you post the PDF?

 

This probably means the font Wingdings. This is installed by default with Windows.

MAC mini M4 | MacOS Sequoia 15.5 | 16 GB RAM | 256 GB SSD 
AMD Ryzen 7 5700X | Sapphire Nitro+ RX 9060 XT 16 GB  | 32 GB DDR4 3200MHz | Windows 11 Pro 24H2 (26100.4351)

Windows 11 Pro on VMWare Virtual Machine (on Mac)
Affinity Suite V 2.6.3 & Beta 2.6 (latest)
Interested in a free (selfhosted) PDF Solution? Have a look at Stirling PDF

No backup, no pity.

Posted
23 minutes ago, Komatös said:

This probably means the font Wingdings. This is installed by default with Windows.

Indeed, and it includes several checkbox glyphs (with and without ticks and crosses).

Alfred spacer.png
Affinity Designer/Photo/Publisher 2 for Windows • Windows 10 Home/Pro
Affinity Designer/Photo/Publisher 2 for iPad • iPadOS 17.5.1 (iPad 7th gen)

Posted (edited)

I believe it is not a bug, but a licensing issue as to how the font may be used.

This is what the license agreement says:

Microsoft supplied font. You may use this font to create, display, and print content as permitted by the license terms or terms of use, of the Microsoft product, service, or content in which this font was included. You may only (i) embed this font in content as permitted by the embedding restrictions included in this font; and (ii) temporarily download this font to a printer or other output device to help print content. Any other use is prohibited.

 

Screenshot 2021-03-27 095120.png

Edited by Komatös
Corrected

MAC mini M4 | MacOS Sequoia 15.5 | 16 GB RAM | 256 GB SSD 
AMD Ryzen 7 5700X | Sapphire Nitro+ RX 9060 XT 16 GB  | 32 GB DDR4 3200MHz | Windows 11 Pro 24H2 (26100.4351)

Windows 11 Pro on VMWare Virtual Machine (on Mac)
Affinity Suite V 2.6.3 & Beta 2.6 (latest)
Interested in a free (selfhosted) PDF Solution? Have a look at Stirling PDF

No backup, no pity.

Posted
11 minutes ago, Komatös said:

I believe it is not a bug, but a licensing issue as to how the font may be used.

Since the font is supplied as standard with Microsoft Windows, it must surely be licensed for use in any software running on that platform. The embeddability flag is set to allow editable embedding, so there’s no reason for any of the glyphs that are embedded in the PDF not to display and be editable.

Alfred spacer.png
Affinity Designer/Photo/Publisher 2 for Windows • Windows 10 Home/Pro
Affinity Designer/Photo/Publisher 2 for iPad • iPadOS 17.5.1 (iPad 7th gen)

Posted

I create a demo file to show what happens.

In the document "winding-step_1.afpub i create a textbox with the windings glyphs.

Th wingings_step-1 show the PDF file, exported by publisher with the adjustment for printing

The winding_step_2-Reimport shows the result by importing the PDF file above. The glyphs are completely different, some of some are not visible. if you check the fount, no warning an the font is recognized as Windings.

winding_step_1.afpub winding_step_1.pdf winding_step_2-Reimport_PDF.afpub

Posted
51 minutes ago, Alfred said:

Since the font is supplied as standard with Microsoft Windows, it must surely be licensed for use in any software running on that platform. The embeddability flag is set to allow editable embedding, so there’s no reason for any of the glyphs that are embedded in the PDF not to display and be editable.

You are right. The PDF exporter importer of the Affinity programs has a problem with fonts where no Unicode ranges are specified.

MAC mini M4 | MacOS Sequoia 15.5 | 16 GB RAM | 256 GB SSD 
AMD Ryzen 7 5700X | Sapphire Nitro+ RX 9060 XT 16 GB  | 32 GB DDR4 3200MHz | Windows 11 Pro 24H2 (26100.4351)

Windows 11 Pro on VMWare Virtual Machine (on Mac)
Affinity Suite V 2.6.3 & Beta 2.6 (latest)
Interested in a free (selfhosted) PDF Solution? Have a look at Stirling PDF

No backup, no pity.

Posted (edited)

The export works well, but the import is the problem. The font has also unicode codes.  Affinity change the codes during import.

 

Edited by erdi12
more explamation
Posted

Wingdings.ttf is a symbol font, not a Unicode font.
Yes, it does have Unicode code points assigned to the glyphs, but they are all up in the PUA (Private Use Area).
And are not used in this case.

The problem is sub-setting the characters when embedding the font.
When the sub-set font is created an index to those particular characters is created in the embedded font.
This index only works for this sub-set embedded font.
This index does not match-up with the full font character set in your installed font.
For it to match you have to embed the entire font, which has the entire character set.
Note: this is a PDF specifications issue not an Affinity Publisher issue, or PDFlib issue.

When you Export to PDF make sure to un-check Subset fonts.
Then when you re-import it works.

This is the new no-subset PDF opened in APub. (The actual PDF is below.)

winding_step_1_no_subset.thumb.png.f52fc9b39370f5b3c808c2fbb8890602.png

winding_step_1_no_subset.pdf

 

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • 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.