23386 Posts in 3989 Topics - by 8545 Members - Latest Member: Loki98

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Martin

Pages: [1]
Suggestions / Re: Test Server Problem Notifier
« on: November 28, 2017, 01:55:46 PM »

Thanks for your suggestions.
I just fixed a bug concerning the automatic update of the test server, hopefully that should work now.

The automatic reboot now also has a 'stuck' detection, which (hopefully) should take care of crashes that don't end the executable.

We do read the forums, so at the moment, the forums is the way to go.

Translations / Re: Question to the Developers
« on: August 25, 2017, 12:38:42 PM »
Well, thanks for reporting. I'll look into that.

Translations / Re: Question to the Developers
« on: July 31, 2017, 03:11:56 PM »
Well, theoretically it should work. Although the "%_t" tag was never intended for dynamic strings, it was made as an attachment to static strings. (like "Hello"%_t, not as an attachment to a variable)
But, I mean, if it works, it works.

Could the problem with your code be that %_t has more priority than the ".." operator?
Meaning, your code implicitely gets evaluated like this?
Code: [Select]
dirString = dir.name .. (" /*direction*/"%_t )
The call to the translation engine would try to translate " /*direction*/", resulting in an empty string, then attach it to dir.name, which, in total, gives the untranslated dir.name?

But, to answer your original question:
The %_t is like a function call the string gets put into. The %_t function then tries to find a translation to the string. If none found, it strips the comment, if existing, and returns the untranslated string.

The comment is important for differenciating between identical strings with different meanings. (In your specific case, W - West and W - Watt)

Also, a string without the %_t should not get translated at all. Do you have a working minimal example to reproduce that behaviour?


It's really hard to replicate your bug, and being able to replicate it is essential for us to fix it.
If you know how to cause it, would you mind sharing something that allows us to (easily!) replicate the problem?
Examples: Problem with minimal amount of blocks necessary to replicate it, upload to steam workshop, images what exactly to do, etc.



Thanks for your question. I guess you are talking about the 'Warning: Lengths of source and translation differ too much.'?
That is a general warning system, that tries to direct the attention of the language admins towards potentially faulty strings.
This is, however, not an error, but rather a warning, and can be accepted anyway.

We will appoint language admins once we have enough translation suggestions for the respective language.

What do you mean with MODEing the steam workshop?

Translations / Re: German language?
« on: June 16, 2017, 03:16:36 PM »

Thank you very much for your offer, but we officially support German and English, and are therefore forced to always keep German and English updated (steam policy).
That means, we can't wait for a community translation, and we are doing the german translation ourselves (as our entire dev-team is german).


News / Avorion Community Translations
« on: June 13, 2017, 03:41:28 PM »
Ever since we first released Avorion, we noticed both the wish and active attempts to translate Avorion into other languages. We think that translations are an essential feature, and after getting lots and lots of propositions for community translations we're now giving you the tools to help in the process.
We decided to do community translations since Avorion is under very active development and texts are constantly changing. This way we can provide a way for the translations to adapt to the current state of the game.
So we launched https://translate.avorion.net, an official community translation hub, where everybody can contribute to translate Avorion to various different languages.

To make things easier for inexperienced people, we also wrote a quick guide where we briefly discuss the pitfalls and problems to consider while translating:

If your language isn't available and you want to translate it, please send us a quick mail at translate@avorion.net.

We also know that there are a few finished translations already around, so if you want your translation to be added to the database, send us a quick mail to translate@avorion.net with your .po file so we can add it to the database.

Thank you all for reading and thank you very much if you decide to help translating Avorion!

Pages: [1]