@adrianliaw I'll keep working on this PR but I need permission to push changes on this branch. Can you grant me the write permission of this repo? or do you prefer me to create a new branch/PR from this branch for syncing?

Currently, the PR created by the github action does not trigger another workflow (e.g. CI pipeline). One of the workaround is simply close and reopen the PR.
See #107 for details.

It's solved by #108

@adrianliaw I believe this PR is safe to be merged now since

• I add several commits for clearing the fuzzy entries induced by syncing with CPython
• Improve current GitHub action workflows #107 is solved and made this PR has passed CI check

The copyright.po had been handled on #93 and merged today.
The sphinx.po had been handled on #99 (not merged yet), and I found that the version tags in your sphinx commit seem not synced with the cpython. May need further review.

@StevenHsuYL Would you please point out which line is not synced?

In your sphinx.po file, below msgstr...
"Python 3.10 (in development)"
"Python 3.9 (pre-release)"
"Python 3.8 (stable)"
"Python 3.7 (stable)"
They're not synced with the official doc page (https://docs.python.org/zh-tw/3.9/).

By the way, I found that this section (version tags) is not "translatable" by checking doc homepages in all other languages.
(https://docs.python.org/ja/3.9/)

@StevenHsuYL
These version tags are translatable as other source strings and they're synced with python/cpython on the 3.9 branch, but the sidebar on docs.python.org are overwritten when building the docs (see the source code in python/docsbuild-scripts). That's why we cannot find the translated version tags.

@mattwang44 Thanks or reply!
I also found out that the version statuses in the sidebar were defined here in docbuild-scripts.
Should our sphinx.po file sync with these definitions as well?

But as you said, it would always be overwritten, so maybe this part is not very important in our translation project... 🙄

@mattwang44 Thanks or reply!
I also found out that the version statuses in the sidebar were defined here in docbuild-scripts.
Should our sphinx.po file sync with these definitions as well?

But as you said, it would always be overwritten, so maybe this part is not very important in our translation project... 🙄

I think the current version is fine and we can just leave it 👍🏽.