I am translating the Storage Administration Guide into Dutch.
As I am nearing the end of this job, I have tried to build the document
for the Dutch language to catch mistyped tags.
In the directory storage-administration-guide I gave the command:
publican build --formats=html-single --langs=nl-NL
After a lot of Merging messages with a lot of warnings, the build stops
with an error:
Processing file tmp/nl-NL/xml_tmp/Book_Info.xml ->
FATAL ERROR: language profiling would prune root node. Do NOT set lang
in a root node. at /usr/share/perl5/Publican/Builder.pm line 465
Can anybody help me to solve this?
I am a newbie, and unfortunately, have been a newbie for a very long
time now. The two biggest hurdles that are stopping me from making any
1. I am afraid I might break something
2. I can't figure out where I can fit in the docs team.
To solve the first problem, I want to ask if it is possible to start a
"Hello World" doc: A doc meant exclusively for newbies, that never gets
published for any release, where everyone is welcome to jump in and get
comfortable with the process without worrying about breaking something.
Every newbie who joins can be asked to create a chapter in his name,
where he can post information about himself, what he likes to work on,
and to say "hello world". This will be a good place to get familiar with
Further, the doc can be about the process, where to start, what tools to
use and all instructions that a newbie will need. This will have the
added bonus that a newbie who reads it and doesn't understand something
will be able to correct it from his own experience, without bothering
Taking this one step further, this doc can also act as a guinea pig for
all changes in the publishing process. In the current discussions about
the QA process, a suggestion was put forward to try out a new method on
one doc and see if it scales up. This can be the guide to be
experimented upon for all such trials.
Can this be done?