I suggest to change the PR title to make it clear it's about the docs.

I'm -1 on this..po files are not very friendly for reading by people, and are designed as a translation format mapping source to translated strings. I similarly see little value in 'show source', as the reStructuredText source is so unlikely to be useful (some themes have replaced this with a link to the source on GitHub, but I'm still unconvinced).

A

I often use "show source" when I want to check, well, the source, for example if there's something amiss.

If there's a translation that's missing or fixing, is the .po file the file that needs editing? If so, this would make it easy to click through and make a quick PR.

Hugo already mentioned the main point.

Another thing is the current „show source” button is useless in the translations as it is the English source.

This will contributions as it is easy to find where the files are as the repo is not linked anywhere else in the docs!

And also, Adam, you don’t have to worry about seeing it :-)

I personally use "Show source" very rarely. But I think "Show translation source" would be as useful as "Show source" is, for translated content.

Is there anything else left to do here@hugovk ?

Friendly ping, so that we can get this in.

Adam is -1, let me check in with him. We're not in a rush to get this in before the beta feature freeze, it can also go in after and be backported.

If there's a translation that's missing or fixing, is the .po file the file that needs editing? If so, this would make it easy to click through and make a quick PR.

That question wasn’t answered directly (assuming it wasn’t just rhetorical). Yes, the .po file should be edited in case of a missing or incorrect translation. That’s a good point—using PR-based translation workflows, this should be a convenient change.

We could usePlausible custom events to track the usage of the show source link. Though it looks like it would require changes in both theme and the show source customization in the CPython's repo.