Then the Level 2 translation can be integrated/released incrementally/iteratively (we can start with a useful set of things, and keep adding/refinining).

In general, will partial translations be integrated or does it have to be completely finished before it is released?

The other flags are in the same dir.

To see the flags in the app, activate the Mathworld window by clicking on it, then click on the Options menu (in the Mathworld window menubar). You will see a flag next to the Language menu.

For the short term though, I think the native word followed by the English in parentheses is an okay choice.

Lets move forward with this thought.

Perhaps an idea would be to use recognizable icons along with the native words, e.g. flags and have the currently selected flag shown in the menu bar itself so you wouldn't have to know the word for "language" in the currently selected language.

You're talking about the top level 'Language' menu here, right. If so, this is a good point (I always find myself hunting for the Language menu item when I'm in a different Language). The embedded GeoGebra does something similar, so all the flags are already available in Kojo!

From an earlier post by me on this thread:

The word 'Language' should be localised.

It already is (and hence the potential usefulness of a flag in the menu).

For the short term though, I think the native word followed by the English in parentheses is an okay choice.

English is not as universal for children as it is for adults, which is why I am translating the app in first place.

Greetings from Sverige ;)

If a user doesn't understand हिन्दी then they probably shouldn't select that menu item :-)

That sounds like a good thing to not do ;). But the idea I'm working with is that - instead of the language names being potentially incomprehensible, you get a bit of a help in figuring out what languages are supported (maybe this will make someone look up a Kojo meetup in a new country that they are visiting!!).

Every language name translated into every other language seems like a bit of a combinatorial nightmare. I suggested English because that seems to be a reasonable common ground in our world today (it has allowed me to converse quite effectively with the Swedish, French, and Polish contributors to Kojo, and is letting me converse quite nicely with you).

In any case, I'll ask the other Kojo Language contributors to take a look at this thread and provide any opinions that they might have in this area.

is that true?

That's true.

Shouldn't it be?

It'll be good if it is.

Wanna do the honors while you're working in the area?

My thoughts on how this should work (the embedded GeoGebra works in a similar fashion):

• The word 'Language' should be localised.
• But the actual language strings should remain the same across languages. So, for example, Swedish should always be Svenska. We could have something like Svenska (Swedish) to provide something familiar for languages that have a different alphabet/script (e.g हिन्दी (Hindi)).

Is there anyone working on translating Kojo into Dutch?

Nope.

I would like to contribute to a translation.

Great!

Here's some info to get you started. In the current scheme of things, there are two levels of translation:

• Level 1 (UI translation) — the following file needs to be translated:

http://code.google.com/p/kojolite/source/browse/src/main/resources/net/kogics/kojo/lite/Bundle.properties

• Level 2 (translation to enable (beginner level) programming in Dutch) — the following two files need to be translated (I'm pointing to the Swedish files for reference):

http://code.google.com/p/kojolite/source/browse/src/main/scala/net/kogics/kojo/lite/i18n/svInit.scala
http://code.google.com/p/kojolite/source/browse/src/main/resources/i18n/initk/sv.tw.kojo

The above file links are for files in the google-code repo. The corresponding files on Bitbucket can be viewed here: https://bitbucket.org/lalit_pant/kojo/src

Please feel free to ask questions as you go along…

Cheers,
- Lalit