d: po4a, initialize either directly with sst or passed through ao

* creates source language directory with source markup files
  (.sst .ssm .ssi) & the po4a.cfg configuration file, then runs
  po4a to place the markup source under po4a translation
  management
* --po4a-sst uses original sisu markup source as described above
* --po4a-ao passes sisu source markup through document abstraction
  before converting back to a sisu markup source markup equivalent
  of the original document, it does this in an attempt to get more
  uniform output, and put footnotes for example if any in a form
  that is easier to translate
  --po4a-ao -v --trans-en:fr,es en/live-manual.ssm
  --po4a-ao -v --trans-en:fr,es en/live-manual.ssm \
    es/live-manual.ssm
  in the latter example also runs sisu marked up "es" document
  through document abstraction and returns a sisu markup source
  version of the document, and against this gettext is (or can be
  run) to (attempt to) have the source and target languages
  together in the po/es file
* all quite rough, will need to be revisited,
* these for now replace the renamed --po4a-shelf (formerly --po4a)

1 files changed, 4 insertions, 0 deletions

diff --git a/lib/sisu/develop/hub.rb b/lib/sisu/develop/hub.rb
index df668922..1b5ac580 100644
--- a/lib/sisu/develop/hub.rb
+++ b/lib/sisu/develop/hub.rb
@@ -133,6 +133,7 @@ module SiSU
       actions.outputs.each_file.xml?
       actions.outputs.each_file.pdf?
       actions.outputs.each_file.man_or_info?
+      actions.outputs.each_file.po4a_make?
       actions.outputs.each_file.sqlite_discrete?
       actions.outputs.each_file.manifest?
     end
@@ -181,6 +182,9 @@ module SiSU
       if defined? actions.outputs.loop_files.run_termsheet?
         actions.outputs.loop_files.run_termsheet?
       end
+      if defined? actions.outputs.loop_files.po4a_setup?
+        actions.outputs.loop_files.po4a_setup?
+      end
       if defined? actions.outputs.loop_files.sql?
         actions.outputs.loop_files.sql?
       end