i18n support about learngitbranching

[pcottle]

I'd totally be willing to add i18n support -- almost all the dialogs and text use string lookup so it wouldn't be impossible. The translations might have to be sourced by the community though

Glad you like the app!!

[bcho]

umm, just have a look on the code. Most dialogs are under src/level and some error messages in src/js, right? Can you show me how to implement the i18n support? (I mean where to store the translated message, how to use the lookup function.) Maybe I can translate it into Chinese sometimes later.

[pcottle]

There's two main types of text around the site -- dialogs within some level or sandbox and small things like button names and headers.

The button names might be hard to change because they are part of the HTML template -- we would need to tokenize all their locations and then pass in the translated strings. It would be somewhat laborious but not horrible

The dialogs, however, could be fairly easy to translate. All the dialogs are located in either src/levels/<level type>/<level name>.js or src/js/dialogs/<dialog>.js Right now they are simply a part of a JSON structure, like

{
   levelName: "rebasing",
   solution: "git commit",
   startDialog: [{
        type: 'ModalAlert',
        options: {
             markdown: "Hello!!!"
         }
   }]
}

To add i18n support, we just make this structure one level deeper:

{
   levelName: "rebasing",
   solution: "git commit",
   startDialog: {
     english: [{
          type: 'ModalAlert',
          options: {
               markdown: "Hello!!!"
           }
     }],
     spanish: [{
          // same
             markdown: "Hola!"
      ]}
   }
}

Obviously we would use locale codes instead of spanish but you get the drift.

Then you just change all the caller locations and drop in new translations!

[bcho]

What does the same in spanish mean? Does it also need type and options attributes?

OK, I will translate the dialogs first. Thanks for your help :)

[pcottle]

Yeah // same just means it will have the same exact structure except for the actual content. I was tired of typing JSON by hand but maybe I should have carried it out.

Awesome! Really cool to have a translator on board, that's a really cool step the project can take. Let me know when you're halfway-ish done with translating a few (ping me at [email protected] ) and I'll begin the intl support

[outsideris]

Should I also ping you via email if I translate to another language?

[pcottle]

@outsideris Sure! Once any given translation gets near completion I'll race to add the i18n support. After the first one or two though, I can just manage the discussion on github. Having an email ping was simply to help prioritize issues / features

[outsideris]

@pcottle Thanks....