Technical & legal background using copyrighted fonts in custom road signs in PowerPoint

Andy Burns wrote:

0xC2 0xAD

Ah unicode U+00AD is a soft-hyphen; trust a typography site to sprinkle
them everywhere :-)

Andy Burns wrote:
Andy Burns wrote:

0xC2 0xAD

Ah unicode U+00AD is a soft-hyphen; trust a typography site to sprinkle
them everywhere :-)

What I don't understand, is why that is invisible.

Some copy/paste method, the tools didn't handle the character encoding
properly, and no other tool seems to have done a consistency check.
I was at least hoping for some empty squares indicating that something
unviewable was present.

As it stands now, it means I'm going to have to toss every
piece of text I get, into a hex editor, to find **** like this.
Which is not a good lesson to be learning.

Paul

On Sat, 16 Sep 2017 09:04:46 -0400, Paul wrote:

What I don't understand, is why that is invisible.

Some copy/paste method, the tools didn't handle the character encoding
properly, and no other tool seems to have done a consistency check.
I was at least hoping for some empty squares indicating that something
unviewable was present.

As it stands now, it means I'm going to have to toss every
piece of text I get, into a hex editor, to find **** like this.
Which is not a good lesson to be learning.

I had never heard of a soft hyphen before but here it is described in the very site that used it.
http://practicaltypography.com/optional-hyphens.html

Here is a verbatim cut-and-paste of the description therein
(I turned off my word wrap so that any wrapping isn't from me):

The op*tional hy*phen, also known as the soft hy*phen, is usu*ally in*vis*i*ble. The op*tional hy*phen marks where a word should be hy*phen*ated if the word lands at the end of a line. You can put mul*ti*ple op*tional hy*phens in a word.

Why would you want to do this? Some words be*devil hy*phen*ation en*gines. For in*stance, True*Type will of*ten get hy*phen*ated as Tru-
eType. To pre*vent this, I put an op*tional hy*phen in the mid*dle (True~Type) so it will be hy*phen*ated correctly.

How do you know whether a word won¢t be hy*phen*ated cor*rectly? The prob*lem usu*ally af*flicts words that aren¢t in a stan*dard hy*phen*ation dic*tio*nary, like jar*gon words, un*usual proper names, and other words with non*stan*dard spellings, like trade names. As for*mer Supreme Court Jus*tice Pot*ter Stew*art might have said, you¢ll know it when you see it.

On Sat, 16 Sep 2017 13:00:42 +0100, Tim Streater
wrote:

And whoever it was wants to put around their long URL (corrected
above).

I've seen those angle brackets around a URL but never understood what use
is adding two completely useless extraneous characters is.

You can tell it's a URL by the http so why add two completely useless
angle-bracket characters to an already long line?

What is the purpose of the angle brackets when they're never needed?

On Sat, 16 Sep 2017 13:01:31 +0100, Tim Streater
wrote:

The oddest thing is that these are just like those curly quotes and the
curly apostrophe, where I see it just fine before I hit the SEND key in my
Usenet client.

It's only when it's received that the funky characters show up.
In my text that I send, everything looks fine when I cut and paste.

Doesn't mean it's not there, though.

I agree that it's there.

What I don't understand is why my Usenet client shows the text perfectly,
but after I send it, the received text has the funky characters in it.

What did the sending to a newsserver do to make it screw up the text?

In article , Chaya Eve
wrote:

And whoever it was wants to put around their long URL (corrected
above).

I've seen those angle brackets around a URL but never understood what use
is adding two completely useless extraneous characters is.

You can tell it's a URL by the http so why add two completely useless
angle-bracket characters to an already long line?

they're not useless.

angle brackets delimit the start/end of a url so that apps can reliably
determine the entire url, even when it spans multiple lines and/or has
embedded whitespace. it can then remove any extraneous characters if
necessary and make the url directly clickable.

another benefit is having a url in text with normal punctuation, such
as http://www.cnn.com. note the period at the end of the sentence,
which is *outside* the and therefore not part of the url. had the
not been there, the period would be assumed to be part of the url and
likely fail, such as he http://www.cnn.com.

What is the purpose of the angle brackets when they're never needed?

they're always needed.

On 2017-09-16, nospam wrote:
In article , Chaya Eve
wrote:

I've seen those angle brackets around a URL but never understood what
use is adding two completely useless extraneous characters is.

You can tell it's a URL by the http so why add two completely useless
angle-bracket characters to an already long line?

they're not useless.

No, but the nym-switching troll currently known as "Chaya Eve" is
certainly useless. To wit: He's been on Usenet trolling the Apple news
groups for a *long* time, and yet in all that time he *still* hasn't
figured out why people enclose URLs in angle brackets in their Usenet
posts. #noobtroll : D

--
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR

In article , Tim Streater
wrote:

What is the purpose of the angle brackets when they're never needed?

They stop the URL wrapping so that in subsequent follow-up posts it may
still be clicked. If you don't, then you get this sort of thing:

www.example.com/part_of_
a_long_URL/

Putting the around it, provided everyone is using a decent
newsreader, leads to this:

www.example.com/part_of_a_long_URL/

more commonly,
http://www.example.com/part_of_
a_long_URL/

which works because the newline and quote characters can be detected
and removed.

On Sat, 16 Sep 2017 19:34:05 +0100, Tim Streater
wrote:

What is the purpose of the angle brackets when they're never needed?

They stop the URL wrapping so that in subsequent follow-up posts it may
still be clicked. If you don't, then you get this sort of thing:

Thanks Tim for explaining why people enclose Urls with angle brackets.
What I do when I have a long URL (see my prior posts) is I simply unwrap
that one line so that my newsreader doesn't wrap it).

This is a long URL I have posted prior, with an unwrap character:
https://blogs.windows.com/windowsexp...uild-16273-pc/

This is the same unwrapped URL with extraneous angle brackets.
https://blogs.windows.com/windowsexperience/2017/08/23/announcing-windows-10-insider-preview-build-16273-pc/

Here is that same long URL without any wrapping by my newsreader:
https://blogs.windows.com/windowsexp...uild-16273-pc/

As a test, here is that unwrapped URL with extraneous angle brackets:
https://blogs.windows.com/windowsexperience/2017/08/23/announcing-windows-10-insider-preview-build-16273-pc/

In those four situations, what does the extraneous angle brackets do for
your newsreader?

On Sat, 16 Sep 2017 18:58:32 +0000 (UTC), Chaya Eve
wrote:

This is a long URL I have posted prior, with an unwrap character:
https://blogs.windows.com/windowsexp...uild-16273-pc/

This is the same unwrapped URL with extraneous angle brackets.
https://blogs.windows.com/windowsexperience/2017/08/23/announcing-windows-10-insider-preview-build-16273-pc/

Here is that same long URL without any wrapping by my newsreader:
https://blogs.windows.com/windowsexp...uild-16273-pc/

As a test, here is that unwrapped URL with extraneous angle brackets:
https://blogs.windows.com/windowsexperience/2017/08/23/announcing-windows-10-insider-preview-build-16273-pc/

In those four situations, what does the extraneous angle brackets do for
your newsreader?

In my newsreader, all four worked just fine when I retrieved the post.
Hence, in my newsreader, the angle brackets are extraneous redundancies.

What happened in your newsreader?
Why?