You are here

A couple of stray non-printable characters in the Queen "Inside Track" article online

Page 1 of 1

A couple of stray non-printable characters in the Queen "Inside Track" article online

PostPosted: Wed Apr 17, 2019 3:27 pm
by Eddy Deegan
Reading through the Queen soundtrack article (https://www.soundonsound.com/techniques ... soundtrack), I noticed that each of the two paragraphs immediately preceding and following the subheading "The Masters" have a stray non-printable 'Left Separator' character that appear as box icons in Chrome.

"works 
even better" and "blended 
in well."

In case anyone cares ;-)

Cracking article by the way, absolutely loved it :clap: :thumbup:

Re: A couple of stray non-printable characters in the Queen "Inside Track" article online

PostPosted: Wed Apr 17, 2019 4:57 pm
by Wonks
No issues for me in Firefox.

Re: A couple of stray non-printable characters in the Queen "Inside Track" article online

PostPosted: Wed Apr 17, 2019 5:45 pm
by Hugh Robjohns
Eddy Deegan wrote:...that appear as box icons in Chrome.

I'm using Chrome (v73.0.3683.103 Official Build 64-bit) on Win 7 and it looks fine to me.

Can you be more specific about your browser and OS, please?

H

Re: A couple of stray non-printable characters in the Queen "Inside Track" article online

PostPosted: Wed Apr 17, 2019 6:28 pm
by BJG145
I think I also noticed a colon that should have been a semi-colon...?

(I'll track it down and raise a proper ticket for it.)

Re: A couple of stray non-printable characters in the Queen "Inside Track" article online

PostPosted: Wed Apr 17, 2019 6:29 pm
by Eddy Deegan
Interesting! I'm running Chrome 73.0.3683.103 (Official Build) (64-bit) on Windows 10.

The section of the article in question looks like this to me (my red arrows of course):

Image

In Firefox they do not appear for me, so it seems to be a Chrome thing.

If I 'view source' on the page in Chrome, they appear as character literals in exactly the same way as shown in the screenshot above. If I enter dev tools then I can edit them out. They are a distinct character that occurs between the space preceding the words 'in' and 'even' and the words themselves.

Re: A couple of stray non-printable characters in the Queen "Inside Track" article online

PostPosted: Wed Apr 17, 2019 6:36 pm
by BJG145
...actually I love this kind of thing....lots of people up in arms about it all over the Internet. Rogue spaces at the end of a line can apparently cause this anomaly...?

Re: A couple of stray non-printable characters in the Queen "Inside Track" article online

PostPosted: Wed Apr 17, 2019 6:40 pm
by Eddy Deegan
I'm guessing this is related - seems to have been around for a while though I've not noticed it on any other articles as far as I recall.

https://stackoverflow.com/questions/396 ... ox-or-edge

https://stackoverflow.com/questions/415 ... site-l-sep

Edit: it's hardly the end of the world though, I have to admit ;)

Re: A couple of stray non-printable characters in the Queen "Inside Track" article online

PostPosted: Wed Apr 17, 2019 6:42 pm
by Folderol
Don't use chrome, but I wonder if when concatenating lines it is treating a space + EOL as a unicode character. Bad programming anyway.

{edit}
Bah Ninja'd again!

Re: A couple of stray non-printable characters in the Queen "Inside Track" article online

PostPosted: Wed Apr 17, 2019 6:51 pm
by Eddy Deegan
Yeah, if I edit them out in dev tools then check the rendered fonts, I see:

Open Sans - Network resource (648 glyphs)

Refreshing the page to see the original again, and checking the rendered fonts again I see:

Open Sans—Network resource (648 glyphs)
Times New Roman—Local file (1 glyph)


So it does look like a bug in Chrome to do with misinterpreting a specific combination of something as the Unicode Line Separator character.

For convenience here's a quote from the first stack overflow link I posted above:

That character is U+2028 Line Separator, which is a kind of newline character. Think of it as the Unicode equivalent of HTML’s <br>.

As to why it shows up here: my guess would be that an internal database uses LSEP to not conflict with literal newlines or HTML tags (which might break the database or cause security errors), and either:

1) The server-side scripts that convert the database to HTML neglected to replace LSEP with <br>

2) Chrome just breaks standards by displaying LSEP as a printing (visible) character, or

3) You have a font installed that displays LSEP as a printing character that only Chrome detects. To figure out which font it is, right click on the offending text and click “Inspect”, then switch to the “Computed” tab on the right-hand panel. At the very bottom you should see a section labeled “Rendered Fonts” which will help you locate the offending font.

Re: A couple of stray non-printable characters in the Queen "Inside Track" article online

PostPosted: Wed Apr 17, 2019 6:57 pm
by Eddy Deegan
"Online publishing!", they said. "It'll be easy!", they said ;)

Re: A couple of stray non-printable characters in the Queen "Inside Track" article online

PostPosted: Wed Apr 17, 2019 7:19 pm
by Forum Admin
Well spotted -- and now removed. [Refresh to clear your browser cache.]

There were indeed 2 spurious space characters that were not HTML but leftover from the XML export from the InDesign layout. I have a script that searches and destroys them, but I must have run it when my cursor was already positioned lower down the main text and not at the top.

Apologies, I'll drag the hair shirt out of the closet and wear it all night in shame. :blush: :blush: :blush:

Re: A couple of stray non-printable characters in the Queen "Inside Track" article online

PostPosted: Wed Apr 17, 2019 10:04 pm
by Eddy Deegan
Forum Admin wrote:now removed. [Refresh to clear your browser cache.]

Hurrah, happy to confirm that it's now fixed at this end :thumbup: :clap: