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

On Sun, 10 Sep 2017 11:45:33 +0100, Andy Burns wrote:

It's a pain and it's ridiculous but there is no other viable option.

What's dictating that this should use powerpoint?

That's a good question, where if you have a better answer, I'm all ears.

You're right that it could just as well be Microsoft Word since what's
dictating the software is that there should be zero learning curve and it
should already be on everyone's system, both Mac & Windows.

But what other slide oriented software do you know of that everyone already
has on their computer and that they are comfortable using that is
compatible on Mac & Windows?

On Sun, 10 Sep 2017 09:52:27 +0100, Tim Streater
wrote:

I'm going to guess that installing, embedding, and then deleting fonts on
the Mac is as easy as it is on Windows, which was as easy as copying the
font file to the "C:\Windows\Fonts\" directory as the unzipped free
font file named: "C:\Windows\Fonts\Roadgeek 2005 Series B Regular.ttf" 44KB

That seems overly complicated. I just double-click the font and answer
"Yes" to the Q about installing it. I've never deleted a font on my Mac
so can't comment on the second issue.

If you're talking about the Mac, then that's great that it's just as easy
on the Mac to install a font as it was on Windows.

Deleting the font on Windows is as easy as right click delete.
I presume it's just as easy on the Mac.

On 2017-09-10, Tim Streater wrote:

That seems overly complicated. I just double-click the font and answer
"Yes" to the Q about installing it. I've never deleted a font on my Mac
so can't comment on the second issue.

Adding and removing fonts on macOS is brain-dead easy.

--
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

On 2017-09-08 13:38, Chaya Eve wrote:

In summary, I ask for your advice on two questions.
Q1: How do I embed a TT font into PowerPoint 2007 for others to edit, and,
Q2: What is this "css" legal stuff and I do I comply with it in PPT 2007?

I've spot read this thread with increasing levels of boredom. Not sure
if anyone asked:

Isn't there some included PowerPoint font that is usable and not
encumbered with copyright issues?

On Sun, 10 Sep 2017 10:53:02 -0400, Alan Browne
wrote:

Isn't there some included PowerPoint font that is usable and not
encumbered with copyright issues?

We want to teach these kids how to do the job right.

It's a good question because there are two kinds of people.
* Those who don't (and almost always can't) do a good job.
* Those who do the job right (which takes intelligence).
It takes attention to detail to do the job right.

It's a good question because there are two kinds of results.
* Results that are only useful for a single use.
* Results that are useful for all similar uses.
It takes intelligent thinking to optimize the results.

WHY does a sign-specific font exist?
* They are tested for readability under horrid lighting situations.
* The spacing & character sizes are optimized for short lines.
* The character selection (e.g., arrows) meets NHTSA standards.

However, as you noted, no sign font is perfect.

If you think choosing a font for signs is easy, then read this article:
http://www.nytimes.com/2007/08/12/ma...12fonts-t.html

In summary, any idiot can easily do a crappy job.
It takes intelligence and attention to detail to do the job right.

We want to teach these kids how to do the job right.

On 2017-09-08 22:18, Chaya Eve wrote:
On Fri, 8 Sep 2017 17:38:51 +0000 (UTC), Chaya Eve
wrote:
S

Troll confirmation.

On Sun, 10 Sep 2017 12:29:22 -0400, Alan Browne
wrote:

Troll confirmation.

Dude. You're the troll here, you Alan Browne moron!
Plonk!

On 2017-09-10 13:01, Dan Jenkins wrote:
On Sun, 10 Sep 2017 12:29:22 -0400,Â* Alan Browne
wrote:

Troll confirmation.

Dude. You're the troll here, you Alan Browne moron!

ROFL!

Chaya Eve wrote:
On Sun, 10 Sep 2017 06:32:21 -0400, Paul wrote:

http://www.microsoft.com/en-us/Typog...roperty21.aspx

Font properties extension 2.30

http://download.microsoft.com/downlo...9f5e/setup.exe

requirements - Windows XP or later (32-bit only)
use - 'Right click' on a font file (TrueType or OpenType)
and choose properties from the menu.

Example:

https://s26.postimg.org/9nskxef21/Mi..._Extension.gif

It looks like the license info is right in the TTF file, but without
the properties extension, may not be (normally) visible in Windows.

Hi Paul,

How the heck did you get that extension to work on Windows 10?
http://www.microsoft.com/en-us/Typog...roperty21.aspx

I had already tested that "Microsoft Font properties extension, version
2.30" shell extension on Windows 10, where it did absolutely nothing, even
after a reboot.

This is your result on Windows 10 on the Roadgeek font:
https://s26.postimg.org/9nskxef21/Mi..._Extension.gif

This is my result on Windows 10 on the Roadgeek font:
http://wetakepic.com/images/2017/09/10/roadsign_1.png

How the heck did you get the Microsoft font properties extension to work?

I tested it on WinXP SP3, because I wanted it to work :-)

For starters, it's 32 bit. Did you test it on Win10 32 bit ?
Not too many people run the 32-bit version. And that still
doesn't *guarantee* it's going to work. I don't think
the Microsoft Typography department gets paid to keep
that working, so it's YMMV as far as that goes.

https://s26.postimg.org/esit5ktyx/wo..._win10_x86.gif

*******

If you run Virustotal on the file, you can get some
similar info in the "Details" tab.

https://www.virustotal.com/#/file/f7...eced00/details

CompatibleFontName Roadgeek 2005 Series 3B

License This font may be freely distributed and
used provided copyright notifications
remain intact

But that method doesn't spell out the details in
quite the same way as the Microsoft method.

Paul

On Sun, 10 Sep 2017 13:47:02 -0400, Paul wrote:

I tested it on WinXP SP3, because I wanted it to work :-)

For starters, it's 32 bit. Did you test it on Win10 32 bit ?

I hear you.
I tested on 64-bit Win10.
It didn't work.

I'm glad it worked on 32-bit WinXP though, so we know what it does.
Thanks.