search

google-code-export / flies

Automatically exported from code.google.com/p/flies
GNU Lesser General Public License v2.1
2 stars 0 forks source link

OS independent build needed for DocBook projects #210

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
Using flies should not require installing OS specific elements on various 
platforms (Windows & OSX, various Linux's)
just to build docs.

What is the expected output?
Being able to run the build with flies/po based docs without requiring multiple 
step process for building.

What do you see instead?
That I and other developers have to install different software for each OS to 
get my build to work.

Original issue reported on code.google.com by max.ande...@gmail.com on 7 Dec 2010 at 12:14

GoogleCodeExporter commented 9 years ago 
To achieve an OS independent docs build, we should add the ability to convert 
DocBook XML to POT and also PO back to XML, rather than using the gettext 
features of "publican update_pot" and "publican build".

Alternatively, the Flies Maven plugin could read and write DocBook XML files 
directly, but we would still need a file format for translation files (to allow 
version control), which might as well be .po.  The best option would probably 
be the ability to convert directly between XML and Flies, but with the option 
to write POT/PO as well.

Original comment by sean.flanigan@gmail.com on 7 Dec 2010 at 12:31

GoogleCodeExporter commented 9 years ago

Original comment by sean.flanigan@gmail.com on 7 Dec 2010 at 1:06

GoogleCodeExporter commented 9 years ago

Original comment by sean.flanigan@gmail.com on 22 Dec 2010 at 1:15