fmommeja
-
Posts
18 -
Joined
-
Last visited
Posts posted by fmommeja
-
-
On 1/19/2024 at 4:03 PM, walt.farrell said:
Have you tried it in the current 2.4 beta, which has the fix for the previously reported problem with the Figure Space?
Nope, I'm downloading it right now.
I'll tell you. -
I just reported this to be sure developers didn't miss it when fixing the Figure Space issue.
-
-
The same issue occurs with Punctuation Space.
Hope this will be fixed in 2.4 as it is not in 2.3.1.
-
Hi Mike,
thank you for your confirmation.
However, it doesn't occur with all fonts but it clearly appeared with the 2.3.0 version.
-
10 minutes ago, walt.farrell said:
Can you explain what the problem was that you had to fix?
Well, I saw in FontForge that there was no content for the U+2007 character…
I copied the space character content (U+0020) to U+2007 then copied the width of a W letter (U+0057) that fitted to my needs for a Figure Space… saved, generated the new .otf file… Et voilà ! ^^
-
I finally managed to edit it with FontForge and everything works fine now.
Thank you !
-
Hi Walt,
this is Myriad Pro Regular from Adobe (converted to OTF using TransType).
I get your point… I opened the font in Font Forge and inspected the U+2007 character but it was empty. No 0.
But it's definitely an issue related to that font as it disappears when changing it to Helvetica for instance.
Well, thanks a lot for your help. I'll manage to use a specific character style for these kind of spaces.
But if you still have a tip to correct a font that displays wrong, I'll be happy to read it! ^^
Have a good day.
-
-
Footnotes are the last frontier to reach/overcome InDesign features !
Go for it guys !
And if you implement this as cleverly as you did it with other features, I'll leave Adobe for good.

-
Hi Sean, thank you for the feedback.

I understand the trickiness of these kind of lines but I guess if you want actual Adobe CC users to switch to Affinity Suite, they need at least to be able to reopen the documents they made before…
As there's no InDesign file import available now, the only way to modify previous jobs is by opening the associated PDF files.
And I think people won't make the switch until they are totally assured that their previous work won't be lost.

-
Hi Affinity Team, hope you had a Merry Christmas!
Here is an annoying bug remaining while opening PDF files containing spotted strokes circles: some spots are missing on left, top and right.
This bug was present in Affinity Designer 1.6.1 and is also present in the last Affinity Publisher Beta release.
Attached are the screen copy and the PDF file having the issue.
Steps to reproduce:
-------------------------------• File->Open… menu
• Select the PDF file (testPDF-ContoursPoints-V.pdf) and click OK

HTH
Kind Regards
--
Frédéric -
Hi Chris_K
it occurs on a brand new TOC as I didn't already have one in an existing file.
Kind regards
-
Please find the crash log attached.
The crash occurred while editing a TOC texte style and trying to change the Tab stop leader from none to character.
How to reproduce:
- Create a TOC with multiple entries
- Select Text tool
- Click on one of the TOC entries
- Edit one of the TOC Text Styles
- Click on Tab Stops
- Click on the Tab stop leader none zone displaying ( ) at the left of the down arrow to deactivate
- Click back on it to reactivate
- Click on the Tab stop leader none down arrow to select Tab stop leader character
- Et voilà !!!
Seems not to happen when waiting some time (more than 1 min) between steps 7 and 8…
Kind regards to all AP devs
-
Hi @Pauls, I totally understand that. :)
My report was only focused on helping your development, not criticizing in any way.
You're doing great job !
-
Thanks @PatrickConnor,
I'll proceed the same way for the next report… if there is one.

-
Here is the debug info attached as : CrashDump-65094.txt
Thanks for that so promising software!
Go for it, we are ready to buy!
Kind regards
Fred



[Solved in 2.4 beta] Affinity Publisher 2.3.1 Bug : Punctuation Space displays as a comma character
in V2 Bugs found on macOS
Posted
Thanks @walt.farrell for the suggestion.
The issue is effectively solved in Publisher 2.4 beta.