public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Marius Mauch <genone@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Fw: [gentoo-portage-dev] changelog encoding
Date: Fri, 8 Oct 2004 17:29:30 +0200	[thread overview]
Message-ID: <20041008172930.29a60601@andy.genone.homeip.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 1861 bytes --]



Begin forwarded message:

Date: Fri, 8 Oct 2004 13:56:17 +0100
From: Ciaran McCreesh <ciaranm@gentoo.org>
To: Marius Mauch <genone@gentoo.org>
Cc: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] changelog encoding


[ not sure if I can post to gentoo-portage-dev, please forward on if
not... ]

On Fri, 8 Oct 2004 14:31:52 +0200 Marius Mauch <genone@gentoo.org>
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) 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).

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.

-- 
Ciaran McCreesh : Gentoo Developer (Sparc, MIPS, Vim, Fluxbox)
Mail            : ciaranm at gentoo.org
Web             : http://dev.gentoo.org/~ciaranm



[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2004-10-08 15:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-08 15:29 Marius Mauch [this message]
2004-10-08 16:26 ` Fw: [gentoo-portage-dev] changelog encoding Luke-Jr
2004-10-08 16:40   ` Ciaran McCreesh
2004-10-09  1:05     ` Ed Grimm
2004-10-09 13:53       ` Ciaran McCreesh
2004-10-09 15:24         ` Brian
2004-10-09 17:10           ` Ciaran McCreesh
2004-10-09 17:38             ` Marius Mauch

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=20041008172930.29a60601@andy.genone.homeip.net \
    --to=genone@gentoo.org \
    --cc=gentoo-portage-dev@lists.gentoo.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox