Talk:Core fonts for the Web
|WikiProject Typography||(Rated C-class, Low-importance)|
|WikiProject Microsoft||(Rated C-class, Low-importance)|
I changed the archive.org link to point to: 20020124085641 as it contains a newer version of Courier New for the Macintosh. 220.127.116.11 21:55, 26 December 2005 (UTC)
I like to bash Microsoft as much as the rest of us, but for the sake of neutrality, might we want to either remove or expand the one-sentence paragraph about Håkon Wium Lie? ~RCanine
Removed.--18.104.22.168 23:40, 27 May 2006 (UTC)
Questioning Presumed Requirement to Keep Archives in Their Original Format
I read the EULA and I do not believe that the following statement is true. Where in the EULA is this required? I do not see how the archive containing the EULA and the font file can be considered to be part of the "SOFTWARE PRODUCT". I think everybody is been jumping through a lot of hoops based on a misunderstanding.
allows redistribution as long as the packages are kept in their original format
UPDATE: I now see that this is specified in the FAQ. However, I still don't see how you can get this out of reading the EULA. How can the FAQ be binding?
You may only redistribute the fonts in their original form (.exe or .sit.hqx) and with their original file name from your Web site or intranet site.
It could be interesting to add a small description on how avalable those fonts are on others plateform (even if it's not the aim of this MS initiative). For example, Impact is not in the standard MAC OS X package, Trebuchet MS is in the standard MAC OS X package but can be disable, Georgia is in the standard MAC OS X package and can't be disabled (). Georgia is serif. What is the most cross-platforme sans-serif one? Could be be very valuable to indicate that kind of thing. Lacrymocéphale —Preceding unsigned comment added by 22.214.171.124 (talk) 10:39, 26 May 2008 (UTC)
Fonts legal on sourceforge?
The Core fonts project page on Sourceforge claims they are being distributed under GPL. (Go here and click "details.") I can't for the life of me see how the original EULA would allow this. Can anyone provide a citation of someone who explains the chain of legal logic here? Otherwise, I still consider it to be unsubstantiated, despite the reference to the original license. As far as I can see, the citation doesn't prove what it's supposed to prove. Hopefully, I'm missing something. Jdavidb (talk • contribs) 01:43, 5 January 2009 (UTC)
- The simple fact is that they are NOT being distributed under GPL, but as long as Sourceforge is hosting the original unaltered Microsoft archive distribution files, then Sourceforge's distribution of such files is presumably legal. However, the article currently says nothing about Sourceforge licensing terms, and doesn't cite any reference about Sourceforge licensing terms, so I'm not too sure what you're asking about... AnonMoos (talk) 11:12, 5 January 2009 (UTC)
I already worked this through with Jdavidb. Here is the breakdown:
|Content||License||Redistribution permission||Hosting on SourceForge|
|Font packages (in .exe)||Microsoft EULA||Allowed in original format||???|
|RPM installer||GPL||of course||of course|
Now the only possible problem is SourceForge not allowing hosting of non-OSS binaries. There might be problem here, since to my understanding SourceForge doesn't even allow developers to host non-OSS libraries. I told Jdavidb to contact SourceForge for clarification. They probably can classify the font under media, which doesn't have to be OSS.
It won't really matter much, even if SourceForge remove the font packages, someone else can host it easily since redistribution was allowed in the original license. --Voidvector (talk) 14:38, 5 January 2009 (UTC)
- However, that's all about whether hosting the files violates Sourceforge's internal policies, not whether such hosting is legal... AnonMoos (talk) 17:38, 5 January 2009 (UTC)
Hello fellow Wikipedians,
I have just modified one external link on Core fonts for the Web. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
- Added archive https://web.archive.org/web/20150424000832/http://web.nickshanks.com/typography/font-descriptions to http://web.nickshanks.com/typography/font-descriptions
When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.
You may set the
|checked=, on this template, to true or failed to let other editors know you reviewed the change. If you find any errors, please use the tools below to fix them or call an editor by setting
|needhelp= to your help request.
- If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
- If you found an error with any archives or the URLs themselves, you can fix them with this tool.
If you are unable to use these tools, you may set
|needhelp=<your help request> on this template to request help from an experienced user. Please include details about your problem, to help other editors.