malodyets
What would HN folk love in a browser?
+ almost as efficient as base64 + no special characters + no padding characters
https://svnbook.red-bean.com/en/1.7/svn.advanced.externals.h...
Rules here: https://en.m.wikipedia.org/wiki/Public_domain_in_the_United_...
Extended copyright harms the public domain, but the only realistic solution is for authors or publishers to believe in the common good more than their own profits. That does happen: Wikipedia for example is licensed under CC-BY-SA. But then you have Jimmy Wales pleading for donations regularly. Authors and publishers depend on copyright for well deserved income. In the US the balance of interests has swung so far away from the common good toward the author’s and publisher’s interests that for example interesting parody literature like The Wind Done Gone (a parody of Gone with the Wind having the same characters) are suppressed.
The Structure of Scientific Revolutions is one of the best books I ever read.
Multiprocessing on Python works great and isn’t even very hard if you use say async_apply with a Pool.
Comparing single-threaded Python with multiprocesssing in Language X is unfair if not disingenuous.
The vast majority of print-interior typesetting is being done with Adobe InDesign.
Some publishers (still) have their own system that does not use Word styles - usually using ASCII tags inserted into the content. These are often legacy approaches dating from the 1980s, but if it works why change it?
A few have begun to use Markdown-based systems, but this is very rare in commercial publishing.
The vast majority of author-to-editor-preproduction workflows are done in Microsoft Word. Some publishers (including the one I worked for, and the ones I work with now) use Word styles for all content formatting. Part of the editorial "pre-production" task is to take what authors give us (font formatting with bold / italic, paragraph formatting with returns and tabs) and convert it to styles.
The ones that your community is using.
The ones you enjoy.
Here’s my setup with Zola: https://seanharrison.org/postgrails/20200523-got-zola/
A couple notes about setting up DNS since the gitlab instructions weren’t 100% clear to me: https://seanharrison.org/postgrails/20200720-gitlab-pages-dn...
XML might not be the best format for everything, and I for one am glad to use other formats for simple structured data. But when it comes to representing complex content, there is no other format that even comes close to being as useful and usable.
* All digital publishing of ebooks uses XML inside ZIP files.
* All contemporary mainstream word processors (Word, LibreOffice) use XML inside of ZIP as the basic file format.
* Automatic customized conversion processes from Word to InDesign or from InDesign to EPUB use XML at the heart.
* Let’s not forget the web itself, which is still mostly SGML in the form of HTML. Not XML per se, but only different in the details.
Not only is XML the only practical serialization format for working with publication content, but the presence of mature schema tooling is intrinsic to making publication automation robust in a given context.
I’m very glad for JSON and JSON schema in the domain of APIs. But in the domain of content data, it’s all XML.
Every serialization format has a domain for which it is most appropriate (whether or not it is the best choice in that domain.)
I’m really liking the shape of nested text for the domains in which I would have used YAML.