Disregard occurrences of "." while backing up

[ptkato]

Fixes #7806.

---

Please include the following checklist in your PR:

• Patches conform to the coding conventions.
• Any changes that could be relevant to users have been recorded in the changelog.
• The documentation has been updated, if necessary.

[Mikolaj]

Is it easy to add the offending example as a test? I guess we don't need a changelog, because in 3.8 we both introduce the bug and fix it?

[ptkato]

It is, I'll add it as a test; Adding a test for that will take a bit of extra effort that I don't think that would fit in this PR proper, considering how FileCreators is laid out; also that's how I've been dealing with changelogs, since the feature + the bugfix will be in the same bag.

[andreasabel]

Please can we make it a habit that fixes come with a regression test?

[Mikolaj]

A compromise we might have is to create a new PR that extend the testing framework and adds the test (marked as failing) and afterwards we could rebase this PR and see that the test passes (and unmark it). Any volunteers?

[ptkato]

@Mikolaj, uh, I volunteer, though I intended to proceed like that anyway.

[Mikolaj]

@Mikolaj, uh, I volunteer, though I intended to proceed like that anyway.

Great minds think alike. :)

But I'm just confirming here, in particular for Andreas, who is not on Matrix/IRC, so didn't hear our conversation about this.

[ptkato]

Okay, the test is now in place. Any other paths that would be deemed invalid?

[Mikolaj]

@andreasabel: I know you are busy right now and I think your feedback has been addressed, so if you don't object (in time), I will take the liberty of dismissing your review block. But we would love to hear any fresh feedback, of course. :)

[ptkato]

@Mikolaj, @andreasabel, I believe this is good to go, yes?

[Mikolaj]

Yes, it is, but we need one more review.

addressed AFAIC

[Mikolaj]

@tchoutri, @Kleidukos: thank you! Let's get this beast merged.