49 results found
-
When importing and Poeditor reports obsolete terms, the report should include context
When I import terms from a .pot file, POEditor detects obsolete terms. However, the report does not include the context so it is very difficult to find out which term is the obsolete/duplicate one.
Please add context information to the report.
1 vote -
Markdown preview not working?
Read about it in the docs but cant get it to work. The term is recognized as context:markdown but I dont get the preview icon?
4 votes -
Add Terms returns Error
I used the example curl on the Add Terms endpoint and it responded with :
{"response":{"status":"fail","code":"4042","message":"Data should be JSON"}}
I updated it to use JSON and then it responded with:
{'response': {'status': 'fail', 'code': '4012', 'message': 'No data sent using POST method'}}
Is this endpoint failing?1 vote -
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 -
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 -
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 -
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 -
Screenshot Attachments
Dear POEditor Team,
we are very happy with the current POEditor solution. But there is one Feature we are missing: Screenshot Attachments. It would be much easier to handle all our IDs if we could add a screenshot in addition to a comment. With screenshots the context would be much easier to understand.
37 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 -
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 -
GLOSSARIES
Ability to define a glossary of terms that can be applied across multiple projects. Glossary items should have part of speech and a description that tells the translator how this term should be used. Would be helpful if translator could look up terms in the glossary while translating terms in the main interface. While using poeditor to translate new terms, suggestions would be provided based on Glossary items. Google Translator Toolkit has a custom CSV format that could be used for importing and exporting glossaries http://support.google.com/translate/toolkit/bin/answer.py?hl=en&answer=147854 Pootle has a mechanism to generate a list of frequently appearing terms as a…
23 votes -
Overview of imported new translations vs obsolete ones
When importing a po file I'm notified how many new terms have been added and am given a list of obsolete terms. It would be great to have a dual window to see, how many terms are actually new and how many terms have just been corrected. It's a hassle to compare them manually and then copy paste translations form an old term to a new one, which is basically the the same with maybe a minor spelling error fixed.
1 vote -
Change nickname
Can i change nicknames, for my information? I have to much contributors.
2 votes -
Polish translation
I would like to translate webui to Polish, please, add this language to the project.
1 vote -
Wrong nplurals on Russian language
Poeditor export Russian PO files with 4 nplurals forms and it's wrong.
Unicode website explain that Russian has 3 nplurarls form like the form:
nplurals=3; \
plural=n%10==1 && n%100!=11 ? 0 : \
n%10>=2 && n%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2;The compilation fail. Can you fix this bug as soon as possible?
Thanks you.
** We're blocked while the bug exists.
1 vote -
CSV export problem
CSV is not exporting in UTF8 as it should. This is major failure.
1 vote -
xml:space="preserve"
Hi I noticed that after fetching the xliff file from PoEditor, it contains
xml:space="preserve"
whit some \n inserted. This breaks a lot of stuff on our side.How can we avoid it?
Angel
1 vote -
Terminology
Your terminology is unclear. For example what is a "string?" What is a "contributor?"
1 vote -
Problem with strings with context
If I try to import POT file into POEditor that has the same string appearing twice, the import fails. But, these same strings have different contexts, so technically they are not the same string, and POEditor should check if the string and the context are duplicated, not just the string. When the same POT file is imported into WordPress GlotPress plugin, it works as expected, POEditor fails.
1 vote
- Don't see your idea?