Implement translated manpage build system with Transifex integration

[OmegaPhil]

No description provided.

[IgnorantGuru]

Thanks overall the method looks good.

Generation Deps

With po4a installed, I get the following error from generate_manpages.bash:

./generate_manpages.bash 
 (94 entries)
po4a::asciidoc: Detection of two line titles failed at udevil.1.txt:2
               Install the Unicode::GCString module!
find: `a2x': No such file or directory

After installing asciidoc I get:

./generate_manpages.bash 
 (94 entries)
po4a::asciidoc: Detection of two line titles failed at udevil.1.txt:2
               Install the Unicode::GCString module!
a2x: ERROR: "xmllint" --nonet --noout --valid "/git/udevil/man/translated/en_GB/udevil.1.xml" returned non-zero exit status 4

So as discussed we need to know the dependencies for your manpage system. Maybe try a live debian CD and try it there - that will show you what's missing.

Also, due to your use of =~ and BASH_REMATCH, generate_manpages.bash requires bash >= 4. I may rework that (or you can) so it only requires generic bash. Then again, that's not required by the build system afaict (used by developers only?), so maybe it's ok as is. Just prefer to keep dependencies and versions minimal. (spacefm requires bash4, but udevil does not)

Build

autogen, configure, make, and make install seemed to work ok to the extent I could test them without udevil.1. (There is no udevil.1 in your source tree, although there should be, as this is manually generated - not part of the build system.)

Misc Notes

• Top of udevil-man.pot needs customization (copyright, etc). I will probably handle this via my release scripts, or add an update-pot script similar to the one in po/ (This is a note for me unless you want to handle it, or add it to generate_manpages.bash?)
• As discussed, change occurrences of "Omega Weapon" to "OmegaPhil" for project consistency. (Not the commits, just in the source files.)
• As discussed, there are many untranslatable strings (not needing translation, eg command lines) in the pot file, but because it's a manpage rather than a C source file, I don't think there's a convenient way to avoid this. (Just noting it here in case others have comments.)
• .tx/config does not enumerate the po file of each language. Is this functional (maybe the file filter does it). (There are now partial polish and swedish translations of the manpot on Transifex to test with.)

Workflow

I'd like a basic workflow for updating the manpage and/or translations. Mine is included below as best I understand it. Perhaps you can update this and include it in man/README so its handy.

# To update manpage, edit man/udevil.1.txt

# To generate pot file (this should be done as a script, or included
# in generate-manpages.bash ?)
cd man/
po4a-gettextize -f asciidoc -m udevil.1.txt -p po4a/udevil-man.pot

# Push source file to Transifex
cd ..  # to dir containing configure
tx push -s

# Get updated translated po files
tx pull

# Generate manpages (includes udevil.1 and translated ones)
cd man/
./generate-manpages.bash

# Commit changes

[OmegaPhil]

Just responding to build system dependencies: I have tested with a fresh Debian Testing install - 'sudo aptitude install asciidoc po4a' was all that was needed to be able to run the generation script.