Long Text not Spaced
7 years 2 months ago #2485
by CK247
Long Text not Spaced was created by CK247
Hi Frank,
There is a problem with the Chinese(Traditional), Chinese(Simplified), and Japanese translations. When these three languages are translated, They become long and not spaced which makes it very difficult to read. This does not happen in any of the other languages except these three. In the attachment named In English, you will see the original text nicely spaced and adjusted.
However, the text is squished into one long line instead of the multiple lines.
This problem is resolved when I manually space every character in that text out.
Also how do I export the current translations that I have and import them back to them use them as local spreadsheet instead of live Google translations?
There is a problem with the Chinese(Traditional), Chinese(Simplified), and Japanese translations. When these three languages are translated, They become long and not spaced which makes it very difficult to read. This does not happen in any of the other languages except these three. In the attachment named In English, you will see the original text nicely spaced and adjusted.
However, the text is squished into one long line instead of the multiple lines.
This problem is resolved when I manually space every character in that text out.
Also how do I export the current translations that I have and import them back to them use them as local spreadsheet instead of live Google translations?
Please Log in or Create an account to join the conversation.
7 years 2 months ago #2491
by Frank
Are you
Give I2L
5 stars!
Are you
Please lets us know how to improve it!
Replied by Frank on topic Long Text not Spaced
Hi,
Some languages like Chinese, Japanese and Thai, don't add spaces between words. That's why the translations show all characters together.
Most UI systems (like Unity UI) process this fine and wrap those characters even when they don't have spaces. But I'm guessing some other targets may not be doing that correctly.
To bypass this problem, I just added a checkbox that allows adding spaces to those languages (this can be set per-label in order to avoid it when the text is small). That should allow you to wrap the text in any target that doesn't do the wrapping correctly.
If you download v2.8.0f2 from the beta folder, you will see the checkbox in the Localize component. If you enable it, the characters will be separated.
Hope that helps,
Frank
Some languages like Chinese, Japanese and Thai, don't add spaces between words. That's why the translations show all characters together.
Most UI systems (like Unity UI) process this fine and wrap those characters even when they don't have spaces. But I'm guessing some other targets may not be doing that correctly.
To bypass this problem, I just added a checkbox that allows adding spaces to those languages (this can be set per-label in order to avoid it when the text is small). That should allow you to wrap the text in any target that doesn't do the wrapping correctly.
If you download v2.8.0f2 from the beta folder, you will see the checkbox in the Localize component. If you enable it, the characters will be separated.
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.
7 years 2 months ago #2492
by CK247
Replied by CK247 on topic Long Text not Spaced
Hi, Frank
I don't know if I did this wrong but I did not know where to find the beta folder so I went to the asset store and updated the I2 program. It was able to update but it came up with this error after the update:
In the console:
In the script:
I think I fixed the error, which was coming from the "GetTermTranslation" to just "GetTranslation" and it worked fine with no error.
I am not sure if this is the right way to do it but I hope that fixed it. Also I do not see the "Separate Words" check box on the inspector:
I am not sure if using unity asset store to update it was the right way.
I don't know if I did this wrong but I did not know where to find the beta folder so I went to the asset store and updated the I2 program. It was able to update but it came up with this error after the update:
In the console:
In the script:
I think I fixed the error, which was coming from the "GetTermTranslation" to just "GetTranslation" and it worked fine with no error.
I am not sure if this is the right way to do it but I hope that fixed it. Also I do not see the "Separate Words" check box on the inspector:
I am not sure if using unity asset store to update it was the right way.
Please Log in or Create an account to join the conversation.
7 years 2 months ago #2493
by Frank
Are you Give I2L
5 stars!
Are you Please lets us know how to improve it!
Replied by Frank on topic Long Text not Spaced
Hi,
Version 2.8.0f2 is not yet in the assetstore, I'm planning in releasing it on Monday, but it will take a few days for the AssetStore team to approve it.
Said that, you can download it right away, by accessing the beta folder, here is how:
inter-illusion.com/forum/i2-localization...ssing-early-versions
Yes, the latest version, renamed that function to make it more consistent, and simply the optional parameters.
Renaming the function as you did will fix the problem. The other solution is to delete ScriptLocalization.cs, that file is auto-generated and the next time you use the Bake Terms Tool, it will be generated with the correct methods. Nonetheless, if you are not using baked terms, then deleting ScriptLocalization.cs will not affect anything else.
Hope that helps,
Frank
I did not know where to find the beta folder so I went to the asset store and updated the I2 program
Version 2.8.0f2 is not yet in the assetstore, I'm planning in releasing it on Monday, but it will take a few days for the AssetStore team to approve it.
Said that, you can download it right away, by accessing the beta folder, here is how:
inter-illusion.com/forum/i2-localization...ssing-early-versions
It was able to update but it came up with this error after the update
Yes, the latest version, renamed that function to make it more consistent, and simply the optional parameters.
Renaming the function as you did will fix the problem. The other solution is to delete ScriptLocalization.cs, that file is auto-generated and the next time you use the Bake Terms Tool, it will be generated with the correct methods. Nonetheless, if you are not using baked terms, then deleting ScriptLocalization.cs will not affect anything else.
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.425 seconds