> I don't do it just for the sake of change. The book needs to be
> maintained and change is inevitable. Sorry if it causes you any
> trouble. Can't you just translate the prose between the xml tags?
It's what we usually do actually. The only problem is, with such changes,
reading diff becomes fastidious as diff considers all paragraphs have been
changed in the file.
A proposal comes now to me: would be hard for you to split things? 1st doing
formal changes and commit (we would "ignore" the commit thanks your log
message); 2nd: apply changes in the text itself, so that diff can display the
differences in the contents, instead of including formal changes. What do you
think of this? Here we're thinking of some script to produce some more readable
diff, so that we know textual changes and not such formal changes. But it will
be long before this to work.
Sincerely,
> Andy
-
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
Le mercredi 04 avril 2012 à 01:04 +0100, Andrew Benton a écrit :
> On Tue, 03 Apr 2012 21:53:58 +0100
> Denis Mugnier <[email protected]> wrote:
>
> > To work, we read all your commits and apply the changes in the
> > frenchversion.
> >
> > It is very difficult for us to process a big commit when a large
> > majority of changes is to add "\n" after xml tags.
>
> That's me that's been doing that.
>
> > Why this new layout of the xml files ?
>
> I've been trying to make the layout of the xml more consistent. At the
> moment it seems a bit confused with different styles in different parts
> of the same file.
>
> > Will this format of the xml files be generalized to all files in the book ?
>
> Probably not if it's just me doing it as the book is large and I don't
> touch a lot of it.
>
> > 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.
>
> It just seems cleaner to me to cut out unneeded cruft. If it doesn't
> install a program, why have an entry for the installed programs on the
> list? The main thing is that the list accurately reflects what is
> installed, simply and cleanly.
>
> > 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
> > appreciate.
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
