-
Notifications
You must be signed in to change notification settings - Fork 3.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fontforge PPA / font-patcher script errors #725
Comments
The fonts should in either
It seems like the repository is not available for your ubuntu version. Is the issue with the apt commands specifically? If so I don't see how this is an issue with the fonts unless you mean the install doesn't seem to install them? |
I faced the exact PPA related issue on Ubuntu 20.04 LTS. Something seems off with the I fixed it by installing the |
Maybe my question is dumb, I never used WSL. But Ubuntu (20.04) (i.e. |
@Finii FontForge's website mentions adding the PPA for some reason. Package from the official repo also does the trick however. |
I went out to fix that, but can not find it.
Emphasis is mine Maybe you can give me the concrete link and/or a screenshot that we can fix that bit of information. |
@ryanoasis @Finii since the docs clearly mention that the Ubuntu PPA is now deprecated, maybe the issue should be closed as well? |
Actually, the patcher script also points to designwithforge.com. Here's the error message:
It needs to be updated as well, I guess. |
[why] When the fontforge python bindings are not installed we fail while importing psMat. The message suggests that fontforge itself is not installed - which is not the real reason. One can use the libfontforfge with the python-fontforge without having the GUI program fontforge. Furthermore we link to outdated installation instructions. [how] We already check and report correctly what needs to be done with the fontforge module import. As both modules are often in the same package we should probably report the same message. That message holds correct hints for Debian/Ubuntu. It does not have a link to fontforge, though. [note] Also update Debian package name. Fixes: #725 Reported-by: Aniket Teredesai <[email protected]> Signed-off-by: Fini Jastrow <[email protected]>
Created 2 PRs ;-) This issue will be autoclosed when merged. |
[why] When the fontforge python bindings are not installed we fail while importing psMat. The message suggests that fontforge itself is not installed - which is not the real reason. One can use the libfontforfge with the python-fontforge without having the GUI program fontforge. Furthermore we link to outdated installation instructions. [how] We already check and report correctly what needs to be done with the fontforge module import. As both modules are often in the same package we should probably report the same message. That message holds correct hints for Debian/Ubuntu. It does not have a link to fontforge, though. [note] Also update Debian package name. Fixes: #725 Reported-by: Aniket Teredesai <[email protected]> Signed-off-by: Fini Jastrow <[email protected]>
This issue has been automatically locked since there has not been any recent activity (i.e. last half year) after it was closed. It helps our maintainers focus on the active issues. If you have found a problem that seems similar, please open a new issue, complete the issue template with all the details necessary to reproduce, and mention this issue as reference. |
[why] When the fontforge python bindings are not installed we fail while importing psMat. The message suggests that fontforge itself is not installed - which is not the real reason. One can use the libfontforfge with the python-fontforge without having the GUI program fontforge. Furthermore we link to outdated installation instructions. [how] We already check and report correctly what needs to be done with the fontforge module import. As both modules are often in the same package we should probably report the same message. That message holds correct hints for Debian/Ubuntu. It does not have a link to fontforge, though. [note] Also update Debian package name. Fixes: ryanoasis#725 Reported-by: Aniket Teredesai <[email protected]> Signed-off-by: Fini Jastrow <[email protected]>
🎯 Subject of the issue
Setup: Windows 11 running WSL2 on Ubuntu 20.0403, Bash shell
I have installed b-ryan's powerline-shell prompt and my goal is to enable the icon glyphs included with the package. I tried the method of simply patching an individual font (CascadiaCode) for Microsoft without luck. Ultimately, I cloned the nerd-fonts repository and ran the install.sh script successfully.
Whenever I cache my fonts, it appears to run successfully and showed that roughly 154 fonts were added; however, the fonts do not show up in the /.local/share/fonts directory. At most, I was able to install CascadiaCode from Microsoft's release and change my font face within Properties -> Fonts.
I run into issues when I get to the font-forge and font-patcher steps.
When running this command I receive the following output:
sudo add-apt-repository ppa:fontforge/fontforge;
🔧 Your Setup
Anonymice Powerline Nerd Font Complete.ttf
)?iterm2
,urxvt
,gnome
,konsole
)?★ Optional
The text was updated successfully, but these errors were encountered: