447 results found
-
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 -
Notifications
It would be great if the admin could be notified when:
- contributor accepted the invitation email
- contributor added some words (an adjustable % of increase vs the last notification could make sense)
- a daily, weekly email stat with activities84 votes -
Copy String from reference language
Simple button to copy translation from reference language. It's sometimes much simpler to just edit the string that retyping it. This is especially true if the string has some formatting with variables going on
78 votesAlthough there currently isn’t a button in the interface for this, copying the source string is possible using the keyboard shortcut Ctrl + .
More on keyboard shortcuts here: https://poeditor.com/kb/poeditor-keyboard-shortcuts
-
Handle automatically string's placeholders
Would be awesome to replace automatically attribute's placeholder according to the chosen export format.
Ex : Declaring a translation with
"[STRING] called you yesterday (total of call : [NUMBER]"iOS Export : "%@ called you yesterday (total of call : %d)"
Android Export : "%1$s called you yesterday (total of call : %2$d)"71 votes -
CORS enabled
Is Poeditor CORS enabled? If not, how can one make a cross-domain request to Poeditor?
53 votes -
feature: support string-array resources (android only?)
when uploading android-style string resources, string arrays are ignored.
not sure if there is an equivalent in the other supported file formats, but it sure would be useful if this was supported...36 votes -
Versioning
It would be nice if there would be list of all changes like revision history in google docs. With this would be great to have a possibility to create a tag (like svn) - the tag would identify the state, where all of the documents belong to so we can see the state of whole localization at that time.
30 votes -
Reorder terms
Reordering terms using drag and drop
27 votes -
Filter by context dropdown
At the moment the only way to filter by context is through search. This only works to a limited extent. It will also pick up strings from other contexts if the search term appears in them. Please improve this. I really wish I could select the context from a dropdown.
26 votes -
Support Chrome JSON translations
Please add support Chrome JSON translations.
https://developer.chrome.com/extensions/i18n-messagesAn example of such translation
https://raw.githubusercontent.com/olsh/Feedly-Notifier/master/src/_locales/en/messages.json25 votes -
add support for iOS stringsdict files
add support for iOS Localizable.stringsdict files, used to handle plurals strings.
17 votes -
When updating translation terms via import, order them like in the imported file
Issue:
- Code changes / moving code between files changes the order of translation strings within the locally generated .po file(s)
- When updating the translation terms on poeditor.com via file import, new strings are added at the end of the list on the web interface, separating strings that contextually belong together
- When downloading the .po file with the translations from poeditor.com, we get a huge diff. Due to the different order of translation terms on poeditor.com, it's nigh impossible to see what has actually changed
- Same problem when re-generating the .po files locally after more changesProposed…
16 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 -
exporting comments?
why do you guys include the comments as part of the xml export? I understand the comments feature on the website for workflow purposes but once I'm ready to export the translated files the comments are unnecessary. Do others still find value in the comments being in the exported file? Could you make it an option to include comments in the export?
14 votes -
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 -
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 -
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 -
Sort keys/terms manually
Sort keys/terms manually to keep them organized.
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 -
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
- Don't see your idea?