From: Robin Rosenberg <robin.rosenberg.lists@dewire•com>
To: Junio C Hamano <junkio@cox•net>
Cc: git@vger•kernel.org
Subject: Re: i18n, alternative solution
Date: Sun, 7 Jan 2007 17:55:33 +0100 [thread overview]
Message-ID: <200701071755.34496.robin.rosenberg.lists@dewire.com> (raw)
In-Reply-To: <7vy7om7cs0.fsf@assigned-by-dhcp.cox.net>
måndag 01 januari 2007 20:44 skrev Junio C Hamano:
> 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.
My is to not convert at all if the uset has locale=UTF-8. Mostly it's an
optimization, but it also has the effect of getting the raw message.
> 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.
According to the unicode FAQ, unicode is a superset of all local
encodings, so why would the conversion be non-reversible for local
vs utf-8?
In five years there will be so much legacy, that fixing it in a simple way
will be unfeasble (just like CVS, FTP, etc).
-- robin
prev parent reply other threads:[~2007-01-07 16:51 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
2007-01-07 16:55 ` Robin Rosenberg [this message]
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=200701071755.34496.robin.rosenberg.lists@dewire.com \
--to=robin.rosenberg.lists@dewire$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=junkio@cox$(echo .)net \
/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