Font Problem

I decided to see what Win 10 would look like if it used say Verdana a
its default font. So I made a reg file with this contents:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts]
"Segoe UI (TrueType)"=""
"Segoe UI Bold (TrueType)"=""
"Segoe UI Bold Italic (TrueType)"=""
"Segoe UI Italic (TrueType)"=""
"Segoe UI Light (TrueType)"=""
"Segoe UI Semibold (TrueType)"=""
"Segoe UI Symbol (TrueType)"=""

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\FontSubstitutes]

"Segoe UI"="Verdana Regular"

and applied it to the registry. After a while, I decided to go back to
Segoe UI so I created a reg file with

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts]
"Segoe UI (TrueType)"="segoeui.ttf"
"Segoe UI Black (TrueType)"="seguibl.ttf"
"Segoe UI Black Italic (TrueType)"="seguibli.ttf"
"Segoe UI Bold (TrueType)"="segoeuib.ttf"
"Segoe UI Bold Italic (TrueType)"="segoeuiz.ttf"
"Segoe UI Emoji (TrueType)"="seguiemj.ttf"
"Segoe UI Historic (TrueType)"="seguihis.ttf"
"Segoe UI Italic (TrueType)"="segoeuii.ttf"
"Segoe UI Light (TrueType)"="segoeuil.ttf"
"Segoe UI Light Italic (TrueType)"="seguili.ttf"
"Segoe UI Semibold (TrueType)"="seguisb.ttf"
"Segoe UI Semibold Italic (TrueType)"="seguisbi.ttf"
"Segoe UI Semilight (TrueType)"="segoeuisl.ttf"
"Segoe UI Semilight Italic (TrueType)"="seguisli.ttf"
"Segoe UI Symbol (TrueType)"="seguisym.ttf"
"Segoe MDL2 Assets (TrueType)"="segmdl2.ttf"
"Segoe Print (TrueType)"="segoepr.ttf"
"Segoe Print Bold (TrueType)"="segoeprb.ttf"
"Segoe Script (TrueType)"="segoesc.ttf"
"Segoe Script Bold (TrueType)"="segoescb.ttf"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\FontSubstitutes]

"Segoe UI"=-

and merged it.

The problem shows up in Facebook. The line under a picture shows up as a
yet unidentified font!

Let me know if you would like a screenshot.

What is wrong with the above procedure???

Thanks.

On 12/12/2017 1:27 PM, Alek wrote:
I decided to see what Win 10 would look like if it used say Verdana a
its default font. So I made a reg file with this contents:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts]
"Segoe UI (TrueType)"=""

snip
The problem shows up in Facebook. The line under a picture shows up as a
yet unidentified font!

Let me know if you would like a screenshot.

What is wrong with the above procedure???

Thanks.




I did not like the fonts either so used this


https://www.wintools.info/index.php/...-changer-usage

Alek wrote:
I decided to see what Win 10 would look like if it used say Verdana a
its default font. So I made a reg file with this contents:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts]
"Segoe UI (TrueType)"=""
"Segoe UI Bold (TrueType)"=""
"Segoe UI Bold Italic (TrueType)"=""
"Segoe UI Italic (TrueType)"=""
"Segoe UI Light (TrueType)"=""
"Segoe UI Semibold (TrueType)"=""
"Segoe UI Symbol (TrueType)"=""

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\FontSubstitutes]

"Segoe UI"="Verdana Regular"

and applied it to the registry. After a while, I decided to go back to
Segoe UI so I created a reg file with

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts]
"Segoe UI (TrueType)"="segoeui.ttf"
"Segoe UI Black (TrueType)"="seguibl.ttf"
"Segoe UI Black Italic (TrueType)"="seguibli.ttf"
"Segoe UI Bold (TrueType)"="segoeuib.ttf"
"Segoe UI Bold Italic (TrueType)"="segoeuiz.ttf"
"Segoe UI Emoji (TrueType)"="seguiemj.ttf"
"Segoe UI Historic (TrueType)"="seguihis.ttf"
"Segoe UI Italic (TrueType)"="segoeuii.ttf"
"Segoe UI Light (TrueType)"="segoeuil.ttf"
"Segoe UI Light Italic (TrueType)"="seguili.ttf"
"Segoe UI Semibold (TrueType)"="seguisb.ttf"
"Segoe UI Semibold Italic (TrueType)"="seguisbi.ttf"
"Segoe UI Semilight (TrueType)"="segoeuisl.ttf"
"Segoe UI Semilight Italic (TrueType)"="seguisli.ttf"
"Segoe UI Symbol (TrueType)"="seguisym.ttf"
"Segoe MDL2 Assets (TrueType)"="segmdl2.ttf"
"Segoe Print (TrueType)"="segoepr.ttf"
"Segoe Print Bold (TrueType)"="segoeprb.ttf"
"Segoe Script (TrueType)"="segoesc.ttf"
"Segoe Script Bold (TrueType)"="segoescb.ttf"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\FontSubstitutes]

"Segoe UI"=-

and merged it.

The problem shows up in Facebook. The line under a picture shows up as a
yet unidentified font!

Let me know if you would like a screenshot.

What is wrong with the above procedure???

Thanks.

But that's what Style Sheets (CSS) on the web page are for.
They give an ordered list of font substitutes. Facebook will have
already loaded a list of fonts to try, if the primary font is
not available.

You don't go messing with the OS side of things, as that's global.
You don't want your entire OS experience to be damaged the same
way by a font substitution change.

If you wanted to *only* edit Facebook, you'd use Tampermonkey
or GreaseMonkey. Good luck finding an expert to help you :-)
Those are web developer technologies, for fixing stuff on
the client side in the privacy of your own home. You can,
in effect, partially rewrite a web page. This allows you
to fix trivial "booboos" in the web pages coming from
a particular site.

https://en.wikipedia.org/wiki/Greasemonkey

https://en.wikipedia.org/wiki/List_o...wsing_software

http://tampermonkey.net/

Browsers can also have their own CSS style sheet or theme,
which controls things browser-wide. The details will vary
with browser. And with the recent changes to Firefox, you'd
expect some of the details to be out-of-date for that browser.
The file involved might have "user" or "CSS" in the name.

Paul

Alek wrote:

I decided to see what Win 10 would look like if it used say Verdana a
its default font. So I made a reg file with this contents:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts]
"Segoe UI (TrueType)"=""
"Segoe UI Bold (TrueType)"=""
"Segoe UI Bold Italic (TrueType)"=""
"Segoe UI Italic (TrueType)"=""
"Segoe UI Light (TrueType)"=""
"Segoe UI Semibold (TrueType)"=""
"Segoe UI Symbol (TrueType)"=""

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\FontSubstitutes]

"Segoe UI"="Verdana Regular"

and applied it to the registry. After a while, I decided to go back to
Segoe UI so I created a reg file with

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts]
"Segoe UI (TrueType)"="segoeui.ttf"
"Segoe UI Black (TrueType)"="seguibl.ttf"
"Segoe UI Black Italic (TrueType)"="seguibli.ttf"
"Segoe UI Bold (TrueType)"="segoeuib.ttf"
"Segoe UI Bold Italic (TrueType)"="segoeuiz.ttf"
"Segoe UI Emoji (TrueType)"="seguiemj.ttf"
"Segoe UI Historic (TrueType)"="seguihis.ttf"
"Segoe UI Italic (TrueType)"="segoeuii.ttf"
"Segoe UI Light (TrueType)"="segoeuil.ttf"
"Segoe UI Light Italic (TrueType)"="seguili.ttf"
"Segoe UI Semibold (TrueType)"="seguisb.ttf"
"Segoe UI Semibold Italic (TrueType)"="seguisbi.ttf"
"Segoe UI Semilight (TrueType)"="segoeuisl.ttf"
"Segoe UI Semilight Italic (TrueType)"="seguisli.ttf"
"Segoe UI Symbol (TrueType)"="seguisym.ttf"
"Segoe MDL2 Assets (TrueType)"="segmdl2.ttf"
"Segoe Print (TrueType)"="segoepr.ttf"
"Segoe Print Bold (TrueType)"="segoeprb.ttf"
"Segoe Script (TrueType)"="segoesc.ttf"
"Segoe Script Bold (TrueType)"="segoescb.ttf"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\FontSubstitutes]

"Segoe UI"=-

and merged it.

The problem shows up in Facebook. The line under a picture shows up as a
yet unidentified font!

Let me know if you would like a screenshot.

What is wrong with the above procedure???

Thanks.

What fonts are specified within Firefox (as fallbacks if a web page
doesn't specify a font or specifies fonts not available on the local
host)? Are the fallback fonts listed in Firefox available on your host?
Can you load Word[Pad] and use those fonts in a document that are
specified in Firefox as its fallback fonts?

What is the URL of the web page with which you are having problems?
Unless you configure web browsers to /not/ use page-specified fonts, a
page can specify a font but maybe you don't have it (hence the need for
fallback fonts in the web client). Look at the "Allow pages to choose
their own fonts". If turned off, pages may not look as legible since
the page layout and formatting was based on using the specified fonts.
However, there is a security issue because some sites use external
resources for fonts.

Since the fonts get retrieved from elsewhere than the page you visit,
because that other site will know your IP address when you connect to it
to get its fonts, and because that font site knows the site you visited
where those fonts are specified, the font site can track where you
visited, when, and how often. If the page calls for fonts from Google,
well, then Google gets to track you some more. Any font provider can do
the tracking. Some companies will block fonts originating anywhere
outside their domain to eliminate this external tracking scheme.

So it is possible that you disabled web fonts in the web browser because
you are leery of having the font provider track when and where you surf.
Or maybe you installed an add-on that, by default, disable web fonts or
led you to believe that web fonts should be disabled so you followed
their advice.

https://protonmail.uservoice.com/for...k-users-browsi
https://collinmbarrett.com/block-web-fonts/

Blocking web fonts increases your privacy but sacrifices web page
usability. For example, my pharmacy uses web fonts (served from other
than their domain) to present "controls": drop-down or back/forward
navigation buttons, symbolic buttons instead of OK to accept data put
into input fields in a page, etc. With web fonts disabled in the web
browser, their pages have oddball characters in their page. That's
because the character code used to index a character within their font
isn't available locally (their web fonts were blocked) so characters
with the same index are used from the font that my web browser has to
use. Often the character code is a high value so the page ends up with
the oddball fonts at the upper end of a font character set.

Alek wrote on 12/12/2017 2:27 PM:
snip
The problem shows up in Facebook. The line under a picture shows up as a
yet unidentified font!

And only in Firefox. So off to look at FF configs.

Alek wrote:
Alek wrote on 12/12/2017 2:27 PM:
snip
The problem shows up in Facebook. The line under a picture shows up as a
yet unidentified font!

And only in Firefox. So off to look at FF configs.

The style-sheet sent to a client, is a function
of the browser type. A Chrome user accessing Facebook
might receive a different style-sheet than a
Firefox user.

For example, if I went to Facebook, I might receive
a "Sorry, your Browser is Too Old" message. Via User Agent
sniffing, a site can craft an appropriate response for
every kind of browser or device you connect with.

Web sites also work via "capability" sniffing, but that
would be too easy. I'm sure there's still a lot of outright
User Agent sniffing.

I can't actually connect to Facebook, because it's
in my HOSTS file :-) And it's one of the few things
in my HOSTS file on this computer. So I never get
to debug a Facebook problem... Think of all the
cat pictures I'm missing out on.

Paul

Paul wrote on 12/13/2017 10:50 AM:
Alek wrote:
Alek wrote on 12/12/2017 2:27 PM:
snip
The problem shows up in Facebook. The line under a picture shows up as a
yet unidentified font!

And only in Firefox. So off to look at FF configs.

The style-sheet sent to a client, is a function
of the browser type. A Chrome user accessing Facebook
might receive a different style-sheet than a
Firefox user.

For example, if I went to Facebook, I might receive
a "Sorry, your Browser is Too Old" message. Via User Agent
sniffing, a site can craft an appropriate response for
every kind of browser or device you connect with.

Web sites also work via "capability" sniffing, but that
would be too easy. I'm sure there's still a lot of outright
User Agent sniffing.

I can't actually connect to Facebook, because it's
in my HOSTS file :-) And it's one of the few things
in my HOSTS file on this computer. So I never get
to debug a Facebook problem... Think of all the
cat pictures I'm missing out on.

Cat pictures? I don't see cat pictures.