NIniutech·Jan 27, 2024
There is Bene ePub reader running in web browser: https://github.com/nota-lang/bene/ - demo: https://nota-lang.github.io/bene/
In Portable Web Documents – An Alternative to PDF Based on HTML5 (2019)nota-lang
bene
TypeScript2024–2024
nota-lang / bene
bene
An EPUB Reading System
2Distinct people
2Mentions
1Explicit recommenders
229GitHub stars
What to know before exploring
What it is
An EPUB Reading System
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
I really like this proposal. Just last night, I was reading an EPUB of The Hobbit and clicked on a footnote, which instructed me to refer to page 24. It turned out that it…
sotix used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by hour2 dated mentions
Observed mentions: 2024-01-26 18:26:48 UTC to 2024-01-27 02:32:43 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Jan 26, 18:00 | 2024-01-26 18:00:00 UTC | 2024-01-26 19:00:00 UTC | 1 | 0 | 1 |
| Jan 26, 19:00 | 2024-01-26 19:00:00 UTC | 2024-01-26 20:00:00 UTC | 0 | 0 | 0 |
| Jan 26, 20:00 | 2024-01-26 20:00:00 UTC | 2024-01-26 21:00:00 UTC | 0 | 0 | 0 |
| Jan 26, 21:00 | 2024-01-26 21:00:00 UTC | 2024-01-26 22:00:00 UTC | 0 | 0 | 0 |
| Jan 26, 22:00 | 2024-01-26 22:00:00 UTC | 2024-01-26 23:00:00 UTC | 0 | 0 | 0 |
| Jan 26, 23:00 | 2024-01-26 23:00:00 UTC | 2024-01-27 00:00:00 UTC | 0 | 0 | 0 |
| Jan 27, 00:00 | 2024-01-27 00:00:00 UTC | 2024-01-27 01:00:00 UTC | 0 | 0 | 0 |
| Jan 27, 01:00 | 2024-01-27 01:00:00 UTC | 2024-01-27 02:00:00 UTC | 0 | 0 | 0 |
| Jan 27, 02:00 | 2024-01-27 02:00:00 UTC | 2024-01-27 03:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
2 sourcesI really like this proposal. Just last night, I was reading an EPUB of The Hobbit and clicked on a footnote, which instructed me to refer to page 24. It turned out that it meant page 24 of the printed edition of the book, which was in the first chapter of the book. Page 24 in the EPUB was still part of the prologue. So I had no idea which page it was referencing. As it stands, my Kobo has an increased font size, so I notice that I can flip the page a few times and still be on page 4 before it finally turns to page 5, which I assume is referencing the pages of the written text. This is a nice compromise, but doesn't solve the issue with the hard coded footnote being misleading.
I wonder if we could instead look at religious texts such as the Bible (e.g. John 3:16) and code editors (e.g. Ln 4, Col 12) for referencing locations in reflowable
Read the rest
text. The same way you can jump to a footnote in a document should allow you to have an actionable reference to a specific location anywhere in the text. But I don't think the text should be stylized like how the Bible has the numbers (e.g. 16) scattered within the text itself. Those should probably be hidden within the text and leave the reading software to display the first line number of the page down at the bottom instead of the page number. That might look like "4" the same as it currently does, but this 4 references a section of the text rather than a page number. Perhaps it could be togglable for greater detail and display word 23 of section 4 as "4:23". Or maybe it could consider the chapter too. For example, chapter 2 section 4, word 23 would look like "2, 4:23". This might get funky in a Terry Pratchett novel, but it would hopefully allow for easier discussion of exact parts in a document and significantly easier linking.
I love the interactive code example for marking up The Rust Programming Language. That gets at what I was saying above although is more targeted at a document than referencing parts of a novel.
Kudos to author for creating Bene[0] as part of this proposal. That was cool to discover I was using their tool to read the proposal itself!
[0] https://github.com/nota-lang/bene/