468 results found
-
Copy Term to Definition on Double-Click
When a definition is empty and only if empty, it would be nice if we can simply double-click on the definition field input to copy the term.
We do not want to use the global 'Copy Terms to Definitions' option. On one of my project, I have about 6000 terms and only ~300-400 need a simple "copy" for a specific language.
6 votes -
add error highlight/validation for HTML tags
our translators often break html tags with extra spaces - e.g. </ strong>
sometimes they even translate tags/attribute values
would be nice to have validation/error highlight for this cases6 votes -
Show percent of Fuzzy translations in the overview chart as different colour.
Currently dashboard charts per project or per language only give understanding how many translations have been added. If you show that info structured - translated/fuzzy/untranslated, that would also give insight on the quality of translations for specific project/language.
6 votes -
Exporter option to include/strip context and comments
Comments and context are very useful for translators, but I don't need to have them in my project. I think there should be an option during exporting to add or omit comments and context in the exported files.
6 votes -
Android String Array Support
Currently android string arrays are not supported. They are completely stripped off. This should not happen.
6 votes -
Create a POEDITOR feature to integrate into live-apps to enable users to suggest a translation for any string & send it to the dashboard.
Create a POEDITOR feature that developers could optionally integrate into their live-apps which would allow app-users to suggest a translation for any string in the app and send it to the dashboard for review/approval.
This "Suggest translation"-feature could be activated via app settings, or via shake, etc...
When "Suggest translation" mode is active, editable strings get highlighted/underlined and the user can EG. triple-tap any highlighter/underlined string on the screen to select it and suggest a translation/correction in any available language (selectable from a list.) (selections are modifiable, but are saved and set as default for that user/device)
The user can…
6 votes -
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 votesYou can use the GitHub integration with an access token: https://poeditor.com/help/how_to_translate_a_language_file_from_a_github_project
But the participation of the owner is still required to make the setup in this case.However, after the owner makes the setup with GitHub (links the project languages to files on GitHub), they can always generate webhooks to import/export data: https://poeditor.com/help/how_to_use_the_github_webhook
Anyone can trigger these webhooks, they don’t even need a POEditor account. -
Support nested JSON
I am using nested JSON for localization in a couple apps and would be nice if you could support it.
here is a sample that you can use to test: http://pastebin.com/fbpjSmQi
6 votes -
WYSIWYG editor for HTML
Please offer the option to translate HTML strings with a WYSIWYG editor. (tinymce, ckeditor)
6 votes -
QA checks: return in the list when translation is identical to reference language
In some cases, you might have copied part of your main language translation files )let's say English) into the other languages (French).
With POEditor, you don't have possibility to check this behavior of same "string" used in both languages, as it will appear as translated.
QA chacks could return an "error", in order to ease the work of the person that needs to translate by pointing out directly those situations.6 votes -
Formal & Informal translations option
Hi, I see some of the translators do a formal translations and some use an informal style. Would be great if instead of us having to specify in comments if we want a formal or informal translation for each translations, that POEditor would introduce a checkbox to specify the translation style for each term.
6 votesThank you for your suggestion.
If you would like to set a particular tone for a translation order sent to Gengo, please use the ‘Comment for translator’ form on the order, as described at point 2 in this article: https://poeditor.com/kb/how-to-get-human-translation-services
In case some strings in order should be treated as exceptions to these general instructions, note that you can also pass to translators what is written in the first comment of each of your strings, as well as in the Context attribute of each string.
-
Language last update timestamp in API
It would be useful to check the last update time/date for a given language using the API. This feature would allow us to decide whether or not import the current language depending on its timestamp matches with the last import.
5 votes -
How to add language variants like formal and informal?
this feature is necessary for some languages like German, French, Russian. It is not possible to add this, is it? MediaWiki has this feature too. It would be a loss of communication to have not this feature, right? I beg you please integrate this feature
5 votes -
Shortcut
Hey there !
Your tool is very cool :)
You can make it even better by adding shortcuts (next string, previous string)
Cheers
5 votes -
Trim whitespace from translations
I have some translations we are working on, but some saved translations have new line characters (\n) at the end, leaving me with a po file like:
: Views\Course\Lessons.cshtml:271
msgid "Complete final exam"
msgstr "完成期末考試\n"
""Maybe your editor could automatically trim whitespace from the beginnings and ends? Maybe a setting, incase some people like it?
Very nice tool :)
5 votes -
Dutch (BE) is missing
Vlamish language is missing, which is Dutch (BE).
5 votes -
Add number of translations to /contributors/list API endpoint
I'd love to be able to get the number of translations a contributor has provided for a project. That way I can incentivize translations and automate distributing rewards based on how many strings they've provided.
I'm thinking of running a script to periodically check if any contributors have passed various milestones and awarding promo codes via email. Currently I have to do this manually.
5 votes -
5 votes
-
2nd reference language
It would be great to be able to set 2nd reference language to be visible when doing translations. E.g. When the translator is translating Spanish, it's useful to see both English and French text, as English is often inconclusive, because you don't have conjugation and many other grammar structures there which other languages do.
I think it's quite useful to be able to see two languages to cross check terms etc, which en ables the translator to avoid mistakes or misunderstanding of the original term.
5 votes -
Comment from Android string file behind string
It's great that POEditor imports comments from Android strings.xml files. However, it assumes that the comments are in front of the string. We have so far followed this format, after the string:
<string name="Exit">Exit</string><!-- exit the application -->
Would be nice to have an option for importing/exporting it like that. Having the comment in the line above (and an extra blank line before) is IMHO a space-wasting layout.
5 votes
- Don't see your idea?