From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32271 invoked from network); 8 Oct 2004 16:26:43 +0000 Received: from smtp.gentoo.org (156.56.111.197) by lists.gentoo.org with AES256-SHA encrypted SMTP; 8 Oct 2004 16:26:43 +0000 Received: from lists.gentoo.org ([156.56.111.196] helo=parrot.gentoo.org) by smtp.gentoo.org with esmtp (Exim 4.41) id 1CFxZq-00031Z-E0 for arch-gentoo-portage-dev@lists.gentoo.org; Fri, 08 Oct 2004 16:26:42 +0000 Received: (qmail 6458 invoked by uid 89); 8 Oct 2004 16:26:40 +0000 Mailing-List: contact gentoo-portage-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail Reply-To: gentoo-portage-dev@lists.gentoo.org X-BeenThere: gentoo-portage-dev@gentoo.org Received: (qmail 8812 invoked from network); 8 Oct 2004 16:26:40 +0000 From: Luke-Jr To: gentoo-portage-dev@lists.gentoo.org Date: Fri, 8 Oct 2004 16:26:33 +0000 User-Agent: KMail/1.7 References: <20041008172930.29a60601@andy.genone.homeip.net> In-Reply-To: <20041008172930.29a60601@andy.genone.homeip.net> Cc: Ciaran McCreesh IM-Address: luke-jr@jabber.org Public-GPG-Key-URI: http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0xD53E9583 Public-GPG-Key: 0xD53E9583 MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart21118057.Faqy7TvqDY"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200410081626.39210.luke-jr@utopios.org> Subject: Re: Fw: [gentoo-portage-dev] changelog encoding X-Archives-Salt: 3dbd294b-db1e-4f04-b51e-449e6789c1fe X-Archives-Hash: 1a7ec200442f4f051524a78ced43b4bc --nextPart21118057.Faqy7TvqDY Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Friday 08 October 2004 3:29 pm, Marius Mauch wrote: > On Fri, 8 Oct 2004 14:31:52 +0200 Marius Mauch > > wrote: > | On 10/07/04 Brian wrote: > | > What is the official encoding method(s) for the changelogs. It has > | > been reported that porthole often fails getting the changelogs due > | > to the encoding. Currently it is assuming ascii. Many are > | > reported to be iso-8859-1. > | > | I don't think we have an official encoding, but I think ciaranm knows > | a bit more about that issue. > > Yup. We *need* to have an official encoding. Reason being, at least one > developer has a non-(ASCII as in characters 0..126 only) ASCII defines 128 characters: 0-127 Why cut the last off? > character in their name. Said encoding should also apply to ebuilds, but = not > to files/ entries (I could give the lengthy explanation if anyone really > wants to know, but basically certain things would break).=20 > > I've been whinging about this on and off for about a year now, and every > time it's been dismissed as irrelevant :) > > If we're going to standardise on an encoding, it's got to be UTF-8. > iso-8859-1 is not sufficient to represent every developer (and potential > patch contributor)'s name correctly. UTF-16 and plain old four byte > unicode aren't compatible with our existing files (in UTF-8, characters > 1 to 126 are the same as in regular ASCII). Yes, UTF-8 kinda sucks in > terms of space when encoding japanese or russian characters, but since > these will be a rare occurance it's not really a problem. Yay for UTF-8! =2D-=20 Luke-Jr Developer, Utopios http://utopios.org/ --nextPart21118057.Faqy7TvqDY Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQBBZr+/Zl/BHdU+lYMRAv1LAJ98sc9kw8x7WPOIpTyXmkMZuXFqwACghbsd X0L8C24bJwVIAHFF9lz86ro= =JFaX -----END PGP SIGNATURE----- --nextPart21118057.Faqy7TvqDY--