From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Jon Seymour <jon.seymour@gmail.com>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org, Erik Faye-Lund <kusmabite@gmail.com>
Subject: Re: Stable ab/i18n branch
Date: Fri, 15 Oct 2010 04:54:58 +0000 [thread overview]
Message-ID: <AANLkTikXnBGHv_TiRNvp35zzpQ5dHW4Y=NZ7a21N5Eho@mail.gmail.com> (raw)
In-Reply-To: <AANLkTin-s8EqssfuOeM6vAmBOFF=JrtgzS96hTSFKZ90@mail.gmail.com>
On Thu, Oct 14, 2010 at 21:50, Jon Seymour <jon.seymour@gmail.com> wrote:
> On Fri, Oct 15, 2010 at 8:18 AM, Ævar Arnfjörð Bjarmason
> <avarab@gmail.com> wrote:
>> On Thu, Oct 14, 2010 at 20:54, Jonathan Nieder <jrnieder@gmail.com> wrote:
>>> Ævar Arnfjörð Bjarmason wrote:
>> So what I've tried to do to make this acceptable for inclusion in core
>> is to make this whole thing a no-op unless it's explicitly
>> requested.
>>
> I agree with Jonathan that there might be some value to clearly
> delineating the i18n infrastructure from the application of it to the
> rest of the code base.The i18n infrastructure should be, relatively
> speaking, less invasive than the application of it throughout the code
> base.
>
> It would be good for Junio (I presume) to have the option to integrate
> the infrastructure in one hit, but allow the application of it to be
> deferred, perhaps on a subject-area by subject-area basis.
It already is pretty much separate internally. To get only the
infrastructure you pull the series and omit the "gettextize"
patches. There is some slight tangling up e.g. here:
6da9243 gettext tests: skip lib-gettext.sh tests under GETTEXT_POISON
234ddee gettextize: git-init basic messages
b161357 gettextize: git-init "Initialized [...] repository" message
3ad3f9f gettext tests: test if $VERSION exists before using it
1f56190 gettext tests: add detection for is_IS.ISO-8859-1 locale
5f24f25 gettext tests: test message re-encoding under Shell
ec31cc6 gettext tests: test re-encoding with a UTF-8 msgid under Shell
45e8a56 gettext tests: mark a test message as not needing translation
c9db9aa po/is.po: add Icelandic translation
83beb97 gettext tests: test message re-encoding under C
Where the tests I'm adding depend on an earlier "gettextize"
patch. That can easily be split up if there's demand for it. But so
far nobody has asked so I haven't done it.
next prev parent reply other threads:[~2010-10-15 4:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-14 4:46 What's cooking in git.git (Oct 2010, #01; Wed, 13) Junio C Hamano
2010-10-14 5:51 ` Nazri Ramliy
2010-10-14 9:23 ` Ævar Arnfjörð Bjarmason
2010-10-14 20:00 ` Stable ab/i18n branch Jonathan Nieder
2010-10-14 20:44 ` Ævar Arnfjörð Bjarmason
2010-10-14 20:54 ` Jonathan Nieder
2010-10-14 21:18 ` Ævar Arnfjörð Bjarmason
2010-10-14 21:26 ` Sverre Rabbelier
2010-10-14 21:50 ` Jon Seymour
2010-10-15 4:54 ` Ævar Arnfjörð Bjarmason [this message]
2010-10-15 0:07 ` Jonathan Nieder
2010-10-15 5:16 ` Ævar Arnfjörð Bjarmason
2010-10-15 5:28 ` Jonathan Nieder
2010-10-15 5:35 ` Ævar Arnfjörð Bjarmason
2010-10-17 4:44 ` Junio C Hamano
2010-10-17 12:33 ` Ævar Arnfjörð Bjarmason
2010-10-17 15:59 ` Jonathan Nieder
2010-10-18 23:39 ` Junio C Hamano
2010-10-19 6:05 ` Michael J Gruber
2010-10-17 4:43 ` What's cooking in git.git (Oct 2010, #01; Wed, 13) Junio C Hamano
2010-10-21 2:14 ` Johan Herland
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='AANLkTikXnBGHv_TiRNvp35zzpQ5dHW4Y=NZ7a21N5Eho@mail.gmail.com' \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jon.seymour@gmail.com \
--cc=jrnieder@gmail.com \
--cc=kusmabite@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).