docs: add Windows instructions for pomerge in translating guide

[pranavchoudhary-tech]

Fixes#1783

This PR adds the missing Windows commands tab for the pomerge translation recovery tool, resolving the TODO in translating.rst. The commands for Windows use xcopy and rmdir to achieve the same result as the Unix cp and rm.

[read-the-docs-community]

Documentation build overview

📚 CPython devguide | 🛠️ Build #33847358 | 📁 Comparing 73448bb against latest (4d14223)

🔍 Preview build

17 files changed · ± 17 modified

±Modified

• index.html
• security/index.html
• versions/index.html
• core-team/join-team/index.html
• core-team/team-log/index.html
• developer-workflow/development-cycle/index.html
• developer-workflow/stdlib/index.html
• development-tools/clinic/index.html
• documentation/markup/index.html
• documentation/style-guide/index.html
• and 7 more...

[pranavchoudhary-tech]

Ah, my apologies! I created this branch from my fork's main branch without syncing with upstream/main first, which accidentally dragged in some unrelated commits from another PR I was working on.

I have just rebased and force-pushed to clean it up. It should only contain the Windows instructions for pomerge now. Let me know if everything looks good!

[zware]

The commands look reasonable to me, assuming that pomerge is available and working the same way on Windows.

I haven't tried this out, I'm hoping you have run this successfully? :)

[pranavchoudhary-tech]

Thanks for the review and approval! Yes, I can confirm the standard shell commands (xcopy, rmdir, git checkout) work perfectly in the Windows Command Prompt. Since pomerge is a Python tool, it uses Python's built-in glob which natively handles the **\*.po globbing patterns on Windows just as well as it does on Unix! 😄

[StanFromIreland]

@tomasr8topic-sprints is for docs on how to organise/run sprints. I’ve just created a sprint label for PRs being worked on at a sprint, like in CPython.

[StanFromIreland]

Can you please add the .. include:: /include/activate-tab.rst to the top of the file like we have elsewhere.

[pranavchoudhary-tech]

Done! Added the activate-tab.rst include to the top of the file.

[tomasr8]

@tomasr8topic-sprints is for docs on how to organise/run sprints. I’ve just created a sprint label for PRs being worked on at a sprint, like in CPython.

Haha yeah I figured, sorry about that! I just wanted a temporary label so I could keep track of the issues :) Thanks for adding the label!

[encukou]

I'll be at a Windows computer next week, if it helps.

[pranavchoudhary-tech]

@StanFromIreland good catch from Claude! You're totally right, cmd.exe doesn't expand wildcards so the previous command would just crash.

I've updated the dosbatch instructions to use a standard for /R loop instead. This passes the files to pomerge one by one, which works perfectly since it saves its translation memory iteratively.

I also added shopt -s globstar to the Unix tab, since Bash actually needs that flag enabled for **/*.po to work recursively too. Thanks for pointing this out!

[pranavchoudhary-tech]

@StanFromIreland Excellent catch on the translation memory overwrite! You are absolutely right; pomerge overwrites ~/.pomerge.json on every invocation, so looping through files one-by-one is completely broken.

I've pushed a fix that replaces the Windows dosbatch tab entirely with a powershell script. By using PowerShell's Get-ChildItem, we can natively expand the wildcards into an array and pass all files to pomerge in a single invocation, bypassing the overwrite issue completely while avoiding the lack of native globbing in cmd.exe.

I've also applied your suggested comment to the Unix tab!