After working on a patch to fix #104512, I noticed that the freefonts ebuild does not use the font.eclass, something that it would need to work with the fix prescribed by the patch I am writing for #104512. Outside of this patch, it is probably useful to have the freefonts ebuild migrate to this new one, because it means that the font.eclass will handle the font processing, something that was redundant with the existing ebuild code.
Created attachment 68791 [details, diff] Patch to freefonts.ebuild and changelog
Mamoru KOMACHI aka usata already fixed this bug in CVS. See freefonts-0.10-r3.ebuild. It was added at 29 Oct 2005, so may be it's good idea to ask for its stabilization? Or just close this bug?
Irrelevant bug.