From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wi0-x22b.google.com (mail-wi0-x22b.google.com [IPv6:2a00:1450:400c:c05::22b]) by hurricane.the-brannons.com (Postfix) with ESMTPS id 1C26578637 for ; Wed, 26 Feb 2014 09:18:06 -0800 (PST) Received: by mail-wi0-f171.google.com with SMTP id cc10so6179095wib.16 for ; Wed, 26 Feb 2014 09:17:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=5mRNtSn0TcQs0K1MDhBk903Ocd072EQxorkjFgyo/ps=; b=XIzHjad72lN5OsoFBwMqJPcygOH70kldHFeuY60bciJziWk2yZIk1eSlf0zN0QKex+ hCpn0pvy4ggsWswRTcelJFu2Y7/eRlgTzfd6IZpFC1jaPw/U8CrVMwpOTqGNfORxPl6y mOS9uirVLAgJ1JT4AJ323FsxO6iLDy9dUwGregWIr+R7nhcvAxvGa8mgpMSdJ/vVTxfa hXmHYoEdyafSkssdTCEX/ZtzJQERxGKLrs6sCkIF57qOPnXFbsag0ga+1vZQfM6Vg6qD +3TBPGWCVxqEu2uTA+PqNI0nSb9MtRWto4MBuiErTkowX1wPDZdGLMlBAUbfCkm3na7S nMhA== X-Received: by 10.194.89.33 with SMTP id bl1mr2900527wjb.64.1393435024721; Wed, 26 Feb 2014 09:17:04 -0800 (PST) Received: from toaster.adamthompson.me.uk (toaster.adamthompson.me.uk. [2001:8b0:1142:9042::2]) by mx.google.com with ESMTPSA id p1sm11984994wie.1.2014.02.26.09.17.02 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Wed, 26 Feb 2014 09:17:03 -0800 (PST) Date: Wed, 26 Feb 2014 17:17:00 +0000 From: Adam Thompson To: Karl Dahlke Message-ID: <20140226171700.GE6911@toaster.adamthompson.me.uk> References: <20140126091001.eklhad@comcast.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="EgVrEAR5UttbsTXg" Content-Disposition: inline In-Reply-To: <20140126091001.eklhad@comcast.net> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Edbrowse-dev@lists.the-brannons.com Subject: Re: [Edbrowse-dev] andTranslate X-BeenThere: edbrowse-dev@lists.the-brannons.com X-Mailman-Version: 2.1.17 Precedence: list List-Id: Edbrowse Development List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Feb 2014 17:18:07 -0000 --EgVrEAR5UttbsTXg Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Feb 26, 2014 at 09:10:01AM -0500, Karl Dahlke wrote: > Yeah, if the user's console is iso 8859-1, I would embed the unicode if l= ess than 256, > or just put a question mark if higher and untranslated in the config file. > I, like you, think this is not a big problem; > almost everyone is utf8 by now. I hope so as otherwise some of the js stuff's going to do odd things. I remember this came up when we were first playing with mozjs 24 and the decision was that it shouldn't be a problem for js strings (intended for co= nsole output) so we may as well take the same approach here. I like the ability to translate things in the config file. I almost wonder if it wouldn't be nicer to have some more generic utf8 translation mechanism available (haven't really thought how to handle input= ), perhaps available as a toggle. This'd help those of us who use edbrowse on odd consoles (or ones which cla= im to be utf8 but won't display it) or with screenreaders which don't do utf8. It'd be kind of nice to tell edbrowse to=20 translate the utf8 in whatever I'm reading into whatever form I've told it to use with a single command, rather than a set of substitutions. I know I can sit down with an utf8 table and set up all the substitutions a= s a function, but if we're going to do the mechanism anyway I wonder if we can = move it from format.c to somewhere else. This way the mechanism would be: - Do all the mandatory html translations (< > etc) as now in format.c - put any utf8 in the output - if console is iso8859 translate according to the existing rules and the c= onfig file - if not and the user wants utf8 translation (broken console, screen reader or whatever) perform just the config file driven part of the = translation If I remember rightly the non-utf8 console step is performed for all files = at the moment, and I'd like to put the utf8 but broken step as a command to be= ran on non-html files as well. As you say though this is a potentially large change and should probably wa= it till the next release (or at least till we've thought through everything). Karl or Chris, is there any chance one (or both) of you could send an email to our debian contact as I've got nothing back f= rom my email. Cheers, Adam. PS: I'll try emailing them again when I get time --EgVrEAR5UttbsTXg Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJTDiGMAAoJELZ22lNQBzHOKGwH/A6vd/SmyyybGhPqEYQFovxS URaHbUAMiFlz6HO2OvS2vvnAOVjvW6jouiIPEFz5RhSrwoBKSLq/RlmcHYcqQ61v nGKySdDWPdX0aHY6Bzlpvylfv9np4VmBDqKilyCmxr0FZgiYeVXWKYMsyKQKaTgB /dDalKO8PvCb4S7fg1R8Xm3JxPwpeNTq3SyPi15/Rf4Kj9Hk/JLx79CY2JngcT5n 8MfQ14M52MVw6JAAut+VIiVxIVdY3dctW70ZxHZXbbEXrjcKOez0h1+FfO9VTBIb O9Us8f0hOCk4BSWLe4QwpZSRQCgiWzED78lVCyl19//yOUDMK9s9z+nWl/c62AI= =1nmI -----END PGP SIGNATURE----- --EgVrEAR5UttbsTXg--