450 results found
-
add support for iOS stringsdict files
add support for iOS Localizable.stringsdict files, used to handle plurals strings.
17 votes -
Report percentage a language is translated
The report per language shows contributions over time. Instead I would like to see how much of a language is translated, so that I can track and see that we have ensured a close to complete translation for a particular language over time.
1 vote -
Без тега
На странице Project_name / Terms при выборе термов по тегам не хватает возможности выбрать термы "без тега"
1 vote -
Add option to search through all languages
We would like to be able to search all languages of a project for a certain string (bonus points for allowing case sensitive search) in order to replace all occurrences of this string. Now we have to look at each language separately which is a bit of a drag.
It would be even better if this could be extended to search all languages of all projects connected to my account.
4 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 -
Process Bars
It would be a great idea to have multiple Process bars...
I was thinking of the following colors:
Yellow = Translated Text
Red = Fuzzy Translations
Green = Proofreaded TranslationsIt would be amazing if it could overlap or something..
1 vote -
website
Your website is not translated to Slovak.
1 vote -
Tags: select and or
Right now, if selecting multiple tags the search is looking for terms with both tags. This makes cross tagging basically useless. It would be great to have an/or search functions.
2 votes -
Public URL to view project contributors
I'd like to be able to give credit to my contributors publicly in my project readme.
The easiest way to do so would be to provide a public link where anybody can go to a project and view the contributor list +/- contributions
130 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 -
Add support for translation in PHP Format
Platforms such as HumHub or Yii framework apps use the PHP format to translate content but POEditor doesn't support this yet, so I'd like to request that this feature be added as soon as possible. :)
6 votes -
resx "
The quotes " in the text are exported to the RESX as ". The VisualStudio 2017 reads the resx file fine, but it replaces all " to ". It would be better to export the text as the VisualStudio does.
Consider the following scenario:
- Export resx from poeditor to Git repository.
- Do a small change in the resx by VisualStudio and save the file.
- resx has many changes compared to the version in Git caused by " converted to ".4 votes -
Android String Array Support
Currently android string arrays are not supported. They are completely stripped off. This should not happen.
6 votes -
Prevent translation of placeholders
It would be nice if you could configure how your placeholders look like. And warn if the translation does not contain them.
I am using https://www.npmjs.com/package/i18n for example.
they allow placeholders like: "Welcome {{name}}" and "Welcome %s"
a russian translater might get the idea to write: "пожаловать {{имя}}"
which will cause the application to fail.14 votes -
Export in one api call
It would be much easier to script the translation export if the export api directly responded with the translation requested rather than a url. I'd love to be able to make a single api call with curl to specify the file and language, and not have to mess with parsing the response.
7 votes -
Add 'tags' field on 'New Term' dialog
Tagging process is too annoying at this time.
Current workflow:
- Add Term
- Click Save
- Go to last page
- Select recently added terms
- Add tags
Improvements:
- Add Term
- Input tags
- Save
16 votes -
Ability to Upload screenshots
Screenshots should be separate from comments.
We should be able to upload an annotated screenshot for reference from several terms.
For each term, we should have the option to specify a screenshot from the ones we've uploaded and add a line of text in case we want to refer to an annotation number on the screenshot.
This would then be better as the users could see the reference in context.
We would no longer have to host and maintain our images elsewhere.
We would not have to use the Comments field which sends emails to all our users every time…
13 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 -
Translation of POEditor
Hi,
I miss the option to switch language of the POEditor frontend, so that the tool can be used in other languages than English.
Is this possible? Because I cannot find the setting for that.2 votes -
Special characters when export to android
When having for example special characters in a string "Cast & Crew", the exported string on iOS is ok, but when comes to Android the code is uncompilable(lint error).
When having special characters on android and do an export & must be replaced with &
Is it a way to export the special string to android in such way?
7 votes
- Don't see your idea?