On Sun, Jan 18, 2009 at 10:33:39PM +0900, furaisanjin wrote:
Hi all.
I created new subject thread since the original one becomes quite long and.
I found one difference between dillo-2.0 and dillo-css. there was a_Decode_charset_init calling at Cache_parse_header in cache.c when HTTP server Content-Type was detected but there isn't this in dillo-css. Because if HTTP server Content-Type is same as META content-type, there isn't any chance to call a_Decode_charset_init. This is one reason why the page is drawn properly.
Yes, there were cleanups on charset decoding. Please clarify me whether 2.1 behaviour is right or wrong! :-) And if you can send an example, better. -- Cheers Jorge.- ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________