Bug#778772: Changelogs shown do not include a correct charset for displaying them

2015-12-12 Thread Raphael Hertzog
Control: retitle -1 use .txt extension on textual extracted files Control: severity -1 wishlist On Mon, 23 Feb 2015, Raphael Hertzog wrote: > Shall we also possibly also consider using a .txt extension for all the > text files that we are extracting? Repurposing this bug to track this as a wishli

Processed: Re: Bug#778772: Changelogs shown do not include a correct charset for displaying them

2015-12-12 Thread Debian Bug Tracking System
Processing control commands: > retitle -1 use .txt extension on textual extracted files Bug #778772 [tracker.debian.org] Changelogs shown do not include a correct charset for displaying them Changed Bug title to 'use .txt extension on textual extracted files' from 'Changelogs shown do not includ

Bug#778772: Changelogs shown do not include a correct charset for displaying them

2015-02-23 Thread Raphael Hertzog
Hi, On Sun, 22 Feb 2015, Christophe Siraut wrote: > > while displaying changelog from the web interface I see that many > > characters are not shown correctly because they have a different charset > > than browser default. > > > > Could you please specify the (utf8) charset in the HTTP response o

Bug#778772: Changelogs shown do not include a correct charset for displaying them

2015-02-22 Thread Christophe Siraut
Hi, > while displaying changelog from the web interface I see that many > characters are not shown correctly because they have a different charset > than browser default. > > Could you please specify the (utf8) charset in the HTTP response or > elsewhere? These files are served by apache, it app

Bug#778772: Changelogs shown do not include a correct charset for displaying them

2015-02-19 Thread Giuseppe Sacco
Package: tracker.debian.org Severity: normal Hello, while displaying changelog from the web interface I see that many characters are not shown correctly because they have a different charset than browser default. Could you please specify the (utf8) charset in the HTTP response or elsewhere? Tha