Quote:
Originally Posted by elibrarian
When you run the plugin, it generates a footnote.css file. When you run it again (which, btw., I would advise against, since the new footnote's numbers would be duplicate, beginning all over from no. 1, and it's a sheer hell to sort that out), the footnote.css exists, and hence "Manifest Id is not unique".
That might be fixed by letting the plugin check for existing footnote.css - I'll look into it next weekend - but still, this is not footnotes the MSWord/Libreoffice way, and I doubt it's possible to get that functionality in Sigil. (But ideas are welcome, and anyone are welcome to tamper with my probably rather crude coding.)
Regards,
Kim
|
Thank you very much for your fast answer. Regarding the ID footnotes number, maybe the plugin could ask the user for the number of the next footnote. Of that way, footnotes number never will be duplicated. And indeed, after erasing "footnote.css", the plugin works, although, footnotes number are duplicated as you said.
So, after you explained me how works your plugin, I could manage a bit the issue by doing the following:
1) By erasing "footnote.css"
2) By opening "plugin.py" and changing manually the values for "lastid" and "fnid".
But of course, if you can check the existence of "footnote.css" and add a field for your plugin where the user can write the number of the next footnote would be great
Many thanks again for your answer!
Rubén