Translation states explained
In the simplest cases an asset is either Translated or Untranslated in any given language.
This is the status before any translation has been entered. Assets in this state don't contribute to the completion of a language and show up as grey in progress reports.
This is the default status when you save any text into a translation. Translated assets contribute to the completion of a language and show up as green in progress reports.
Things aren't always so black and white. Sometimes an asset may be translated, but the work may not be finished or it may have a problem. Flagged translations don't contribute to the completion of a language and show up as red in progress reports.
Translations can be flagged as one of the following:
The translation should be reviewed for its accuracy or relevance; e.g. the source text changed since it was translated.
The translation is marked as being wrong in some way. This might be used when reviewing someone else's work.
The translation isn't final, but not necessary in error either. You may just want to improve it.
The translation requires someone to approve it. Approval can be done simply by removing the flag.
The translation is still being worked on. You may do this if you want to save your changes, but haven't finished.
The translation has been reviewed in an unapproved state, but was not approved.
Flagging empty translations
Flags are intended for marking non-empty translations, but (with the exception of fuzzy) the flags above may be applied to empty strings if need be. This may not always make sense, but it isn't prohibited.
In most cases empty strings will either be left "untranslated" or marked with one of the special redundant states as shown below.
Sometimes an asset doesn't need translating into a particular language, but should still be regarded as complete. Marking untranslated assets in one of the following states indicates that it doesn't require a value but should still contribute to completion.
- Blank translation
This option saves an intentionally blank translation. This tells Loco that the translation does not need a value and will be exported as an empty string.
- Same as source
This option is similar to a blank translation except when you export your project the asset will use the source text from your default language instead of an empty string.
Note that translations set to either of these redundant states do not show up in the Translate tab as they are not for editing. You can only assign redundant states from the Manage tab.
A note about the Fuzzy flag
The fuzzy flag shows up as a :cloud icon:. It's a special case within Loco because it's recognized by other localisation platforms and most commonly used in Gettext PO files.
- Translations can be automatically flagged as Fuzzy when the source text changes. This option can be enabled from your project settings and can alert translators to review their work after an update.
- The Fuzzy flag is automatically cleared when a translation is saved via the editor in the "Translate" tab. It can also be toggled from the editor with the Ctrl U keyboard short cut.
- Empty strings cannot be flagged as Fuzzy. By its very nature a value cannot be fuzzy if it has no content.
How do flags differ from tags?
When you tag an asset it applies across all locales so that translatable items can be grouped together. In contrast, a flagged state only applies to individual translations of an asset. This makes it useful for identifying work that needs to be done in a specific locale.