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
正在加载...
这个人很懒,什么都没留下。