Git development
 help / color / mirror / Atom feed
From: Marco Costalba <mcostalba@yahoo.it>
To: Matthias Urlichs <smurf@smurf.noris.de>
Cc: git@vger.kernel.org
Subject: Re: GIT character codecs
Date: Sun, 13 Nov 2005 22:31:25 -0800 (PST)	[thread overview]
Message-ID: <20051114063126.27817.qmail@web26306.mail.ukl.yahoo.com> (raw)

Matthias Urlichs wrote:

>Hi, Junio C Hamano wrote:
>
>>I suspect you could just take the default from LANG and LC_CTYPE
>>to cover 98% of the cases, and to cover the rest 2% the
>>problematic cases have a per-window override menu.
>
>
>Or, if you want to be super-flexible, just try to decode as UTF-8.
>Success? fine -- otherwise use whatever your application's default is
>set to, or your local encoding (which may of course also be UTF-8), or
>fall back to 8859-15.
>

How it is possible to test for success?

The codec could see everything decodable, but It's only from the context,
i.e. the user who reads, that it is possible to realize it's the wrong codec.  

Anyhow, as I posted previous in this thread, qgit-0.97.2 now has a codec selector
 as a persistent setting, defaulting to local codec.


  Marco



		
__________________________________ 
Yahoo! FareChase: Search multiple travel sites in one click.
http://farechase.yahoo.com

             reply	other threads:[~2005-11-14  6:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-14  6:31 Marco Costalba [this message]
2005-11-14  7:42 ` GIT character codecs Matthias Urlichs
  -- strict thread matches above, loose matches on Subject: below --
2005-11-13 20:52 Marco Costalba
2005-11-13  8:14 Marco Costalba
2005-11-13 10:21 ` Junio C Hamano
2005-11-14  4:47   ` Matthias Urlichs
2005-11-13 17:51 ` Linus Torvalds
2005-11-12 12:37 Marco Costalba
2005-11-12 22:00 ` Junio C Hamano

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=20051114063126.27817.qmail@web26306.mail.ukl.yahoo.com \
    --to=mcostalba@yahoo.it \
    --cc=git@vger.kernel.org \
    --cc=smurf@smurf.noris.de \
    /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