| Git Clone URL: | https://aur.archlinux.org/ttf-google-fonts-git.git (read-only, click to copy) |
|---|---|
| Package Base: | ttf-google-fonts-git |
| Description: | TrueType fonts from the Google Fonts project (git version) |
| Upstream URL: | https://github.com/google/fonts |
| Keywords: | fonts google ttf |
| Licenses: | custom:SIL Open Font License, custom:Ubuntu Font License v1.0 |
| Conflicts: | jsmath-fonts, lohit-fonts, ttf-andika, ttf-arabeyes-fonts, ttf-cardo, ttf-comfortaa, ttf-google-fonts-typewolf, ttf-lekton, ttf-lora-cyrillic, ttf-medievalsharp, ttf-nova, ttf-oxygen, ttf-oxygen-git, ttf-pt-fonts, ttf-source-code-pro-ibx, ttf-source-sans-pro-ibx, ttf-vollkorn-ibx |
| Provides: | jsmath-fonts, lohit-fonts, ttf-andika, ttf-cardo, ttf-carlito, ttf-comfortaa, ttf-lekton, ttf-lora-cyrillic, ttf-medievalsharp, ttf-nova, ttf-oxygen, ttf-oxygen-git, ttf-pt-fonts, ttf-source-code-pro-ibx, ttf-source-sans-pro-ibx, ttf-vollkorn-ibx |
| Submitter: | sebstar |
| Maintainer: | andrewSC |
| Last Packager: | andrewSC |
| Votes: | 557 |
| Popularity: | 0.32 |
| First Submitted: | 2013-04-27 20:41 (UTC) |
| Last Updated: | 2024-08-06 23:47 (UTC) |
Anybody getting this error?
==> Starting package()... mv: cannot stat ' ... pkg/ttf-google-fonts-git/usr/share/fonts/배달의민족-한나': No such file or directory
Fixed by removing the
# NOTE: Since the nanum* and hanna Korean font families have special characters we need to change # those folder names to prevent errors during package compression.
section
Google currently packages only 3 Indic fonts from the Lohit project: Bengali, Devanagari, and Tamil. However, the Lohit project supports many more Indic languages and fonts, viz. Assamese, Gujarati, Gurmukhi, Hindi, Kannada, Kashmiri, Konkani, Maithili, Malayalam, Marathi, Nepali, Odia, Oriya, Punjabi, Sindhi, Tamil-Classical, Telugu.
Could you please make the following changes to PKGBUILD:
If you think it's important, you could add 'lohit-fonts' to your depends array. But if you don't, people who need it can install 'lohit-fonts' on their own, and not worry about conflicts with existing packages.
misc: No worries, my autobuilds were still showing successful (and I tested this build in a clean chroot just to be sure) so I just wanted to double check about things on your end. Thanks for sharing the diff!
Ugh, apologies, I was too dumb to keep in mind that my fontconfig is actually from git, always newer (now at head from 05-25) than Extra's (03-15). Reverting for the build made the issue go away.
Since this will thus likely show for everyone with the next bump in Extra, here's the diff between build with fontconfig 03-15 (having the lines) and 05-25 (not having them): https://www.pastiebin.com/5b0dd0235c347
misc: What is the locale you have set on your machine? Can you provide links to pastes of the build output both with and without the korean lines commented out?
Still can't build this package without removing the lines containing Hangul.
They don't appear to be required anymore anyway, the first font file is already named / installed as bm-hanna_ttf, the second nanummyeongjo, the third nanumgothic.
deathtrip: There's a good amount to read though, but my recommendation would be go to back through the commentary on the package for why things are the way they are. If that raises more questions, I'm happy to answer them here or via email.
Some fonts in the conflicts list, like ttf-anonymous-pro or the adobe fonts, are in the official repos. Shouldn't they also be removed from this package? Or is there a reason they are in conflict?
mv for the first file with Korean moonrunes fails with not found.
e: nvm, seems my repo clone got corrupted e2: Or not, not found in new one as well.
Hi all, terribly sorry for not giving this package some TLC sooner! I've removed the cwtex fonts from the bottom of the PKGBUILD and added the nanum family in its place to get the package back to functional.
If there's anything you would like to see or have any comments, I'm all ears :)
Pinned Comments
thatgeek commented on 2017-11-17 03:56 (UTC)