【ZeloEngine】 Localization process /ImGui Chinese culture

Conclusion

Chinese culture and icon The pit of （2021/12/19 Open pit ）

1. ImGui Culture in the editor interface
2. A fully automated translation process that can translate what you see
3. 【 pit 】 Chinese character set range
4. 【 pit 】icon font and id Mechanism
5. 【 pit 】 Shielded node

Localization process

First, a version of the standard process was made v1, Then do some optimization v2

v1 Localization process

【ZeloEngine】 Localization process /ImGui Chinese culture _ Bili, Bili _bilibili

v1 The standard process is ：

1. I open the game , notice “Open all” It's English , No translation
2. I'll search the code "Open all", Find the string , use gettext Function package , Convert to Chinese
3. Go to .pot add to "Open all", Then translate .po
4. Chinese is displayed in the game

v2 Localization process

Q： What is localization ？
A： All text that users can see should be in Chinese

So we can monitor ImGui All text parameters that will be displayed in the , stay ImGui Implement the package gettext, And output all the problems encountered in the runtime / See the text , Automatically update the translation template file .pot

Directly modifying imgui.cpp The risk is still too great ,imgui It's still being updated

Good thing we have Lua Script binding layer , It is a layer of encapsulation , And all imgui Logic is all about Lua Written , Just change it here

v2 The process is ：

1. I open the game , notice "Open all"
2. Close the game , Automatically refresh .pot, newly added "Open all"
3. translate .po
4. Chinese is displayed in the game

The optimization is gone

• Observe which text has not been translated
• Search the code key Change code
• stay .pot Add in key

pit

A vision of complete automation , Will often be a variety of corner case break , Turn automation into a black box for handling all kinds of strange situations

v1 The standard process is not completely bad , Implement a simple , No, BUG, Completely controllable

Chinese character set range

GetGlyphRangesChineseSimplifiedCommon is misleading · Issue #2882 · ocornut/imgui

imgui Two ranges in Common and Full All have problems

1. Common Too small , Many words are garbled
2. Full Too big , Measured additional consumption 300MB Memory

issue The one in , Actually measured 100MB, There is no garbled code , Use it first

label ID & icon font

Direct use ImGui The interface of gettext The problem is ,imgui It's similar my_name##1 Of ID Mechanism

icon font It's a good thing , General icon The method is small pictures ,icon font It's a icon Painted as a character , similar emoji

But a string has icon It's very troublesome. , Need to do a simple parse, Identify beginning icon And the ending id, Cut out the text , Spell it back after translation

"%icon% my name ##1"
=> "%icon%" gettext("my name") "##1"