Hello.
I tried the e-ukraine font files you put in your Dropbox. I was able to open them on my pc. Thank you so much.

I understand your desire to use these fonts in EsoUA.
So I would like to explain how the fonts are handled in ESOUI.

In my earlier comment on esoui font faces, I mentioned fontstrings, which defines where the font files are located.

For example, MEDIUM_FONT is a special string constant whose value is "EsoUI/Common/Fonts/Univers57.otf".
To refer to the value of MEDIUM_FONT, write code like $(MEDIUM_FONT).

In ESOUI, many font objects are defined in the following files in the form of referencing fontstrings.
- keyboard font
- gamepad font
These font objects may be changed or added or deleted with each future version of ESO.


I am not familiar with unofficial language mods.
However, the following threads should be a technical reference for anyone who creates an unofficial language mod that includes their own fonts.
I believe the thread is a discussion of the development process of the RuESO add-on. Please read it over and over to understand.

By perusing the thread, you will generally understand the following current status regarding the method of replacing fonts with custom fonts.
(1) It would be extremely easy to work with if we could replace the fontstrings values with our own font file paths. But there is no way to do that.
(2) For glyphs that are not included in the font file specified by fontstrings, we can specify a fallback font by defining a backup font file. However, glyphs included in the font file will not be replaced, of course.
(3) There is a method to override the value of the font object.
For this, you can find the footprints at the beginning of ru_client.str of RuESO v24.1 in the days of unofficial language mod.
For example, you can create the following statement for all ZoFont**** and add it to ua_client.str.
Unfortunately, this is not enough.
(4) It is known that in ESOUI's vanilla code, font object names are not always used when specifying fonts. For example, in tooltipstyles.lua, there are places where fontstrings is referenced. You would have to replace the value of fontstrings with your own font file name for all the places where fontstrings is referenced, because you cannot replace the value of fontstrings. This will be tough work.


I am only here to ask you a technical question to update the LibMediaProvider add-on. My business is done.
I do not know if the content of this comment is helpful to you.
I wish you the best of luck with your add-on.

- Calamath

I confess that I tried to load those custom font glyphs in Windows 10 using a tool named FontBase, but it could not load them. So I am questioning if they are valid font files.

Then I think it seems that the code you pasted has no chance of having any effect because the file path to the font file is wrong.


BTW, you can see here the font linking for the font faces used in ESO.
From this, it appears that the glyphs of the Ukrainian alphabet are in the fallback font.
To give you a hint, I recently discovered that only ANTIQUE_FONT does not contain some of the Cyrillic glyphs for Ukrainian.

So, could you please paste here an example of one of the Ukrainian strings you say is not displayed correctly?
Thank you.

- Calamath

Hi, I just wanted to confirm a few things.

EsoUA includes custom fonts to support Ukrainian.
But according to my recent research, it seems that some of the Cyrillic fonts included in ESO contain glyphs specific to the Ukrainian alphabet. The following glyphs.

ҐґЄєІіЇї

Do you use any special techniques to support Ukrainian, such as code shifting of strings as done in EsoKR?
Or for visual design reasons?

- Calamath

Thank you Sharlikran!

I can answer this. So the official two letter designation is UA for the language. If you want to support the Ukrainian language just add that.

The reason for the UT files are for the translators only. When you see {{39619172-0-9428:}}Drink when using the UT files that is from ut.lang and it is from the 900,000+ lines of game strings. Which covers quest text from the NPCs, zone names, quest names, and much more. If you see {C:5493}Назва that is from the file ut_client.str and {P:613}Грати if from ut_pregame.str.

UT is simply a mode for translating. Users would not use that for normal play. It is not a compatibility mode for fonts.

Korean uses KR for the language and KB for the tags files. Same concept, KB is only for translators and KR is for normal play that users would use. C = Client and P = Pregame.

Basically once the game switches to UA using SetCVar("language.2", "ua") then the game looks for various files. The three files the mod uses are, ua.lang, ua_client.str, and ua_pregame.str.

Okay, forgive me, I'm new to this kind of strings but I'm interested into it:
What does "{C:5493}Назва" mean or do with the text compared to "Назва" so that you need 2 files for the texts?
Is it some kind of compatibility mode for fonts?

Hello, I maintain the LibMediaProvider add-on.
I'm happy to inform you that LibMediaProvider will support EsoUA in future versions because listed as an unofficial language mode in the custom language section of the ESOUI Wiki.

- Calamath

So what is the tag to use ingame via e.g. /script SetCVar("language.2", <tag here>) ?
Is it ua or ut?

What is the difference between ua and ut?