FUEL: An initiative in language standardization via collaboration
10-06-2008 01:00 PM FUEL (Frequently Used Entries for Localization) aims to solve the problem of inconsistency and lack of standardization in computer software translation in a new and unique way. Initiated by Red Hat, the project is trying to give a better experience to end users of a localized desktop by resolving the issues of standardization and inconsistency.
Hi there,
I'm a newbie in unix and am fishing for options related to how raw input data files are handled. The scenario, as I'm sure y'all must be very familiar with, is this : we receive upwards of 50 data files in ASCII format from various source systems - now each file has its own structure... (3 Replies)
Hi,
I am trying to do standardization (subtracting the mean from original value and dividing by stdev) using an automated script.
I have a file with 10000 rows. I need to initially calculate mean and stdev for each column and then using those values I have to obatin the new standardized... (7 Replies)
It's a metacafe video, doesn't work with tags. Here's the link
Man Develops a Car Which Runs Solely on Water ! Video
This is good news,
I guess if water replaces oil we won't get a heart attack any more when we see fuel prices keep escalating because arabs and israeli's keep fighting. (1 Reply)
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)