Premier pro wont include french accents in captions

[VolfMedia]

When I am copying the french captions into the caption text box, the french looks fine. But in the program screen, none of the accents are in place and are all replaced with apostrophes. Please help to fix this. 

Win 10

Premier V22.0 

[VolfMedia]

Here is a side by side, caption box and program monitor. 

[VolfMedia]

Well looks like I rushed here before updating! It's fixed in 22.3

[VolfMedia]

So it looks like the problem still persists 

the following characters won't display properly in premier pro: ê + à

[Stan Jones]

These are unicode characters that are composed of 2 characters and a nonspacing mark. Staff will need to chime in....

I describe my discovery of this issue here:

https://community.adobe.com/t5/premiere-pro-discussions/text-appears-without-caron-s-while-copied-to...

At that point, probably PR 2021, the problem was addressed by changing the text engine to South Asian and Middle Eastern:

https://community.adobe.com/t5/premiere-pro-discussions/text-appears-without-caron-s-while-copied-to...

But that selection of text engine was removed Dec 2021 with PR 22.1.1 in favor of a universal text engine:

https://community.adobe.com/t5/premiere-pro-discussions/cant-see-the-middle-eastern-option-in-premie...

I get the same problem you do when pasting these unicode multi-character codes in 22.3.0. What is the fix?

@Trent Happel @Mike-Berry 

Stan

[Mike-Berry]

I have no problem pasting in the above characters into a 22.3 Pr caption layer as long as I choose a font which supports them. For example, in this screenshot you can see the results of the paste in Minion Pro (unsupported) and Lato (supported). Not all fonts will support combining characters, but many will.
Also note that fonts like Minion Pro do support unicode that does not use combining unicodes, like "précédent". All of these words can be created using either single unicodes for "à" or combining unicodes for "à". If you want to use the combining version, then you need to choose an appropriate font.

[Stan Jones]

Thanks, Mike!

Stan

[VolfMedia]

I'd like to agree with this, but it's not correct. The same fonts that used to work are having the issue.

[Mike-Berry]

I should have been more precise in my answer. The Pr text layout engine now handles this for some fonts and not others, based on the glyph availability in the font. If you choose one of the fonts that does not support it, then you need to use the single unicode version to get the glyph.

Mike

[Richard van den Boogaard]

@Kevin-Monahan is this a known issue?