Trouble with using global parameters
7 years 5 months ago #1872
by Frank
Are you
Give I2L
5 stars!
Are you
Please lets us know how to improve it!
Replied by Frank on topic Trouble with using global parameters
Hi,
Things to check:
- If you added a copy of the GlobalParametersExample.cs to an object, verify that the object is enabled.
- The parameters are not called, if there the localization is not found: Can you verify that the localization is been set.
e.g. If you have the term PARAM_EXAMPLE and english is "Age: {[CHAR_AGE]}" and spanish is "Edad: {[CHAR_AGE]}", check that switching languages also changes the text.
- If you use LocalParameters, then that script needs to be in the GameObject with the Localize component.
Can you post or send me the modified script you are using, maybe I can spot something from there!
Things to check:
- If you added a copy of the GlobalParametersExample.cs to an object, verify that the object is enabled.
- The parameters are not called, if there the localization is not found: Can you verify that the localization is been set.
e.g. If you have the term PARAM_EXAMPLE and english is "Age: {[CHAR_AGE]}" and spanish is "Edad: {[CHAR_AGE]}", check that switching languages also changes the text.
- If you use LocalParameters, then that script needs to be in the GameObject with the Localize component.
Can you post or send me the modified script you are using, maybe I can spot something from there!
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.
7 years 5 months ago #1878
by Frank
Are you Give I2L
5 stars!
Are you Please lets us know how to improve it!
Replied by Frank on topic Trouble with using global parameters
Ahhh, that makes sense now.
The issue is that ScriptLocalization.Get(xxx) doesn't add the parameters. Instead, you have to call LocalizationManager.ApplyLocalizationParams after the .Get call.
that was done to allow the possibility of doing your own parsing before the parameters were added (it is used in the Localize component, to allow the LocalizationCallback to run before the parameters).
Nonetheless, I agree, its not too intuitive. So, I will enable the parameters when you call ScriptLocalization.Get, and have an extra parameter that could be set to false to avoid having the parameters applied! I think that will make more sense.
While I add that, you can call the ApplyLocalizationParams directly and it will work!
Hope that helps,
Frank
The issue is that ScriptLocalization.Get(xxx) doesn't add the parameters. Instead, you have to call LocalizationManager.ApplyLocalizationParams after the .Get call.
string text =I2.Loc.ScriptLocalization.Get("AgeText")
LocalizationManager.ApplyLocalizationParams (ref text, null);
pugDetails.text = text;that was done to allow the possibility of doing your own parsing before the parameters were added (it is used in the Localize component, to allow the LocalizationCallback to run before the parameters).
Nonetheless, I agree, its not too intuitive. So, I will enable the parameters when you call ScriptLocalization.Get, and have an extra parameter that could be set to false to avoid having the parameters applied! I think that will make more sense.
While I add that, you can call the ApplyLocalizationParams directly and it will work!
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.185 seconds