Localization params auto-translating design flaw
5 years 8 months ago #3195
by Frank
Are you
Give I2L
5 stars!
Are you
Please lets us know how to improve it!
Replied by Frank on topic Localization params auto-translating design flaw
I see your point. That can happen when you are using parameters entered by the player.
v2.8.8a3 now has a bool to set if you want the parameters to localize as well. Otherwise, it just displays the parameter as is.
I also added that flag to the LocalizedString, the LocalizationManager and Localize component.
However, the number of checkboxes in the Localize component was becoming too big, so instead, I added an Options popup where you can select which features to enable/disable for that component.
if you are querying the translation by code, you can use the allowLocalizedParameter:
Hope that helps,
Frank
v2.8.8a3 now has a bool to set if you want the parameters to localize as well. Otherwise, it just displays the parameter as is.
I also added that flag to the LocalizedString, the LocalizationManager and Localize component.
However, the number of checkboxes in the Localize component was becoming too big, so instead, I added an Options popup where you can select which features to enable/disable for that component.
if you are querying the translation by code, you can use the allowLocalizedParameter:
LocalizationManager.ApplyLocalizationParams (ref translation, allowLocalizedParameters:false);Hope that helps,
Frank
Are you
Give I2L
5 stars!
Are you
Please lets us know how to improve it!
To get the betas as soon as they are ready,
check this out
Please Log in or Create an account to join the conversation.
Time to create page: 0.295 seconds