* gitweb commitdiff output error
@ 2006-09-28 7:20 Dongsheng Song
2006-10-03 9:01 ` Jakub Narebski
0 siblings, 1 reply; 2+ messages in thread
From: Dongsheng Song @ 2006-09-28 7:20 UTC (permalink / raw)
To: git
Hi,
When the file enconding is not utf8, the gitweb commitdiff output
error for non-ascii characters.
Can I do iconv for commitdiff ?
Dongsheng
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: gitweb commitdiff output error
2006-09-28 7:20 gitweb commitdiff output error Dongsheng Song
@ 2006-10-03 9:01 ` Jakub Narebski
0 siblings, 0 replies; 2+ messages in thread
From: Jakub Narebski @ 2006-10-03 9:01 UTC (permalink / raw)
To: git
Dongsheng Song wrote:
> When the file enconding is not utf8, the gitweb commitdiff output
> error for non-ascii characters.
>
> Can I do iconv for commitdiff ?
You can, most probably, but perhaps not as something that is universal.
In git you can set commit message encoding, but git does not remember
(and has no set place where to save it) information about file encoding.
You would have either use default UTF-8 encoding of gitweb page, and do
iconv equivalent, by using "encoding" module and/or "Encode" module,
and by opening diff with "-|:encoding(utf16)" (where of course you have
to put correct encoding). And you would have to set default file encoding
(and perhaps filename encoding) somewhere.
Still, it wouldn't help for example diff of encoding _change_...
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2006-10-03 9:01 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-09-28 7:20 gitweb commitdiff output error Dongsheng Song
2006-10-03 9:01 ` Jakub Narebski
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).