Updates:
Status: Started
Owner: js...@chromium.org
Cc: -js...@chromium.org w...@chromium.org
Labels: -Mstone-X Area-BrowserBackend Mstone-3
Comment #10 on issue 2939 by js...@chromium.org: Non-ASCII characters will
be displayed as garbage using FTP
http://code.google.com/p/chromium/issues/detail?id=2939
The current Windows-only ftp_job does not give us the raw byte sequence and
we can't
do much with the encoding (as it was the case with the old HTTP
implemention which we
replaced with 'new_http').
With new_ftp_job, it's possible to apply the encoding detection before
making up an
html output. Actually, I want to call the encoding detector after building
the whole
html output in OnReadComplete(), but given the way the html output is built
using
GetDirectoryListing* which in turn calls JsonDoubleQuote(), it's not easy.
As long as we get a chunk of bytes with a reasonable size, detecting the
encoding in
the middle should work decently.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---
