From: Marius Mauch <genone@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] changelog encoding
Date: Sat, 9 Oct 2004 19:38:20 +0200 [thread overview]
Message-ID: <20041009193820.29ab0f87@andy.genone.homeip.net> (raw)
In-Reply-To: <20041009181004.62a91f7a@snowdrop.home>
[-- Attachment #1: Type: text/plain, Size: 869 bytes --]
On 10/09/04 Ciaran McCreesh wrote:
> On Sat, 09 Oct 2004 08:24:38 -0700 Brian <dol-sen@telus.net> wrote:
> | I have changed porthole's code to try decode(utf_8), then try
> | decode(iso-8859-1). Failing either of those Porthole will display
> | an unknown encoding error and to please report it to bugs.gentoo.org
> | as well as porthole's bug tracker.
>
> Since there's no documented standard... Could one of you portage
> people please post a message to -dev saying "as of now, use UTF-8 for
> ebuilds and changelogs if at all possible"? I can update
> app-vim/gentoo-syntax and the default vimrc to encourange fileencoding
> to be uft-8 for these things...
No problem for ChangeLogs, but for ebuilds we probably need to make a
difference between the portage-visible parts and the normal bash stuff
as portage itself can only handle ascii internally.
Marius
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-10-09 17:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-08 15:29 Fw: [gentoo-portage-dev] changelog encoding Marius Mauch
2004-10-08 16:26 ` 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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-10-08 4:19 Brian
2004-10-08 12:31 ` Marius Mauch
2004-10-08 17:34 ` George Shapovalov
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=20041009193820.29ab0f87@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