Kunda, can you please tell us the main advantage of such functionality? What should happen after you switch from Crowdin to GitHub? It's just for checking whether translation was exported fine?
Commonly repos are private, so you translators don't have a direct access there. They might see 404 page quite frequently
Since the recent time, they should work and won't be intercepted
Yes, did you try Cmd+Space on Mac or Ctrl+Shift+Space or Alt+0160 on Windows?
Personally, I love the idea. You don't need to see all translations unless you're the project manager or you want to make sure that specific term is also not translated into other languages.
Meantime, there is already a solution to make things easier: add Croatian, Montenegrin and Bosnian language as preferred ones in the profile settings:
This way, you languages will be always shown on top of other languages. Of course, languages won't be shown if they don't exist in the project ;)
Let's keep this idea open and collect votes. It was UX designers decision, since according to the statistics Activity tab was not used so often, it's not a tool for daily usage.
If you want to know what was happening around projects you're working on, you may setup any RSS client on your machine (there are many browser plugins) and track Activity URL there. For example:
The Language Activity feed was not removed completely, it was just re-designed to simplify the work for the project managers first of all. On the project page, you can click the Activity feed and there you can specify your language.
You already can add as much proofreading steps as necessary using the Advanced Workflows feature:
No problem, updated the status of idea and let's see how many votes it will collect :)
Though I must admit this is proofreader's job to fix translations (add new ones, improved) and approve them afterwards.
The possibility to forbid proofreaders to translate the untranslated strings might be useful in rare cases, but it's not very common workflow. Also usually proofreaders indeed just review existing translations and don't touch untranslated strings because they're not asked to perform translation ;)
Well, voting might be helpful here instead of proofreading. Translators can vote for translations made by others but cannot upvote / downvote their own translations. :)
Seems it's the best and easiest workflow
Yes, proofreader on the 1st step will approve translations first (it might be even your translator) and another person (e.g. "Final Proofreading" role) will verify approvals made on the step #1. Translations will be considered as fully approved once proofreading on the step #2 is done
Not sure if this approach will work. Some strings in English may be untranslated as well. Consequently, you will acquire 3 languages in exported file: target language, English fallback, French source.
There is alternative solution, but it requires 2 projects to be handled:
1) French to English project;
2) You extract translated strings from the first project, then create another one (English to Other Languages) and upload English texts for translation. In result, you will always have English as a fallback language in exported files.
Hmm, that's quite interesting and I totally understand your main problem. :)
Did you try to activate the "Skip untranslated strings" option in the project settings? This way, French texts shouldn't be included for untranslated strings in the target language.
Mostly projects on Crowdin are localized from English into other languages, so switching the fallback language might be not useful for everyone. Anyway, we keep collecting the votes and feedback for this request and it might be implemented in the future updates.
What if English is not fully localized? We will need to mix French + English texts, it might confuse end-users of your app even more.
The most common approach when the source language is not English is the following:
1) Localize from your base language (e.g. French) into English in one project;
2) Upload these English translations to another project and use these files as sources to localize from English into other languages.
In active development, should be announced soon
The fourth form is applied to few cases which are not common in apps. In order to prevent any confusion, the fourth form is ommitted and translators should process three forms only:
one: 1 день
few: 2 дня
other: 5 дней
The same behavior is applied to Ukrainian language.
In English, there are only 2 plural forms (one / other), the other plural forms (e.g. zero/many/few) would not be imported.
Thanks for your idea!
You already can allow your translators to download files for translation in XLIFF file format, just enter the project settings -> switch to "General" tab and activate "Translators may download files to their computers" option.
The possibility to export translations in CSV probably would be implemented for translators as well.
Thanks for submitting your idea. It will be implemented in case it will get much voices. We must admit that many users got used to American flag, so British flag may confuse them a little bit.
Thanks for all your suggestions, probably we'll consider to change the English flag in next UI update. :)
Kindly note that top voted suggestions which are not approved yet are always used while export, so there is nothing to worry about for project managers.
> Option to filter strings which were translated by another user(s).
This option is already available. Click on the "Filter" button on translation page -> choose the "Custom filter..." option -> check the option "translated by user" and enter translator's username in the field -> click "Filter" button to view all the strings translated by certain user.
Tip: In order to simplify the search, click the "Project" head menu on translation page -> choose "All strings" option -> apply the custom filter.
Thanks for your time sharing a feedback. It sounds quite reasonable.
In case your idea will get much votes, it might be implemented!
Thank you for making Crowdin better, we highly appreciate it.
Thanks for your feedback, we really appreciate it.
In case your idea will get much votes it might be implemented by our developers team.
Feel free to share any ideas you might have. Thank you.
By default Crowdin considers changed strings as new. If you've fixed a typo in source string you can preserve translations while updating source file(s).
Let me suggest you the best workflow to use this handy tool:
1) Before updating source files we recommend you to approve translations for strings you've modified in source file;
2) While source file update via Crowdin UI, "Changed strings in the new file version" dialog will appear. Mark strings for which you'd like to preserve translations -> click the button situated on the right to "Preserve translations for selected" and choose "Preserve translations and remove validations" option. Afterwards, click on this button. You may see the screenshot:
If you're using API to update source files, you can use the following parameter:
It makes the same as mentioned above. Let me suggest you to read this documentation to find out more:
I will appreciate to know that this method resolves your issue, so I will mark this idea as "Completed". :)
All of the translators in the project are able to vote for project translations. There is no defined limit that will get the suggestions approved.
Only proofreader (the person that is responsible for suggestions approval / disapproval) can approve translations. In case the project does not have proofreader, translations with a the biggest number of votes are getting to the final version of translated file.
In order to complete translation it should be fully approved by proofreader. Translation progress for each language is displayed on project page (% translated / % approved).
Hopefully I clarified a bit.