OmegaT: stable version 1.7.3 last update


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News OmegaT: stable version 1.7.3 last update
# 1  
Old 09-13-2008
OmegaT: stable version 1.7.3 last update

OmegaT® is a free and open source multiplatform Computer Assisted Translation tool with fuzzy matching, translation memory, keyword search, glossaries, and translation leveraging into updated projects.
Image Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

6 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Need to update the text file with next version of deployment(V1,V2,V3)

Hi.. am new to shell and trying to write the script for the below task. Intially new.txt will be empty. Requirment is to update the version of deployment packages.First time CMD_HG-120-V1 should be updated in new.txt. Next time when i run the script it should be CMD_HG-120-V2..Simiraly... (8 Replies)
Discussion started by: naresh2389
8 Replies

2. Red Hat

Which is the most stable version in RHEL 5 series.?

hi, Which is the most stable version in RHEL 5 series ? since i'm learning EL 6, it has some bug such as created partitions will be enabled after a reboot. so i like to start my learning from EL 5 series for practice. thanks in advance. (1 Reply)
Discussion started by: redhatlbug
1 Replies

3. Red Hat

Specify version in yum update

Hello All, I am trying to upgrade redhat from 5.6 to 5.8. When i use Code: yum update -y it installs 5.9 I dont want 5.9, instead i would like to upgrade to 5.8 is there anyway to specify a version when you are doing Code: yum update (4 Replies)
Discussion started by: adam25ca
4 Replies

4. UNIX for Dummies Questions & Answers

Auto Version update

We have a version for every file like RHZ 1.0 / Ver 1.4.2 etc. Whenever I place a new file with same file name i want the version to get auto upgraded. So can anyone suggest code.. Eg: RHX 1.0 -> RHZ 1.1 Ver 1.4.2. -> Ver 1.4.3 (1 Reply)
Discussion started by: krishna87
1 Replies

5. Solaris

Update java version in Zone

I am using a solaris zone in Sun blade-T6320 which has a java version "1.5.0_18" i want to update it to 1.6.0.16 or higher , how can i do that , does i need to add the new java package to the global server or just instal it in the zone itself. do i need to remove the older version or and install... (1 Reply)
Discussion started by: Sojourner
1 Replies

6. Solaris

Solaris ASR - Update JAVA version

Hi, all I wish to implement ASR for a SUN server in my production. currently the version of JAVA for this SUN server is root@procyon # java -version java version "1.5.0_12" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_12-b04) Java HotSpot(TM) Server VM (build 1.5.0_12-b04,... (3 Replies)
Discussion started by: SmartAntz
3 Replies
Login or Register to Ask a Question
DEBCONF-GETLANG(1)						      Debconf							DEBCONF-GETLANG(1)

NAME
debconf-getlang - extract a language from a templates file SYNOPSIS
debconf-getlang lang master [translation] debconf-getlang --stats master translation [...] DESCRIPTION
Note: This utility is deprecated; you should switch to using the po-debconf package. This program helps make and manage translations of debconf templates. There are basically three situations in which this program might be called: A translation is just being started. You want to provide the translator with a file they can work on that has the English fields from your templates file, plus blank Field- ll fields for the target language that they can fill in. To do this, run the program with first parameter being the code for the language that is being translated to, and the second parameter being the filename of the English templates file. A translation is well under way. You have changed some English text, or added more items to your templates file, and you want to send the translators a file with the English text plus their current translations (or you are the translator, and you want to generate such a file for your own use). To accomplish this, run the program with the first parameter being the the code for the language that is being translated to, the second parameter being the filename of the master English templates file, and the third parameter being the filename of the current translated file. When run this way, the program is smart enough to notice fuzzy translations. For example a fuzzy Description will be output as Description-<lang>-fuzzy, and a new, blank Description-<lang> will be added. Translators should remove the -fuzzy fields as they correct the fuzzy translations. Checking the status of a translation To check the status of a translation, use the --status flag, and pass the english template file as the first parameter, and all the other translated templates after that. It will output statistics for each of them. For example: debconf-getlang --stats debian/templates debian/templates.* NOTE
Note that the text in the generated templates may be word-wrapped by debconf. SEE ALSO
debconf-mergetemplate(1) AUTHOR
Joey Hess <joeyh@debian.org> 2012-09-10 DEBCONF-GETLANG(1)