Other Tools in the Editor
The History tab shows how the selected string was translated in the past and is useful as a reference. You can quickly access the History tab using the Ctrl+3 keyboard shortcut.
If you have a question about the meaning of a string or see an error, you can leave a comment and/or open an issue.
You can submit your comments and discuss the translation with other collaborators or ask any questions related to the source string.
How can I find strings with comments in the Editor?
There are several ways to find strings with comments in the Editor:
To find all the strings that have at least one comment, use the Comment filter followed by
To find a specific comment, use the Comment filter followed by a keyword or phrase in the comment. For example, "Comment: context".
To find all the strings that include comments that have been marked as issues, use the Issue filter and select the "yes" option.
Issues are meant for typos or grammatical errors in the source string. In this case, you can open an issue and the project's maintainers will be notified so as to proceed with the necessary fixes.
However, vendors/translators working in Transifex, might use Issues to ask clarification questions about the strings they're translating. Opening and closing issues is an excellent way to track which questions have been addressed and implemented and which ones haven’t.
Comments and issues can be viewed by any collaborator of the translation team: so if one translator asked a question about a string, all other translators/reviewers will also see the question and answers and won’t need to ask the same question again.
Open issues can be accessed directly via the link that is available on the project's overview page:
Issues can also be filtered in the Editor: Label > Issue > Open/Resolved/None.
Adding a comment/issue
To add a comment or issue:
With a string selected, click the Comments tab or use Ctrl+5 keyboard shortcut, then hit the Comment button.
Enter your message into the comment box.
Hit Add to simply add a comment, or Add as issue to add a comment and mark it as an issue.
If you want to leave a comment for a specific user, you can @mention them. Simply type @ followed by their username.
The recipient will receive an email notification and will be able to go to the mentioned string(s) right from the email.
Once the question that was added as an issue has been answered by you or your teammate, and a translator or reviewer updates their translation according to the information received, the Issue needs to be marked as Resolved. This way it will not appear as an open issue anymore.
Who can mark the opened issues as resolved?
- Someone who opened the issue
- Project Maintainer
Sometimes a developer might include notes about how a string is used within an app or there are translation instructions for that string. These notes appear between the source string and the translation box.
Developer Notes are imported within the resource file.
String Instructions can be added by clicking on "Edit Context" button, in the Context tab.
It will appear also under the Source string:
If you have String Instruction and Developer Notes, both will appear between the source string and the translation box:
Tags let you group a set of strings within a resource in any way you like. For example, you can use tags to specify where certain strings came from, or prioritize strings for translation using a tag called "Urgent." Only maintainers and administrator users have the privileges so assign tags to source strings.
Tags work on a string level, and when you add a tag, it is applied to all languages, even if you have selected a specific language in the Editor.
To tag strings, first select one or more string using the checkbox to the right of each string. Then in the Edit tags section, type in a tag, and hit Add.
Another way to add tags to your strings is via the Edit context button that is available under the Context tab in the editor.
Also, Transifex supports two smart tags locked & notranslate. These tags allow you to lock a string or prevent it from being translated into other languages. More information about these tags can be found here.
If you need to modify the translation of a word or phrase en masse, you can do so using the search and replace functionality in the Editor. First, select the strings containing the word or phrase you want to update. Then in the Find and replace section of the right panel, type in the term you want to replace, then below that, the new term. Finally, hit Find and Replace.
The Editor supports a number of keyboard shortcuts so you can quickly take actions without using your mouse.
To see all the available shortcuts, enter the Editor, click on the Gear icon in the top right corner of the header, and hit Shortcuts.
If you're translating to two similar languages, such as French (France) and French (Canada), you can view the translations of one as the source strings when translating the other. If, for example, you translated your content from English to French (France), you'd be able to see your French (France) translations as the source strings when translating to French (Canada).
From within the Editor, click the Gear icon in the top right.
Select Show source string in X.
In the popup, select the translation language that you want to see as source strings.
Click Set language.
Once you select a string from the string list to translate it there are some tools and functionality that you can use in the translation area.
The area where the source string is displayed has some functionality that you can access using your mouse. Clicking on an active element in the source string will copy a part of that active element to the translation string area.
Control characters are special characters that when they are added in a text they don't have a visual symbol displayed by default (like when writing the character a the symbol 'a' is added in the text). Those control characters are:
- New line
- Carriage return
- Paragraph break
- Line break
When one of these characters is present in the source string there is a visual representation so that you know what control character is there. You also have the option to click on it and copy it to your translation.
In order to protect variables and HTML tags that exist in the source string, Transifex replaces them with special placeholders.
When you click on those placeholders in the source string area they are copied in the translation string area. Alternatively use the keyboard shortcut Alt+number to copy an HTML placeholder, or Ctrl+Alt+number to copy a variable placeholder. See Translating HTML Content for more details on what you can do with placeholders.
When Transifex identifies that a word in the source string is also in the glossary, an underline is added to that word. When you hover on that word in the source string area you will see a tooltip with the translation of that term in the target language you have selected. Clicking on that term in the source string area will copy it's translation to the translation string area.
See Using the Glossary for more details on how to use the glossary in the Editor.
Tools in the translation string area
Those are the buttons right above the translation. These include:
- Copy source string – Copy the source string into the translation box (you'll still need to hit Save). This is useful if you're translating between two similar languages, such as English (United States) and English (United Kingdom).
- Machine translate – Use machine translation to translate the string. You'll need to have Machine Translation set up first.
- Revert translation – Reverts any changes that you have made to the translation. If the string was untranslated then it clears your translation, otherwise reverts to last saved translation.
- Add special character- Insert special characters into the translation box (see below for details).
This is a dropdown that holds some common special characters so that you can easily add them while translating.
To add a special character, first place your cursor where you want to add the special character. Then:
- Click the Special characters button .
- In the dropdown, click on the special character you want to add.
Special characters RLM and LRM are used to change the way adjacent characters are grouped with respect to text direction. Check out Right to left mark in Wikipedia for more information. NBSP adds a non-breaking space (Unicode U+00A0) to the translation.
For some strings, you may see a number in the bottom left of the translation box. This is a character limit; it's the maximum number of characters your translation for that string can have and a translation won't be saved unless it's within the limit. This means that a translation check that a project manager or administrator has set is checking the translation against the character limit. So if the number says 12, your translation should have 12 or fewer characters.
In order to set a character limit for a specific string, you need to:
- Click on that string and go to its context tab in the editor
- Click on the "Edit Context" button
- Enter the desired limit into the corresponding field.
If a string has a character limit and contains placeholders, then those placeholders are not contributing any characters for that character limit.
The default mode of Transifex Editor is the rich mode. In this mode it is easier to work when you are a translator and want to focus on translation and context, hiding and protecting all technical details that usually don't offer any value to the localization process.
Still there are cases where you want to have full access to the exact source string as this is stored in the database. To view the exact source strings without the placeholders for variables and HTML tags you have to use the Editor settings on the top right corner of the editor page.
Raw mode of the editor is ideal for:
- Editing all html attributes and values
- Editing and adding all characters that you want without the editor applying special compatibility escaping for your file format (JSON, android XML)
In raw mode of the editor we maintain some functionality to help you while translating but this is optional:
- Variables are displayed in italics and you still can click on them in the source string area
- Control and Special characters are also visible and clickable
- Glossary terms can also be used
For usage details on the above please see tools in the translation area.