1 (edited by kneekoo 2011-04-03 01:50:45)

Topic: Romanian translation

Hello! I translated Teeworlds in Romanian. Please note that the link to the translation points to PHP-Fusion Romania - the community I own -, where I can easily update it while the links stays the same. I actually translated it because we plan an "online meeting" in Teeworlds somtimes soon. lol

Details about the translation
Last update on: 2011-Apr-03
Tested on this package: teeworlds-b72-r5beae410-linux_x86.tar.gz
The language file is here.
The language name is Română

I reported the tiny issues I discovered in this post.

2

Re: Romanian translation

Thanks a lot kneekoo

Antoine de Saint Exupéry: It seems that perfection is reached not when there is nothing left to add, but when there is nothing left to take away.
Besides -  I am the gfx guy!

3

Re: Romanian translation

Thank you too for your work. smile  When can we expect the translation to slip in the main package? Are there plans for server-side messages translations? That would be great. smile

4

Re: Romanian translation

Translation of server-side messages is not planned as far as I know. There was the suggestion to do this on github, but Oy had some arguments against it, I don't remember them however. Oy's final result was that this won't be done, at least not for the 0.6 release.

Your translation will probably be included, as soon as someone makes a pull request for it on github wink. You can create your own github account and fork teeworlds from oy and create the pull request yourself, if you want.

5

Re: Romanian translation

Fortunately the localization is now considerably easier after all the work involve in translating the user interface. I'm not just saying this off the top of my head. I read some of the source code files and I noticed how it's done. I hope the developers will make this effort --at least-- for the messages that get displayed in the UI while playing.

6

Re: Romanian translation

There was the suggestion to use "status codes" for the server-side messages, which should be sent to the client. The client could then use use the text message, which corresponds to that status code. Localisation would be very easy in that case, and also we maybe could save a bit of bandwidth, as not the whole text would need to be sent. However, this would require the add of status codes, every time we include a new server side message. I believe this was also the on reason why Oy did not like that method.

7 (edited by kneekoo 2011-01-11 10:02:03)

Re: Romanian translation

Well... it's not like there are a plethora of server-side message types so adding new IDs every once in a while is not too different than adding new locale - that's why it's still worth considering the idea. Yes, it could save some bandwidth. I'm just not sure how much considering I don't have too much of an experience with Teeworlds' logs.

What would be nice though, is explaining the logging format. That way I could help with a log analyzer - being a developer myself. I just don't know the meaning of all the entries so I'm in the dark on this one.

8 (edited by kneekoo 2011-01-13 14:08:51)

Re: Romanian translation

I noticed my translation made it in the latest source build. I also noticed there was a string that needed to be translated, which I did and I updated my translation package. The link is the same as mentioned in my first post, which I just updated with the latest information. Thank you for integrating it so soon! smile

9 (edited by kneekoo 2011-02-02 17:54:08)

Re: Romanian translation

I just updated 3 strings in my translation - 2 untranslated, 1 fixed. My first post is updated accordingly.

10

Re: Romanian translation

Thanks a lot for your efforts! smile

Antoine de Saint Exupéry: It seems that perfection is reached not when there is nothing left to add, but when there is nothing left to take away.
Besides -  I am the gfx guy!

11

Re: Romanian translation

Thank you too for your continued work! smile

P.S. It would be nice if we would have a newsletter to automatically send news to translators when strings get added/changed/removed so we can quickly update our strings. smile An online translation log could help as well: date + changes.

12

Re: Romanian translation

The translation is now updated according to the latest 0.6 trunk and tested in Linux. If anyone can enlighten me how "Netversion" should be translated, I'd be grateful. Where does that word get displayed? At least I can translate it from its context.

13

Re: Romanian translation

It's the version of the netcode. It's "0.6 <hash>" currently. (Since the network code is still subject to change the hash varies.)

14 (edited by choupom 2011-04-03 10:39:36)

Re: Romanian translation

The "Netversion:" string is displayed in the demo details.

15

Re: Romanian translation

Good. The translation is now updated accordingly. Please note I kept the same link, available in my opening post.

Thanks again for your effort, guys! smile