Jump to content

Problem with "combining accent" use.


Recommended Posts

I'm new to Affinity, and moving work over from InDesign.

I am experimenting with a transliteration of Chinese that looks more sensible to Western (or at least Anglophone) eyes than does Pinyin. The font I'm using is Gentium Plus. Unfortunately, I need accent combinations that are not available even in that font's exceptional range of pre-composed characters.

To get them, in InDesign, I was using "combining accent" glyphs when precomposed glyphs are not available for the desired combination. I've never had any problems with this before.

It works in Publisher too, but only for the first such combination in a paragraph. In succeeding combinations in the same paragraph, the combining accent is displaced toward the beginning of the line.

Thus, in illustration 1, both combinations (accents in red circles) display properly, when there is a paragraph break between them:

image.png.7e174f8fba56a5d19dc959581af72eb8.png

But when they are in the same paragraph, as they should be, this happens:

1Line600.png.31abee8bcfda15f2f4a8ee7648741b5a.png

I've searched the settings for possibly relevant options, and (as far as I can tell) it's not an issue with any setting. It's not, for example, a question of whether I specify manual kerning or auto kerning in the text style.

I realize that this is perhaps rather an abstruse issue, which may not quite make Affinity's priority list at this stage. But if there's anything to be done about it, I'd love to know.
 


----------------------------------------------------------------------------------
Affinity V2.1.1 | macOS 13.3.1(a) Ventura | 24" iMac M1
 

Link to comment
Share on other sites

  • Staff

Hi Compositor K,

Would be willing to provide a sample file and a copy of the font that demonstrates this problem so I can look into this further with you?

Thanks
C

Please tag me using @ in your reply so I can be sure to respond ASAP.

Link to comment
Share on other sites

@Callum

PLEASE DISREGARD--SEE NEXT POST.

 

Edited by Compositor K
Sent wrong file in response to request.


----------------------------------------------------------------------------------
Affinity V2.1.1 | macOS 13.3.1(a) Ventura | 24" iMac M1
 

Link to comment
Share on other sites

Callum,

In case I didn't edit the previous post soon enough, please disregard the previous .zip archive. I put the wrong file in it. (The note about the backgrounds pertains to that file, about which I have another post pending.)

Correct file and font is attached to this post.

The illustrated text is at the bottom of page 8, if that helps, but the problem occurs in many places. (The Chinese, by the way, means "eggplant" (aubergine).)

Apologies if this cost you any trouble.

Thanks again for your interest.

to_Callum_correct files.zip

Edited by Compositor K
Additional information to save trouble.


----------------------------------------------------------------------------------
Affinity V2.1.1 | macOS 13.3.1(a) Ventura | 24" iMac M1
 

Link to comment
Share on other sites

@Callum

Forgot to @ you in the last post. I'm new to this forum, and to Affinity, so please bear with me.


----------------------------------------------------------------------------------
Affinity V2.1.1 | macOS 13.3.1(a) Ventura | 24" iMac M1
 

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.