| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- sisupod.manifest
- list alternative processable files with paths
e.g.:
media/text/en/live-manual.ssm
media/text/fr/live-manual.ssm
...
- name file followed by list of language codes
e.g.:
live-manual.ssm
en, ca, de, es, fr, it, ja, pl, ro
live-manual_next.ssm
en, de, es, fr, it, ja
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- src pod dir structure changes
- notes
- the plan is to have a src manifest of related .sst or .ssm files
that can be pointed to for processing
- multilingual documents [ponder persistence for multilingual
documents]
- in the case of multilingual documents, there will be multiple
source documents on list with different language codes, and to
build this list, persistence is required
- inserted documents (from master .ssm or .sst) must track document
root
so inserts can be located, else not found
- consider a commandline -o --output path specifier
- steps
- auto create filelist
- for single source file
- for multilinugual source files
- process document by pointing at filelist (rather than file)
- if necessary manually create filelist (for multilinugual source)
- keep document root for document inserts (.ssi)
process filesystem/unzipped sisupod.zip
- source/sisupod path/dir structure representation changes
|
