Hello to all! I would also like to share my experiences so far with new Pootle plataform.
>It turns out, that there is no easy way to work on po files > directly (via API) or externally (by API or Webinterface). Even the > really ugly workaround (they all have to be renamed to be usable in a > Tryton installation and of course would have to be renamed back to match the > pootle naming) to download all po files via zip and reupload doesn't work > and can not be tested, because this download option gives a 404. Like Mathias commented, the renaming of files is certainly an inconvenient. Portuguese (Brazil) is a new language, not yet officialy relesased with Tryton. Before Pootle, we have been using Transifex and Tryton Client to perform the translations. Now, we are uploading our .po files to Pootle, and we have to change their names or choose the correct destination file by hand in order to work. I think this renaming issue could be easily resolved with a script (I will work on it as soon as possible) but the uploading seems to be an issue. > A simple search in the pootle web interface for a string [1][2] over the > German project took foreever (didn't finish). In the Tryton client this > is a matter of 1-2 seconds, in pootle it is unusable. Search is slow. Sometimes, the inteface takes a long time to respond also. Maybe it is a question of more memory ou configuration tunning. Positive points so far: - It allows a more colaborative way of translation. More people can work in a distributed way on the translation process and the permission/suggestion control is more intuitive and less complex than to work with issues and commits. - Is is a very nice feature to allow to see different languages when translating (My Account >> Translation Settings >> Alternative Source Languages). For example, I have enabled French and Spanish. It is specially usefull when translating very technical stuff (like accounting). - Commit through Pootle interface directly to hg repo. - Autocorrection features: Pootle points out some possible errors on translation (punctuation, brackets, etc). Very useful for revision. I still have to learn: Terminology, but it also seems helpful (I have only read the docs, but have not used so far. Roberto Novaes www.silexsistemas.com.br Belo Horizonte - MG - Brasil 2015-06-19 9:06 GMT-03:00 Mathias Behrle <mbeh...@m9s.biz>: > * Mathias Behrle: " Re: [tryton-dev] Re: Using Pootle to translate > Tryton" (Tue, 16 Jun 2015 13:50:16 +0200): > > > > > I am not the one to block improvements just for the sake of > established > > > > procedures. But if the established procedures turn out to be much > more > > > efficient > > > > for power users, then it is just wrong to eliminate them. > > > > > > Totally agree. Is not there a way to reconcile both procesees? > > > > If there is a will, there is a way...;) You even don't have to reconcile > > something, you can just use both ways in parallel. > > > > > I do not > > > know enough about your workflow and I am starting to learn how to do > things > > > in Pootle. But isn't possible to use the client interface to translate > and > > > then upload the files to pootle? Is there a pootle API that would > allow to > > > automate this process (like, for instance, transifex client or > something?) > > > > Yes, there is an API. I didn't have a closer look at it yet. I expect it > to > > work, otherwise it will be a real degradation of the process. The point > I am > > claiming is, that I have yet to use now another API to get my > translations > > into the system. We will see by the time how it works. > > I now took the time to have a closer look at the pootle installation. > > My results so far are: > > 1) It turns out, that there is no easy way to work on po files > directly (via API) or externally (by API or Webinterface). Even the > really ugly workaround (they all have to be renamed to be usable in a > Tryton installation and of course would have to be renamed back to > match the > pootle naming) to download all po files via zip and reupload doesn't > work > and can not be tested, because this download option gives a 404. > > Note: Currently the API seems to be not enabled or doesn't work, the > simple example from [0] returns > slumber.exceptions.HttpNotFoundError: Client Error 404: > http://pootle.tryton.org:8000/api/v1/languages/ > > Note: There is one project [1] featuring a pootle client. I didn't give > it a > try, since it received the last commit two years ago, has an unkown > build > state and thus seems to be unmaintained. > > Thus sadly pootle seems to be quite inferior to the transifex platform, > which allows for any kind of project configuration and API acces via > client. > > > 2) A simple search in the pootle web interface for a string [1][2] over the > German project took foreever (didn't finish). In the Tryton client this > is a matter of 1-2 seconds, in pootle it is unusable. > > > The conclusion is, that the current pootle setup doesn't offer in any way > the > environment, that the long time translators of well established and > sophisticated translations need. Of course I recognize the concerns about a > (partially) closed source project like transifex, but OTOH I have to admit, > that pootle currently can not serve the tools for power translators. > > Thus I propose to keep the old established way of translation contribution > as a > possibility, until pootle can provide the proper means to do this work via > this > channel. > > Cheers, > Mathias > > [0] > > http://docs.translatehouse.org/projects/pootle/en/stable-2.5.1/api/using.html#list-matching-a-criteria > [1] > > http://docs.translatehouse.org/projects/pootle/en/latest/features/searching.html > [2] > > http://pootle.tryton.org/de_DE/tryton/translate/#search=Spezialzeichen&sfields=source,target > > -- > > Mathias Behrle > MBSolutions > Gilgenmatten 10 A > D-79114 Freiburg > > Tel: +49(761)471023 > Fax: +49(761)4770816 > http://www.m9s.biz > UStIdNr: DE 142009020 > PGP/GnuPG key availabable from any keyserver, ID: 0x8405BBF6 >
