From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from resqmta-ch2-07v.sys.comcast.net (resqmta-ch2-07v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:39]) by hurricane.the-brannons.com (Postfix) with ESMTPS id 2E9D077AF8 for ; Fri, 22 Jan 2016 06:29:41 -0800 (PST) Received: from resomta-ch2-16v.sys.comcast.net ([69.252.207.112]) by resqmta-ch2-07v.sys.comcast.net with comcast id 92Wp1s0022S2Q5R012WyMV; Fri, 22 Jan 2016 14:30:58 +0000 Received: from eklhad ([IPv6:2601:405:4001:e487:21e:4fff:fec2:a0f1]) by resomta-ch2-16v.sys.comcast.net with comcast id 92Wx1s00H2MDcd7012Wx8e; Fri, 22 Jan 2016 14:30:58 +0000 To: edbrowse-dev@lists.the-brannons.com From: Karl Dahlke Reply-to: Karl Dahlke References: <20160122130158.GA2555@Kraftkrust> User-Agent: edbrowse/3.6.1+ Date: Fri, 22 Jan 2016 09:30:57 -0500 Message-ID: <20160022093057.eklhad@comcast.net> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1453473058; bh=EFXEblXawoTU8lRVjv27N/eE441f5Ik2xSJi9iHvBYc=; h=Received:Received:To:From:Reply-to:Subject:Date:Message-ID: Mime-Version:Content-Type; b=ByX743zRLAo5baKFtZK27kqSkv6E4OBkZcpU180Vgv3yTQzR+evLSp3G2iciblzR6 4akKBwxz/T+FEz+BMW+AlwOVI+IVMopW2CgvMY8LBd583vk1vAbTmLLaxc6s7BRpZP R7+LjtuGcTGkMv9I/h9No/yqJbgV5JBv2gRfbfxqkRexN7BYwDYPI8h72ak/zglGw+ sQTPDSd52QLXriMbird6xOavh/6Sp++SwpvkknDvpGmFfJQgMG2LRavXyYXBAHzIUq oZJUrFtMel5yzJMPbv+ytKIB5sGMV3ZfzxYB11FT+ShG0T0wvPafO+iy6WjEH1RYS1 1GZrPWkaz011Q== Subject: [Edbrowse-dev] Edbrowse recognizing site as binary data X-BeenThere: edbrowse-dev@lists.the-brannons.com X-Mailman-Version: 2.1.20 Precedence: list List-Id: Edbrowse Development List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Jan 2016 14:29:41 -0000 > edbrowse https://portal.slm.tu-dresden.de > cannot browse a binary file > I presume that's a bug? Is there anything I can do to help resolving this issue? Not a bug technically, it's a feature not yet implemented. Save the data to a file and run /bin/file on it and get this HTML document, Little-endian UTF-16 Unicode text The problem is utf-16, which edbrowse does not recognize. This has been discussed on the group. It is very rare on the internet and becoming rarer still, so not sure if it is worth the bother to implement. similar comments for utf-32. Though these are more common on Windows, I'm told, so maybe we should implement. Anyways this is the first time a user has reported such a page to us. Use the bd command to get around it, like this. But any unicode chars above 256 will be garbled. bd e edbrowse https://portal.slm.tu-dresden.de 1s/^..// ,s/\0//g b Karl Dahlke