Sivan_

If this is a bug in Affinity, is it logged?

Thanks @Alfred, that definitely explains to me why this happens. In that case, the expected behavior is that the font subset will point to to the correct glyph so in the case it is a font I have installed this problem won't happen. From looking around, I don't see this how to make that happen and embedding the entire font is not an option.

I've encountered an annoying bug in opening an old .pdf file that was created in Publisher (sadly I've lost the source 🥲, and I needed the text to recreate it). When viewed in a regular pdf viewer it renders correctly, but when opened in publisher it renders\reads the text ligatures incorrectly. in the pdf viewer: in publisher: I've created a sample file in publisher and it shows the same problem and can be shared (attached the pdf and afpub) in publisher: the pdf file when opened in Publisher P.S. I am using Publisher 2.4.1 on a Windows 10 machine. test ligature.afpub test ligature.pdf

Thanks all of you. 😄

Hello everyone, I'm currently working on a document that requires the use of end-notes for references. However, I've encountered a situation where I need to reference the same note multiple times throughout the document. Specifically, I want the same end-note number (e.g., "4") to appear on different pages, all pointing to the same note at the end of the document. Is it possible to do so without adding manually the extra endnote numbers? Thanks in advance for any help, Sivan

+1

I have done the following steps: create a graphic in Affinity Designer. copy it and put it into a Word document with "copy items as SVG" convert the SVG into a shape The reason for converting the SVG into shape is compatibility issues with organizations that use old Office versions.

While trying to place docx file within Affinity Publisher 2.1, I noticed that the vector graphics got messed up. The attached docx file: The placed docx within Affinity Publisher test1.docx

Would definitely be a time saver. +1

bump

I didn't know whether to bump the old thread or create a new one as this feature was already requested in version 1. Would very much love if the pressure control tool would be improved for easier editing of stroke width.

Hi, The following bug still exists within Affinity Publisher 2.0. I am using Publisher 2.0.0 on a Windows 10 machine (Ver 21H1, intel i7-9750H with NVIDIA 1660 Ti).

I've noticed in that in Publisher 1.10.5.1342 the scrollbars act weirdly in rotated view. Attached a video demonstration. P.S. I am on Windows 10 machine (i7-9750H with NVIDIA 1660 Ti) Publisher rotated view.mp4

Bumping as well, will be really helpful.

Thanks for the response, Is there any workaround to export the nodes? Best, Sivan

Hi, When exporting SVG there seems to be an extra optimization step that is being done to the objects. I am trying to export vector graphics for an animation software, and I need the extra nodes. I cannot find how to remove this optimization, or whether it can be removed. This optimization is also being done through the clipboard copy as SVG. I've created a minimal example to show the problem: The source: The exported SVG: Searching on the forum, it seems related to: P.S. I am using Designer 1.10.4.1198 on a Windows 10 machine (i7-9750H with NVIDIA 1660 Ti, Windows Version: 10.0.19043 Build 19043) exclamation_mark.afdesign exclamation_mark.svg

+1 for this feature, please

The arrow was created fully within Affinity Designer. I only have the fixed source after I fixed the problem (recreated the arrow from scratch). In my process: I created some basic diagram elements (some of them containing arrows) Grouped them together Moved and transformed the elements to fit the target diagrams Tweaked them to look nice Rotated them Used the Node tool to change their endpoints Changed their properties (width, color) I had over dozen different elements with arrows, all of them probably went through similar processes, only one of them did not export correctly. Sadly, I can't pinpoint exactly what caused the problem.

Happy new year, I somehow created a problematic arrow in affinity designer inside a much more complex diagram. The exported file showed a giant black bar across the image instead of an upward arrow. I isolated the arrow in a new file and it still exports wrongly. I am using Affinity Designer 1.10.4.1198 on a Windows 10 machine. When exporting it as SVG, it acts differently on different programs. In PowerPoint, it shows as a giant black box. Attached is a minimal example of an affinity designer file containing the arrow and the created SVG. problem arrow.afdesign slice1.svg

Hi @Wosven, I am not using print for exporting, the "Microsoft Print to PDF" is just an easy way to reproduce the problem. When I am printing documents containing RTL texts from the application I get this "corrupted" prints. I usually print sample pages of the document to check for readability problems. Exporting the document to PDF and than printing adds another step. I can deal with it, it's just annoying to always export, open another program and from there to print.

Hi, I am encountering a problem in printing documents containing RTL text within it. Exporting the document yields correct results, printing the document does not. Attached is a minimal example as well as a video recording of their creation. The same incorrect result (created by "Microsoft Print to PDF.") is also given by printing through a regular printer. 2021-10-09 22-05-11.mp4 I am using Publisher 1.10.1.1142 on a Windows 10 machine (i7-9750H with NVIDIA 1660 Ti). test_hello.afpub test_hello.pdf test_hello2.pdf

Hi, I am encountering a strange bug in the union operation in between two paths. I have tested it in both destructive and non destructive union operation. Affinity Designer 2021-02-07 21-42-03.mp4 Attached is a minimal example that seems to reproduce the problem. Test.afdesign