Your message dated Sun, 29 Jul 2007 11:51:45 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#384907: privoxy: Messes up document encoding
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: privoxy
Version: 3.0.3-3
Severity: normal
Tags: l10n

When connecting to http://www.google.lt in firefox directly, fonts are 
displayed properly.  Going through privoxy, some of the 
document encoding is messed up.

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (650, 'testing'), (600, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.17.7-grsec-nomods-aoe
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages privoxy depends on:
ii  adduser                    3.63          Add and remove users and groups
ii  libc6                      2.3.6-15      GNU C Library: Shared libraries
ii  libpcre3                   4.5-1.2sarge1 Perl 5 Compatible Regular Expressi
ii  logrotate                  3.7-5         Log rotation utility

-- no debconf information


--- End Message ---
--- Begin Message ---
On Sun, 10 Sep 2006, Roland Rosenfeld wrote:

> On Sun, 27 Aug 2006, Vincas Ciziunas wrote:
> 
> > Package: privoxy
> > Version: 3.0.3-3
> > Severity: normal
> > Tags: l10n
> > 
> > When connecting to http://www.google.lt in firefox directly, fonts
> > are displayed properly.  Going through privoxy, some of the document
> > encoding is messed up.
> 
> Hmmm, I cannot reproduce this problem here.  If I connect the URL
> above, it is translated to German because of using cookies, so I tried
> wget to get different results.
> I did a 
>  wget --save-headers http://www.google.lt
> and 
>  env http_proxy=localhost:8118 wget --save-headers http://www.google.lt
> and compared the output.  I see no differences, which could influence
> the character encoding.  All I see is a removed "expires" tag from the
> cookie and 
>  <script>function PrivoxyWindowOpen(){return(null);}</script>
> added to the head as well as 
>  <script>function PrivoxyWindowOpen(a, b, c){return(window.open(a, b, 
> c));}</script>
> below the body of the HTML page.
> 
> These changes shouldn't influence the character encoding of the HTML
> page.  So I don't see how the page could be broken on your system.
> 
> Did you modify some of the configuration?  I tried this out with a
> freshly installed privoxy 3.0.3-3 (removed /etc/privoxy before to get
> rid of everything manually touched before).
> 
> I attached the two wget results, so you can compare them yourself.
> Maybe you can load them into your browser and have a look whether they
> look correct for you (sorry, I don't know which characters are
> displayed properly in your language).

You didn't react to my questions for nearly a year now and the problem
isn't reproducible to me, so I close this bug report now.

Tschoeeee

        Roland

--- End Message ---

Reply via email to