From: "Alejandro Riveira Fernández" <alejandro.riveira@gmail.com>
To: Wincent Colaiuta <win@wincent.com>
Cc: git <git@vger.kernel.org>
Subject: Re: [PATCH] git gui spanish translation.
Date: Wed, 03 Feb 2010 21:37:54 +0100 [thread overview]
Message-ID: <1265229474.23299.15.camel@varda> (raw)
In-Reply-To: <F0288AB4-A1C8-4D72-BA2F-B35B0FDE4180@wincent.com>
[-- Attachment #1: Type: text/plain, Size: 3267 bytes --]
El mié, 03-02-2010 a las 20:13 +0100, Wincent Colaiuta escribió:
Comments
>
> > +#: lib/branch_create.tcl:80
> > +msgid "Fast Forward Only"
> > +msgstr "Solo Fast Forward"
>
> Solo -> Sólo
You only have to use sólo in case there is the posibility of
missanderstand it. Does not aply here or anywhere else in the
patch
>
> > +#: lib/browser.tcl:267 lib/browser.tcl:273
> > +msgid "Browse Branch Files"
> > +msgstr "Explora los ficheros de la rama"
>
> Explora -> Explorar
>
> You need to use the infinitive consistently for command verbs. You are
> doing it in some places but not in others.
Changed my mind during the translation about using one of the other ...
>
> Style issue here... Do you think "obtener" might be a better
> translation than "traer" here (and in the other places where you are
> translating "fetch")?
I'm open to sugestions. the same problem with "commit" (either verb or
noun) tracking branch, push ( propagar is ok? ) etc...
Those terms do not have a clear translation to spanish so we are
inventing language here
>
> Traer is closer to "bring", imo.
Ok will ponder
> > +#: lib/merge.tcl:55
> > +#, tcl-format
> > +msgid ""
> > +"You are in the middle of a change.\n"
> > +"\n"
> > +"File %s is modified.\n"
> > +"\n"
> > +"You should complete the current commit before starting a merge.
> > Doing so "
> > +"will help you abort a failed merge, should the need arise.\n"
> > +msgstr ""
> > +"Esta en el medio de un cambio.\n"
> > +"\n"
> > +"El fichero %s ha sido modificado.\n"
> > +"\n"
> > +"Debería completar la revisión actual antes de comenzar la fusión.\n"
> > +"Hacer eso le ayudará a cancelar una fusión fallida si surgiese la
> > \n"
> > +"necesidad.\n"
>
> Esta -> Está
>
> fallida -> fallada
They are equivalent
>
> > +#: lib/remote_branch_delete.tcl:189
> > +#, tcl-format
> > +msgid ""
> > +"One or more of the merge tests failed because you have not fetched
> > the "
> > +"necessary commits. Try fetching from %s first."
> > +msgstr ""
> > +"Una o mas de las comprobaciones de fusión fallaron porque no se
> > trajeron las\n"
> > +"revisones necesarias. Intente trayendolas de %s primero."
>
> Don't you think:
>
> trayendolas -> traerlas
Ok
> > +#: lib/spellcheck.tcl:388
> > +msgid "Unexpected EOF from spell checker"
> > +msgstr "EOF inesperado desde el corrector ortográfico"
>
> I'm not sure what the standard translation of EOF is, but seeing as it
> stands for "End Of File" it wouldn't surprise me if there is something
> similar in Spanish like "FDA" (Fin De Archivo) or something similar...?
I think people use the EOF just like they use NULL or cd-rom or many
other neologism
> > +#: lib/transport.tcl:175
> > +msgid "Use thin pack (for slow network connections)"
> > +msgstr "Usar paquete ligero (thin pack) (para conexiones de red
> > lentas)"
>
> Don't think you need "thin pack" here.
Well believe my first translation had many other terms in both
English and Spanish. I feared to just create confusion translating
everything (because there are no docs in spanish)
>
> Cheers,
> Wincent
>
>
>
[-- Attachment #2: Esto es una parte de mensaje firmado digitalmente --]
[-- Type: application/pgp-signature, Size: 835 bytes --]
next prev parent reply other threads:[~2010-02-03 20:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-01 19:51 [PATCH] git gui spanish translation Alejandro Riveira Fernández
2010-02-03 19:13 ` Wincent Colaiuta
2010-02-03 20:04 ` Alejandro Riveira Fernández
2010-02-03 20:37 ` Alejandro Riveira Fernández [this message]
2010-02-08 8:44 ` Peter Krefting
2010-02-08 16:00 ` Alejandro Riveira Fernández
-- strict thread matches above, loose matches on Subject: below --
2010-02-01 19:51 Alejandro Riveira Fernández
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1265229474.23299.15.camel@varda \
--to=alejandro.riveira@gmail.com \
--cc=git@vger.kernel.org \
--cc=win@wincent.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.