lr., 2011.eko apiren 16a 00:25(e)an, Leandro Regueiro(e)k idatzi zuen: > On Fri, Apr 15, 2011 at 11:29 PM, F Wolff<[email protected]> wrote: >> >> Op Vr, 2011-04-15 om 19:01 +0200 skryf Leandro Regueiro: >>> I can't find any way to specify which translation memory files Virtaal will >>> use. >>> >>> In OmegaT you just only drop them in a folder within the project >>> folder and it works without setting nothing. In Lokalize you can >>> create translation memories importing PO and TMX files and then use >>> those translation memories. But I can't find how to make this in >>> Virtaal. Can you help me? >>> >> >> Hi Leandro >> >> Virtaal moves all non-fuzzy strings to its own database when you save a >> file, so the easiest might be to open the file, and save it. (You might >> need to make a zero change to be able to save.) > > Well, this is a way. I just tried and seems to work. Maybe you should > document it on the wiki. Thanks a lot. > > IMHO you should put some way on the interface to specify a file (or > list of files) to Virtaal add them to the translation memory.
Oh yes, can I say "I want this too"? Moreover, recently some bad translations ended up in my local TM, and I didn't have any way to remove those unless going into the internals and editing the SQLite db file. The current behaviour works fine and is simple and transparent for the unexperienced user as it doesn't require any setup or special actions, but translators need the flexibility to manage their TMs: have predefined sets to use in certain translations (not all translations need the same TMs), the ability to import a bunch of files, remove existing translations... Virtaal's current implementation doesn't give any idea of the contents of its TM, it's a blind bag where translations come from, and you can't certainly know beforehand if you could trust them, because you can't control 100% what's in it. So I would like to kindly ask to give priority to bugs 997[1] and 1416[2] for the next release after 0.7 if possible. >> If you want to import several files, you can look at the command line >> tool, build_tmdb. > > It seems interesting but I don't know how can I install this tool or > find any documentation about it. It is not important since the other > way seems to work. > build_tmdb comes bundled in the Translate Toolkit, so you already have it installed on your system. I think you are interested on passing the Virtaal tm.db to the tool: $ build_tmdb -d ~/.virtaal/tm.db -s en -t gl <files_to_import> But I was under the impression that Virtaal was using tmdb through tmserver, and as I see tmserver has also a command line option (-f) for importing files, so either way should be fine I think. Julen. [1] http://bugs.locamotion.org/show_bug.cgi?id=997 [2] http://bugs.locamotion.org/show_bug.cgi?id=1416 ------------------------------------------------------------------------------ Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev _______________________________________________ Translate-pootle mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/translate-pootle
