Project

General

Profile

Forums » Help »

GIT browsing: files shown in wrong encoding

Added by Jürgen Hörmann almost 14 years ago

Hello,

I'm using GIT and I'm having a problem with the encoding of the files.

My files in the repository are encoded in iso-8859-15 (german).
My server is running in UTF-8, therefore Redmine (Apache/fcgi) puts out pages with charset=utf-8

I see Redmine does not convert the iso-8859-15 files to utf-8 before sending to the browser, what results in garbeld characters (German umlauts).

Is there a way to fix that?
I did consult the GIT manual but did not find any information If I can tell GIT to convert from iso-8859-15 to utf-8 on commit. So I need Redmine to handle the encoding of textfiles.

Here my sysinfo

About your application's environment
Ruby version              1.8.7 (i486-linux)
RubyGems version          1.3.7
Rack version              1.0
Rails version             2.3.5
Active Record version     2.3.5
Active Resource version   2.3.5
Action Mailer version     2.3.5
Active Support version    2.3.5
Edge Rails revision       unknown
Application root          /var/www/redmine
Environment               production
Database adapter          mysql
Database schema version   20100221100219
script/about:6: [BUG] Segmentation fault
ruby 1.8.7 (2008-08-11 patchlevel 72) [i486-linux]


Replies (4)

RE: GIT browsing: files shown in wrong encoding - Added by Toshi MARUYAMA almost 14 years ago

Please see #5251.

RE: GIT browsing: files shown in wrong encoding - Added by Jürgen Hörmann almost 14 years ago

Thanks, that solved it for me.

I did miss to add the list of repository encodings in my settings.

RE: GIT browsing: files shown in wrong encoding - Added by Toshi MARUYAMA almost 14 years ago

Jürgen Hörmann wrote:

Thanks, that solved it for me.

I did miss to add the list of repository encodings in my settings.

Try #2664 patches.

RE: GIT browsing: files shown in wrong encoding - Added by Jürgen Hörmann almost 14 years ago

Thank you very much for the information. My problems are solved now.

I choose to not install the patches for now, because I do not use special chars in file- and pathnames. But I will bookmark this information, I'll need it some future day.

    (1-4/4)