@StevenHsuYL I noticed that several new source strings are added after this PR is opened. Would you mind also translating them?

noticed that several new source strings are added after this PR is opened. Would you mind also translating them?

Of course not! Could you point out the newly added source strings?
BTW, I have also updated the "masOS" term here, which was updated in cpython on Sep, 23 byGH-28515.

Of course! Could you point out the newly added source strings?

You can refer tothis link for the untranslated source strings inlicense.po.

BTW, I have also updated the "masOS" term here, which was updated on Sep, 23 by GH-28515.

Yeah I've noticed that you discover the modification in CPython and made the change in advance! That's pretty nice! I just want to mention that we have aGitHub Action workflow checks if any string in CPython is modified and sends a PR if so (such asthis PR also handles the changes ofmacOS terms). So we probably do not need to spend effort on checking CPython doc from now on!

Of course! Could you point out the newly added source strings?

You can refer tothis link for the untranslated source strings inlicense.po.

I did. I found these three "untranslated" sentences had already been translated in theabove codes,
Therefore, they're "redundant" source strings.

BTW, I have also updated the "masOS" term here, which was updated on Sep, 23 by GH-28515.

Yeah I've noticed that you discover the modification in CPython and made the change in advance! That's pretty nice! I just want to mention that we have aGitHub Action workflow checks if any string in CPython is modified and sends a PR if so (such asthis PR also handles the changes ofmacOS terms). So we probably do not need to spend effort on checking CPython doc from now on!

Great! It's excellent that we can sync with CPython automatically!

aw, i got it!
I'll take those string down if needed. Thanks again for your effort!