changing default font
75 views
Skip to first unread message
Mike Frysinger
May 4, 2017, 3:58:38 PM5/4/17
to chromium-hterm
how do people feel about changing the default font to either Google Noto or Roboto (the Android standard one) ? we'd have to bundle them with the extension to avoid hitting the network, but that shouldn't be a big deal as it'd be like <100k.
the current default fonts have problems rendering combining characters. i'm not sure it's the fault of Chrome/Blink, or the font. i suspect the font.
for example, https://crbug.com/212705 and https://crbug.com/212708. you can see the examples below. both DejaVu and the default monospace on Chrome OS and Linux render things incorrectly while Noto & Roboto render correctly.
i'd lean towards Noto as i believe it has better glyph coverage than Roboto, especially since that's the entire point of the project :).
-mike
Brandon Gilmore
May 4, 2017, 4:05:08 PM5/4/17
to Mike Frysinger, chromium-hterm
+1 to shipping Google Noto
It's a reasonable default, and we can document how to set a userstyle to switch to another web font (if such a FAQ entry doesn't already exist)
--
You received this message because you are subscribed to the Google Groups "chromium-hterm" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-hterm+unsubscribe@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-hterm/CAAbOScnJt25iRKw65v0norXcDQyGZfBFV8R-hskZ8q6ZmPuPDA%40mail.gmail.com.
Mike Frysinger
May 4, 2017, 4:20:40 PM5/4/17
to Brandon Gilmore, chromium-hterm
i FAQ-ed the webfont angle with the latest release:
but people also have the "font-family" option to select system fonts. i'd just change the default value of "font-family" to list "Noto Mono" before any other, and update the default css to import the local web copy.
-mike
Matt Tennant
May 4, 2017, 8:07:27 PM5/4/17
to Mike Frysinger, Brandon Gilmore, chromium-hterm
I'll ask the question: what about supporting people who need "combining characters" to change the font and leaving the default, rather than changing the default and supporting people who didn't want their font changed to change the font back? Both scenarios involve some people changing their font. Is supporting "combining characters" by default compelling enough to force a default change on all users?
-Matt
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-hterm/CAAbOScmmqMnDNbxjJyEp6JToZcNXxWin2Tdf_0NbpH4_jwPJ%3DQ%40mail.gmail.com.
Mike Frysinger
May 4, 2017, 8:35:22 PM5/4/17
to Matt Tennant, chromium-hterm
the issue is that the font in question is broken. if people want to use a broken font, they can opt into that. if they want the font to not be broken, they have to report it to whoever maintains/created that font. hterm can't workaround this. we aren't taking away any functionality here.
as for the default font, i contend that the default behavior should be correct behavior. while us anglophiles don't usually encounter or care about combining characters, it's pretty common in many languages elsewhere.
keep in mind that hterm already has a default font list and we're giving some fonts higher priority than whatever the system monospace font is configured. i'm suggesting we change it make a known good font the default out of the box.
what is your concern here ?
-mike
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-hterm/CA%2BLHHCZC1Axz48hbVmpr4NaU9xoR5-F-_E8D0H_ZgV96B8JeDQ%40mail.gmail.com.
Matt Tennant
May 4, 2017, 8:46:57 PM5/4/17
to Mike Frysinger, chromium-hterm
I'm mostly just adverse to change that isn't by choice. :) I understand all your points. It makes sense. Hopefully I won't even notice the change and I'll go on using it without a hiccup.
Mike Frysinger
May 4, 2017, 9:08:14 PM5/4/17
to Matt Tennant, chromium-hterm
from what i can tell, it shouldn't impact existing installs. the defaults are initialized when you run it, and they stick across your browser syncs. so even if you sign into a new chromebook, your prefs would sync across, and nothing would change for you.
if i wanted it to proactively switch the default, i would have to add some code for it. at this point, i don't think i will. if people notice combining character issues here, we can tell them to switch fonts (and we bundle a sane one they can easily switch to).
i might change my mind in the future though :).
-mike
Robert Ginda
May 4, 2017, 9:45:36 PM5/4/17
to Mike Frysinger, Matt Tennant, chromium-hterm
It'll impact everyone who hasn't changed the default font, which is probably most installs. I'd lean towards not changing this.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-hterm/CAAbOSckodAyajod99ykysOq-9PULDscD7mDhis-3YXRzQNzDLQ%40mail.gmail.com.
Mike Frysinger
May 4, 2017, 10:40:04 PM5/4/17
to Robert Ginda, Matt Tennant, chromium-hterm
sure, that's what i'm suggesting :). but OK, it's less work for me to not do that.
i'll assume you're OK with bundling Google Noto.
-mike
Nicholas Sielicki
May 5, 2017, 3:56:51 AM5/5/17
to chromium-hterm, vap...@chromium.org, mten...@chromium.org
I'd imagine that most users are happy with any monospaced font until
they're given reason to change it (eg: a missing glyph, etc)
they're given reason to change it (eg: a missing glyph, etc)
I think that among the subset of users that are using the default font
settings, more of them would be inconvenienced by their font not
rendering correctly than would be inconvenienced (or even notice) that
their font changed to Noto. That being said, I think the amount of
chromium-hterm users that would ever encounter that particular
rendering error within the context of a terminal window is probably
smaller than the amount of people who would notice their font changing.
settings, more of them would be inconvenienced by their font not
rendering correctly than would be inconvenienced (or even notice) that
their font changed to Noto. That being said, I think the amount of
chromium-hterm users that would ever encounter that particular
rendering error within the context of a terminal window is probably
smaller than the amount of people who would notice their font changing.
All in all, I'd still say +1 to Noto as default.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-hter...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-hterm/CAAbOScnJt25iRKw65v0norXcDQyGZfBFV8R-hskZ8q6ZmPuPDA%40mail.gmail.com.
--
You received this message because you are subscribed to the Google Groups "chromium-hterm" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-hterm/CAAbOScmmqMnDNbxjJyEp6JToZcNXxWin2Tdf_0NbpH4_jwPJ%3DQ%40mail.gmail.com.--
You received this message because you are subscribed to the Google Groups "chromium-hterm" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-hterm/CA%2BLHHCZC1Axz48hbVmpr4NaU9xoR5-F-_E8D0H_ZgV96B8JeDQ%40mail.gmail.com.
Paul Fox
May 5, 2017, 2:06:47 PM5/5/17
to chromium-hterm
nicholas wrote:
> I'd imagine that most users are happy with any monospaced font until
> they're given reason to change it (eg: a missing glyph, etc)
>
> I think that among the subset of users that are using the default font
> settings, more of them would be inconvenienced by their font not
> rendering correctly than would be inconvenienced (or even notice) that
> their font changed to Noto. That being said, I think the amount of
> chromium-hterm users that would ever encounter that particular
> rendering error within the context of a terminal window is probably
> smaller than the amount of people who would notice their font changing.
>
> All in all, I'd still say +1 to Noto as default.
agreed on all of the above. i'd go ahead and fix it. speaking for
> I'd imagine that most users are happy with any monospaced font until
> they're given reason to change it (eg: a missing glyph, etc)
>
> I think that among the subset of users that are using the default font
> settings, more of them would be inconvenienced by their font not
> rendering correctly than would be inconvenienced (or even notice) that
> their font changed to Noto. That being said, I think the amount of
> chromium-hterm users that would ever encounter that particular
> rendering error within the context of a terminal window is probably
> smaller than the amount of people who would notice their font changing.
>
> All in all, I'd still say +1 to Noto as default.
myself, i didn't even know the font was selectable, and certainly not
how to select it. i have to imagine there are a lot of folks like me,
including in places where the current font bug would be noticed.
(i'm actually a little confused by the exchange between rginda and mike,
below, as to whether installations using the current default, unchanged,
will be affected.)
paul
>
> On Thursday, May 4, 2017 at 8:45:36 PM UTC-5, rginda wrote:
>
> It'll impact everyone who hasn't changed the default font, which is
> probably most installs. I'd lean towards not changing this.
> wrote:
> from what i can tell, it shouldn't impact existing installs. the defaults
> are initialized when you run it, and they stick across your browser syncs.
> so even if you sign into a new chromebook, your prefs would sync across,
> and nothing would change for you.
...
> from what i can tell, it shouldn't impact existing installs. the defaults
> are initialized when you run it, and they stick across your browser syncs.
> so even if you sign into a new chromebook, your prefs would sync across,
> and nothing would change for you.
=----------------------
paul fox, p...@foxharp.boston.ma.us (arlington, ma, where it's 44.1 degrees)
Mike Frysinger
May 5, 2017, 2:13:31 PM5/5/17
to Paul Fox, chromium-hterm
Rob & i were also confused by our exchange, so we sorted it out over hangouts ;)
the plan is to integrate Noto and add Noto/Roboto to the head of the default list. i thought i could make it work so existing default users wouldn't be changed, but Rob says my testing was incorrect ;), and it's prob not worth the effort to actually pull it off (as you guys suggested). progress is tracked here:
however, to help keep people from getting confused, we'll improve the initial UX so that we list release highlights at the start of the first few sessions. this will also allow us to announce features that users might be interested in (like webfonts or IPv6 or ssh:// or IDN or ...). that's tracked here:
-mike
--
You received this message because you are subscribed to the Google Groups "chromium-hterm" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-hterm/20170505180645.36A4251803D3%40grass.foxharp.boston.ma.us.
Reply all
Reply to author
Forward
0 new messages