| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
| |
* removed lib/sisu/{current,develop} dir branches
v7 (v5 & v6 retired)
* simplify dir structure, offer single version per snapshot
* have enjoyed carrying stable and development versions v5 & v6
in a single tarball, may return to this structure
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* 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)
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* --po4a run against different language versions of sisu markup
files (representing the same document in different languages)
initializes po4a structure to place those documents under future
po4a management
* includes command line translation request
(use command line program 'trans' to pass request to
translation.google.com, stopped for now)
NOTE in case future development is restarted: to test, remove
code line 'auto_translate?(:skip)' that follows
'def auto_translation(src_txt,markup=:src)'; place identical
english sisu markup files in en/test.sst fr/test.sst (or under
the language code to be tested) and run against en/test.sst
fr/test.sst e.g. '--po4a --trans --glob test.sst'
this send identical text objects to translate.google using
'trans' and populate po file with results for placing future
translation under po4a management, however in initial tests
insufficient cleanly translated paragraphs were returned,
so stopped development for now. (no attempt at initialization
of new non-existent files using --trans-en:es,fr,de format)
* [hub_options, if development of trans is pursued later consider
the possibility of modifying the --trans string options to add
an optional timeout value, &; possibly modifying po4a code so
timeout may occur a fixed number of times before skipping
translation request attempts for the remainder].
|
| | |
|
| | |
|
|
|
* 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))]
|
