Translation problem ( Chinese )

Modding Translation and Localization
41

We’re probably doing something wrong; if you know what it is, please let us know. :slight_smile: We haven’t looked at the localization as much as you have, to be honest. :slight_smile: For example, are we using the localization library right? Is there some setting we should have added to our html? Apologies for being so paged out; our attention is just elsewhere at the moment.

2 Likes
42

I have found some interesting things, see pictures:

10006.png1274×741 222 KB
10007.png866×637 88.6 KB

But!!! It took all the names of the objects into a “wood”.(wood=木头)

So, I see a lot of files again, it is about "{{i18n stonehearth:mutou}}" .
This is a kind of call text code?I am so understand.
i18nIs the code. stonehearth:mutou is Path in the en.json…

So, why not use this code, the path to follow to the xxxx.json(entities)file?

So I have looked at the game files,I found out about, "i18n files and code:

  1. xxx\Stonehearth v0.1.0 r20600\mods\stonehearth\lib\i18n\i18n.luac
  2. xxx\Stonehearth v0.1.0 r20600\mods\stonehearth\ui\root\index.html
  3. xxx:\Stonehearth v0.1.0 r20600\mods\stonehearth\ui\root\js\libs\i18next-1.6.3.js
    10008.png850×529 27 KB

10009.png850×529 26.1 KB

@sdee @RepeatPan @tkh @Wiese2007 @Ponder @Tom I don’t understand the code, but I know these documents are useful, hope someone can change the problem.I hope very much radiation team can make changes, whether Chinese needs, such as Japanese language also need

43

This would require mods to mixinto the locales/en.json… which, while technically possible I guess, seems a bit… eh.

I mean, it could work, right. Instead of a name, you just give it the entity ref/an unique name and that is then thrown into the i18n…

It’s really just not there yet. You can’t translate the game yet.

44

Right. Not just the only name,I want to can start study from i18n.

45

like i know ln18 can only be used in htmlfiles - and sry to kill your hopes - the most of use already know that they use ln18 for name relink ^^

46

I think of a stupid way, add the statement, if is XXX, it shows what?All the name added.

47

why should that a stupid way thats the normal way statement ln18 xxx -> en.json xxx = xxx … thats the normal code^^ but its works only for htmlfiles and not json or luac

48

i18n (internationalisation, “nternationalisatio” is 18 characters long) is merely the term for localizing stuff. It’s not a library or a fixed process.

Honestly, Radiant is still working on that. Sure, we could go ahead and make entity translations working right now, but I would advise against it. I do have some experience with translating stuff (from a software provider point of view) and let me tell you: It’s an awful lot of work to get it right. Sure, we could modify systems here and there and have it nicely going for entities too, but you would end up overriding and monkey patching a rather large chunk of the code… Not to mention that you need fallbacks.

2 Likes
49

Because of this i have already said… Just wait it still alpha :wink: i have my Translation and some Tester and when they have finished the development they can use it if they want… Until then i have my workpart and some statisfied Players and letsplayer who Show the game to the german Folks - so that we get a bigger community :wink: