[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn commit: r11950 - trunk/doc/translations/spanish/book

From: Daniel Rall <dlr_at_collab.net>
Date: 2004-11-19 12:19:41 CET

On Fri, 2004-11-19 at 09:45 +0000, Grzegorz Adam Hankiewicz wrote:
> Sorry Erik, I didn't notice you had made this email public, so I'm
> going to copy my answer here for completeness.
>
> On 2004-11-18, Erik Huelsmann <ehuels@gmail.com> wrote:
> > > Book Spanish. Reverting r11882 because it didn't follow
> > > the correct commit procedure and author doesn't clear up
> > > source/authority.
> >
> > I'm not sure I understand the objection. Is the translation
> > incorrect?
>
> Yes, there are two mistakes in the translation and one mistake in
> the log message. For a one liner patch this puts into doubt the
> credibility of both Daniel Rall and Laila Cory Rall as responsible
> translators.

I didn't realize that spelling castellano in phonetic English in the log
message would cause such a reaction. Yikes.

I hadn't notice any messages from you, and was at ApacheCon during that
time period and without decent net access. And now I'm back home with a
painful head cold. After searching through a few thousand emails, I've
found the two messages you sent. In the future, please CC the dev list
or translation list (most of what I get to my tigris.org address is
spam). Here's the one from the 13th (referenced below), with a
response:

--- snip ---
> I've noticed this commit and I wonder why. It breakes the commit
> rules we have set up for the translation project, mainly, that file
> is being worked on by Rubén Gómez and we avoid working on the same
> files to mix translation styles.

The translation style mimics what's used in the file.

> Second, it implies adding your contribution to the author list. But
> from the commit message it is not clear whether the translator is
> you or Laila Cory Rall.

When you see "Reviewed by" in a commit, it implies that the person
referenced there is the reviewer. If no author is listed, you can
assume that to be the committer (as in this case).

I didn't add myself to the translation-specific author list because I
doubt I will be making significant contributions due to other time
constraints.

> Third, there's a mistake in the translation. It is questionable
> the used past tense in the translation of the copy verb, but more
> importantly, "debajo el" is incorrect, and should be either "debajo
> del" or "bajo el", with the latter use being more extended.

By more "extended" do you mean more common? I concur that it's not
accurate as written, but in speach would've chosen "debajo del" rather
than "bajo el". For the translation in chapter 3, both forms have been
used.
--- snip ---

...
> With authority of the patch I mean that attribution has to be
> given to the correct person, otherwise patches cannot be accepted.
> Every contributed patch has to be traceable to a person, and this
> person has to accept the terms of the license. I've done this so
> far with all the contributors and will continue doing it to avoid
> legal problems I've had in previous projects.

All patches are traceable through the Subversion repository itself. See
`svn blame` and `grep dlr COMMITTERS`. As to "accept[ing] the terms of
the license" (noted in LEAME), I've been foisting my paltry
contributions on this project for over four years, and accepted the
book's Creative Commons license a very long time ago.

Erik, thanks for following up with the usual dev procedure. Grzegorz, I
appreciate that you made an effort with the two emails before reverting
the patch. I don't hold it against you. :)

- Dan

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Nov 19 12:20:30 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.