kicad-developers team mailing list archive
-
kicad-developers team
-
Mailing list archive
-
Message #16772
Re: Build options for asciidoc documentation
On Sat, Feb 14, 2015 at 07:58:11PM +0300, Fat-Zer wrote:
> 2015-02-14 1:36 GMT+03:00 Marco Ciampa <ciampix@xxxxxxxxx>:
> > On Fri, Feb 13, 2015 at 08:52:28PM +0000, Brian Sidebotham wrote:
> >
> > From the start I said that I will be grateful for every help I receive...
> > and this is not amazing if you understand my motivation...
> >
> > 1) First of all I am lazy
> > 2) I was willing to start translating in Italian KiCad docs
> > because
> > a) I was willing to know more about KiCad and this is a good method
> > to read all docs throughly,
> > b) I find that translating into my native language all the KiCad docs,
> > I understand them better.
> > 3) updating a translation from ODT is a nightmare and I am not willing to
> > wasting my time translating something that in a few months could become
> > obsolete and not easy to update
>
> I was wondering how you have gettextized the translations?
> Converted both them to asciidoc? If so, what toolchain you have used
> for that and have you do some manual actions?
It is all described here:
https://github.com/ciampix/kicad-doc/blob/master/doc/kicad-doc-doc.adoc
I have used po4a. The toolchain was done with the method of trial-and-error.
PS: I have discovered that the epub generation is broken since something
in the asciidoc tool a2x does not permit to have references to files
(images) outside the build dir ... this disable the ../common images
reference. PDF and HTML generation are ok.
--
Marco Ciampa
I know a joke about UDP, but you might not get it.
+------------------------+
| GNU/Linux User #78271 |
| FSFE fellow #364 |
+------------------------+
References