328 results found
-
Figma Plugin Layer name
For us the Figma plugin only makes sense if we have the option to sync based on layer name instead of layer ID. It would be great to have this simple possibility in the Settings of the Figma Plugin.
1 voteImporting layer names as terms is now possible: https://poeditor.com/kb/poeditor-plugin-figma
-
exact
I would like to see a possibility to do an exact word/phrase search. In our system a search for the term "Patient" gives 62 pages of results, many of which are long phrases or sentences containing the word "Patient".
Since I often know exactly what phrase/word I want to translate, an exact search would narrow my scope immensely.4 votesExact match searches can be performed as described here: https://poeditor.com/kb/advanced-search
-
improve contributors and language management
Now it is difficult to add new language to projects and assign contributors. If I have 10 projects I have to go to each of theme add 3 languages and for each language set contributors :/
3 votesYou can now group your contributors into teams in order to bulk assign them to project languages: https://poeditor.com/kb/poeditor-teams
-
Select which terms to go through automatic translation (AT)
It would be user-friendly if the AT would allow only specific terms to go through it. Currently it is either all untranslated terms or nothing. Having the ability to select which terms to pass through would make it a lot easier.
3 votesStrings can be filtered for automatic translation with tags: https://poeditor.com/kb/advanced-automatic-translation-options
-
GitLab integration, export result in empty file
For a given language with many tags,
only one tag has translation,
upon export with tag filter (to GitLab), the tags in this language which don't have translation result in empty file.Expected result: no empty file for those tags, so no file.
4 votesWe’ve changed the export behavior so that now, when no strings are found for the set filter, the export throws an error instead of exporting an empty file.
-
Support DeepL formal/informal tone option
Many languages like (French, German, Dutch, etc.) use formal or informal terms of address. DeepL is definitely the best automatic translation option out there and to specify the tone would be a big win. This should require only little effort at POEditor but I am not sure about implications concerning the price.
From the DeepL Website: "Customize your results to use formal or informal terms of address with DeepL Pro."
6 votesThe Automatic Translation feature now supports DeepL's Formality option: https://poeditor.com/kb/advanced-automatic-translation-options
-
YAML breaks when string contains doble dot :
When exporting to YAML, if a string contains the double dot character it should be enclosed between double quotes to prevent breaking the YAML file format.
3 votesThank you for signalling this. We’ve just put a fix online, please feel free to check.
-
Integration access for project admins
It would be good to have some role that has integrations access (bitbucket/github, etc) on specific project. Currently only master account can access the integrations and in order to give a person ability to export translations into the project, we need to share access for master account for all projects, which is really not a secure way to do this.
It would be preferable to be able to give access to a certain user e.g. admin on the project to be able to work with integrations for this project - get terms, export translations to bitbucket etc.
7 votesIt is now possible to allow project admins to import/export strings using the integration(s) with GitHub, Bitbucket, Azure DevOps or GitLab: https://poeditor.com/kb/how-to-give-admins-access-integration-github-bitbucket-gitlab-azure-devops
-
1 vote
-
focus in Comments field
when I click on a Comments link, the dialogue should open with the cursor in the Comments field
1 vote -
Support for XLF
Hello,
Your tool does not support .xlf extensions
This causes us to rename every .xlf file to xliff and back despite its the same format.Are there any plans to add support for that?
4 votesFor Angular app localization, we now also support XLIFF .xlf files (beside the .xmb and .xtb formats we already support for a good while).
https://poeditor.com/kb/how-to-translate-angular-apps-using-xliff-files
-
Don't hide already-joined languages on the "Join" page
We had an issue where a translator used a "Join" page link to sign up for the German translation team, but somehow forgot that they had done so.
When they went to the "Join" page a second time, German was not an option in the already-allowed languages (because they were already a member of the team), and also it was not an option in the "suggest a new language" input, because it already had a team formed for it.
It took us a while to figure out what was going on!
It would be clearer in the UI for the…
1 vote -
[BUG] remove formatted="false" part from xml item
Hello,
I cannot use POEditor for my project because you guys removed formatted="false" part from xml itemimported
<string name="consumed_ruby_to_challenge" formatted="false" >"Consumed %d rubies to enter challenge mode"</string>exported
<string name="consumed_ruby_to_challenge">"Consumed %d rubies to enter challenge mode"</string>I import and export xml string for Android
Thanks,
Khanh1 voteWe now support the formatted=“false” flag. If you re-import your terms to the same project, they will be updated with this flag where needed.
-
Automatic translation in hebrew actually translates to Greek instead
You have a bug where Automatic translation in hebrew actually translates to Greek instead.
When importing terms i also asked to import to other languages (hebrew) and it translated the terms to greek instead.1 vote -
Remember term overview order
Please remember the ordering of the terms.
Once you select, "Untranslated first", navigate to another page, and navigate back, the order is set to Default again.1 vote -
Github integration with access token
Github integration is allowed only for the owner of the project... That's really not good for entreprise usage as if this person is in holiday, all the integration is freeze because no body can run the export...
By allowing the usage of a GitHub token it will allow anyone to export to GitHub and respect privacy of users as the token given will have only rights to do that exports to the repo and nothing more.
6 votesGit integrations can also be shared with admins at this time: https://poeditor.com/kb/how-to-give-admins-access-integration-github-bitbucket-gitlab-azure-devops
-
1 vote
Exporting to .xlsx instead of .xls now solves this problem.
-
Add option for "Export to Excel" to include default reference language
We often need to send texts for translations to outsource teams that we don't won't to add as contributors in Poeditor.
To send untranslated keys with English reference to translations, we need to export all English keys, all keys for second language. Then we need to merge those 2 files, filter out already translated keys for second language and just keep keys and English reference for those not translated. And the same routine for 25-30 languages in multiple projects.
It would be much easier to do if during export to Excel you could choose to Export Untranslated, and Add Default…
12 votesWe’ve updated the Excel export.
Now, when you export a language in Excel format, you get the strings in the Default Reference Language (if one is set on the project) in the 6th column.
This 6th column is ignored on import.
-
Strings with translatable="false" are still imported (Android)
<string name="app_name" translatable="false">Example</string>
This should not be imported.1 voteWe’ve added support for the translatable=“false” flag, so that users can no longer edit them: https://poeditor.com/kb/how-to-set-strings-as-non-translatable-in-android-localization-projects
-
Avoid users to modify proofread translations
Currently, contributors can edit proofread translations with a disclaimer which says that the current string is marked as "proofreaded".
I want to avoid people modifying them, and may ve useful on a lot of cases, such as unwanted abuses (in case an user changes all translations for a spammy text).
They will be able to add comments to notify proofreaders. A toggleable option for that will be more than welcome!
1 voteNow you can prevent proofread strings from being edited by contributors who do not have proofreading rights.
You can find this functionality in any project’s Settings page, under the name ‘Lock proofread translations’.
- Don't see your idea?