Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > sci.physics > #534452 > unrolled thread

Re: "OCR A" is a highTech, nextGeneration font.

Started bySnit <usenet@gallopinginsanity.com>
First post2015-11-21 16:29 -0700
Last post2015-11-21 20:33 -0700
Articles 5 — 1 participant

Back to article view | Back to sci.physics

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: "OCR A" is a highTech, nextGeneration font. Snit <usenet@gallopinginsanity.com> - 2015-11-21 16:29 -0700
    Re: I like <PRE>; I can't please everyone, nor do I want to. Snit <usenet@gallopinginsanity.com> - 2015-11-21 16:49 -0700
      Re: <PRE> works _nicely_ on small screens. Snit <usenet@gallopinginsanity.com> - 2015-11-21 17:33 -0700
        Re: <PRE> works _nicely_ on small screens. Snit <usenet@gallopinginsanity.com> - 2015-11-21 17:59 -0700
          Re: <HTML> and <Body> do _not_ need closing tags. Snit <usenet@gallopinginsanity.com> - 2015-11-21 20:33 -0700

#534452 — Re: "OCR A" is a highTech, nextGeneration font.

FromSnit <usenet@gallopinginsanity.com>
Date2015-11-21 16:29 -0700
SubjectRe: "OCR A" is a highTech, nextGeneration font.
Message-ID<D2764C7E.64E9C%usenet@gallopinginsanity.com>
On 11/21/15, 4:01 PM, in article Jeff-Relf.Me@Nov.21{3.01P.Seattle.2015},
"Jeff-Relf.Me" <@.> wrote:

>  
> Steve_Carroll,
> 
> "OCR A" is a highTech, nextGeneration font, apparently.

Bigger issue is using PRE which prevents wrap.

> "Jeff-Relf.Me" used to have a "monospace" font on Androids.
> 
> Since I started using the "OCR A" font, that changed, apparently,
> and I didn't think to reCheck it because anything in a <PRE> tag
> _should_ be using a "monospace" font -- this is an Android bug.

If it is not monospace on Android that IS a bug. And if you did not know
that shows you did not, as you claim, check it on all devices.

> Now, on crappy/buggy Androids,
> "Jeff-Relf.Me" has a "monospace" font, if not "OCR A"; see:
> 
>   
> https://developers.google.com/speed/pagespeed/insights/?url=http%3A%2F%2Fjeff-
> relf.me%2F
> 



-- 
* OS X / Linux: What is a file?     <http://youtu.be/_dMbXGLW9PI>
* Mint MATE Trash, Panel, Menu:     <http://youtu.be/C0y74FIf7uE>
* Mint KDE working with folders:    <http://youtu.be/7C9nvniOoE0>
* Mint KDE creating files:          <http://youtu.be/N7-fZJaJUv8>
* Mint KDE help:                    <http://youtu.be/3ikizUd3sa8>
* Mint KDE general navigation:      <http://youtu.be/t9y14yZtQuI>
* Mint KDE bugs or Easter eggs?     <http://youtu.be/CU-whJQvtfA>
* Easy on OS X / Hard on Linux:     <http://youtu.be/D3BPWANQoIk>
* OS / Word Processor Comparison:   <http://youtu.be/w6Qcl-w7s5c>

[toc] | [next] | [standalone]

#534460 — Re: I like <PRE>; I can't please everyone, nor do I want to.

FromSnit <usenet@gallopinginsanity.com>
Date2015-11-21 16:49 -0700
SubjectRe: I like <PRE>; I can't please everyone, nor do I want to.
Message-ID<D2765122.64EAD%usenet@gallopinginsanity.com>
In reply to#534452
On 11/21/15, 4:39 PM, in article Jeff-Relf.Me@Nov.21{3.39P.Seattle.2015},
"Jeff-Relf.Me" <@.> wrote:

>  
> You (Snit) replied to me:
>>> "OCR A" is a highTech, nextGeneration font, apparently.
>> 
>> Bigger issue is using PRE which prevents wrap.
> 
> I like <PRE>; I can't please everyone, nor do I want to.

It is not about pleasing people, it is about making your content be more
accessible. The fact it does not wrap makes it less accessible.

>>> "Jeff-Relf.Me" used to have a "monospace" font on Androids.
>>> 
>>> Since I started using the "OCR A" font, that changed, apparently,
>>> and I didn't think to reCheck it because anything in a <PRE> tag
>>> _should_ be using a "monospace" font -- this is an Android bug.
>> 
>> If it is not monospace on Android that IS a bug.
> 
> Yes, it is.  Androids are crappy/buggy.
> "OCR A" is a _basic_ font, I think.

Certainly not uncommon and I see you have a fall-back of monospace. That
should certainly work even if they do not have the font. Or did you lack the
fall-back?

>> And if you did not know, [it shows that]
>> you did not, as you claim, check it on all devices.
> 
> I did, just not often enough.  I'm not perfect.

Hence the reason understanding the code and playing some attention to
validation is important - which does not mean all invalid notes are
problems.

>>> Now, on crappy/buggy Androids,
>>> "Jeff-Relf.Me" has a "monospace" font, if not "OCR A"; see:
>>>   
>>> https://developers.google.com/speed/pagespeed/insights/?url=http%3A%2F%2Fjef
>>> f-relf.me%2F
> 
> I fixed it, as best I could.

Still does not wrap so hard to read on a device with a small screen.



-- 
* OS X / Linux: What is a file?     <http://youtu.be/_dMbXGLW9PI>
* Mint MATE Trash, Panel, Menu:     <http://youtu.be/C0y74FIf7uE>
* Mint KDE working with folders:    <http://youtu.be/7C9nvniOoE0>
* Mint KDE creating files:          <http://youtu.be/N7-fZJaJUv8>
* Mint KDE help:                    <http://youtu.be/3ikizUd3sa8>
* Mint KDE general navigation:      <http://youtu.be/t9y14yZtQuI>
* Mint KDE bugs or Easter eggs?     <http://youtu.be/CU-whJQvtfA>
* Easy on OS X / Hard on Linux:     <http://youtu.be/D3BPWANQoIk>
* OS / Word Processor Comparison:   <http://youtu.be/w6Qcl-w7s5c>

[toc] | [prev] | [next] | [standalone]

#534464 — Re: <PRE> works _nicely_ on small screens.

FromSnit <usenet@gallopinginsanity.com>
Date2015-11-21 17:33 -0700
SubjectRe: <PRE> works _nicely_ on small screens.
Message-ID<D2765B57.64EB6%usenet@gallopinginsanity.com>
In reply to#534460
On 11/21/15, 5:20 PM, in article Jeff-Relf.Me@Nov.21{4.20P.Seattle.2015},
"Jeff-Relf.Me" <@.> wrote:

>  
> You (Snit) replied to me:
>>>>> Now, on crappy/buggy Androids,
>>>>> "Jeff-Relf.Me" has a "monospace" font, if not "OCR A"; see:
>>>>>   
>>>>> https://developers.google.com/speed/pagespeed/insights/?url=http%3A%2F%2Fj
>>>>> eff-relf.me%2F
>>> 
>>> I fixed it, as best I could.
>> 
>> Still does not wrap so hard to read on a device with a small screen.
> 
> As the link above shows,
> <PRE> works _nicely_ on small screens.
> Besides, you could zoom it, if need be.

But it does not wrap so you have to move from side to side and not just
scroll down.

> It works well on _large_ screens too, of course.
> 
>>>> And if you did not know, [it shows that]
>>>> you did not, as you claim, check it on all devices.
>>> 
>>> I did, just not often enough.  I'm not perfect.
>> 
>> Hence the reason understanding the code and playing
>> some attention to validation is important
>> - which does not mean all invalid notes are problems.
> 
> Testing is important (thank you Steve_Carroll!),
> but HTML syntax "RoboValidators" are worthless.

Well, it would have helped you catch your unclosed tags and the like. :)
 
>>> "OCR A" is a _basic_ font, I think.
>> 
>> Certainly not uncommon and I see you have a fall-back of monospace.
>> That should certainly work even if they do not have the font.
>> Or did you lack the fall-back?
> 
> Adding the "monospace" fallBack font was the fix.
> But I shouldn't have to do that,
> because, by default, <PRE> uses a "monospace" font.





-- 
* OS X / Linux: What is a file?     <http://youtu.be/_dMbXGLW9PI>
* Mint MATE Trash, Panel, Menu:     <http://youtu.be/C0y74FIf7uE>
* Mint KDE working with folders:    <http://youtu.be/7C9nvniOoE0>
* Mint KDE creating files:          <http://youtu.be/N7-fZJaJUv8>
* Mint KDE help:                    <http://youtu.be/3ikizUd3sa8>
* Mint KDE general navigation:      <http://youtu.be/t9y14yZtQuI>
* Mint KDE bugs or Easter eggs?     <http://youtu.be/CU-whJQvtfA>
* Easy on OS X / Hard on Linux:     <http://youtu.be/D3BPWANQoIk>
* OS / Word Processor Comparison:   <http://youtu.be/w6Qcl-w7s5c>

[toc] | [prev] | [next] | [standalone]

#534471 — Re: <PRE> works _nicely_ on small screens.

FromSnit <usenet@gallopinginsanity.com>
Date2015-11-21 17:59 -0700
SubjectRe: <PRE> works _nicely_ on small screens.
Message-ID<D2766187.64EBE%usenet@gallopinginsanity.com>
In reply to#534464
On 11/21/15, 5:42 PM, in article Jeff-Relf.Me@Nov.21{4.42P.Seattle.2015},
"Jeff-Relf.Me" <@.> wrote:

>  
> You (Snit) replied to me:
>>> https://developers.google.com/speed/pagespeed/insights/?url=http%3A%2F%2Fjef
>>> f-relf.me%2F
>>> As the link above shows,
>>> <PRE> works _nicely_ on small screens.
>>> Besides, you could zoom it, if need be.
>> 
>> But it does not wrap so you have to move
>> from side to side and not just scroll down.
> 
> Not true; _test_ it, you'll see.

I have. I saw. It is rather annoying to view on my ancient iPod running iOS
6.

> Even if you were right, you could zoom it down;
> you don't have to scroll SideToSide.

Even sideways it is too small to read.
 
>>> Testing is important (thank you Steve_Carroll!),
>>> but HTML syntax "RoboValidators" are worthless.
>> 
>> Well, it would have helped you catch your unclosed tags and the like. :)
> 
> I added "monospace", that's all.
> Not all tags need closing.

Some, like image, do not. Sure. But things like PRE do. :)
 



-- 
* OS X / Linux: What is a file?     <http://youtu.be/_dMbXGLW9PI>
* Mint MATE Trash, Panel, Menu:     <http://youtu.be/C0y74FIf7uE>
* Mint KDE working with folders:    <http://youtu.be/7C9nvniOoE0>
* Mint KDE creating files:          <http://youtu.be/N7-fZJaJUv8>
* Mint KDE help:                    <http://youtu.be/3ikizUd3sa8>
* Mint KDE general navigation:      <http://youtu.be/t9y14yZtQuI>
* Mint KDE bugs or Easter eggs?     <http://youtu.be/CU-whJQvtfA>
* Easy on OS X / Hard on Linux:     <http://youtu.be/D3BPWANQoIk>
* OS / Word Processor Comparison:   <http://youtu.be/w6Qcl-w7s5c>

[toc] | [prev] | [next] | [standalone]

#534489 — Re: <HTML> and <Body> do _not_ need closing tags.

FromSnit <usenet@gallopinginsanity.com>
Date2015-11-21 20:33 -0700
SubjectRe: <HTML> and <Body> do _not_ need closing tags.
Message-ID<D276859C.64ED4%usenet@gallopinginsanity.com>
In reply to#534471
On 11/21/15, 6:41 PM, in article Jeff-Relf.Me@Nov.21{5.41P.Seattle.2015},
"Jeff-Relf.Me" <@.> wrote:

>  
> Speaking of my website, Jeff-Relf.Me, you (Snit) wrote:
>> It is rather annoying to view on
>> my ancient iPod running iOS 6.
> 
> On your "ancient iPod", are you serious ?

Yes, it is capable of viewing the web. Well, some of it. On a lot of modern
sites the browser crashes - on yours it does not. I will grant you that. :)

> Who browses the web on their "ancient iPod" ?

I do sometimes... but not often. As I said, it does not deal with the modern
web well.
 
> That's _your_ problem, not mine.

Depends on the goals of your site.
 
>>> Not all tags need closing.
>> 
>> Some, like image, do not. Sure. But things like PRE do. :)
>  
> <HTML> and <Body> do _not_ need closing tags.
> Test it, you'll see.

The standard says they do. Not saying the world ends if you do not use them.



-- 
* OS X / Linux: What is a file?     <http://youtu.be/_dMbXGLW9PI>
* Mint MATE Trash, Panel, Menu:     <http://youtu.be/C0y74FIf7uE>
* Mint KDE working with folders:    <http://youtu.be/7C9nvniOoE0>
* Mint KDE creating files:          <http://youtu.be/N7-fZJaJUv8>
* Mint KDE help:                    <http://youtu.be/3ikizUd3sa8>
* Mint KDE general navigation:      <http://youtu.be/t9y14yZtQuI>
* Mint KDE bugs or Easter eggs?     <http://youtu.be/CU-whJQvtfA>
* Easy on OS X / Hard on Linux:     <http://youtu.be/D3BPWANQoIk>
* OS / Word Processor Comparison:   <http://youtu.be/w6Qcl-w7s5c>

[toc] | [prev] | [standalone]

Back to top | Article view | sci.physics

csiph-web