Translating Jargon

Isaac Jurado diptongo at gmail.com
Mon Feb 9 01:48:28 CST 2009


On Sun, Feb 8, 2009 at 5:00 PM, Rafael Villar Burke <pachi at rvburke.com> wrote:
>
> I think a good, compact and meaningful translation of those concepts
> are needed, even if the original command name is used side by side (to
> explain workflow).

But there are cases, such as the verb/noun "commit" in a database
related context, where the term is directly imported without
translation.

> what about these?:
> changeset = conjunto de cambios

Of course, that's the literal translation.  But it makes me doubt due to
its length.

This reminds me of another question, how "literal" the translations
should be?  Because some explanations can be improved by rephrasing
them.  I've never translated any piece of software, so I don't really
know where the limits lie.

> hook = punto de enlace o ganchos (I don't like this last one too much,
> as it's too literal, but it's used in the django, python, subversion
> and other doc translations...)

I've also seen "script de enganche" in the Spanish version of the SVN
book.  Ironically, "script" is another imported term without translation
(the correct one would be "guión de enganche").

> [1]
> http://blog.rvburke.com/2006/08/25/control-de-versiones-con-mercurial-i-conceptos-generales/
> http://blog.rvburke.com/2006/09/08/control-de-versiones-con-mercurial-ii-uso-de-mercurial/
> http://blog.rvburke.com/2006/09/11/control-de-versiones-con-mercurial-iii-publicacion-de-proyectos/

Nice, but I miss the translation of "manifest".

> [2]http://svnbook.googlecode.com/svn/trunk/src/es/glosario_traduccion

Very nice.  Interesting comment about the "commit data" translation.
Thanks for the link, that gives some valuable insight.

Regards.

-- 
Isaac Jurado
http://www.krenel.net

"The noblest pleasure is the joy of understanding"
Leonardo da Vinci



More information about the Mercurial-devel mailing list