Essay on the Importance of Text Table (StringTable)

As an aside: Why is the localization item of text not edited together with the other resource localization items? This increases the cost of learning and reduces the ease of use.

Reason one: Text localization items tend to be much more numerous than other types. If you had all the text localization items edited in a long list GUI, imagine that finding the right place to insert a localization item would be a headache, even if you added a search function to help. There are also performance issues that can be large enough to cause GUI stutters.

Reason two: the text often needs to be divided into functional modules or chapters, divided into tasks, such as deleting a previously designed plot task, if the text is not stored separately, but stored in a large list, it will become very difficult to delete, if not deleted, it may lead to too much useless text, but also increase the translation cost.

Reason three: When the localization component needs to associate localization items, click the name of the localization item field, open the drop-down list, to select a field you want, if the drop-down list is not optimized, the drop-down list of options will be almost impossible to operate.

Reason four: Text localization items need to be translated, while others often do not; Text localization items may require associated speech, while others usually do not, so you need to design separate GUI controls for text localization items.

The above reasons are also there are ways to solve, but separate design ideas can make the whole system management much easier, if it is you, how to choose?