Asbjørn Ulsberg

This is related to #8. The current algorithm is a bit naïve and should probably rather be based on [the definition of an XML Name from the XML specification](http://www.w3.org/TR/xml/#NT-Name).

Ah, I see. Then [the definition Text in the XML specification](http://www.w3.org/TR/xml/#dt-text) might be of help.

Magnificent, @EliotJones! The only problem I have left is that sentences are broken differently on Mac and Windows. But I don't expect PdfPig to be able to do anything about...

I created #449 for the line break issue. Also, I thought that it may be more extensible and flexible if `bool ReplaceWhitespaceWithSpace` instead was `string ReplaceWhitespaceWith`, so the replacement character...

Thanks for the response, @EliotJones. If you take a look at the PDFs I sent you, I believe the text is actually in different places in the source PDF as...

As the accompanying issue #2454 is closed with a workaround, is this PR relevant anymore?

> I'm just wondering why we are not separating this two aspects and make it configurable. For instance we can introduce a new property with the name VersionInBranchNamePattern="{Major}.{Minor}.{Patch}^" or VersionInBranchNamePattern="{Major}.{Minor}^"...

Resolved by https://github.com/Homebrew/homebrew-core/pull/113622.

I believe #3190 touched upon many of the same files as this PR. Can you please rebase and assess whether this PR is relevant and needed anymore?

Could perhaps a `Link` header be used to disambiguate the two use-cases? ```http Link: ; rel="latest-version", ; rel="memento" ``` The chosen link relations are probably not appropriate, I just picked...