Simplify translation process with Weblate

maicol07 I was talking only about Italian language - if you're able to translate extension to Italian by yourself, it is better to do that directly in extension and not rely on Weblate and language packs (there will always be a delay in adjusting language pack, and translators may not fully understand the context of specific phrases, so as an author of extension you may be more competent to translate them correctly). For other languages it is better to keep translations on Weblate and language packs, since you will not be able to verify them anyway.

But in any case I don't think it is a good idea to have duplicated translations both in extension and language pack. I'm not sure how Flarum merges duplicated translations for the same key, but there is always the risk that outdated translation will take precedence.

Translations for Flarum core and official extensions are updated for 1.0.0 on Weblate, so currently Flarum 1.x is a target. I'll keep old extensions for beta 16 for few months to give developers time to catch up. As always I recommend to use translation status pages to find which extensions are compatible and focus on them.

Justoverclock If by "reupload new translation files" you mean upload them to Weblate, then yes, you can always do that and you didn't have to wait for 1.0.0 release. But if you want to upload them directly to language pack, then bot will overwrite them again and 1.0.0 relase didn't changed anything in this matter - language pack will always be overwritten by state from Weblate.

Justoverclock Wait, what?! There are only few changes in core and official extensions for 1.0.0, you should be able to copy them from old commits. If you don't want to use Weblate, I can remove your language from Weblate and bot will no longer overwrite your changes, there is no need for separate repo.

Justoverclock I don't understand what you're trying to achieve. If you want to update your language pack for Flarum 1.0.0, then go to https://rob006-software.github.io/flarum-translations/status/it.html and complete translations for extensions with green dots (+ core and validation). That's it. Just don't translate directly in language pack and always do this through Weblate, then nothing will be overwritten by bot.

HINT

If you struggle with new ICU format for plurals, you can use https://format-message.github.io/icu-message-format-for-translators/editor.html to edit message and then copy result to input in Weblate. This editor provides syntax check and allows you to test translation (you can use "count" field to check how result will look for different numbers), so it should help you avoid basic mistakes.

DursunCan I contacted with you on Discord.

I improved attributing original translation author while exporting translations from Weblate to language pack. So far all commits in language pack were authored by bot, so from perspective of language pack repository, there were no info about who made particular changes. You had to check it in commit history of main repository.

Since now original authors are attributed using Co-authored-by trailer in commit message. Bot is still main author of the commit, but GitHub should detect and display you as an co-author of particular commit.
Detection of original author is really simple and may glitch in some edge cases (especially if you modify language pack repository directly), but it should work fine most of the time.

Example: rob006-software/flarum-lang-polish91c78c5

Littlegolden Yes, Apache died at night, I restarted it when I woke up, it should work right now.