Every patched font has 2 versions: fixed-width and double-width. The former has all icons fit into 1 cell, the later retains icons' ratio. Most people prefer the second option.
The problem
Scoop installs 2 versions.
The user is supposed to install either of them, but not both. The fonts are named identically with the exception that one of them has Mono in its name. So you can set mono version explicitly, but not the other way around. This results in most (if not all) software on Windows (and Linux) using monospaced font version even if you define font name without Mono in it. Because of that, I have to manually install double-width font versions instead of using Scoop.
Proposed solution
Add a separate NF-mono entry for every font and leave usual entries for double-width fonts, so it will correspond to original NF naming convention. Or add separate entry for double-width fonts as well, to retain backward compatibility.
You can tell monospaced and non-monospaced versions apart by replacing *Windows Compatible.* in filtering query to *Mono Windows Compatible.* and *Complete Windows Compatible.*
matthewjberger
commented
4 years ago
General
Every patched font has 2 versions: fixed-width and double-width. The former has all icons fit into 1 cell, the later retains icons' ratio. Most people prefer the second option.
The problem
Scoop installs 2 versions.
The user is supposed to install either of them, but not both. The fonts are named identically with the exception that one of them has
Monoin its name. So you can set mono version explicitly, but not the other way around. This results in most (if not all) software on Windows (and Linux) using monospaced font version even if you define font name withoutMonoin it. Because of that, I have to manually install double-width font versions instead of using Scoop.Proposed solution
Add a separate
NF-monoentry for every font and leave usual entries for double-width fonts, so it will correspond to original NF naming convention. Or add separate entry for double-width fonts as well, to retain backward compatibility.You can tell monospaced and non-monospaced versions apart by replacing
*Windows Compatible.*in filtering query to*Mono Windows Compatible.*and*Complete Windows Compatible.*