Reference: <a class="ref" href="api/r[eferences]/pk:page">title, author, publishing house, year</a> (Each reference has an object in our db. We might replace the link by an URN urn:isbn:number in exports.)
Bible: <a class="ref" href="api/r[eferences]/pk:book:chapter:verse">title, publishing house, year</a> (Each reference has an object in our db. We could/should calculate the differnt verse counts automatically. We should provide a tool that interacts with an online bible resource in the translation language (DBP?) to show the verses quickliy in different editions. We should replace the href in exports.) See also: Reftagger using Bibleref. We should also give the user the option to open references in his Logos Bible Software like so <a href="logosref:Bible.Jn1.1">logosref:Bible.Jn1.1</a> (docs).
Page: <a class="page" href="api/(o|t)/id/p/page">page</a> In translation mode this should be invisible but you might choose to see it in reading mode. Will not be included by the translators but will be included automatically after a translation got printed. (We should adjust the href in exports with a custom html id, e.g. <a id="page_7" class="page" href="#page_7">7</a>.)
Footnote: <sup><a class="ftn" href="#fn1" id="ref1">1</a></sup> The footnote itself should be the next section(s) to translate (or better at the end of the chapter?). What do I write into the JSON tag field? p class="ftn", or just ftn? How do I know which sections are footnotes? And how do I know where a footnote beginns and ends? Maybe we wil have an extra db table for them.
Just suggestions:
<a class="url" href="protocol://domain.tld/path/file.ext">
<a class="ref" href="api/r[eferences]/pk:page">title, author, publishing house, year</a>
(Each reference has an object in our db. We might replace the link by an URNurn:isbn:number
in exports.)<a class="ref" href="api/r[eferences]/pk:book:chapter:verse">title, publishing house, year</a>
(Each reference has an object in our db. We could/should calculate the differnt verse counts automatically. We should provide a tool that interacts with an online bible resource in the translation language (DBP?) to show the verses quickliy in different editions. We should replace the href in exports.) See also: Reftagger using Bibleref. We should also give the user the option to open references in his Logos Bible Software like so<a href="logosref:Bible.Jn1.1">logosref:Bible.Jn1.1</a>
(docs).<a class="page" href="api/(o|t)/id/p/page">page</a>
In translation mode this should be invisible but you might choose to see it in reading mode. Will not be included by the translators but will be included automatically after a translation got printed. (We should adjust the href in exports with a custom html id, e.g.<a id="page_7" class="page" href="#page_7">7</a>
.)<sup><a class="ftn" href="#fn1" id="ref1">1</a></sup>
The footnote itself should be the next section(s) to translate (or better at the end of the chapter?). What do I write into the JSON tag field?p class="ftn"
, or justftn
? How do I know which sections are footnotes? And how do I know where a footnote beginns and ends? Maybe we wil have an extra db table for them.Corresponding Article