Open rebeccacremona opened 7 years ago
August 29 2017 discussion:
While trying to get capture via Chrome working in our Vagrant box (which is how we did things before we switched to Docker), Jack was debugging problems and found https://bugs.chromium.org/p/chromium/issues/detail?id=695212#c18. It suggests installing gnu-free-sans-font. Jack says he's not sure of the debian equivalent. Ben says, "libosmesa6-dev? fonts-freefont-otf or fonts-freefont-ttf?"
Jack:
I took a look at font rendering -- here's http://www.cssfontstack.com/ with Chrome on my local dev (with fonts-freefont-otf installed):
so if we cared about font rendering in screenshots, that would be a thing to work on
Did code result? The above says we should "merge it in." If yes, I don't see any relevant branches (only the earlier https://github.com/jcushman/perma/tree/chrome-support). I think probably there is no code to consult.
Evidently, we are not installing fonts-freefont-otf, the one that Jack mentioned.
root@3862cfab2df6:/perma/perma_web# apt-get install fonts-freefont-otf
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages will be installed:
fonts-freefont-otf
0 upgraded, 1 newly installed, 0 to remove and 61 not upgraded.
Need to get 3171 kB of archives.
After this operation, 7081 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian bullseye/main arm64 fonts-freefont-otf all 20120503-10 [3171 kB]
Fetched 3171 kB in 0s (12.6 MB/s)
debconf: delaying package configuration, since apt-utils is not installed
Selecting previously unselected package fonts-freefont-otf.
(Reading database ... 46262 files and directories currently installed.)
Preparing to unpack .../fonts-freefont-otf_20120503-10_all.deb ...
Unpacking fonts-freefont-otf (20120503-10) ...
Setting up fonts-freefont-otf (20120503-10) ...
Processing triggers for fontconfig (2.13.1-4.2) ...
Let's just install that and not think about it! Though I wonder if there are other fonts we should install too. I don't know really how a person would find out.
To be investigated for Scoop deployment.
@jcushman did some work on this, as we experimented with using Chrome for capture. Let's not lose that work; let's do some more work, and, once we are using Chrome, merge it in.