From: "David Rodríguez de Dios" <deivid.rodriguez@gmail.com>
To: Jiang Xin <worldhello.net@gmail.com>
Cc: Git List <git@vger.kernel.org>, Paco Molinero <paco@byasl.com>,
Dimitri John Ledkov <dmitrijs.ledkovs@canonical.com>
Subject: Re: Ubuntu may break Git upstream translations
Date: Tue, 10 Dec 2013 11:07:27 +0100 [thread overview]
Message-ID: <52A6E7DF.5070504@gmail.com> (raw)
In-Reply-To: <CANYiYbF--_51hJmp=28ucwBa6YEuUn97kTAd87POuqrD4SU5gw@mail.gmail.com>
I agree with Jiang.
We should join translation efforts. And in this case, the best place to
do it is upstream.
El mar 10 dic 2013 10:56:19 CET, Jiang Xin escribió:
> Hi all,
>
> David find a typo in Spanish translations of Git, and ask me how
> to contribute, because he cannot find Spanish translations in
> Git source code. To my surprise, I cannot find either.
>
> Later I find out that David using Ubuntu (I use debian instead),
> and Ubuntu reinvent the wheel. Ubuntu has its own translation
> platform, and releases Git translations not with Git package
> itself, but releases Git translations in separate language
> specific packages. E.g. Spanish translations on Git is released
> in package "language-pack-es-base". This language specific
> package includes not only Git translations, but also translations
> of over 200 other packages.
>
> URL of Ubuntu translation homepage on Git:
>
> * https://translations.launchpad.net/ubuntu/saucy/+source/git/+pots/git
>
> Version of Git in Ubuntu Saucy (13.10) is 1.8.3.2, but obviously
> the translations are based on git v1.8.0 (8 months older than
> v1.8.3.2). That's why even Ubuntu provides git translations
> in 21 different languages, but only 2 of them are 100% translated.
> We (Git upstream) provide Git translations in only 7 languages,
> but 5 of them are 100% translated now.
>
> Without context, it's hard to translate well. And contribute to
> upstream will benefit to more people than contribute to one
> specific Linux distribution.
>
> I cc this mail to Paco, the creator of Spanish translations for
> Git I found in this page:
>
> * https://translations.launchpad.net/ubuntu/saucy/+source/git/+pots/git/es/+details
>
> Paco may have interest on David's question.
>
> I also send this mail to Dimitri, the owner of Git translations
> for Ubuntu, for reference.
>
> 2013/12/9 David Rodríguez de Dios <deivid.rodriguez@gmail.com>:
>>
>>> El lun 09 dic 2013 16:33:44 CET, Jiang Xin escribió:
>>>>
>>>> 2013/12/9 David Rodríguez de Dios <deivid.rodriguez@gmail.com>:
>>>>
>>>>> El lun 09 dic 2013 15:59:12 CET, Jiang Xin escribió:
>>>>>
>>>>>> 2013/12/9 David Rodríguez de Dios <deivid.rodriguez@gmail.com>:
>>>>>>>
>>>>>>> Hi Jiang Xin!
>>>>>>>
>>>>>>> I want to contribute to the Spanish translation by fixing a typo
>>>>>>> but I can't find the translation. Where is it?
>>>>>>
>>>>>> All available translations are in "po/" directory of Git, such as
>>>>>> po/de.po, po/pt_PT.po, etc. And all l10n teams, maintainers
>>>>>> and locations of the official repositories are listed in "po/TEAMS" file.
>>>>>>
>>>>>> I can't find a Spanish translation either, but there is a Portuguese
>>>>>> translation and the maintainer is Marco Sousa.
>>>>>>
>>>>>> I don't know how much differences between Spanish and Portuguese.
>>>>>> Maybe the typo you found is belongs to "po/pt_PT.po"?
>>>>>>
>>>>>
>>>>> No way... My "git" is translated into Spanish, that's why it
>>>>> surprises me that the translation is not there...
>>>>>
>>>>
>>>> What's your platform? version of your platform? git --version?
>>>> And what's the output message (with the typo you found)?
>>>> Maybe we could "git grep" in Git source code or google the output
>>>> message.
>>>>
>>> So
>>>
>>> $ uname -a
>>> Linux pantani 3.11.0-14-generic #21-Ubuntu SMP Tue Nov 12 17:07:40 UTC
>>> 2013 i686 i686 i686 GNU/Linux
>>>
>>> $ git --version
>>> git version 1.8.3.2
>>>
>>> $ locale
>>> LANG=es_ES.UTF-8
>>> LANGUAGE=es_ES
>>> LC_CTYPE="es_ES.UTF-8"
>>> LC_NUMERIC="es_ES.UTF-8"
>>> LC_TIME="es_ES.UTF-8"
>>> LC_COLLATE="es_ES.UTF-8"
>>> LC_MONETARY="es_ES.UTF-8"
>>> LC_MESSAGES="es_ES.UTF-8"
>>> LC_PAPER="es_ES.UTF-8"
>>> LC_NAME="es_ES.UTF-8"
>>> LC_ADDRESS="es_ES.UTF-8"
>>> LC_TELEPHONE="es_ES.UTF-8"
>>> LC_MEASUREMENT="es_ES.UTF-8"
>>> LC_IDENTIFICATION="es_ES.UTF-8"
>>> LC_ALL=
>>>
>>> I've downloaded git sources with
>>> $ apt-get source git
>>> $ apt-get source git-core
>>> ...
>>>
>>> and grep the string, nothing. I've also forked the git repo and grep
>>> and nothing either.
>>>
>>> The message is
>>> msgid ""
>>> " (use \"git checkout -- <file>...\" to discard changes in working
>>> directory)"
>>>
>> Oh, and the incorrect message I'm getting is
>>
>> # (use «git checkout -- <archivo>...« para descartar cambios en le
>> directorio de trabajo)
>>
>>
>> El lun 09 dic 2013 16:45:17 CET, David Rodríguez de Dios escribió:
>>
>
> --
> Jiang Xin
next prev parent reply other threads:[~2013-12-10 10:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-10 9:56 Ubuntu may break Git upstream translations Jiang Xin
2013-12-10 10:07 ` David Rodríguez de Dios [this message]
2013-12-10 10:52 ` Dimitri John Ledkov
2013-12-10 13:39 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52A6E7DF.5070504@gmail.com \
--to=deivid.rodriguez@gmail.com \
--cc=dmitrijs.ledkovs@canonical.com \
--cc=git@vger.kernel.org \
--cc=paco@byasl.com \
--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.
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.