In the left pane Xliffix shows the source files included in the Xliff file, so you know what part of the application you are translating.
There is also a part with build in search filters over all contained files, so you can search for strings over all files
Progress and status
A developer can mark strings as ‘To be translated’. This way the translators don’t have to search all strings to see which should be done.
Coloured bullets show the status of a string: green is done and ok, orange indicates there is a warning and red is for strings that are not yet translated
You can sort on status, helping you to see your progress
A powerful search function, search through all contained source files for key, source or translation string
XliffiX has two user modes: Developer and Translator.
In developer mode, the developer can mark strings as needed for translation. Xcode creates a lot of superfluous strings, especially for the .Xib files. Marking the strings as needed makes it easier for the translator to keep oversight and prevent unnecessary translation work.
Unique feature: Xliffix can easily show other strings in the Xliff file that use the same noun (both singular and plural forms), adjective or verbs (even in other conjugations!) as the string you are translating. This helps you to translate terms in a consistent way through the whole translation project.
This ‘Related strings’ popover can be dragged to a separate window to keep it in sight.
You can edit the translated strings right within the table, or in a large textfield at the bottom
The developer comments are always visible while editing translations
Xliffix provides warnings when:
- translations are equal to the base string, a
- translations are more than twice as long as the base string
- Number of substitution placeholders (like %@, %d) is unequal between base and translation