Hm, however, when I installed pre5 from apt-get, HTTPS/SSL worked, but when I do it now from pre6, it doesn't.
Even when I have openssl from apt-get installed. K On Sun, Nov 18, 2012 at 4:45 PM, Karel Bílek <k...@karelbilek.com> wrote: > Ah, nevermind. Updating to pre6 from pre5 made it working. > > Karel > > On Sun, Nov 18, 2012 at 4:35 PM, Karel Bílek <k...@karelbilek.com> wrote: >> In the header info, there is clearly written "charset=ISO-8859-2" >> >> yet elinks ignore this and thinks the data is in unicode (everything >> looks like it) >> >> On Sun, Nov 18, 2012 at 4:32 PM, Karel Bílek <k...@karelbilek.com> wrote: >>> Hello, >>> >>> I have elinks. I want to use it for googling (pretty obvious request). >>> >>> I have a terminal set to UTF8. >>> >>> When I open google.com, I get redirected into Czech google (so far so >>> good). The Czech google has correct encoding. >>> >>> But as soon as I search for something, I get indecypherable mess with >>> <?> instead of diacritics. >>> >>> The address of the search is >>> http://www.google.cz/search?ie=ISO-8859-2&hl=cs&source=hp&q=gfd&btnG=Hledat%20Googlem&gbv=1 >>> >>> When I look at the "page info" in elinks, I see "Codepage: Unicode UTF-8" >>> >>> So, something seems to be wrong. >>> >>> Karel _______________________________________________ elinks-users mailing list firstname.lastname@example.org http://linuxfromscratch.org/mailman/listinfo/elinks-users