Open c3-hoge-fuga-piyo opened 1 year ago
Can someone confirm that the various platforms support all the different possible scripts for the name? Like Chinese characters? Otherwise there's a risk of the game running on a language that results in a window with garbled text of the title
Can someone confirm that the various platforms support all the different possible scripts for the name? Like Chinese characters? Otherwise there's a risk of the game running on a language that results in a window with garbled text of the title
This should pretty much always work as the window title is drawn using the system font, which has a pretty extensive set of fallbacks available for various scripts. The only case where it may fail is with applications that don't have proper Unicode handling, but Godot sure does :slightly_smiling_face:
Describe the project you are working on
Various 2D games.
Describe the problem or limitation you are having in your project
While working on settings for localization, I noticed that the game window's title is always set to
application/config/name
, regardless of the contents ofapplication/config/name_localized
.Upon examining the relevant implementation, I found that
TranslationServer::translate
is being executed forapplication/config/name
. However,TranslationServer
does not take into account the contents ofapplication/config/name_localized
, resulting in it not being properly translated.Describe the feature / enhancement and how it helps to overcome the problem or limitation
Currently, it's redundant to have to add the same content in both
application/config/name_localized
and the regular localization settings.Moreover, it would become possible to obtain the localized game title through the TranslationServer from
application/config/name
.Describe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams
Based on the current implementation, it would become possible to obtain the locale-appropriate contents of
application/config/name_localized
by usingTranslationServer.translate(ProjectSettings.get_settings("application/config/name"))
.If this enhancement will not be used often, can it be worked around with a few lines of script?
Is there a reason why this should be core and not an add-on in the asset library?
It seems that localization is considered in the implementation, so it might not be a feature omission but an unintended bug.