FreeGameDev

It's always a joy seeing a code freeze being called. It means we're close to a release.

There's two translations I need help with.
"Desert Point" - Do you mean a specific place in the desert, a dot in a desert or a switch in a rail-road track in the desert?
"Xue" - Do you mean the chinese character? Or the old name for Shandong? Or one of the famous called Xue?

Karts name should not be translated

Ah! So Xue is the name of a kart... I didn't know that.

asciimonster {l Wrote}:"Xue" - Do you mean the chinese character? Or the old name for Shandong? Or one of the famous called Xue?

I think it's the name of the Xfce mouse.

asciimonster {l Wrote}:"Desert Point" - Do you mean a specific place in the desert, a dot in a desert or a switch in a rail-road track in the desert?

I don't know, I assume it just means "Desert Track".

It's the name of the Xfce mouse in SuperTuxKart, as it seems Xfce folks weren't that interested in giving it a proper name...but did someone actually ask on their forums/ML?

"Desert Point" actually, I have no idea where this string comes from :/ will need to investigate. For now you don't need to come up with a translation, I'm pretty sure it's unused

Talking about translations: I plan to update the German translation asap.

Edit:
Talking about string freeze: There are untranslatable strings in the game: “Anisotropic”, “Bilinear” and “Trilinear”. Those words appear next to the “Texture filtering” setting in the extended graphics settings menu. Too bad the strings are frozen now.

Just an idea: Maybe we could have a string freeze heads-up the next time, so anybody who notices issues with the strings can report them. This way, the devs would have a chance to fix them before the freeze

By the way: How do you pronounce “Xue”?

And where does that name come from? Did someone ask the people from Xfce how they would like to call their mouse?

We asked on their IRC channel and they all went "meh, we don't have any name, and we don't care". And then we all went Chinese on the name.

Auria {l Wrote}:"Desert Point" actually, I have no idea where this string comes from :/ will need to investigate. For now you don't need to come up with a translation, I'm pretty sure it's unused

It said that it comes from "tracks/dp.xml" or so I don't know if it's a track or battle arena...

Need update translation on the launchpad.net (supertuxkart.pot)
because some strings in game shows on English only.

dimproject {l Wrote}:Need update translation on the launchpad.net (supertuxkart.pot)
because some strings in game shows on English only.

can you please specify which ones? that would help us

Hi,

first of all, the 'Desert Point' string was my mistake. I had somebody's test track installed, forgot to remove it, and then our script picked up the name

GunChleoc {l Wrote}:Just an idea: Maybe we could have a string freeze heads-up the next time, so anybody who notices issues with the strings can report them. This way, the devs would have a chance to fix them
before the freeze

I totally agree with that. Our main problem is that we are not sure how to contact translators, and also I didn't want to annoy people with too many emails (announcing upcoming string freeze, then string freez, then RC, ...)

We have a special stk-translation email list, but only a few people have subscribed. Afaik launchpad does not offer an option to contact all translators. What would be your suggested solution?

Anyway, because of the various problems noticed, we will update the translation file in the near future.

So for now, please keep your valuable feedback up - anything noticed now can still be fixed

Thanks a lot!
Joerg

I using translation from launchpad.net
(this translation full, with game translation not full).
I found some strings shows on English only.

dimproject:
you're using an outdated SuperTuxKart version, now these state screens look different. So some strings are eliminated and some are added. Please don't make our devs more work
However, I agree with others, it'd be a good idea to update translations in trunk sooner or later to watch them ingame.

dimproject, please follow the instructions described at : http://supertuxkart.sourceforge.net/Translating_STK

the translation process is fully automated and should require no intervention from us, or uploading files on forums

What is doing old translations in developing version?

dimproject {l Wrote}:What is doing old translations in developing version?

I'm sorry, I don't understand

GunChleoc {l Wrote}:Just an idea: Maybe we could have a string freeze heads-up the next time, so anybody who notices issues with the strings can report them. This way, the devs would have a chance to fix them before the freeze

I've added this to our release procedure. From the next release on we will contact all translators before declaring the official string freeze, in order to avoid the problems we have seen this time.

Thanks a lot!
Joerg

As a localizer, I don't remember if i'm signed up to the stk translation list, but I am signed up to some list where I got the string freeze notification per e-mail. The best thing you can do is announce on the list and on the forums I think. Also, you could suggest people sign up to the mailing list on this page: http://supertuxkart.sourceforge.net/Translating_STK

It would also be good to have current builds out to test translations with when you announce an upcoming string freeze, since many localizers are not programmers and unable to create builds from source.

GunChleoc {l Wrote}:As a localizer, I don't remember if i'm signed up to the stk translation list, but I am signed up to some list where I got the string freeze notification per e-mail. The best thing you can do is announce on the list and on the forums I think. Also, you could suggest people sign up to the mailing list on this page: http://supertuxkart.sourceforge.net/Translating_STK

It would also be good to have current builds out to test translations with when you announce an upcoming string freeze, since many localizers are not programmers and unable to create builds from source.

Good point, though it usually takes us a few days to get all binaries sorted out, so doing this once more isn't really helpful for us On the other hand, we always put translations into the final release after the RC is out. So we could just do a single (perhaps windows only??) 'beta' release, so that someone can check all strings and tell us anything that needs to be fixed, then the RC could be used to finish all translations. Or perhaps someone figures out a build system to automatically create builds for linux, osx, and windows

I've also added the link to the email list to our translation page.

Thanks a lot!
Joerg