I suggest to hold different parts (or even implementations) of the project in separate repositories besides to make it possible to organize rights management.
@HOSTERS: consider to not allow any connection to clearnet from onion service as it should be reachable via overlay only; separate systematically to limit the impact of further vulnerabilities.
limit user name length
and alphabet on validation
replace usage of handle by id everywhere other than output, best generate handle via id
no user input on system calls (e.g. file operations such as pack, unpack, move after upload, …)
a book can be committed from a librarian right now, but mainly for the manual a change happens outside of the box, so when #8 is possible (also in support of man#8) we could just pull in an approved revision (e.g. by an appointed maintainer rather than the original librarian)
maybe also other books reside as opendocument somewhere else in future after #47 got in and mirroring ( #21 ) is in practice
needs
recognize remote origin as another metadata option (maybe on colophon as there are some examples already)
new action for a "maintainer" role (fallback on submitting librarian)
new book maintainer role, might fallback on subject maintainers
message to maintainers if remote origin changed (to sth. like getmaintainers(docid) or getdoc(id)[maintainers])
seems the substitution wringfully make everything italic for now instead only <text:span text:style-name="Emphasis">. should be possible to fix with $xml->xpath()
and custom styles on character lever could be defined in the template just like the paragraph styles where done.
todo:
limit italic to <text:span text:style-name="Emphasis"> (prepared)
fix bold for <text:span text:style-name="Strong_20_Emphasis"> (prepared)
implement source (inline) for <text:span text:style-name="Source_20_Text"> (prepared)
implement underlined for e.g. <text:span text:style-name="underlined"> (custom)
implement underlined-double for e.g. <text:span text:style-name="underlined-double"> (custom)
implement strike-through for e.g. <text:span text:style-name="strike-through"> (custom)
implement blackened for e.g. <text:span text:style-name="blackened"> (custom)
implement smallcaps for e.g. <text:span text:style-name="smallcaps"> (custom)
For multi language support, clearer code structure and performance add some kind of MVC Structure, suggestions are Smarty Templating or something even simpler.
The main part of the code is licensed under GPL v2
some minor parts might change license/version depending on their authors.
Contributors have to agree to publish under these terms.
I am missing some structure information of the database. Can you please dump the CREATE TABLE statements with some dummy data (sample user, sample admin, sample book etc) ?
Just as PaulPetring mentioned it in #32 - Would be nice for some people to not have not only English books but also not solely English text on the site. Translation work is not so much it seems. But the Code is not really fit for adopting some translated template or bunch of constants.
There are other languages for books than English, just no possibility to look for a certain language.
(languages used already: DA, DE, EN, FR, IT, NL, NO, PL, SE)
Would be nice to have this in different places, such as
have bibtex (and later maybe other formats) file for citation at hand
implement or find solution for bibtex output
maybe restructure db for easier access to data (maybe even add data such as for format to distinguish between books, articles etc.)
apply for books using the colophon data (delimiter ":", data[] = {Language, First Published, ISBN, Series, Number}) combined with book metadata = {title, subtitle, author.fullname}
query db for lists table (should be in the same query as for the docs )
e.g. in case illustrations are not embedded but just linked the ToC doesnt show up after upload but no error message is given for the obviously missing content. In general error should be displayed and tested for regularly.
collected ERROR/WARNING/NOTICE missing for now:
ERROR: picture only linked, not embedded, thus picture is missing
svg title or desc is given and not yet ignored (better use or ignore it and give NOTICE how it was handled)
submit more of the kind on this issue; reopen when closed and new ones appear
we may have a book without pictures but then old captions - for now realized with other paragraph styles - will remain useless
we need
proper paragraph styles for captions that apply to the next (it may be over/under) "box", "picture" or object alike we might have implemented in future
either separated or as a single one that is taken semantically right (problem: 2 pictures/objects in a row)
for fixing problems with images or xml it would be nice to see have the pictures included in a book on a view for easier testing, also some people may just want to have a look on pictures and not search the whole text.
you may call it an index for illustrations as well
replace all problematical characters (e.g. preg_replace("/[^0-9a-zA-Z\-\_\.]/", "", $str) for not allowing anything in filenames that does not belong there)
…