470 results found
-
Create badges similar to Continuous Build systems
Create badges we can post on wikis, build pages, markdowns, github, etc. They would show basic stats for the project (translation %s, etc) and link back to POEditor.
14 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 -
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 -
Search field case-sensitive
Would be great if there would be an option in the search field to make your search case-sensitive
13 votes -
Terms information on edit page
Example: http://imgur.com/a/si88N
Summary:
* Link to term
* View or edit tags12 votes -
Directly export to Github from a language or a project page
It would be nice if I could automatically export from a language page, or if I could export all to Github from the project page.
12 votes -
Add escaped unicode character highlighting
Please add highlighting in the web text editor for escaped unicode characters, e.g. \u00A0, so that translators can know the start and end of these sub strings, so they can avoid editing them in translation
12 votes -
Sort keys/terms manually
Sort keys/terms manually to keep them organized.
12 votes -
default reference language lockdown / block
My team wrote the website in English initially, which is our default reference language.
Very simple:
We don't want people to be able to change English. We want control over the English to make sure it's correct.The existing options aren't feasible:
A) Control contributors (and deny anyone requesting access to English)
B) Remove languages that are "completed"A simpler option I'm asking for would be:
Create an option so project admins can check a box:
Allow default reference language to be modified by non-admins?
Yes/No11 votes -
i18n in POEditor.com
This site makes it a lot more easier to edit po files =)
But it can be a bit confusing for some translators because not everyone knows English. For example, my app uses Spanish and Portuguese.11 votes -
Version control
Version control for translation history
11 votes -
Use the entire sentence to carry out a search
Currently, poEditor only take a string ID or one word of the content which is not easy as most of the time, it is the entire sentence which is known to us, no the string ID.
11 votes -
Tag from excel
Adding a sixth column to import from an excel with a tag would be very useful.
Obviously, a tag inside associated to a string inside the excel file wins against a tag choosen through the import tool.10 votes -
Please add an Export button to the language row
Right now, when on a project's page, each language's row has three buttons (add, edit, delete). Please add an export button so that we can quickly export a language from that page w/o having to to into the language just to hit the button in there.
10 votes -
Get number of contributions from a contributor through the API
As the maintainer of a project, when I call the contributors listing API (
POST /v2/contributors/list), I'd like to get also the number of times each contributors has translated a string in the project.This can be useful for instance when creating our own contributors listing page, to order the contributors top down.
9 votes -
Ability to share terms and translations between projets
If I have a project Android and a project IOS, I would like to have the same translations between projets but Ids are differents. So the idea is to have for one term an id (which can be the term) for each project.
9 votes -
Add Slack notification when all Fuzzy translations in the project have been unflagged
We need to somehow keep track of what our translations are doing with fuzzy texts. It would be good to have a Slack notification when all Fuzzy texts for project have been unchecked for admin to verify.
Also perhaps it's reasonable to consider change of Flag Fuzzy as update of translation.. So you can sort by updated and see texts that have been marked as not fuzzy.
9 votes -
Custom icon for a custom languages.
Custom languages only shows a generic green icon, it's difficult to edit text when you have multiple of them.
9 votes -
Administration: parent-child projects/subprojects
When dealing with larger projects it's useful to have the ability to create a main project and have multiple subprojects underneath that main project as in a parent-child relation. If possible even multiple levels deep.
9 votes -
Pricing Issues
I think you should have a lower pricing model for the longer term. Our company would perhaps use this software in the long term, but we're only going to be in active development/translation for the next few weeks. We'll revisit now and then as we add more languages, but the monthly pricing gets a little steep for us to retain the service on an ongoing basis, considering we won't use it for in months.
8 votes
- Don't see your idea?