Hi Sylvain Chiron, So I will translate the entire file, then do the corrections based on context. I'm also going to translate the content of the site as shown on the wiki. I'm still not doing the merge of files, I know how to work with Tortoise SVN and TFS from Microsoft, because I work with software development and I have no problems with the command line. I don't work with translations, do it because it needs to be done, in fact I like development, but as there's not much support on the website to Portuguese of Brazil, I will be devoting my time to solve it.
Regards, Roberto Silva twitter: @Tipigao
2016-07-06 19:37 GMT-03:00 Sylvain Chiron <chironsylvain@...364...>:
Le 06/07/2016 à 23:49, Tipigão Bob a écrit :
I translated almost all, but have things to be seen in context.
Yes, that was the same for me. I translated everything but many times without any idea of the context; then I encountered many strange things and worked on it.
I'm getting to know the procedures to collaborate, started by .po files because I think it is simpler. There is another way that translators
work?
In the Inkscape project, we mainly use PO files, everywhere — except for the Windows installer, the tutorials' header and footer, the website's contents and the default document as far as I know. If you want to translate the website's contents, you'll have to follow the procedure that is described on the wiki: http://wiki.inkscape.org/wiki/index.php/WebSite (I don't have the rights to provide a website account, you'll need Martin for that.) Here it's simply like the standard page editing, where you duplicate English pages and replace the content with translated content. You could note than the Mozilla Developer Network's translation system is quite alike.
I also collaborate to other translation projects on web translation platforms, which probably make the joining procedure easier (but they generally do not improve the quality of translations this way!). I have known Crowdin, Transifex, and translatewiki.net — the last one apparently uses the translation system of MediaWiki, which is also used on some projects of the Wikimedia Foundation such as Meta.
About PO files, we integrate them into our projects' repository (this is also what the web translation platforms usually do under the hood: they write into PO files), and then they're compiled and can be read by the programs (the website's server, the Inkscape program, the tutorials' compiler, the man pages' compiler, the keyboard shortcut pages' compiler, etc.). To add your file into the repository (we're not randomly allowing people to do it), you'll need to send it to us. A Launchpad bug report or merge request is a nice place to discuss your translation. Making a bug report is easy: click on the button, write a small sentence and give your file. Making a merge requests requires a few more steps: you'll have to interact with the repository's files with the control version system (we're using Canonical's Bazaar) as the developers do, which is quite simple but can be repulsive if you don't like the look of the command line (sure, it's visually ugly, I do agree, but nevertheless I use it very often). Note that you can also use a GUI (Bazaar Explorer?) but we probably won't offer support for it. Interacting with repositories will probably be the better if you want to invest. Wait, actually… I'm not so sure if you only work on translations.
I love to philosophize again and again about the wonders of the wheel. This is what brings modernity and better systems.
Best regards,
Sylvain