Playmaker Forum
PlayMaker News => PlayMaker Announcements => Topic started by: Alex Chouls on November 16, 2012, 08:27:22 PM
-
In 1.5.0 we've started translating the Playmaker editor into other languages.
I think we'll get the best translations from Playmaker users who actually use the software, so we're using an online service that lets users pitch in and offer translations.
Progress so far:
Chinese Simplified: 100%
Chinese Traditional: 100%
Japanese: 100%
French: 100%
Portuguese Brazilian: 80%
Dutch: 43%
German: 100%
Spanish: 100%
Swedish: 39%
And a bunch of languages at 0%
If you're a bilingual Playmaker user, who can help translate Playmaker into another language, we want to hear from you! Please contact us at info@hutonggames.com
Thanks!
Alex
-
Hi,
Just to point out that I am currently translating French, but I could do with a hand on corrections and suggestions as I am the first to admit I am really bad at grammar and spelling... :)
also, I am having some dilema as to how to translate ( or not actually) typical keywords such as:
-- GameObject
-- FSM
-- Gizmo
-- Float
-- Int
-- Vector3 Vector2
-- Child
etc. There are more of course, but your opinion would be appreciated here.
bye,
Jean
-
I think types that appear in the Unity API should not be translated.
I'll mark those in the project...
-
any chance with some Indian Languages
-
Russian? :)
-
Russian? :)
Sure.. but only tooltips, NOT expressions or functions, operators etc..
(Конечно, но только описание..Но НЕ переводить выражения, функции, операторы и т.д.)
-
hi, i'm Dutch, no problem testing a dutch version if you want. But lemme tell you , the dutch people are practically bilingual. Especially young poeple and anybody in in any digital profession. I have yet to meet an artis,coder or heck anyone in the dutch game industry that prefers dutch language versions.
Dutch versions tend to confuse, as we're just basically all used to english software.. Heck I make sure to order english versions of Windows,cuz people just feel dutch windows is for dummies..
So unless there's another dutchie that disagrees, I wouldn't put to many resources on a dutch version.. ;) It's a cultural thing.. (there is no voice dubbing of anything in holland, its all english/original versions on tv/film/web anything basically)..
cheers
-
Hi,
Yes, it's incredible how you are all truly bilingual, the same goes with Denmark, where I went there for the first time few weeks ago, and it's very much is the same. Kudos :)
bye,
Jean
-
Hi, i don't sure that you need it but i can help you with Russian :)
-
Hi, i don't sure that you need it but i can help you with Russian :)
Thanks! I'll PM you an invite :)
-
I'm a Spaniard from Madrid and would gladly help you with the Spanish translation if you still need help with that. :)
-
Jean: it is always a good idea to translate technical term and use them along the original one. The reason for this is that some concepts are more understandable: FSM are known in spanish as Máquinas de Estado Finito and as such it is easier to grasp the whole meaning and implications of this concept. After that, is is simple to use the abbreviation of Finite State Machines (FSM).
-
Hi,
Yeah. Tricky all these translation and how it will be perceived.
Bye,
Jean
-
Hi JeanFabre,
translating into french is not easy for this type of software...
As far as I now, Unity is not translated into french (but I must admit I never checked...) So I think there are some terms that should remain in english in ordrer to ensure global coherence...
I would suggest :
-- GameObject --> GameObject. I would not translate this term... If I had to, I would use "Brique Objet" (as a reference for object-oriented design)
-- FSM --> In french I think we say "MEF" for "Machine à états finis" (a literal translation from english, when a more accurate translation would be "Machine avec un nombre d'états fini"...)
-- Gizmo --> Gizmo! I don't think there is a french word for this... Maybe "vignette" (but I think the literal translation would be "Gadget"...)??
-- Float --> (nombre) Décimal
-- Int --> (nombre) Entier
-- Vector3 Vector2 --> Vecteur3 Vecteur2 or Vecteur3D Vecteur2D... Not very important I think : the term is explicit...
-- Child --> Child. I would not translate... ("Enfant" or "Fils/Fille" would look strange to me)
-
Hi,
you seem a lot more legitimate to give a new pass on the french translation than me :) do you want to have access to the translation system so you can have an input?
bye,
Jean
-
Jeanfabre : if I could help, off course!
(sorry for the loooong delay of answer, have been away for a while...)
-
Hello! I speak Spanish and I would like to collaborate to translate the official documentation of the playmaker (manual), if you are interested please contact me at my email.
email: matt.zweaz@gmail.com
-
Hi,
Cool, email sent :)
bye,
Jean
-
I am German and would help with the german translation if needed.
I mainly replied to this thread to throw in some thoughts :
Float/Int/GameObject/FSM...basically all variables and technical terms from the documentation should not be translated. All the resources concerning programming concepts (tutorials,books,papers etc) are using those terms unified and these should stay as they are - to make support and cross language support simpler and more effective.
I use Adobe software alot when it comes to filmmaking - they made the horrible mistake to translate everything into the localized language - all tutorials and help forums are basically useless for me.
F.E a "Float" - it is a technical term that nearly all software has agreed on - it is like "Keyframe" in video - it does not make sense to translate it. Unity has no native localization for the editor - this is what makes Unitys resources so powerful - they are international and can be understood due to agreements that were made beforehand.
Things to translate :
Tooltips, Actions like "Wait" (non technical, general actions) or "Activate GameObject" to "Aktiviere GameObject" <-- Keep the technical term for consistency and translate the part that might be easier to understand in the mother tongue.
Alex
-
Hi,
can you pm me with your email, I'll forward it so that you can get access to the translation system to make these mods if you want. We would appreciate that greatly!
Bye,
Jean
-
Hi Jean,
i translated a lot of IT stuff via transifex (one of the bigger feats was about 5000 string for Alfresco CRM), i don't know if you've got many customers from Serbia, but i can do it in a jiffy.
-
Hi,
Cool, simply get back to me in a pm with your email, and I'll forward it so you can get access to our system.
Bye,
Jean
-
Hi, why does Spanish have 30%? still do not confirm the rest of the translated words or are they wrong?
-
Hi,
I am not sure, I'll enquire with Alex,
Bye,
Jean
-
Hmmm, just checked on Crowdin and Spanish is 100% Approved. It might not have made it into an update yet, but I'll make sure it gets into the next one...
Thanks for your work on this!
-
How about German? 59%?
Would be happy to help translating. :)
-
Ahhh, I just realized you’re looking at the summary in the first post. I need to update that with the current data from CrowdIn. Not sure where German stands, but would love the help! We will be updating the text strings with new strings added in the last few updates, so it's an ongoing effort! Thanks everyone!
-
Hi,
I can help for German and Dutch as well when needed.
-
I am having some dilema as to how to translate ( or not actually) typical keywords such as:
-- GameObject
-- FSM
-- Gizmo
-- Float
-- Int
-- Vector3 Vector2
-- Child
You don't really translate those, because they are very technical terms that don't get usually translated.
In example, CHILD in italian is BAMBINO, but it sounds HORRIBLE and doesn't make any sense to translate it. It's just few words to learn in english... any programmer or coder wannabe will have to learn these words early anyway.
Another reason for not translating is that english has one of the shortest words average in the world.
In example, FLOAT in italian is VIRGOLA MOBILE. You don't really want to put VIRGOLA MOBILE in place of FLOAT in the actions. It would be crazy.
GIZMO has no translation at all.
FSM... you will explain to the user in the manual that it's Finite State Machine (Macchina di Stato Finito) and that's it, you don't translate that acronym.
GAMEOBJECT translates literally to GIOCO OGGETTO, doesn't make any sense.
Right translation would be OGGETTO DI GIOCO, but again, that's so long to put in the windows... much better GAMEOBJECT, and all people in the world know what GAME means and OBJECT is easy to understand as well.