No Kerning Pairs on TMP font import

Hi all, i'm having some issues with importing the kerning pairs for any font file with text mesh pro.

I've tried multiple fonts now, with the 'import kerning pairs' option checked, but the Kerning table info section is always empty. I can open them in other software (such as FontForge) and see the Kerning data is there, but I've just not been able to get anything to show up inside TMP.

I'm on a windows machine, Unity 2017.4.2, running TMP 1.0.55.2017.1.0b12.

Anyone have any suggestions? Does this work in the most recent version of text mesh pro?

 

Thanks for the quick response.

That makes sense, all the fonts I've tried are newer google or adobe fonts that likely only use the GPOS table.

Any workarounds that you know of? I haven't been able to find any information about a conversation from GPOS to kern tables. Maybe there's a way to at least copy/paste the TMP kerning info from one font to another?

 

Ok i'll take a look at some tools, thanks for the help.

 

Hi all,

I'm still getting empty Glyph Adjustment Table after importing a TTF font into Unity 2019.2.
Are there any known workarounds or chances to provide support for new fonts soon?

On the screenshot there is a table of 1712 kerning pairs imported, but each has no values...

 

I'm encountering the same issue after creating a font asset using the LiberationSans font included in the TMP Essential Resources.

I'm on Unity 2019.2.12 using TextMeshPro 2.10 preview.

See screenshot for setup.

As a result I'm getting 3000+ pages of Adjustment Pair that are empty!

Is there anyway to remove these on bulk and not one by one? Or prevent Font Asset Creator from generating empty pairs?

 

Hello. It still doesn't work with AcuminPro fonts (for example). Look at them, please. Even in preview 3.

 

Does TMP still not fully support importing kerning data?

The Glyph Adjustment Table is empty when I create a Font Asset with TMP's Font Asset Creator using Rubik Medium from Google Fonts as the Source Font.

This is making TMP impossible for us to use in production.

(Using TMP 2.0.1 in Unity 2019.4.4f1)

 

Thanks for the reply. I've upgraded to 2.1.3 and followed your instructions but I'm still getting an empty Glyph Adjustments Table.

Here's a video of me following the steps given. Could you please tell me what I'm doing wrong here?

 

Hello,

Is there a way to export the Glyph Pair Adjustment records from a given TMP font asset to another? If I created custom Glyph pair adjustment records for a particular TMP font asset, can I reuse this same data in a another one? Any easy import/export functionality?

Currently, relying on Glyph pair adjustments in the only way to get Arabic fonts displaying properly with all diacritical marks and ligatures, and having this import/export functionality would be make it easier to setup multiple Arabic fonts without starting the process from scratch. Thanks!

 

Thanks for your reply, Stephan. Yes, I'd like to copy it to a different Arabic font asset that uses a different font source. Different Arabic fonts appear differently in the TMP and require different glyph pair adjustments to make them appear correctly in Unity. For example, the Arabic diacritic Fatha (short 'a' sound) doesn't always appear above the Arabic letter when displayed in Unity (it often overlaps with the letter it is supposed to be above), and different fonts have different letter heights, so the amount of yPlacement needed for the diacritic Fatha would vary for each font and each letter combination involving Fatha as the second character. Single glyph kerning/adjustment for Fatha isn't sufficient here and the same goes for all other diacritical marks.

Copying the Glyph pair adjustment table record data from one font asset to another would allow one to make the necessary tweaks to the records to make the other Arabic fonts appear correctly. The copied Glyph pair adjustment table would act as a master data table (or template) that includes the glyph pair combinations that require custom kerning/adjustment. Creating these records from scratch each time is a very time consuming. Thank you.

 

This is really good news! I look forward to these!

How often are TMP releases? Do they typically align with Unity major releases? Thanks!

 

Cool! How do I access preview releases of TMP?

 

Hi Stephan,

I tried the Mark-to-base and mark-to-mark adjustment tables in the 3.2.0-pre.1 release of TMP, and they don't seem to be impacting the TMP object in the scene. While I see the live changes ln the preview below the adjustment tables, the TMP object doesn't change when I modify the X and Y offsets. I have kerning enabled. I am using Unity version 2020.3.15f2.

Below is a short clip of the behaviour I'm seeing with the Mark-to-base adjustment table for the Lalezar font that supports Arabic glyphs. Similar behaviour is seen in the mark-to-mark adjustment of the same font. Please advise. Thanks!

 

Oh? Which ranges would those be? Just wondering if the issue is specific to the TTF font I'm using or if the Mark-to-base positioning wasn't designed with Arabic diacritics in mind.

Arabic diacritics are contained in the Unicode range u064B-u0652 (within the Arabic Unicode block), and there are some other less common special forms found elsewhere.

 

Thank you Stephan. The mark-to-base and mark-to-mark adjustment tables seem to be functioning properly with Arabic diacritics now.

I don't think you have missed any of the Unicode ranges for the main Arabic diacritics. But personally, I think it would be nice to add the ranges 0x0617-0x061A, 0x08D3-0x08E2, and 0x08F0-0x08F3 (Quranic annotations) and 0xFBB2-0xFBC1 (Arabic pedagogical symbols) for completeness sake. Thanks again.

 

Awesome! Thanks Stephan!

 

That's great, Stephan! I look forward to seeing this feature!

And you are right ... manually populating positioning data into these tables is a pain! It took me two workdays just to populate the glyph adjustment data for one Arabic font! However, if I want to recreate the same font to increase the padding value (or the SP/PD ratio) to allow more room for effects like glow, outline, dilation, etc.., all the positioning data in these tables disappears! And this is the case I am in now ... the font's SP/PD ratio is too small.

Is there a way to keep the data from disappearing when re-creating the same font asset in order to modify the font size, padding, atlas dimensions, and render mode? I would imagine that the existing positioning data in the glyph adjustment table, the mark-to-base table, and the mark-to-mark table should all still be functional in the newly created font asset so long as no characters/glyphs have been removed or added, yes? Please advise. Thanks!

 

That is excellent news!

Does this also apply to glyph pair adjustment tables?

That would be wonderful! I look forward to seeing this feature and I would be happy to test it out!

 

Hello,

What is the recommended way for reusing TMP font assets from project to project? I tried exporting and importing them as a part of an asset package, but the reference to the font material disappeared (as well as the reference to the source font itself). I wasn't able to re-assign the font material manually (as it was greyed out on the font asset's inspector). I was, however, able to re-assign the source font, but applying that change to the font asset required the clearing "the font asset's character, glyph, and texture data".

While I know its easy enough to re-create the font asset using the font creator tool, or update the font atlas (or reset the font asset) in the inspector window, , this becomes really problematic for Arabic font assets - especially considering that there is so much manual entry of glyph adjustment, mark-to-mark adjustment, and mark-to-base adjustment records that needs to be done before the Arabic text can render correctly with all diacritical marks, and unfortunately all that data doesn't get saved upon re-creating, updating or resetting the font assets.

Please advise. Thanks!

 

Howdy,

@Stephan_B Do you know when importing Glyph Adjustment Pairs will be supported? If it is already supported what version of Unity and/or the TMP package is it supported in?

Thanks,
Shawn

 

We are currently using 2020.3.17f1 and TMP v3.0.6.

 

Hello,
Thank you very much for your work! Is there a version of the editor that can be installed now that has this new feature of importing the position data of diacritical marks please? If not, when do you think will this feature be available please? I'd like to use Unity for a new project that requires diacritical marks on Arabic text. I would just add the data manually but the problem is that I want to add many fonts to my project, so I'd need to add thousands of new records manually.

 

Is there any update on when this will be available? I assume this is locked behind the required changes to the TextCore FontEngine?

 

Hi, I'm also keen to hear an update on this - the lack of GPOS support causes text rendering problems in many Indic scripts (such as Thai - as described in this article: State of Thai in Unity).

 

It looks like the FontEngine changes landed in 2021.3.16f1 based on the changelog. I installed 2021.3.16f1 and TMP 3.2.0-pre.3 and created a new font asset in the Font Creator based on the latest 2.1.5 TTF version of LiberationSans from their GitHub page. However, kerning still doesn't seem to be working correctly for me in TMP. See screenshot below (the "Ty"). Is there any step I missed here? Thanks.



Edit: Nevermind, it seems to work properly in a fresh Unity project. I must have not completely uninstalled the old TMP or something. It's great that this feature went through, thanks!