Hi,
>
> I don't understand what layout you mean. There was no discussion about
> changing the layout.
Here's a very short example. Instead of:
<para>To test, issue: </para>
We have:
<para>
To test, issue
</para>
and so on with <seg>, <para>, and other tags.
> > We note also that the english version of the book is not consistent
> > about this stuff: some commits keep the former layout; some commits
> > change the layout (with \n after tags), and also some commits fix a
> > layout change.
> >
> > For example, in the file commited in r9802
> > (general/prog/python-modules.xml), the author remove the
> > lines<segtitle>Installed Program</segtitle> and <seg>None</seg> when no
> > program is installed . In all other pages of thebook, these lines are
> > present.
>
> I wondered why Andy did that, but I didn't think it was an issue that
> really mattered.
Actually the problem mentioned by Denis is that this evolution is not in the
whole book, but only in some commits (and some commits revert such change). And
you're right, theorically it doesn't matter, but the problem here is that svn
diff become not relevant. Instead of displaying differences in commands, words,
descriptions, diff displays as if all the paragraph was changed, although
nothing has changed except this evolution. As we do our commits from the commit
mail on blfs-book, the fact diff isn't relevant anymore is a bit fastidious.
Example:
<para>No test are available.</para>
<para>
No test are available.
</para>
diff displays such change, whereas actually, nothing is changed in the text. So
don't care such change.
Same problem with <seg>, in dependencies descriptions.
Denis adds to that the fact that sometimes we write "Installed Programs" then
None; sometimes we don't write the entry at all. So not consistent.
> > Your work is great and it is a pleasure for us to offer it in French,but
> > if you could make our work a little easier by avoiding the commits
> > without significant repercussion on the review of the book, we would
> > apreciate.
>
> We appreciate your efforts too. We can make changes to help you.
Thanks very much. I let Denis write because I prefer upstream to know all the
contributors to the project. Coordinating with 2 guys allows the project to be
updated and ensures a longer life. :)Especially that for BLFS, a lot of commits
(it's cool), a lot of editors, so... I'm happy to have some help to follow the
updates. :)
Thanks for this work. Very happy this book is alive and active! :)
Best regards,
> -- Bruce
>
>
>
-
Jean-Philippe MENGUAL
Président de l'association traduc.org
Coordinateur du projet Linux From Scratch
Coordinateur au sein du projet Trad GNU de l'April
Animateur suppléant du groupe de travail Accessibilité de l'April
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
