The thing is that each UI decision depends on countless other UI decisions. A simple example is keybindings. On UNIX/Linux, it’s nearly impossible to pick reasonable default bindings for global desktop navigation because they all conflict with bindings that some app is using. On Windows, the desktop navigation bindings are hardcoded, and no app uses them, because apps know for sure which bindings to avoid.

It is optimized for building complex, data-dense web interfaces for desktop applications which run in modern browsers and IE11. This is not a mobile-first UI toolkit.

I'd also try opening the .svg file in Scribus and outputting to pdf from there. You've got more output settings, can handle bleed and add printers' marks etc.

one wonders about the relationships between scholarship, technology, and the academic institution that engendered that turn from printing materials to printing ideas.

as the software that defines digital content creation for the next decade.

the possibility of exporting comments from an on-line Hypothes.is application to a desktop application (which could be an extension of the pdf viewer) and back, might be a crucial point for the further development of hypothes.is.