Sebb

To be clear: if a release breaks binary compatibility, in Commons we change both the package name and the Maven co-ordinates.

Component has been marked dormant due to lack of activity

Component has been marked dormant due to lack of activity

Looks like the correct syntax requires square brackets: ```theme = ["github.com/theNewDynamic/gohugo-theme-ananke"]``` See https://github.com/theNewDynamic/gohugo-theme-ananke#as-a-hugo-module-recommended for all the details

I have only ever used IRC for members meetings. I suspect there is no longer a Commons IRC channel (if there ever was one), but I am not 100% sure.

Note that the README is automatically generated, so applying this patch may not work long-term

And all the README files regenerated (every time the plugin is subsequently changed) ... there has to be a better way.

As far as I can tell, none of the issue types are suitable. Which one should I use?

It would be a lot easier to raise website issues in the website repo, because one can then make use of the GitHub bug linking feature.

I think the issue may perhaps be caused by the following code: https://github.com/yob/pdf-reader/blob/6cc5c6663eb83c20ce5c43c06b3db716829ba969/lib/pdf/reader/page_text_receiver.rb#L117 Removing the SPACE check fixes the missing spaces on the second line of the 1st para for...