git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Alex Henrie <alexhenrie24@gmail.com>
To: "Christopher Díaz Riveros" <christopher.diaz.riv@gmail.com>
Cc: Carlo Arenas <carenas@gmail.com>,
	Git mailing list <git@vger.kernel.org>,
	git-l10n@googlegroups.com, Jiang Xin <worldhello.net@gmail.com>
Subject: Re: Problems with Git's Spanish translation
Date: Sat, 7 Aug 2021 10:00:32 -0600	[thread overview]
Message-ID: <CAMMLpeQmbT-YmK3RrhPwe1bs8KNkEztony0QtbzoSbgNYjH3zA@mail.gmail.com> (raw)
In-Reply-To: <CAHCo6sqi0WmxxKMU=Nx=z_3PDx84YmUOa+ACRcBbM=R_nr4nrg@mail.gmail.com>

On Sat, Aug 7, 2021 at 6:17 AM Christopher Díaz Riveros
<christopher.diaz.riv@gmail.com> wrote:
>
> Just as an fyi, as Carlo mentioned, the window for updates is the moment when I make some time to review patches (not currently a full time developer nor translator)...

Nor am I, but I have some time to work on this. Please let me help by
trusting that I'm not going to totally screw it up.

> Some come through PRs and others directly through email, and sometimes, as Carlo mentioned I have over 5k lines to review in a single commit, so I have to pick some of the most important changes and apply them directly in another commit,

5,000 lines might seem like a lot, but I didn't even attempt to
harmonize the terminology in the translation. For example, the
translation still uses a mix of "tú" and "usted" (although some work
was done previously to try to standardize on "tú"), and many terms
like "amend" and "bundle" are sometimes translated and sometimes left
in English.

> and those PRs are the easy ones because there are others which have over 100 commits from development branches not even related to localization...

You can reduce the displayed diff on GitHub in an instant by
fast-forwarding <https://github.com/ChrisADR/git-po> to
<https://github.com/git-l10n/git-po>.

> Sometimes the commiter adds extra changes trying to fix "Spanish correctness" according to their country... Which makes the diffs bigger and harder to read... And those same correctness changes are then "fixed" in another commit by another person...

In my opinion, the "generic" Spanish translation (which is the only
Spanish translation we have at the moment) should avoid using words
that can have different meanings in different countries. If I've made
changes that seem to just change from one dialect to another, this is
why. And if you want me to drop any of the changes, just note them on
GitHub and I will. Right now I'm just trying to fix things that are
not controversial.

> That being said, thanks for taking the time to review and propose changes, I'll try to review and pick the most important ones for this release candidate :)

You're welcome!

-Alex

  parent reply	other threads:[~2021-08-07 16:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-07  5:10 Problems with Git's Spanish translation Alex Henrie
2021-08-07  6:12 ` Carlo Arenas
2021-08-07  6:29   ` Alex Henrie
     [not found]     ` <CAHCo6sqi0WmxxKMU=Nx=z_3PDx84YmUOa+ACRcBbM=R_nr4nrg@mail.gmail.com>
2021-08-07 16:00       ` Alex Henrie [this message]
2021-08-09  4:42         ` Jiang Xin

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAMMLpeQmbT-YmK3RrhPwe1bs8KNkEztony0QtbzoSbgNYjH3zA@mail.gmail.com \
    --to=alexhenrie24@gmail.com \
    --cc=carenas@gmail.com \
    --cc=christopher.diaz.riv@gmail.com \
    --cc=git-l10n@googlegroups.com \
    --cc=git@vger.kernel.org \
    --cc=worldhello.net@gmail.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).