From: Junio C Hamano <junkio@cox•net>
To: Robin Rosenberg <robin.rosenberg.lists@dewire•com>
Cc: git@vger•kernel.org
Subject: Re: i18n, alternative solution
Date: Mon, 01 Jan 2007 11:44:15 -0800 [thread overview]
Message-ID: <7vy7om7cs0.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <200701011547.48697.robin.rosenberg.lists@dewire.com> (Robin Rosenberg's message of "Mon, 1 Jan 2007 15:47:47 +0100")
Robin Rosenberg <robin.rosenberg.lists@dewire•com> writes:
> What disturbes me is the complexity that the approach of storing multiple
> encodings in the same repository results in.
We are not encouraging mixed encodings, mind you.
Even though we check and warn comits that do not have a valid
UTF-8 string, the users can make mistakes and people need be
able to look at them later. That is what we are solving.
At the same time we do NOT force inconvenience on projects that
want to use legacy encoding for whatever reason. The world is
not UTF-8 only, and encoding to UTF-8 is non-reversible a times
(positive return value from iconv(3)). Always re-coding to
UTF-8 will NOT be accepted to git for now. We can revisit this
perhaps in 5 years.
next prev parent reply other threads:[~2007-01-01 19:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-01 14:47 i18n, alternative solution Robin Rosenberg
2007-01-01 19:44 ` Junio C Hamano [this message]
2007-01-07 16:55 ` Robin Rosenberg
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=7vy7om7cs0.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox$(echo .)net \
--cc=git@vger$(echo .)kernel.org \
--cc=robin.rosenberg.lists@dewire$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox