| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
* libs & version files under new branch names: current & develop
* previously under branch version numbers (v5|v6)
* version .yml files moved
* associated adjustments made as required, notably to:
bin/sisu se* qi* (file headers); breakage potential, testing
required
* [on dir names, want release to (alphabetically) precede
next/development, considered (cur|dev)
(current|(dev|development|progress|next)) (stable|unstable),
alpha sorting fail (release|(next|develop))]
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
* without fix sisu reports loading of .ssm & .ssi files but not .sst
(sub-documents are imported correctly and resulting document outputs are
correct and unaffected, but unless aware of this bug it would seem otherwise
until the correct operation of sisu was manually verified e.g. by examining
documents produced); (issue somewhat mitigated by not being the most common
sisu operation)
* sisu is in development freeze, this fix is provided for Debian Jessie
(Closes: #767761)
|
| | |
|
| | |
|
| |
|
|
| |
* v5 dp, indentation changed to retain easy comparison with v6
|
| |
|
|
|
| |
* v5 file renames sync with v6 for easier comparison
* v5 here (5.5.6) remains as in previous version (5.5.5)
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* .ssm can contain/include .sst or .ssi
.sst files can be processed independently, they do not contain other files
.ssi files have been only insertions of text & are not processed independently
but as part of an ssm
change proposed:
.ssm unchanged,
.sst unchanged,
.ssi as before, but can include .sst or .ssi, so:
files are only insertions & are not processed independently but as part of an
.ssm or another .ssi
i.e. as before with the addition that it like a .ssm can contain/include
.sst or .ssi
* requested feature, (Closes: #744408)
User beware. In previous versions there has been a deliberate attempt to keep
it easy to follow documents & not have to dig through different levels of
includes, as this is more likely to lead to errors in markup.
The idea of nested includes has not been attractive (messy for a document),
however, this is now made possible, use with care
* it is not as easy to see document structure at a glance, and structural
errors may be introduced and will need to be taken care of (requiring
document markup debugging)
* allowing .ssi to also include other .ssi or .sst could lead to infinite
recursion if an .ssi includes another which includes itself; stopping after
an additional level of includes seems arbitrary, and possibly prone to error
if you are dealing with many documents
* requires testing
* version bump, new behavior added to .ssi one of the 3 sisu filetypes
|
| | |
|
| | |
|
|
|
* ao_composite.rb (from composite.rb)
* html_concordance.rb (from concordance.rb)
|
