edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev]  bad byte in NASA's vendor.js
Date: Thu, 29 Dec 2016 22:24:46 -0500	[thread overview]
Message-ID: <20161129222446.eklhad@comcast.net> (raw)
In-Reply-To: <8760m2w4i0.fsf@the-brannons.com>

[-- Attachment #1: Type: text/plain, Size: 788 bytes --]

Wel it's easy enough to transliterate every breakspace into space, and that would fix this problem, but would it break something else?

alert("hello world");

That works now, but if I replaced breakspace mindlessly the string would change.
And probably breakspace could be part of a regexp.
I don't know, but other browsers manage it,
some using the same js engine we are using, so they must do something.

I see in that nasa js lots of other utf8 symbols in strings, just not breakspace, as it happens.

Kevin this is good detective work.

any thoughts on replacing breakspace with space, or other ideas?

You notice I remove the leading byte order mark, if any, at the start of javascript, jseng-moz.cpp line 2465.
I must have run into that one before.

Karl Dahlke

  reply	other threads:[~2016-12-30  3:24 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 [this message]
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

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=20161129222446.eklhad@comcast.net \
    --to=eklhad@comcast.net \
    --cc=Edbrowse-dev@lists.the-brannons.com \
    /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).