These are the different storage formats for translations and files associated with translations that are supported by the toolkit. See also Standards conformance for standards conformance.
INI Files (including Inno Setup .isl dialect)
Java Mozilla and Java properties files (also Mozilla derived properties files)
Mozilla Mozilla DTD format
OpenOffice.org OpenOffice.org GSI/SDF format (Also called SDF)
PHP translation arrays
Qt Linguist Qt .ts (both 1.0 and 1.1 supported, 1.0 has a converter)
Symbian localization files
Windows Windows RC files files
Mac OSX Mac OSX strings files (also used on the iPhone) (from version 1.8)
Adobe Adobe Flex properties files files (from version 1.8)
Haiku Haiku catkeys (from version 1.8)
Android string resources (supports storage, not conversion)
.NET Resource files (.resx) .NET Resource files (.resx)
Mozilla .lang files
Formats that we would like to support but don’t currently support:
Glossary tab-delimited “source,target,comment” i.e. like OmegaT but unsure if any extension is required.
unoconv – Python bindings to OpenOffice.org UNO which could allow manipulation of all formats understood by OpenOffice.org.
Tcl: .msg files. Good documentation
These formats are either: too difficult to implement, undocumented, can be processed using some intermediate format or used by too few people to justify the effort. Or some combination or these issues.