In general, this would be a beefed up version of the current footnote management: in the same document, numbering automatically. PLUS you can chose if it is a footnote or an endnote of the chapter.
But it would still not allow to decide in total
- if you want footnotes or endnotes for chapter OR book
- if you want numbering per chapter OR numbering for the entire book
Is this correct?
To leap into the complete solution, I don't see how footnotes can work without being managed separately in a database.
--
Micz Flor
Co-Founder and Director, Sourcefabric
micz...@sourcefabric.org
www.sourcefabric.org
Sourcefabric
Prinzessinnenstraße 20
10969 Berlin, Germany
twitter: @Sourcefabric
...
To leap into the complete solution, I don't see how footnotes can work without being managed separately in a database.
Not quite. The point with this solution is not to create the final HTML that is being used for the final output display. The point is that the footnotes/endnotes are stores in a way similar to XML, so that it is easy to make different types of final outputs -- either in Objavi Python code, in Booktype Python code or even in javascriptcode that is put in before BookJS is fired to make the PDF (in which case another solution has to be found for epubs).
On Mon, May 27, 2013 at 6:47 PM, Johannes Wilm <johann...@sourcefabric.org> wrote:
Not quite. The point with this solution is not to create the final HTML that is being used for the final output display. The point is that the footnotes/endnotes are stores in a way similar to XML, so that it is easy to make different types of final outputs -- either in Objavi Python code, in Booktype Python code or even in javascriptcode that is put in before BookJS is fired to make the PDF (in which case another solution has to be found for epubs).
Not really. There is 0 difference between having <div class="footnote"> and <ul class="footnotes><li class="footnote_33233"> (or whatever is the correct syntax right now). Both of the solutions provide possibility of post processing and creating different output. Which is the case with out new ebook engine. That engine easily creates iPad friendly footnotes from the current scheme. The only difference is really: 1) your solution provides only 1 on 1 relationship 2) in second case, because you can reference one endnote from multiple places, you have to do extra processing to be sure all references are deleted.
Aco--
Aleksandar ErkalovićBooktype Developer
aleksandar...@sourcefabric.org
www.sourcefabric.org
mobile: +385-(0)91-6425220
twitter: @aerkalov | skype: aerkalov
On Mon, May 27, 2013 at 11:55 PM, Johannes WilmThis is correct. What i have found out after couple of years is that
<johann...@sourcefabric.org> wrote:
> In the current solution you cannot copy a pice of text with a footnote
> connected to it and then paste it somewhere else and have the footnote
> follow it then and have the numbering auto-updated -- for example into
> another chapter, or another book or another instance of Booktype on a
> different server, etc.
people copy+paste a lot between 2 different instances of Booktype.
Footnotes all over the servers :)
Well..... to be honest, you have created a new moment here. There are
> Also, the user can currently manually delete the endnote, and the
> endnotereference will continue to be there. If you then enter another
> endnote, it will start from 1 again.
two blocks now, one where the content is and 2nd one where the editing
is happening.
If we take the current situation (one footnote can have
many references) to the new model, then it is also possible
(especially with the new editor) to have chapter of the content and
footnote content separate and out of user (he or she will not be able
to delete or touch it). Minimal effort to make it work really. Well...
more like _a must_ and less _it is also possible_. The situation where
one does copy+paste between different instances and maybe chapters
still remains.
I think we should see what is what we want with the footnotes feature
and how you should develop this plugin really.
Aco
--
Aleksandar Erkalović
Booktype Developer
aleksandar...@sourcefabric.org
www.sourcefabric.org
mobile: +385-(0)91-6425220
twitter: @aerkalov | skype: aerkalov