G Karunakar wrote: > Thanks Runa, for following up on this
Thanks Karunakar for taking time out to read through this. Replies in-line. > > In above maybe some sample strings could be added. > eg. Since I have not been heavy into translations recently, was not sure > what "Defined strings" mean. > > To add to the list - spellchecker is very important (Hindi atleast).. not > sure if it needs to be made an after step or to happen during translation > (ie intergrate spellcheck with translation tool). > > Another useful feature to have is a Dictionary lookup, while there is > freedict, stardict etc.. but more useful to have a custom tool which acts > as live translation memory, not necessarily integrated into the > translation tool. Here idea being to mine existing PO files or have > multiple memories (PO compendium, FUEL, gnome-glossary...etc). Kbabel had > these features, but newer tools dont seem to have that flexible memory. > In this case defined stings would generally encompass things of various categories like application-names, commands, command-line options, brand names, trademarks or any other content identified by the translation group not to be translated. This can perhaps be extended to add a feature to allow 'translation of the strings in a pre-defined format' in addition to 'non-translation of defined strings' (as currently mentioned). In that case, we can make use of multiple translation memories, compendiums, glossaries or any other customized string lists which can be added/modified/defined as per the language team's requirements. A spell-checker is an expected addition to any translation editing method and it would surely be good to have it integrated. > > translate toolkit seems to implement lot of things, so one way could be to > extend it, or use parts of it, or extend it. Precisely. Translation-filter[1] developed by Kushal Das does use features from translate-toolkit and is a pretty handy tool. However, it would be interesting to explore if translate-toolkit or any other tool presently includes features for extensive validation of translated Indic content and how we can utilize them for this particular case. On the other hand, I would also like to understand how this can be approached independently with perhaps an open perspective of integrating it with other existing tools. > > Writing fresh scripts would also be fine, but still need a generic set > which can do basic handling of POT, PO files, do pair level manipulation. > > Translate toolkit has some API, but I couldnt find a generic class, which > could handle PO file, though it has internal functions for it. Could you perhaps mention a few examples that can be part of the generic set. I can try and see if it can be fit into the checkpoint details and modify them if required. > Will put up more on this on wiki. That would be really good. Thanks. regards Runa [1] https://fedorahosted.org/translation-filter/ -- blog: http://arrbee.wordpress.com irc: mishti or runa_b on Freenode ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ IndLinux-group mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/indlinux-group
