This is interesting:
The OSTD ( http://littlesvr.ca/ostd/ ) is an automatic translations system – it will take your .POT file and populate it with translations based on strings in other open source software, generating .PO files. Given that you can see which software the strings come from – this will be much more accurate than other automatic translation systems such as Google Translate.
In short, the beginnings of an automated glossary. Maybe worth exploring a collaboration? No API at the moment.
Carlos E. G. Barbosa 5:22 pm on March 9, 2012 Permalink |
Supposing those other strings are products of human labour, and not of another (or the same) automated source – it seems good.
I see it as a very short term solution, however. As long as more and more translatorlings leave their job to automated systems, that system becomes vicious, so more and more garbagge will populate those new .PO files.
Automated good translations are just a dream to this moment. And this OSTD is not an automatic translator, but an automatic searcher for hopefully human strings spread around elsewhere…
Zé 5:33 pm on March 9, 2012 Permalink |
Very true, and yes, the strings are products of human labor. I agree with the system becoming polluted, but I like the idea of having previous translations as helpers. The ideal scenario would be to have this functionality in a tight system (like GP), where consistency can be a little more accurate. In other words, an internal, human generated, glossary.
Gabriel Reguly 6:22 pm on March 9, 2012 Permalink |
Speaking about glossaries, how can one generate a glossary from GlotPress?
Is it possible?
Zé 6:28 pm on March 9, 2012 Permalink |
Not at the moment, but patches welcome.
Carlos E. G. Barbosa 2:37 pm on March 10, 2012 Permalink |
Zé,
I totally agree with your ideal scenario. When we have a trustable crew (sharing the same semantic universe and) providing equally trustable strings to such a glossary, then we can get consistent suggestions coming from that ‘automated’ system.
That is a must indeed…