Ambiera ForumDiscussions, Help and Support. |
|
|
|||||
|
Hi guys! I've got a couple of questions about localization. 1. How can I localize a string for extension. I mean text that appears in menu "Scripted actions" and "Scripted behaviors" in the Properties -> Behavior tab. The properties from any extension is localized perfectly if you write <str name="someprop">Blablabla</str> But what about the description of extension that appears in the menu? Is there any way to do it? 2. Why some strings are not localized, though they are in the xml file? I think it's a bug. I'm not posting full bug report because there are many strings and I'm not yet inspected Coppercube deeply. For example, most combobox buttons not localized though in the xml file they are. |
||||
|
You can translate only those strings that are available in the language file in your Coppercube installation directory. Custom extensions or plugins that you download from the internet should be translated and altered manually by editing the .js file |
||||
|
The fact is that when you change text in description (for example here <behavior jsname="behavior_2DJumpNRun" description="?????? ??????"> )you'll get not readable symbols in Coppercube. Even if you change the charset to cyrillic for .js file, nothing will happened - still another not readable symbols. But if you add property name (for example here <property name="JumpLengthMs" type="int" default="200" />) to <str name="pJumpLengthMs">???????????? ??????</str> in the file coppercube_language_ru.xml, this property show exactly that it should! |
||||
|
I see that the bug is not fixed in version 6.7.1. It may not be entirely clear what was discussed. So, here are the images that will help you understand the problem. |
||||
|
And yet, some localized strings are not shown correct in the Scene Manager, like here: |
||||
|
TpaHc/\uT u3 Hy/\eBbIx, HacTa/\o TBoe BpeM9| |
||||
|
Have you tried other encodings? Windows 1251? |
||||
|
wrote: Have you tried other encodings? Windows 1251? ??-??, ?????????????? ???????? ????... ????. Yes, I've tried this charset. This bugs is exactly with Unicode in source files. |
||||
|
okeoke wrote: TpaHc/\uT u3 Hy/\eBbIx, HacTa/\o TBoe BpeM9| Bce HoBoe – xopowo 3a6blToe cTapoe, BepHo? |
||||
|
Ec, eHg Bu Hug Ty 6u BaH cTen axeg |
||||
|
|
){kind=link}