New submission from Jules Lasne email@example.com:
I've come to open this issue today because of the apparent split there is in the documentation about double spaces after a period.
Here is a link to an article explaining some of the issue https://www.writing-skills.com/one-space-two-full-stop
Anyway, the opinion isn't really important here but, when translating the documentation we waste a lot of time removing the double spaces that are ugly and useless in French.
I'd like to propose a PR to remove all double spaces after a period from the documentation as they serve no apparent purpose.
I'm open for discussion of course
---------- assignee: docs@python components: Documentation messages: 341977 nosy: docs@python, seluj78 priority: normal severity: normal status: open title: Double Spaces in the documentation
Julien Palard firstname.lastname@example.org added the comment:
Some people are liking the double space thing. Some are not.
It's in the documentation style guide  and there's arond 20k use of it.
I don't think we want to change it: modifing 18900 lines in the docs will make most opened PRs conflict, we don't want that. Also it'll pollute git blame a lot. Also it'll mark most translations as fuzzy in all languages, nobody want that.
You say it costs you time removing them from the translation, just don't remove them, and if you don't like them nobody will complain if you're not typing them both while translating.
---------- resolution: -> wont fix stage: -> resolved status: open -> closed