Added: New translations #752

已關閉
floreal 請求將 1 次程式碼提交從 floreal/translations-update 合併至 master
floreal 已留言 4 年前 (已從 github.com 遷移)

When building, new translations appear. This PR is here just to update translation files and update translations on crowdin.

When building, new translations appear. This PR is here just to update translation files and update translations on crowdin.
elegaanz 已留言 4 年前 (已從 github.com 遷移)

We usually do that only once before each release, but I can merge it if you want. Maybe our translation workflow is not ideal? And we should probably document it better…

We usually do that only once before each release, but I can merge it if you want. Maybe our translation workflow is not ideal? And we should probably document it better…
floreal 已留言 4 年前 (已從 github.com 遷移)

I don't know how Crowdin works, will merging it and sending translations through Circle CI delete al pending translations ?
If not, I think it's a good idea to send them before a release is made so that this could buy some time to translators to work before releases are made.
How other projects do that ?

I don't know how Crowdin works, will merging it and sending translations through Circle CI delete al pending translations ? If not, I think it's a good idea to send them before a release is made so that this could buy some time to translators to work before releases are made. How other projects do that ?
elegaanz 已留言 4 年前 (已從 github.com 遷移)

I don't really now how Crowdin works when you do that either…

I don't really now how Crowdin works when you do that either…
KitaitiMakoto 已留言 4 年前 (已從 github.com 遷移)

Hi, @floreal

will merging it and sending translations through Circle CI delete al pending translations ?

No, they won't delete any pending translations.

If not, I think it's a good idea to send them before a release is made so that this could buy some time to translators to work before releases are made.

@elegaanz said the reason why they merge translations just before new release:

We usually pull translations just before publishing a release, to avoid polluting the git history with repetitive commits.

How do you think about this?

In an aside, you can download pending translations from Crowdin once you create an account.

  1. Visit project page
  2. Select your language
  3. Open menu alongside file name: Screenshot from Gyazo
  4. Tap "Download" link

After that, you can replace po files with it and check translations on local app although it takes some time.

Hi, @floreal > will merging it and sending translations through Circle CI delete al pending translations ? No, they won't delete any pending translations. > If not, I think it's a good idea to send them before a release is made so that this could buy some time to translators to work before releases are made. @elegaanz said [the reason why they merge translations just before new release](https://matrix.to/#/!EQCycwwoFqVhWztkfh:disroot.org/$1587278737846KfPpi:disroot.org?via=disroot.org&via=matrix.org&via=bau-ha.us): > We usually pull translations just before publishing a release, to avoid polluting the git history with repetitive commits. How do you think about this? In an aside, you can download pending translations from Crowdin once you create an account. 1. Visit [project page](https://crowdin.com/project/plume) 2. Select your language 3. Open menu alongside file name: [![Screenshot from Gyazo](https://gyazo.com/f9d20d45f3624af1539091e1db81ae53/raw)](https://gyazo.com/f9d20d45f3624af1539091e1db81ae53) 4. Tap "Download" link After that, you can replace po files with it and check translations on local app although it takes some time.
KitaitiMakoto 關閉了這個合併請求 3 年前
無法重新開放此合併請求,因為該分支已刪除。
您也可以查看命令列指南

第一步:

在您的儲存庫中切換到新分支並測試變更。
git checkout -b floreal/translations-update master
git pull origin floreal/translations-update

第二步:

合併變更並更新到 Forgejo。
git checkout master
git merge --no-ff floreal/translations-update
git push origin master
登入 才能加入這對話。
沒有審核者
未選擇里程碑
沒有負責人
1 參與者
通知
截止日期
截止日期無效或超出範圍,請使用「yyyy-mm-dd」的格式。

未設定截止日期。

先決條件

未設定先決條件。

參考: Plume/Plume#752
載入中…
尚未有任何內容