https://bugs.documentfoundation.org/show_bug.cgi?id=159950
--- Comment #13 from Eyal Rozenberg <eyalr...@gmx.com> --- (In reply to Cor Nouws from comment #10) > Can 'relevant online sources' be made specific enough to be workable and > maintainable? Extending my reply from the design meeting: I believe the most common cases of missing fonts would be those fonts people use with other office suites and apps, especially on Windows and to some extent on web platforms or Mac. Consequently, major candidates for font distribution sources would be public font repositories of Microsoft, Google and Apple (the likely suspects). Google: https://fonts.google.com/ https://github.com/google/fonts Apple: https://developer.apple.com/fonts/ Microsoft: this is trickier... but see at least https://learn.microsoft.com/en-us/typography/font-list/ https://corefonts.sourceforge.net We should look into (at least) the following points regarding each of these: 1. Can one (stably) automate the location of font by name in the repository? 2. Can one (stably) automate the download of a located font from the repository? 3. Can one (stably) automate the download of license text from the repository? 4. Is it legally allowed for a program to do these three things, and for the user to be considered the actor, under appropriate conditions? (Appropriate conditions could be presentation of appropriate confirmation dialogs, e.g. "Would you like to download font family Foo from repository BigCorp Font Galleria?", "Do you accept the following license for font family Foo?") PS: It doesn't have to be just these big commercial three. other possibilities include: The Font Library (various licenses listed per font): https://fontlibrary.org Font Squirrel (only freeware fonts): https://www.fontsquirrel.com OpenFoundry: https://open-foundry.com/info etc. but of course - smaller sites are less likely to have the more popular missing fonts; so perhaps these would be better-suited for optional additions to the list? via an extension? Hard to say. -- You are receiving this mail because: You are the assignee for the bug.
