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 #33647673 | 📁 Comparing 01ee673 against latest (4d14223)

  🔍 Preview build  

2 files changed

± versions/index.html
± documentation/translations/translating/index.html

[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]

@tomasr8 topic-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.

[StanFromIreland]

I can't test this, and I don't really know anything about this (hence the TODO note ;-), but I asked Claude to check for me and it said:

The command relies on the shell to expand ***.po into an actual list of files, but cmd.exe never expands wildcards and pomerge doesn't glob its arguments itself, so pomerge receives the literal pattern string and crashes trying to parse it as a PO file.

Is this correct?

[tomasr8]

@tomasr8 topic-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!