From: Kevin Carhart <kevin@carhart.net>
To: Karl Dahlke <eklhad@comcast.net>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] bad byte in NASA's vendor.js
Date: Fri, 30 Dec 2016 21:28:06 -0800 (PST) [thread overview]
Message-ID: <alpine.LRH.2.03.1612302103060.9360@carhart.net> (raw)
In-Reply-To: <20161130181351.eklhad@comcast.net>
> Kevin this is good detective work
> any thoughts on replacing breakspace with space, or other ideas?
Thank you - I am glad you both have been able to run with this today
because I may not know or may not have known where to take it. I get
what you mean about the unpleasant nature of regular expressions sitting
there in JS. We implemented the TidyEscapeScripts flag recently for
something on a similar theme, thanks to Geoff's assistance.
I will march on & report back.
Kevin
prev parent reply other threads:[~2016-12-31 5:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-30 1:30 Kevin Carhart
2016-12-30 2:11 ` Chris Brannon
2016-12-30 3:24 ` Karl Dahlke
2016-12-30 18:52 ` Chris Brannon
2016-12-30 19:58 ` Karl Dahlke
2016-12-30 20:07 ` Chris Brannon
2016-12-30 23:13 ` Karl Dahlke
2016-12-31 5:28 ` Kevin Carhart [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LRH.2.03.1612302103060.9360@carhart.net \
--to=kevin@carhart.net \
--cc=Edbrowse-dev@lists.the-brannons.com \
--cc=eklhad@comcast.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).