From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from resqmta-ch2-12v.sys.comcast.net (resqmta-ch2-12v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:44]) by hurricane.the-brannons.com (Postfix) with ESMTPS id B587C77C8F for ; Thu, 28 Jan 2016 00:00:28 -0800 (PST) Received: from resomta-ch2-17v.sys.comcast.net ([69.252.207.113]) by resqmta-ch2-12v.sys.comcast.net with comcast id BL0C1s0032TL4Rh01L0VPK; Thu, 28 Jan 2016 08:00:29 +0000 Received: from eklhad ([IPv6:2601:405:4001:e487:21e:4fff:fec2:a0f1]) by resomta-ch2-17v.sys.comcast.net with comcast id BL0U1s00E2MDcd701L0UCN; Thu, 28 Jan 2016 08:00:29 +0000 To: Edbrowse-dev@lists.the-brannons.com From: Karl Dahlke Reply-to: Karl Dahlke User-Agent: edbrowse/3.6.1+ Date: Thu, 28 Jan 2016 03:00:28 -0500 Message-ID: <20160028030028.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=1453968029; bh=13T1i5HUKvpBpmRyI37zEi72TImzZIkyvNdgRODKc08=; h=Received:Received:To:From:Reply-to:Subject:Date:Message-ID: Mime-Version:Content-Type; b=emE58HxLDEcRdNcdRI8xed+lZh47GjmBAjf3WEJMQP6Thdpj66sm3Q6Fpw+PQsIsc Ix9WpZPiMJMVP7o8nXBrSc3sDWo9U6/F4QiRD6LeweqS4i4gi2DmXI00cQxBXwjk75 xdwfUq9fQvUPypwIN+UN+g3VrRn63aeP8RjAYn6H8oO90dByqcDKBKWxYUTv6Jqzc0 RVd12Z2T/tRMP8lfRIzMutvyDTCy+aqHNPCPqDEDGAU9oEduruWjVTrNtoLoE+SftN 5WZGqdou/COz7MQwGj97cK7cbC6vgbCude4FpiPXZQnmYC2rUrkgsm4B5O0zpwRi1a nVFBtEEXvFxhA== Subject: [Edbrowse-dev] entering high unicodes 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: Thu, 28 Jan 2016 08:00:29 -0000 As per my last email about emojis, I did something very simple that will probably meet my needs, for as rarely as I do such things. ~u....; becomes the utf8 sequence for the hex unicode on input. Semi is optional. So my messsage to my wife is now written concisely as: Love you ~u1f499 ~u1f49a ~u1f49b ~u1f49c Strings become utf8, which are read by my adapter as love you blue heart green heart yellow heart purple heart so I know all is well. This does not prevent a feature like ~[green heart] in the future, with green heart in the config file, if I want to go to all that bother, but I probably don't cause I just wouldn't be doing this on a regular basis, and for the rare times I do I don't mind looking up the unicodes. I just needed an easy portable way to get them in, and u hex digits is pretty standard, though sometimes written u+hex. Karl Dahlke