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

Double Breve below/above


Recommended Posts

Hello, I am using Affinity Publisher on Windows. I am using Unicode glyphs U+035c (Combining Double Breve Below) and U+036c (Combining Double Inverted Breve) to produce ties below and above two characters. On the Publisher canvas, it looks good (screenshot 1), while exporting to a PDF makes the ties and characters overlap (screenshot 2). Any ideas how I could fix this? Thanks for your assistance, Dirk

combining_breve_publisher_canvas.PNG

combining_breve_pdf.PNG

Link to comment
Share on other sites

Hello @Dirk Schmücker

I think you use the wrong glyph. And if I testing with various fonts, it is the font itself.

Have had testet with Calibri. The export is faulty. Exported with Dejavu, the result shows as expected.

image.png.fc3f831bca8792601b28929d866b9fb3.png

AMD Ryzen 7 5700X | INTEL Arc A770 LE 16 GB  | 32 GB DDR4 3200MHz | Windows 11 Pro 23H2 (22631.3085)
AMD A10-9600P | dGPU R7 M340 (2 GB)  | 8 GB DDR4 2133 MHz | Windows 10 Home 22H2 (1945.3803) 

Affinity Suite V 2.3.1 & Beta 2.(latest)
Better translations with: https://www.deepl.com/translator  
Need a system wide color picker? Try Microsoft's (New) Power Toys
Need a robust PDF Solution? Have a look at Stirling PDF

There's nothing you get used to faster than working slowly!

Link to comment
Share on other sites

Thank you, Komatös, changing the font only helps with the ties above, but not those below (the glyph U+035c is not even in the Dejavu font). Any other ideas? Cheers,

Dirk

P.S. Using Times New Roman, U+0361 produces the same faulty export as U+036c

P.P.S. Used a word processor to check the glyphs and the font, and it works ok. Must be something with APub ...

Edited by Dirk Schmücker
Link to comment
Share on other sites

@Dirk Schmücker

Could you please attach your test document?

And confirm you are using Times New Roman?

I have seen these double breves handled successfully in OpenType code, but I am not sure how or if it can work manually. It looks like in the PDF output the anchor points are ignored or broken, or it is a bug in the PDFlib, or ... ?

UPDATE: this does appear to be a bug.
Tested in TNR and multiple other fonts.
Tested your text and other text which includes those characters.
All did not work in APub.
All did work LibreOffice (Harfbuzz).

FYI: 036C is Combining Latin Small Letter R

Link to comment
Share on other sites

Thank you, @LibreTraining

a) yes, I use Times New Roman, as included in Windows

b) U+036c was wrong, U+0361 was the glyph I used for the tie above. Sorry for the confusion.

c) Testdok and pdf are attached.

d) UPDATE: Exporting from AfPub to EPS or PNG works ok, but not to PDF.

Thanks for your time and energy, best regards,

Dirk

 

testdok-breves.afpub testdok-breves.pdf

Edited by Dirk Schmücker
Link to comment
Share on other sites

8 hours ago, Dirk Schmücker said:

d) UPDATE: Exporting from AfPub to EPS or PNG works ok, but not to PDF.

I printed my test doc to the ImagePrinter printer driver - some of it worked, some of it did not.
But I had other text combinations than just those that you had.

Printed your test doc to my ImagePrinter - it looks the same as the Export to PNG.

Some bugs here for sure.

Link to comment
Share on other sites

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.