RPG Maker Forums

Closed beta conditions
 
Conditions for every type of beta tester:

• Us English or German if possible.
  If possible you should write German or English in order to communicate with us. You can also write in Spanish but then we need to let it be translated by a third person.
• Be reliable.
  We rely on you finishing the job, simple and easy.

The beta tester types
 
The bug hunter
Yours is the first turn. You need a lot of patience. Your job is to find every single bug, glitch etc. Quite some busy work. It requires you to check every wall, every dialog option and every other such stupid action nobody else would try out. Gamebreakers have highest priority – Tell us about them immediately. Under aggravating circumstances this task can eat a lot of time. Still want the job?
 
The grammar nazi
No, this is no offense, it’s what we need. Your job is to meticulously find every single one of the misspellings or grammatical errors we possibly made. Even phrases that are just utterly wrong. (Except for the few obviously intended ones.) We need the grammar nazi in three editions:

• German
• English
• Spanish

You need to be a native speaker or master of the language you chose to do this job. Obviously.
 
Of course the bug hunter can also report misspellings or grammatical errors and the other way around, but your focus should be on the main task you chose.

The beginning of the closed beta phase is intended for 04/30/2015 until 05/24/2015. If things work out the official release will be on 06/01/2015.
 

Translation conditions
If you want to translate Listen you should fulfil these basic requirements:

• Be a native speaker or master of the target language
  This is very important because Listen contains slang, polite form and occasionalism that should be translated correctly.

• understand english or german
  You should understand german or english in order to communicate with us. This is also required, as the german and english translations are ones we did ourselves.

• be reliable
  We rely on you finishing the job, simple and easy. Ideally, we should be able to ask you any time again in case we need further translations.

• … and have fun to translate

F.A.Q.
 

Question: Can I translate Listen into language X?
Answer: Basically, yes. If Listen isn’t already translated into that language and we don’t have someone. But you should fulfil the basic requirements listed above.

Question: What if I find misspellings or grammatical errors?
Answer: We’d appreciate you correcting these. However, you should put these corrections into a separate file with a note where the error was found, due to intentional misspellings or for example the favouritism of BE over AE.

Question: Shall I start translating right now?
Answer: No. First, you need our permission. With our permission, we send you the files you need to translate. Without these files the translation process would be double the work for either you or for us.

Question: Which program should I use for translating the files?
Answer: You may use any text editor you are used to. However, it is recommended to use an editor that supports Ruby syntax highlighting and Unix line breaks, e.g. Notepad++ or Gedit.
 

Preview: Translationcode

The translationcode looks like this.

:girlsroom => { # Missis Red. :mrs_red => { :adventure => { :EN => %q{\p[0]\n[Girl]\sp[2]Hi Missis Red! I'm going on an adventureoutside! Do you want to join? }, E => %q{\p[0]\n[Mädchen]\sp[2]Hallo, Frau Rot! Ich gehe nach draußen aufein Abenteuer! Willst du mitkommen? }, :ES => %q{\p[0]\n[Niña]\sp[2]¡Hola Señorita Roja! ¡Voy a una aventura afuera!¿Quieres unirte? }, :XX => %q{Your translation here. }, },},For explaination on the syntax read Ruby String Literals and Ugly Horst’s Hermes.

What is this creature that wanders the earth, unseen by everyone?
 

Unseen but sometimes noticed by those who are about to die.
 

He was almost broken when he met a young girl. She can see him! Why?
 

Let's play! Can we make it to the top?
 

Push me! Oh, you know what that means?