rhythmvs

8 ms·

31.
by rhythmvs 10y ago
I guess we should take a better look at something like http://www.pangloss.com/seidel/Poem/ or http://rhymeless.hamiltonulmer.com and implement some rhyming name generator to add to our app :-) Just ki
32.
by rhythmvs 10y ago
That’s why we also have Pride and Prejudice on offer ;-) And soon enough, you’ll be able to write your very own greatest love story, and have it typeset and published with our typographic design engine. As You Like It :-p
33.
by rhythmvs 10y ago
That’s exactly what we are building. And self-publishing authors are at the center of our focus. I hope we will indeed ‘get it right’. I can tell you, it’s not something so trivial as ‘put a fancy GUI on top of LaTeX’. Instead, we are dev
34.
by rhythmvs 10y ago
Definitely! This is but a sneak preview for our upcoming product, which powers this whole search/replace/print spin-off: a typographic intelligence engine, which analyzes arbitrary text input, and then designs, templates and types
35.
by rhythmvs 10y ago
We have tested cross-browser behavior on most common platform combo’s. Which version of Windows + Firefox are you on? Care to tell what you see more specifically? I know there’s still an unresolved issue with the <picture> element on
36.
by rhythmvs 10y ago
Happy to hear you love our work! You’re right: we don’t html-sanitize user input in the form, so one can indeed do some colorful hacks and put in some easter eggs. <i style='color:pink;font-family: cursive;'>Darcy<&
37.
by rhythmvs 10y ago
You mean you expected “James’ faithful wife” but got “James’s faithful wife” instead? We could implement it your way, but since – as far as I know – grammar rules* diverge (allowing both orthographies), we opted for the uniform application
38.
by rhythmvs 10y ago
Thanks a lot! We’re working on the input issue you mention.
39.
by rhythmvs 10y ago
Hi, OP here! Multilingual support is core and center of our development. We do a lot more than accents, and go great lengths to make all of our stack, Unicode-based. That means ES6 regexes, up to designing and developing our own fonts. If t
40.
Show HN: Personalize Romeo and Juliet or Pride and Prejudice(textusclassics.com)
56 points by rhythmvs 10y ago|36 comments
41.
by rhythmvs 10y ago
I believe it a good thing that the EPUB standard will henceforth be further developed by and within the same body that develops the standards on which EPUB relies. After all, EPUB is “stripped down html5” anyway. As a developer of Web-based
42.
IDPF, EPUB Standardizing Body, Has Combined with W3C(idpf.org)
131 points by rhythmvs 10y ago|46 comments
43.
Flawless Typography Checklist(typographychecklist.com)
1 points by rhythmvs 10y ago|1 comments
44.
by rhythmvs 10y ago
PhD History of Art, BA Typography, art school degree graphics
45.
Show HN: The Polyglot Bible Typography Project(dodecaglotta.com)
9 points by rhythmvs 10y ago|5 comments
46.
by rhythmvs 10y ago
Besides what looks like a well-executed writing and reading experience on e-paper (at last…), the live syncing of sketching looks especially promising (as shown in the video).
47.
10.3-inch reMarkable Paper Tablet and eReader(getremarkable.com)
6 points by rhythmvs 10y ago|6 comments
48.
by rhythmvs 10y ago
But then again, by what number did opensource and package managers decrease the clerical workload? — Sure, if we’d not only consider machine architecture, language design and compile times, but add social factors to the equation, like ecosy
49.
by rhythmvs 11y ago
Related discussion on the CommonMark (markdown standardization initiative) forum: http://talk.commonmark.org/t/ietf-request-for-input-text-mar...
50.
A jazzy 1972 history of the computer [Eames video](aeon.co)
1 points by rhythmvs 11y ago|0 comments
51.
How to run a web application when JavaScript is disabled(glebbahmutov.com)
5 points by rhythmvs 11y ago|0 comments
52.
by rhythmvs 11y ago
That’s exactly the sort of use case we are focussing on and building our automated typesetting service for.¹ You’ll probably also benefit from file inclusions so that you can keep a library of text snippets, with variables, keeping them ver
53.
by rhythmvs 11y ago
Thanks! And yeah, if people would only know their history… Relatively new, to me, unfortunately, means that lightweight markup still is not something which the broader public is familiar with, not even by its proxy brandname “Markdown”, ev
54.
by rhythmvs 11y ago
You are right. But “markdown” — not the brand, but the concept of lightweight markup — is a work in progress still. Just look at the list of “feature requests” on the CommonMark forum.¹ Pandoc’s Markdown supports lots of extra features from
55.
by rhythmvs 11y ago
Relative to widespread brand recognition, I guess, and relative to similar initiatives. But indeed, Markdown — as in, the concept of _lightweight markup_ — predates the Web and is at least as old as Usenet. I footnote 9, I linked to my Gith
56.
by rhythmvs 11y ago
Though they are linked, see e.g. http://rhythmus.be/md2indd/#fn2 — it’s Pandoc after all, which creates those ;-) The wide margins are due to typography best practices, which dictates between ~50 and 70 characters on a
57.
by rhythmvs 11y ago
At the time of writing my article cited above, I didn’t yet came across this one: [Sustainable Authorship in Plain Text using Pandoc and Markdown]( http://programminghistorian.org/lessons/sustainable-authorsh... )
58.
Sustainable Authorship in Plain Text Using Pandoc and Markdown(programminghistorian.org)
1 points by rhythmvs 11y ago|0 comments
59.
by rhythmvs 11y ago
Kudos for this great, yet simple and lean toolchain! Anyone familiar with command line tools and a corresponding aversion for bloated WYSIWYG apps will second the underlying idea that MS Word (and the likes) “should die” in favor of plain t
60.
From Word to Markdown to InDesign: Fully Automated Typesetting Using Pandoc(rhythmus.be)
114 points by rhythmvs 11y ago|41 comments

More ›