POEditor's tagging system has the role of helping you organize the strings inside your software localization projects. You can set custom tags to groups of terms, to filter them during translation or on export.
Tags should be up to 255-character long and can be made of lowercase letters, numbers, minuses and underscores. Any other characters are replaced with underscores and uppercase letters are converted to lowercase.
Tagging on import
Go to Import > Advanced options, select a file to localize, and then add tags for the terms to be imported. You can set tags for all the terms, including the new ones (that are in the file, and not in the POEditor localization project) or the obsolete (which are in the POEditor localization project, but not in the file). If you want to overwrite the translations, you have the option of tagging the terms that have been modified.
Tagging during translation
Go to Terms and select the terms you want to tag, by checking the boxes next to them. Then go to the bottom of the page, choose Add tags to selection and write the name of the tag in the box, which can be an existing tag or a new one.
Filtering by tags during translation
Select the desired tag from the top left drop-down menu, in order to view in the language page only the terms that have been tagged that way.
Filtering by tags on export
While on a language page, select Export > Advanced Options and click on the filters you want to apply for export. It will generate a file containing the terms and translations grouped by the selected tag(s).
You can remove the tags set on a term or on a group of terms in the user interface in the Terms page. Select the Remove Tags from Selection option in the dropdown menu and pressing Go. Must have at least one tag to see this option.
This API method also allows you to remove tags.
Note: 1) All of POEditor's integrations with code hosting platforms (GitHub, Bitbucket, GitLab, Azure DevOps) support tags. You can find out here how to use tags this way.
2) POEditor treats identical terms as one string (the only way to have duplicates in a POEditor software localization project is by importing identical terms with different context).