Scribus's new a footnote / endnote system

Previous topic - Next topic

jeepe

Hi,

I'm experimenting with Scribus and text. So far, we did cover pages "together".
Text is a different thing.
Especially a book.

I'm using now v1.7

I've checked 3 features:

hyphenation and languages ✓
justification ✓
endnote system *

The first two works excellently.

The 3rd one is under development. Which is a great thing - the greatest news possible! :)

I'd like to make some suggestions.

------
I am not a programmer, but I think I can imagine how this should work.
What I'm trying to say is that it  can be approached simply.
------

[1st]
focus on an intermittent index-database.

That could be the basis for importing from Libreoffice (LO).
Whatever happens, you only have to get that data our of that document, and you can do whatever you want.

It could be a plugin.
It should parse an .odt, get the indexes.

[2nd] 
forget footnotes, go for endnotes

How it natively works is the key, cause with imports it should be the same thing eventually.

I'm trying to use footnote/endnote with v1.7.

Feels very clumsy.
Footnotes are a very oldfashioned thing, that is, typography being done manually.

I think that the manual editing of footnotes (the height of the text-block) can be ruled out.
Cause book editing demands flowing text over the pages. If someone takes out one paragraph, s/he shouldn't be damned to resize all footnote blocks.

AI? :) An AI can sure do that, too.
But it could be better to focus on endnotes.

Personally, I'd never use footnotes. Endnotes are great. Footnotes change the layout, which is unacceptable :) But forget me.
Let's look at ebooks and print versions existing in parallel.

[3rd]
Endnotes don't have to be shown in the page.

Place an insert in the text box, and somewhere else list your notes, your endnotes.
Also, raise the number of total sum of endnotes by one.

With endnotes all you have to do is bookkeeping. Keeping track of index and value pairs, in a database.

[4th]
Endnotes could be edited as text...

Right now, v1.7, we have Marks Manager (opening from menu: Edit / Marks (at the bottom)
However, editing the note means editing "inline", in the text block in the text frame... at a tiny size.
This shouldn't be like that.
Editing could be done like with Story editor.
like

#1
textblock
# next id
textblock


Which means, they could be edited in a simple text editor, by the author herself...
and on Monday, she could send over a lightweight, robust text file to the pre-press team.

[5th]
The index could also have the unique ID, which is necessary anyway.

like:

#1 | 50450320506
text block
#2 | 43455634545
text block

[6th]  a working table (in an sqlite db)


from the list of all endnotes an index-id pool can be generated on the fly,
the next random unique ids also.

Plus, to every index, its position in the text would be added in another cell, so that when placing a new one anywhere, by the cursor position the new index number can be generated (to which a new unique id could be attached).


[7th] 
as to some the extra features

Numbering can be set to restart at chapter (section) boundary. << I'd love that! :)

This could be the default, BTW.
Ten merging / importing / adding / inserting text blocks wouldn't make handling endnotes a nightmare.

Two sections,however, could be merged, including merging the indexes (endnotes).

The entire endnote "subsystem" could also be used for other indexes, like figures...


[8th]
Exporting text as HTML! (almost forgot)

Since Scribus exports text, exporting HTML would be only one more step :)
okay, a step upwards in complexity.
But as soon as Scribus can export HTML,
A book edited in Scribus, and made ready for printing, could be fed back to Libreoffice, including the endnotes! :)

I'm talking about books, not magazines, of course.
But even magazines could be exported as HTML, too, just like it works with text.


---------------

I'm sure (I do hope!! :)) I'm not impolite to post this...
including that y'all pardon the length of this post

I adore Scribus, plus I yearn for some features.
And love talking about exciting things, like Scribus, for example :)

I would love FOSS to be the way to go in the field of CMYK printing, too.



* * * * * * Thank you for developing Scribus * * * * *





a.l.e

Some comments from my side:

- I just tried the endnotes. For me, they just don't work.
- Generally speaking, the whole foot/endnotes part needs a bit of love.
- Yes, endnotes (and footnotes) should optionally be by section.
- For importing them from LibreOffice: let's see what is in the work you commented on earlier today...
- Index: I think that we need somebody who sits down and create a concept on how Scribus should support indexes.
- You can export to HTML by exporting to EPUB and then unzipping the resulting file.

jeepe

Quote from: a.l.e on <strong>Today</strong> at 07:00:39 PMSome comments from my side:

- I just tried the endnotes. For me, they just don't work.
- Generally speaking, the whole foot/endnotes part needs a bit of love.
- Yes, endnotes (and footnotes) should optionally be by section.
- For importing them from LibreOffice: let's see what is in the work you commented on earlier today...
- Index: I think that we need somebody who sits down and create a concept on how Scribus should support indexes.
- You can export to HTML by exporting to EPUB and then unzipping the resulting file.


Hi,

thank you for your kindness to review my fuzzy thoughts :)


Quote from: a.l.e on <strong>Today</strong> at 07:00:39 PM- Generally speaking, the whole foot/endnotes part needs a bit of love.

Sure... but developing applications always does, as we users can tell :)

Quote from: a.l.e on <strong>Today</strong> at 07:00:39 PM- Yes, endnotes (and footnotes) should optionally be by section.
I'm happy you say that... :)

Quote from: a.l.e on <strong>Today</strong> at 07:00:39 PM- Index: I think that we need somebody who sits down and create a concept on how Scribus should support indexes.

That this is possible is the greatest thing!
This openness and flexibility is a great potential!!

________________________________



As to importing fro Libreoffice Writer (LO-Wr):

I am talking about endnotes.

Someone suggested it, and I tried it, and confirm, it works:

From LO-Wr: export to html (save as HTML).
Then in Scribus, get text...

And it's there... the indexes... (references)
as well as the references notes, at the end of the document.

This could be the beginning of a great workflow :)



jeepe

+1


Quote from: a.l.e on <strong>Today</strong> at 07:00:39 PM- Index: I think that we need somebody who sits down and create a concept on how Scribus should support indexes.

Perhaps it could be done collectively, to some extent...