Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #220812 > unrolled thread
| Started by | Beco <rcb@beco.cc> |
|---|---|
| First post | 2020-04-02 22:50 +0200 |
| Last post | 2020-04-05 00:50 +0200 |
| Articles | 7 — 2 participants |
Back to article view | Back to linux.debian.user
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.
Re: Missing a "9" (possible font missing) Beco <rcb@beco.cc> - 2020-04-02 22:50 +0200
Re: Missing a "9" (possible font missing) Dan Ritter <dsr@randomstring.org> - 2020-04-03 01:10 +0200
Re: Missing a "9" (possible font missing) Beco <rcb@beco.cc> - 2020-04-04 17:40 +0200
Re: Missing a "9" (possible font missing) Dan Ritter <dsr@randomstring.org> - 2020-04-04 18:00 +0200
Re: Missing a "9" (possible font missing) Beco <rcb@beco.cc> - 2020-04-04 20:10 +0200
Re: Missing a "9" (possible font missing) Dan Ritter <dsr@randomstring.org> - 2020-04-04 23:40 +0200
(solved - part 2) Re: Missing a "9" (possible font missing) Beco <rcb@beco.cc> - 2020-04-05 00:50 +0200
| From | Beco <rcb@beco.cc> |
|---|---|
| Date | 2020-04-02 22:50 +0200 |
| Subject | Re: Missing a "9" (possible font missing) |
| Message-ID | <zReWJ-2Ro-3@gated-at.bofh.it> |
[Multipart message — attachments visible in raw view] — view raw
Hi guys,
A while ago I started this thread.
After installing tt-mscorefonsts-installer I wrote a new email with the
subject "solved" on it.
Guess I was wrong. The problem persists, now it looks like the problem is
Helvetica.
I found this link:
https://support.google.com/chrome/thread/2120514?hl=en
I don't use chrome, I use firefox. But it appears that the problem happens
in both browsers.
Still a mystery.
Maybe I messed up my system fonts. I wonder if there is a way to clean all
fonts and the the system back to its original set of fonts from the
installation.
Any clue on how to do that?
My best,
Bèco
On Mon, 21 Oct 2019 at 19:04, Michael Lange <klappnase@freenet.de> wrote:
> Hi,
>
> On Mon, 21 Oct 2019 17:39:24 -0400
> Larry Martell <larry.martell@gmail.com> wrote:
>
>
> >
> > There are many font finder apps. I use the WhatFont Chrome extension.
> > That page looks to be entirely in Verdana.
> >
>
> that depends on which fonts you have installed, according to the style
> sheet the requested font for the body is one of:
>
> "Segoe UI", Verdana, "Lucida Grande", Arial, Helvetica,sans-serif;
>
> however in the section "für die Turnierdatenbank" (tournament database)
> there is only
>
> FONT-FAMILY: "Lucida Grande", Verdana, Helvetica;
>
> Maybe this is the problem (although I would be surprised to learn that
> neither firefox nor chrome can handle this)? Anyway, installing
> ttf-mscorefonts-installer might be worth a try.
>
>
> Regards
>
> Michael
>
>
> .-.. .. ...- . .-.. --- -. --. .- -. -.. .--. .-. --- ... .--. . .-.
>
> There's a way out of any cage.
> -- Captain Christopher Pike, "The Menagerie" ("The Cage"),
> stardate unknown.
>
>
--
Dr Beco
A.I. researcher
"I know you think you understand what you thought I said but I'm not sure
you realize that what you heard is not what I meant" -- Alan Greenspan
GPG Key: https://pgp.mit.edu/pks/lookup?op=vindex&search=0x5A107A425102382A
Creation date: pgp.mit.edu ID as of 2014-11-09
[toc] | [next] | [standalone]
| From | Dan Ritter <dsr@randomstring.org> |
|---|---|
| Date | 2020-04-03 01:10 +0200 |
| Message-ID | <zRh8d-4mu-5@gated-at.bofh.it> |
| In reply to | #220812 |
Beco wrote: > Guess I was wrong. The problem persists, now it looks like the problem is > Helvetica. > > I found this link: > > https://support.google.com/chrome/thread/2120514?hl=en > > I don't use chrome, I use firefox. But it appears that the problem happens > in both browsers. > > Still a mystery. Open up the offending page in Firefox. Find a paragraph where the 9 is missing. Use the three-bar menu, Web Developer, Inspector. That should open up a debugging console underneath the webpage. On the left of the debugging console you should see a tree of HTML elements. When you mouse over them, they will be highlighted and so will the relevant portion of the page. Some parts of the tree might be folded down into triangles, which you can open up. Find the smallest element that contains the 9. Click on it in the tree to select it. Now look over at the right side of the debugging console. There's a Fonts tab. It will show you the precise font being used. That is your culprit. Tell us and we'll see if we can help you remove it. -dsr-
[toc] | [prev] | [next] | [standalone]
| From | Beco <rcb@beco.cc> |
|---|---|
| Date | 2020-04-04 17:40 +0200 |
| Message-ID | <zRT3Q-2aI-13@gated-at.bofh.it> |
| In reply to | #220813 |
[Multipart message — attachments visible in raw view] — view raw
On Thu, 2 Apr 2020 at 20:03, Dan Ritter <dsr@randomstring.org> wrote: > Beco wrote: > > Guess I was wrong. The problem persists, now it looks like the problem is > > Helvetica. > > > > I found this link: > > > > https://support.google.com/chrome/thread/2120514?hl=en > > > > I don't use chrome, I use firefox. But it appears that the problem > happens > > in both browsers. > > > > Still a mystery. > > > Open up the offending page in Firefox. Find a paragraph where > the 9 is missing. > > Use the three-bar menu, Web Developer, Inspector. That should > open up a debugging console underneath the webpage. > > On the left of the debugging console you should see a tree of > HTML elements. When you mouse over them, they will be > highlighted and so will the relevant portion of the page. Some > parts of the tree might be folded down into triangles, which you > can open up. > > Find the smallest element that contains the 9. Click on it in > the tree to select it. > > Now look over at the right side of the debugging console. > There's a Fonts tab. It will show you the precise font being > used. > > That is your culprit. Tell us and we'll see if we can help you > remove it. > > -dsr- > Thanks Dan, Did that. Still Lucida Grande. I failed to install this font like 3 times from 3 different download sites. Any official debian solution to it? Thanks. Dr. Bèco -- Dr Beco A.I. researcher "I know you think you understand what you thought I said but I'm not sure you realize that what you heard is not what I meant" -- Alan Greenspan GPG Key: https://pgp.mit.edu/pks/lookup?op=vindex&search=0x5A107A425102382A Creation date: pgp.mit.edu ID as of 2014-11-09
[toc] | [prev] | [next] | [standalone]
| From | Dan Ritter <dsr@randomstring.org> |
|---|---|
| Date | 2020-04-04 18:00 +0200 |
| Message-ID | <zRTnb-2hA-9@gated-at.bofh.it> |
| In reply to | #220880 |
Beco wrote: > On Thu, 2 Apr 2020 at 20:03, Dan Ritter <dsr@randomstring.org> wrote: > > > Beco wrote: > > > Guess I was wrong. The problem persists, now it looks like the problem is > > > Helvetica. > > > > > > I found this link: > > > > > > https://support.google.com/chrome/thread/2120514?hl=en > > > > > > I don't use chrome, I use firefox. But it appears that the problem > > happens > > > in both browsers. > > > > > > Still a mystery. > > > > > > Open up the offending page in Firefox. Find a paragraph where > > the 9 is missing. > > > > Use the three-bar menu, Web Developer, Inspector. That should > > open up a debugging console underneath the webpage. > > > > On the left of the debugging console you should see a tree of > > HTML elements. When you mouse over them, they will be > > highlighted and so will the relevant portion of the page. Some > > parts of the tree might be folded down into triangles, which you > > can open up. > > > > Find the smallest element that contains the 9. Click on it in > > the tree to select it. > > > > Now look over at the right side of the debugging console. > > There's a Fonts tab. It will show you the precise font being > > used. > > > > That is your culprit. Tell us and we'll see if we can help you > > remove it. > > > > -dsr- > > > > > Thanks Dan, > > Did that. Still Lucida Grande. > > I failed to install this font like 3 times from 3 different download sites. > > Any official debian solution to it? Let's try substitution at the X11 layer. This syntax in your ~/.fonts.conf will change the response for one font into an answer from another: <alias> <family>Lucida Grande</family> <prefer> <family>DejaVu Sans</family> </prefer> </alias> Add as many stanzas as you like; then run fc-cache and restart your application. -dsr-
[toc] | [prev] | [next] | [standalone]
| From | Beco <rcb@beco.cc> |
|---|---|
| Date | 2020-04-04 20:10 +0200 |
| Message-ID | <zRVp0-3IQ-5@gated-at.bofh.it> |
| In reply to | #220881 |
[Multipart message — attachments visible in raw view] — view raw
Dear Dan, Yes, this test indeed solved the "9" becoming a dash. I could let that as is, but after many years using linux I learned that the less you personalize your system, the less headache you will have in the future. So, how can I undo some probable mistake in my system and get it back to what it is like when first installed? Is there a debian package for Lucida Grande. I know I've tried to install many out-of-repositories alternatives for Lucida Grande that I'm willing to remove them all. Thanks, Béco On Sat, 4 Apr 2020 at 12:58, Dan Ritter <dsr@randomstring.org> wrote: > Beco wrote: > > On Thu, 2 Apr 2020 at 20:03, Dan Ritter <dsr@randomstring.org> wrote: > > > > > Beco wrote: > > > > Guess I was wrong. The problem persists, now it looks like the > problem is > > > > Helvetica. > > > > > > > > I found this link: > > > > > > > > https://support.google.com/chrome/thread/2120514?hl=en > > > > > > > > I don't use chrome, I use firefox. But it appears that the problem > > > happens > > > > in both browsers. > > > > > > > > Still a mystery. > > > > > > > > > Open up the offending page in Firefox. Find a paragraph where > > > the 9 is missing. > > > > > > Use the three-bar menu, Web Developer, Inspector. That should > > > open up a debugging console underneath the webpage. > > > > > > On the left of the debugging console you should see a tree of > > > HTML elements. When you mouse over them, they will be > > > highlighted and so will the relevant portion of the page. Some > > > parts of the tree might be folded down into triangles, which you > > > can open up. > > > > > > Find the smallest element that contains the 9. Click on it in > > > the tree to select it. > > > > > > Now look over at the right side of the debugging console. > > > There's a Fonts tab. It will show you the precise font being > > > used. > > > > > > That is your culprit. Tell us and we'll see if we can help you > > > remove it. > > > > > > -dsr- > > > > > > > > > Thanks Dan, > > > > Did that. Still Lucida Grande. > > > > I failed to install this font like 3 times from 3 different download > sites. > > > > Any official debian solution to it? > > > Let's try substitution at the X11 layer. > > This syntax in your ~/.fonts.conf will change the response for one > font into an answer from another: > > <alias> > <family>Lucida Grande</family> > <prefer> > <family>DejaVu Sans</family> > </prefer> > </alias> > > Add as many stanzas as you like; then run fc-cache and restart > your application. > > -dsr- > -- Dr Beco A.I. researcher "I know you think you understand what you thought I said but I'm not sure you realize that what you heard is not what I meant" -- Alan Greenspan GPG Key: https://pgp.mit.edu/pks/lookup?op=vindex&search=0x5A107A425102382A Creation date: pgp.mit.edu ID as of 2014-11-09
[toc] | [prev] | [next] | [standalone]
| From | Dan Ritter <dsr@randomstring.org> |
|---|---|
| Date | 2020-04-04 23:40 +0200 |
| Message-ID | <zRYGe-5D7-23@gated-at.bofh.it> |
| In reply to | #220894 |
Beco wrote: > Yes, this test indeed solved the "9" becoming a dash. > > I could let that as is, but after many years using linux I learned that the > less you personalize your system, the less headache you will have in the > future. > > So, how can I undo some probable mistake in my system and get it back to > what it is like when first installed? > > Is there a debian package for Lucida Grande. I know I've tried to install > many out-of-repositories alternatives for Lucida Grande that I'm willing to > remove them all. Sorry, there is not. Lucida Grande is a variant of Lucida Sans that Apple commissioned and holds the copyright on. It's very likely that one of those out-of-repo alternatives is causing your problem; left to its own devices, the X11 font system will look for a reasonable match when it doesn't have precisely the font asked for. The fontconfig trick that I showed you is the proper way to inform it of a user preference; it is probably overriding something claiming to be Lucida Grande but with a poor excuse for a 9 glyph. Remove all the alternatives, and it should cope well enough. -dsr-
[toc] | [prev] | [next] | [standalone]
| From | Beco <rcb@beco.cc> |
|---|---|
| Date | 2020-04-05 00:50 +0200 |
| Subject | (solved - part 2) Re: Missing a "9" (possible font missing) |
| Message-ID | <zRZLY-6go-5@gated-at.bofh.it> |
| In reply to | #220899 |
[Multipart message — attachments visible in raw view] — view raw
On Sat, 4 Apr 2020 at 18:32, Dan Ritter <dsr@randomstring.org> wrote: > Beco wrote: > > Yes, this test indeed solved the "9" becoming a dash. > > > > I could let that as is, but after many years using linux I learned that > the > > less you personalize your system, the less headache you will have in the > > future. > > > > So, how can I undo some probable mistake in my system and get it back to > > what it is like when first installed? > > > > Is there a debian package for Lucida Grande. I know I've tried to install > > many out-of-repositories alternatives for Lucida Grande that I'm willing > to > > remove them all. > > Sorry, there is not. Lucida Grande is a variant of Lucida Sans that > Apple commissioned and holds the copyright on. > > It's very likely that one of those out-of-repo alternatives is > causing your problem; left to its own devices, the X11 font > system will look for a reasonable match when it doesn't have > precisely the font asked for. The fontconfig trick that I showed > you is the proper way to inform it of a user preference; it is > probably overriding something claiming to be Lucida Grande but > with a poor excuse for a 9 glyph. > > Remove all the alternatives, and it should cope well enough. > > > -dsr- > Dan, I removed all Lucida crap from my system, and then I also removed that small hack from ~/.fonts.conf It is working ok now. It is using an automatic alternative in the absence of Lucida Grande. I can't say exactly what font it is using, but it is probably what is configured as firefox default (Dejavu Sans). (That trick with firefox console don't show the actual font, only the one chosen by the webmaster) So, as a (second) solution, now I would again try to finish this thread with (solved). In summary: Do not install crap Lucida Grande fonts on your system. If I find a better solution on days to come, I reply to this email. Att., -- Dr Beco A.I. researcher "I know you think you understand what you thought I said but I'm not sure you realize that what you heard is not what I meant" -- Alan Greenspan GPG Key: https://pgp.mit.edu/pks/lookup?op=vindex&search=0x5A107A425102382A Creation date: pgp.mit.edu ID as of 2014-11-09
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.user
csiph-web