gettalong / hexapdf-website Goto Github PK

Hey! First of all, thanks for hexapdf and its extensive documentation!

tl;dr: Lato isn't being used, but if you happen to have Lato fonts installed locally, the website fonts are very thin.

While reading through the documentation I had the – subjective – impression that fonts were too thin.

I checked which fonts it used.

While this repo contains the Lato font files, it doesn't seem like they are loaded by the website. I happen to have them installed on my system so Lato ended up being used. I checked with different font-weights and here are some screenshots when I change the font-weight. On my system, 300 seems even thinner than 100.

100	300	400

Then I uninstalled Lato from my system to check, and indeed, it now renders better:

However as you can see, it doesn't render using Lato, but rather the System Font Stack that also GitHub uses.

So while this only renders wrongly on my system because I had Lato installed locally, perhaps the CSS should switch to only using system fonts or include Lato when loading the website. WDYT?

Hey! I was wondering if it's possible to have permalinks to the changelog of hexapdf. Currently, the link to the latest version is always https://hexapdf.gettalong.org/documentation/changelog.html#section. That is currently 0.22.0 (which is not in this repo yet btw), once e.g. 0.22.1 is released that link will point to #section again, while 0.22.0 will be #section-1.

It would be great to be able to link to specific releases. Not a big issues, since there's the CHANGELOG.md in the repo: https://github.com/gettalong/hexapdf/blob/master/CHANGELOG.md#0220---2022-03-26, but even that's not really permanent like GitHub Releases would be for example.

WDYT?

Hi! I'm evaluating HexaPDF for work and started adapting this example here:

which did not work for me, I got A PDF dictionary object needs a hash value, not a String (ArgumentError). Eventually I found field_value=(str) in the docs and get my test working.