Hello Scott, This is exactly what I need, thank you, really appreciate!
I do my translations locally in Lokalize since 2011 and prefer doing all the file conversions manually also. Not a big fan of online Open Source translating tools for various reasons. The moment I have the translation ready and tested by our admins in working oVirt enviroment, I'll upload the Russian .po into Zanata. The link says 404 btw :) Thanks alot again! Best regards, Julia Dronova On 19 December 2016 at 18:49, Scott Dickerson <[email protected]> wrote: > Hi Julia, > > The easiest way to do the translations is in Zanata [1]. I can enable > Russian for the project. > > Because we use Zanata to manage the translations, we have a 5 step process > to generate translation files. That process goes like this: > 1. 'npm run intl:extract' -- converts > "ovirt-engine-dashboard/src/intl-messages.js" > into "extra/messages/src/dashboard-messages.pot" > 2. push the "dashboard-messages.pot" file to zanata for the correct > dashboard version > 3. translations are performed in Zanata > 4. pull the translated "*.po" file from Zanta, one for each language > 5. 'npm run intl:apply' -- converts each of the .po files into an entry > in "ovirt-engine-dashboard/intl/translations.json" > 5a. I run a small script to sort the keys in the JSON file so viewing > the version diff is reasonable > > The process may sound like a pain, but it is straightforward and > scriptable. The POT and PO files are just transitions files to and from > Zanata. > > If you want to manually do the translations, you will need to modify the > "ovirt-engine-dashboard/src/translations.json" file. Copy one of the > other locales, rename the key to "ru-RU" and do the translations there. > Every key will match a key in "src/intl-messages.js". > > There is one big caveat to doing the translations directly in the > translations.json file. If you post a patch to add those translations to > the source repo, there is a risk that the next time we run the Zanata > process, your translations will get dropped. The "translations.json" file > is generated automatically based on what is in Zanata. If your > translations aren't there, we'll have to do an extra manual merge to bring > them back in. Manual is error prone and makes scripting the process that > much more difficult. > > TL;DR - Try to do the translations in Zanata to leverage the existing > process. However, if that's not an option, add your translations directly > in "intl/translations.json". If you manually add translations, be aware > they will need to be manually merged back in ever time we update from > Zanata. > > [1] - https://translate.zanata.org/iteration/view/ovirt-engine-dashboard > > Regards, > Scott > > On Mon, Dec 19, 2016 at 7:54 AM, Juliette Tux <[email protected]> > wrote: > >> Hello, >> Ehm, hate to say it, but it seems I did not make myself clear. My >> question was (using now as few words as it's possible): "how can I extract >> translatable messages from the file 'src/intl-messages.js' "? They are >> supposed to be exctracted into .pot, you see, as far as I can read it in >> the file 'package.json' . I want to translate the dashboard into Russian, >> you see. >> >> Best regards, >> Julia Dronova >> >> On 16 December 2016 at 20:16, Greg Sheremeta <[email protected]> wrote: >> >>> Hi Juliette, >>> >>> You can grab the json here: https://gerrit.ovirt.org >>> /gitweb?p=ovirt-engine-dashboard.git;a=blob;f=intl/translations.json >>> >>> Best wishes, >>> Greg >>> >>> >>> On Fri, Dec 16, 2016 at 11:39 AM, Juliette Tux <[email protected]> >>> wrote: >>> >>>> Hello gentlemen, >>>> >>>> Could anyone pls throw me some light on .js to .pot extracting, >>>> regarding the ovirt-engine-dashboard. I have grabbed the >>>> 'ovirt-engine-dashboard-1.0.6' zipped version from resources.ovirt.org, >>>> and the 'package.json' file gives very useful info abt json to pot >>>> converting process, but as far as I can see, the messages are all in the >>>> 'intl-messages.js' file. >>>> >>>> What should I do to overcome this js not being the json issue? I'm >>>> quite familiar with .properties atm, but this is a new step for me. >>>> >>>> PS I have the full metal 100% Russian translation for oVirt-engine >>>> 4.0.4 including the new audit log messages added in v4, but still not sure >>>> abt how well my work would be protected from not fully adecuate edits by >>>> random 'translators' on Zanata :/ And anyway I have to do the dashboard >>>> first :) >>>> >>>> Pls help, really love you all! >>>> >>>> Best regards, >>>> Julia Dronova >>>> >>>> -- >>>> С уважением, Дронова Юлия >>>> >>>> _______________________________________________ >>>> Devel mailing list >>>> [email protected] >>>> http://lists.ovirt.org/mailman/listinfo/devel >>>> >>> >>> >>> >>> -- >>> Greg Sheremeta, MBA >>> Red Hat, Inc. >>> Sr. Software Engineer >>> [email protected] >>> >> >> >> >> -- >> С уважением, Дронова Юлия >> > > > > -- > Scott Dickerson > Senior Software Engineer > RHEV-M Engineering - UX Team > Red Hat, Inc > -- С уважением, Дронова Юлия
_______________________________________________ Devel mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/devel
