Do you want to see OpenShot in your native language? So do we! Please help us translate OpenShot for as many languages as possible. We have uploaded all of our English words and phrases to our LaunchPad Translation website.
You don't need any special software to help us translate... all you need is a web browser and the ability to read English and type the phrase in your native language. Sounds easy, right?
Don't have time to translate the entire list of phrases, no problem... you can translate one word or phrase at a time. Your contribution can be as small or as large as you want! Thanks for helping us make OpenShot better and more accessible.
OpenShot Video Editor(TM) is an open-source program that creates, modifies, and edits video files. Copyright (C) 2008 Jonathan Thomas.
This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
August 3, 2009 4:48 PM
Hi, I'm the admin of the Gimp Italian Community. I've translated 60% of OpenShot in my language. I will continue tomorrow... If you need help with the graphics, feel free to ask.
August 3, 2009 5:10 PM
Greeks not included?
August 3, 2009 5:17 PM
Thanks so much for your help! It is very appreciated.
August 3, 2009 5:20 PM
BlackFateGR, I believe you can add new languages to the list. I'm not an expert with LaunchPad and it's translation system yet, but I saw someone had added Romanian without my assistance. Let me know if you can't figure it out and I can assist. Thanks!
August 4, 2009 12:26 AM
I did some translation work for Finnish. Any Finns / Finnish speakers out there, please recheck my work with thought, and don't hesitate to change them as necessary.
Paljon kiitoksia. Thank You.
August 4, 2009 2:59 AM
@ Jonathan
Been looking through a bit of the danish translation. Does every string in you code automatically get converted into something which needs translation?
If not, you might look through you script and remove numbers and such which doesn't need translation.
Btw. it think at if someone wants to translate a language which isn't on the list - you need to set up you LaunchPad profile's prefered languages - and it will pop up as an optional language on the list.
August 4, 2009 3:19 AM
good news... I've started to translate for Turkish... thanks...
August 4, 2009 5:07 AM
Swedish is almost 100% now
August 4, 2009 7:01 AM
I did most of the french translation, it's now 100% done! :-)
Thanks for giving this opportunity to participate even to those with no python skills.
When do you plan to include it in the code?
August 4, 2009 10:06 AM
Danish 100%
August 4, 2009 12:33 PM
tin2tin, I probably need to clean out a few of the strings. I didn't realize that some of the stock icon names got in there, such as "gtk-cancel", etc... These don't need to be translated, as well as numbers, etc... I'll take a look at updating this soon. Thanks!
August 4, 2009 1:57 PM
Merci Poussa, ça été une vraie course pour l'equipe française qui a été la 1ere à traduire totalement Openshot.
It was a race for the french translation.
Now, french hour, we can see on launchpad than OpenShot is translated totaly in
French
Danish
Finnish (thanks tjh)
Italian
Openshot is nearly translated in :
German (miss 2 words)
Swedish (miss 3 words)
Spanish (miss 12 words)
The translations are missing in
Romanian
Dutch
Turkish
Please, help us with launchpad, it 's a pleasure.
For BlackFateGR, you can look on launchpad in your natural language team. If it doesn't work you can dowload the po file and translate the pot file with poedit. (new catalog and after you''ll create the po file when it will be finish.
August 4, 2009 2:42 PM
Hi!
I've revised some italian phrases.
Keep up the good work!
August 4, 2009 2:44 PM
@ Luca Andrea, I was thinking about mantaining all those strange capital letters, but I prefer the actual way too.
August 4, 2009 5:14 PM
Good to see i18n is implemented!
Though I agree with in2tin the strings could need some cleaning.
Remove numbers, speeds, file extensions and other non-translatable items and put them directly in the code or in a technical configuration file, not in the i18n strings.
If you have lists like "10x,5x,3x,2x,normal speed,1/2x,1/3x,1/5x,1/10x" I suggest putting only the actually translatable value ("normal speed") in Launchpad and adding the fixed values hardcoded in code or from technical configuration file.
Do not include GUI related indicator symbols e.g. ":" (and perhaps "...") in the i18n. Use "Folder name" not "Folder name:" or "Folder name :"
Do not include any HTML code at all in i18n unless absolutely necessary.
Very long units of text like the GPL license is not suitable for translation in Launchpad. Instead put the license text for each language in a separate txt-file, e.g. license.en.txt and license.fr.txt. There are probably already GPL license translations for a multitude of languages already and probably with a more juridical wording than what video enthusiasts will come up with.. ;-p
All this is 3rd degree nitpicking of course, but it does make the translations more manageable over time and make for more manageable code. Say you want to add a "7x" speed, you don't want to leave that to the translators you the developer want to do that without fiddling with i18n :-)
But no criticism at all only my hard earned advice.
Thank you for all the hard work you put into this project and the enthusiasm you radiate through this blog!
August 4, 2009 5:18 PM
I totally agree with Atmos. It's a very good piece of advice.
August 4, 2009 6:46 PM
GPL translations can be copied from http://www.gnu.org/licenses/translations.html . Do note that a translated GPL text never is legally binding
August 4, 2009 11:11 PM
Great post Atmos. I agree. Those changes would make translations higher quality as there's less chance for messing up. Also comment about GPL (license text) is spot on. I left Finnish version unchanged from English, because I've understood that English version is the only one that is "legal" and I think it's common practise to include the official version. If translations are used, get them from (http://www.gnu.org/licenses/translations.html) and be sure to mention its not a official version.
Happy to see so many translations so quickly. Thanks for everyone involved. Also happy to see our western neighbour. :-) Finland has two official languages, Finnish and Swedish.
Most of the time geeks in Finland choose to use English versions of programs as Finnish translations suck. But for avarage users or beginners or people who don't have wide English vocabulary, Finnish versions make programs easier to approach. Quality of translations have gone up lately, maybe because it's not just programmers any more who participate in translation work. (not that they couldn't do it, but they have higher priorities)
Again, any Finns, please go ahead and check my translations and change what ever is needed. :-) I'm currently unable to run OpenShot and thus can't verify very well that all translations are accurate / appropriate (would be easier to see the original text in context). I was relatively happy with Launchpads translation feature, but occasionally it hanged up and showed an error page (when saving).
August 6, 2009 10:07 AM
Hi,
I am making Slovenian translation but I am little lost with "Frames per Image". Those words together I do not find in Google as well. Of course there is “Frames per Second” but this is not it I believe.
Thanks.
August 6, 2009 11:34 AM
Hi, si zorancek, that's that.
August 6, 2009 1:02 PM
"Frames per Image" refers to how many frames does each image represent (most likely 1). It must be 1 or greater.
Imagine you have an image sequence of the following files:
01.png
02.png
03.png
skip a few
25.png
If you import them with "Frames per Image" = 1, then the clip will be 25 frames long (i.e. 1 second long... if your project is 25 frames per second).
If you import them with "Frames per Image" = 2, then each image will appear for 2 frames, thus making the clip 50 frames long (i.e. 2 seconds). This would appear as a slow motion effect.
It's confusing... I know. Maybe this setting needs to go away, since it's easy to change the speed of a clip later (with the clip properties).
August 7, 2009 1:35 AM
Jonathan: Yeah, that "frames per image" setting seems confusing. If it stays, I'd prefer some other kind of wording. Perhaps something like "duplicate each image as xxx frames" or "show each image xxx times" where xxx is 1..n (user selects). That'd make it easier to understand.
Thanks for your excellent work and especially that you listen thoughts and suggestions so closely. Great improvements. OpenShotvideo is already gathering a community around it. That's what is needed for great applications - user feedback loops. :-)
August 8, 2009 1:41 AM
FYI
With the latest build wizard (1.0.6) I'm able to install and run OpenShot on Ubuntu 9.10 (32-bit version) successfully.
August 9, 2009 4:46 AM
Hi,
Can anyone write me what the function of Snapping Tool is? I have problem translating it.
Thanks.
August 9, 2009 4:47 AM
hi,
Can anyone write me what the function of Snapping Tool is? I have problem translating it.
thanks
August 10, 2009 3:14 AM
Hello Zorancek,
The "Snappping Tool" is selected by default, and works like this:
When you place a clip on the timeline and move it into position, the snapping tool automatically aligns it with a grid, so that if it is the first clip on the timeline and you place it very close to the beginning, the "Snapping Tool" will place it exactly at the beginning. Also if placing a clip very close to the end of another clip, "The Snapping Tool" will automatically place it exactly at the end of the previous clip.
If you do not want this behaviour, you can push the button to switch it off.
Hope this helps, Helen
August 11, 2009 5:53 AM
Hi,
I have just a general question.
Should we use the formal or informal forms of adress?
Personally I prefer the informal... ;)
greetings
August 11, 2009 6:18 AM
I'm pretty sure informal is what should be used here. Like talking to a friend, not like talking to the CEO of a Japanese corporation. ;-)
August 11, 2009 4:06 PM
Hi there :-)
Sorry if my greetings have been misunderstood.
I speak UK English where "hello" is the informal greeting, and with me it is always very informal and welcoming when I say it my way.
Where I live in the South West, "hello" is said in much the same way as the Spanish "hola" as an informal friendly greeting.
In UK English the formal is "good morning", "good afternoon" etc.
So when you see me write "hello", please try to imagine me saying it the way I do in speech with bright, cheery, ringing tones. ;-)
Best wishes, Helen
August 12, 2009 4:25 AM
sorry, but it seems I caused some confusion because I've just missed to add a little detail to my message - but my question was related to the translation and not the blog!
And seems this was a blog entry about the translation I just thought it would be clear what I mean ;)
So here it a second attempt:
Should we use the formal or informal forms of address in the translation?
August 12, 2009 11:37 AM
Hello Reinhard (in bright cheerful tones)
The German language has much greater distinction between formal and informal than modern English. Most of the formal English became obsolete 200 years ago, and words like thee, thou, thy and thine would look very peculiar in a software translation.
You should translate to whatever is the most natural and useful in your language, according to the Launchpad guidelines. If that is informal, then that should be your choice.
Best wishes, Helen
September 3, 2009 4:46 AM
Indonesian translation is 100% !
(of course, I'm not the only translator..)
big thanks for the great software!
September 7, 2009 4:03 PM
Hi Helen,
thanks for your answer, but it is hard for me to decide what is the most natural and useful in my language.
This may be the reason why the team has made informal AND formal translations. And this is a bad actual state...
So it would be nice if Jonathan could just make a general decision if he like to have informal or formal translations!
greetings
September 7, 2009 6:14 PM
Hello Reinhard,
I understand your predicament.
Unless Jonathan says otherwise, I would personally suggest make it all Formal.
Though I will admit my German is very poor.
Think of the way in which an artist would describe his or her work. I think that would be Formal wouldn't it?
If so then Formal would be the natural way to describe working in OpenShot.
I hope this helps,
Helen
September 8, 2009 12:49 AM
I'm going to leave this decision up to the translators. I would suggest whatever is most natural. Maybe some investigation into other projects' translations would provide some answers. Good luck!