List for cgit developers and users
 help / color / mirror / Atom feed
From: john at keeping.me.uk (John Keeping)
Subject: Encoding problem
Date: Mon, 30 Sep 2013 11:33:51 +0100	[thread overview]
Message-ID: <20130930103351.GG27238@serenity.lan> (raw)
In-Reply-To: <00ca01cebbd8$0b121eb0$21365c10$@jorge@decimal.pt>

On Sat, Sep 28, 2013 at 12:19:38AM +0100, Jorge Bastos wrote:
> Is it possible to define charset in cgitrc?
> 
> I'm having encoding problems in the frontend, in the latest version 1.8.4
> from version 0.9.2, and now non-ascii chars are shown with ?? or some other
> char instead of the correct one.
> 
>  
> 
> Is there a charset option for cgit ? I can't find it.

The charset is hardcoded to "UTF-8", which should be the default
encoding for Git commit messages and CGit does attempt to transcode Git
messages to the correct encoding.

Are you seeing '??' in the commit message or in blob/tree content?

Do you have a public repository that is exhibiting these symptoms?


  reply	other threads:[~2013-09-30 10:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-27 23:19 mysql.jorge
2013-09-30 10:33 ` john [this message]
2013-10-05 10:32   ` mysql.jorge
2013-10-06 10:46     ` john

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=20130930103351.GG27238@serenity.lan \
    --to=cgit@lists.zx2c4.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).