From: Ivan Kanis <ivan@kanis.fr>
To: esr@thyrsus.com (Eric S. Raymond)
Cc: emacs-devel@gnu.org
Subject: Re: Policty question - encoding to use in git repository?
Date: Mon, 17 Feb 2014 20:22:13 +0100 [thread overview]
Message-ID: <87vbwdk0ii.fsf@tao.kanis.fr> (raw)
In-Reply-To: <20140217152937.8D831380525@snark.thyrsus.com> (Eric S. Raymond's message of "Mon, 17 Feb 2014 10:29:37 -0500 (EST)")
February, 17 at 10:29 Eric S. Raymond wrote:
> While continuing to try to identify correct deletion points for attic
> files, I have run across a minor problem: Latin-1 characters in
> Changelog files. I have seen two, c-cedilla and something I can't
> identify that renders as a backtick. There may be more. I can fix
> them up.
>
> I request a policy decision about what encoding the repository
> content should use. I see three reasonable choices:
>
> * Leave Latin-1 in place.
>
> * Transcode to UTF-8. (I favor this as the best long-term solution.)
>
> * Transcode to ASCII approximations - easy in the two cases I've
> found so far.
Transcode to UTF-8 would be best I think.
--
A faith is something you die for; a doctrine is something you kill
for: there is all the difference in the world.
-- Tony Benn
next prev parent reply other threads:[~2014-02-17 19:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-17 15:29 Policty question - encoding to use in git repository? Eric S. Raymond
2014-02-17 15:41 ` Juanma Barranquero
2014-02-17 16:30 ` Eric S. Raymond
2014-02-17 17:03 ` Andreas Schwab
2014-02-17 17:12 ` Eric S. Raymond
2014-02-17 16:39 ` Karl Fogel
2014-02-17 16:52 ` Eli Zaretskii
2014-02-17 17:01 ` Eric S. Raymond
2014-02-17 17:04 ` Andreas Schwab
2014-02-17 17:24 ` Eli Zaretskii
2014-02-17 19:22 ` Ivan Kanis [this message]
2014-02-17 21:47 ` Paul Eggert
2014-02-17 22:08 ` Eric S. Raymond
2014-02-18 0:50 ` Glenn Morris
2014-02-18 1:07 ` Stefan Monnier
2014-02-18 16:30 ` Karl Fogel
2014-02-18 6:40 ` David Kastrup
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=87vbwdk0ii.fsf@tao.kanis.fr \
--to=ivan@kanis.fr \
--cc=emacs-devel@gnu.org \
--cc=esr@thyrsus.com \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.