Arch Linux User Repository

If you're having an issue upgraded with errors related to fonts like merriweather, here's my steps to resolve the issue (assuming you have Yaourt):

#Clear out what you had before

yaourt -R fonts-meta-extended-lt
sudo pacman -Rns $(pacman -Qtdq)
sudo pacman -R ttf-google-fonts-git
sudo pacman -Rns $(pacman -Qtdq)

#Install dependencies

yaourt -S ttf-merriweather-sans ttf-opensans ttf-oswald ttf-quintessential ttf-signika
yaourt -S fonts-meta-extended-lt

#Heads up, if ttf-impallari-cantora isn't fixed yet, change the PKGBUILD source to the URL in the comments on the package

yaourt -S ttf-impallari-cantora
yaourt -S ttf-google-fonts-git

Announcement
--------------------
If you're getting an error building but it's not dependency related, check and make sure the installed version of fontconfig is at least 2.12.6+5+g665584a-1. You can find this out by running: `pacman -Q fontconfig`

There was an upstream regression in 2.12.6-1 that is resolved in 2.12.6+5+g665584a-1. This package now reflects that fix.

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:

1. The last line of the package() function should have: find ${pkgdir} -iname "lohit" -delete
2. Remove 'lohit-fonts' from the conflicts and provides arrays.

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 :)

Since cwTeX-* fonts have already been removed in upstream (https://github.com/google/fonts/commit/98670058578c5d93f157347bccce91b23f6b245e) Do we still need the "mv's" for these fonts at PKGBUILD?