Thread: Best way to do italic and bold
View Single Post
Old 04-04-2016, 03:04 AM   #89
fbrzvnrnd
Fanatic
fbrzvnrnd ought to be getting tired of karma fortunes by now.fbrzvnrnd ought to be getting tired of karma fortunes by now.fbrzvnrnd ought to be getting tired of karma fortunes by now.fbrzvnrnd ought to be getting tired of karma fortunes by now.fbrzvnrnd ought to be getting tired of karma fortunes by now.fbrzvnrnd ought to be getting tired of karma fortunes by now.fbrzvnrnd ought to be getting tired of karma fortunes by now.fbrzvnrnd ought to be getting tired of karma fortunes by now.fbrzvnrnd ought to be getting tired of karma fortunes by now.fbrzvnrnd ought to be getting tired of karma fortunes by now.fbrzvnrnd ought to be getting tired of karma fortunes by now.
 
Posts: 559
Karma: 400004
Join Date: Feb 2009
Device: ONYX M96
Quote:
Originally Posted by BetterRed View Post
What you're describing seems to be a lot like the margin notes I have some in multi volume leather bound editions of Macaulay and Gibbon, published early 20th century. They are short explanatory notes/reminders, quite distinct from footnotes and references. I don't have the books here, however I have a vague recollection the margin notes are indexed by their keyword/phrase - headword index is ringing a bell, and of course they both have a massive normal index - the references, notes and index for the Macaulay is an entire volume.

BR
Thank you, I'll take a look on internet for this. Btw I remember some medieval books with something similar you are talking about.
Anyway, the basic concept is: you are working with a digital document. Not an ebook. A ebook is a product of our digital product. You can (if you want oblivious) add more informations: you can add informations that are non-readeable from the user, but that could useful for you to end the ebook, or could be useful to add another way to access the content. Often we work on digital XHTML that will be ePub2, CMYK printing, website. The digital content has got a lot of informations I could use. A plain example: if I use the xml:lang attribute the user maybe do not see it: but a screen reader could change the voice for the right language, or a PDF render could use the correct hypenation for it.
When you meet an italic you don't have to use <i> as a robot, but ask yourself: "ok, in this paper book the author need to say something and use italic. Why? What he was going to formalize with a italic? Oh, it is a latin sentence, so <em xml:lang="la">quod erat demostrandum</em> is the correct way to handle it. Umh, maybe I can do a javascript to translate this for non-latin readers, so I can do <em xml:lang="la" title="what we had to prove">quod erat demostrandum</em>". And so on. Maybe, tomorrow, a scholar need to extract all the latin sentence from a book for a school thesys, or your publisher want to add a glossary terms section, during the work.
Last edited by fbrzvnrnd; 04-04-2016 at 03:59 AM.
fbrzvnrnd is offline   Reply With Quote