Take a Gettext PO or XLIFF file and segment the entries outputting a new file that has been segmented.
This is useful for the creation of a file that can be used as a Translation Memeory as you should then be able to get better matching for as you will have exposed translated sentences that might occur elsewhere in your work.
poswap [options] <input> <segmented>
Where:
<input> | translations to be segmented |
<segmented> | translations segmented at the sentence level |
Options:
--version | show program's version number and exit |
-h, --help | show this help message and exit |
--manpage | output a manpage based on the help |
--progress=PROGRESS | show progress as: dots, none, bar, names, verbose |
--errorlevel=ERRORLEVEL | show errorlevel as: none, message, exception, traceback |
-iINPUT, --input=INPUT | read from INPUT in pot format |
-xEXCLUDE, --exclude=EXCLUDE | exclude names matching EXCLUDE from input paths |
-oOUTPUT, --output=OUTPUT | write to OUTPUT in po, pot formats |
--psyco=MODE | use psyco to speed up the operation, modes: none, full, profile |
-P, --pot | output PO Templates (.pot) rather than PO files (.po) |
-l, --language=LANG | the target language code |
--source-language=LANG | the source language code (default 'en') |
--keepspaces | Disable automatic stripping of whitespace |
You want to reuse all of your Pidgin translations in another Instant Messenger:
posegment pidgin-af.po pidgin-af-segmented.po
Now all of our Pidgin translation are available, segmented at a sentence level, to be used as a Translation Memory for our other translation work.
You can do the same at a project level. Here we want to segment all of our OpenOffice.org translation work, a few hundred files:
posegment af/ af-segmented/
We start with all our files in af
which are now duplicated in af-segmented
except files are now fully segmented.