[Durian-svn] [7806] Adding the files for the closing titles (a bunch more to come, but tis a start)
dolf
institute at blender.org
Fri Aug 20 10:33:14 CEST 2010
Revision: 7806
https://blenderinstitute.dyndns.org/durian-svn/?do=log&project=durian&path=/&rev=7806
Author: dolf
Date: 2010-08-20 10:33:13 +0200 (Fri, 20 Aug 2010)
Log Message:
-----------
Adding the files for the closing titles (a bunch more to come, but tis a start)
Added Paths:
-----------
pro/scenes/10.1_closingtitles/
pro/scenes/10.1_closingtitles/10.1a_comp.blend
pro/scenes/10.1_closingtitles/10.1b_comp.blend
pro/scenes/10.1_closingtitles/10.1l_comp.blend
pro/scenes/10.1_closingtitles/fonts/
pro/scenes/10.1_closingtitles/fonts/FONTLOG.txt
pro/scenes/10.1_closingtitles/fonts/OFL-FAQ.txt
pro/scenes/10.1_closingtitles/fonts/OFL.txt
pro/scenes/10.1_closingtitles/fonts/OFLGoudyStM-Italic.otf
pro/scenes/10.1_closingtitles/fonts/OFLGoudyStM.otf
pro/scenes/10.1_closingtitles/fonts/OFLGoudyStMTT-Italic.ttf
pro/scenes/10.1_closingtitles/fonts/OFLGoudyStMTT.ttf
pro/scenes/10.1_closingtitles/textures/
pro/scenes/10.1_closingtitles/textures/dark_wood.png
pro/scenes/10.1_closingtitles/textures/dark_wood.xcf
pro/scenes/10.1_closingtitles/textures/dark_wood_normal.png
pro/scenes/10.1_closingtitles/textures/dark_wood_normal.xcf
pro/scenes/10.1_closingtitles/textures/tiles/
pro/scenes/10.1_closingtitles/textures/tiles/01-ziggurat-temple_005.png
pro/scenes/10.1_closingtitles/textures/tiles/02-backalley_006.png
pro/scenes/10.1_closingtitles/textures/tiles/03-dragon-baby-screen_005.png
pro/scenes/10.1_closingtitles/textures/tiles/04-sintel-bedroom_005.png
pro/scenes/10.1_closingtitles/textures/tiles/05-chicken-attack_004.png
pro/scenes/10.1_closingtitles/textures/tiles/06-illu-sintel-loose-baby-final.png
pro/scenes/10.1_closingtitles/textures/tiles/07-bamboo-scene_005.png
pro/scenes/10.1_closingtitles/textures/tiles/08-screen-snow_06.png
pro/scenes/10.1_closingtitles/textures/tiles/09-shaman-scene_010.png
pro/scenes/10.1_closingtitles/textures/tiles/10-dragon-cave-mid_007.png
Added: pro/scenes/10.1_closingtitles/10.1a_comp.blend
===================================================================
(Binary files differ)
Property changes on: pro/scenes/10.1_closingtitles/10.1a_comp.blend
___________________________________________________________________
Added: svn:mime-type
+ application/octet-stream
Added: pro/scenes/10.1_closingtitles/10.1b_comp.blend
===================================================================
(Binary files differ)
Property changes on: pro/scenes/10.1_closingtitles/10.1b_comp.blend
___________________________________________________________________
Added: svn:mime-type
+ application/octet-stream
Added: pro/scenes/10.1_closingtitles/10.1l_comp.blend
===================================================================
(Binary files differ)
Property changes on: pro/scenes/10.1_closingtitles/10.1l_comp.blend
___________________________________________________________________
Added: svn:mime-type
+ application/octet-stream
Added: pro/scenes/10.1_closingtitles/fonts/FONTLOG.txt
===================================================================
--- pro/scenes/10.1_closingtitles/fonts/FONTLOG.txt (rev 0)
+++ pro/scenes/10.1_closingtitles/fonts/FONTLOG.txt 2010-08-20 08:33:13 UTC (rev 7806)
@@ -0,0 +1,26 @@
+1. FONTLOG for OFL Sorts Mill Goudy
+
+ This file provides detailed information on the OFL Sorts Mill Goudy
+ Font Software. This information should be distributed along with
+ the OFL Sorts Mill Goudy fonts and any derivative works.
+
+2. Basic Font Information
+
+ A digital version of Goudy Oldstyle and Italic.
+
+3. ChangeLog
+
+ 2 Jul 2010 (Barry Schwartz) OFL Sorts Mill Goudy version 3.1.
+
+ 9 Jan 2010 (Barry Schwartz) OFL Sorts Mill Goudy version 3.0.
+
+3.4 Acknowledgements
+
+ If you make modifications be sure to add your name (N), email (E),
+ web-address (W) and description (D). This list is sorted by last
+ name in alphabetical order.
+
+ N: Barry Schwartz
+ E: See http://crudfactory.com
+ W: http://crudfactory.com
+ D: The original developer of these exceptional digital fonts
Added: pro/scenes/10.1_closingtitles/fonts/OFL-FAQ.txt
===================================================================
--- pro/scenes/10.1_closingtitles/fonts/OFL-FAQ.txt (rev 0)
+++ pro/scenes/10.1_closingtitles/fonts/OFL-FAQ.txt 2010-08-20 08:33:13 UTC (rev 7806)
@@ -0,0 +1,235 @@
+OFL FAQ - Frequently Asked Questions about the SIL Open Font License (OFL)
+Version 1.1-update1 - 31 March 2009
+(See http://scripts.sil.org/OFL for updates)
+
+
+1 ABOUT USING AND DISTRIBUTING FONTS LICENSED UNDER THE OFL
+
+1.1 Can I use the fonts in any publication, even embedded in the file?
+Yes. You may use them like most other fonts, but unlike some fonts you may include an embedded subset of the fonts in your document. Such use does not require you to include this license or other files (listed in OFL condition 2), nor does it require any type of acknowledgement within the publication. Some mention of the font name within the publication information (such as in a colophon) is usually appreciated. If you wish to include the complete font as a separate file, you should distribute the full font package, including all existing acknowledgements, and comply with the OFL conditions. Of course, referencing or embedding an OFL font in any document does not change the license of the document itself. The requirement for fonts to remain under the OFL does not apply to any document created using the fonts and their derivatives. Similarly, creating any kind of graphic using a font under OFL does not make the resulting artwork subject to the OFL.
+
+1.2 Can I make web pages using these fonts?
+Yes! Go ahead! Using CSS (Cascading Style Sheets) is recommended. Direct usage of fonts retrieved from a remote server - also referred to as font linking - using cross-platform open standards like @font-face is encouraged. This is considered to be use and distribution for which the OFL explicitly grants permission. The font file itself is not embedded in the webpage but referenced through a web address (i.e. a URI regardless of file format or access protocol) which will cause the browser to retrieve and use the corresponding font to render the webpage. This usage scenario is different from font embedding within a document (i.e. a PDF) where the font or some of its elements become part of the document. Note that embedding in a document is also permitted by the license as indicated in 1.1. (See 1.10 for details related to URL-based access restrictions methods or DRM mechanisms).
+
+1.3 Can I make the fonts available to others from my web site?
+Yes, as long as you meet the conditions of the license (do not sell by itself, include the necessary files, include the necessary copyright and license information, rename Modified Versions, do not abuse the Author(s)' name(s) and do not sublicense). In the case where you are hosting fonts to be served on the web, make sure the file contains the needed copyright notice(s) and licensing information in its metadata. Please double-check the accuracy of every field to prevent contradictory information. If you are making the font available for use via the @font-face open standard, putting this information in the standard font metadata fields is sufficient. Other font formats, including EOT and proposed superior alternatives, already provide fields for this information.
+
+1.4 Can the fonts be included with Free/Libre and Open Source Software collections such as GNU/Linux and BSD distributions?
+Yes! Fonts licensed under the OFL can be freely aggregated with software under FLOSS (Free/Libre and Open Source Software) licenses. Since fonts are much more useful aggregated to than merged with existing software, possible incompatibility with existing software licenses is not a problem. You can also repackage the fonts and the accompanying components in a .rpm or .deb package and include them in distro CD/DVDs and online repositories.
+
+1.5 I want to distribute the fonts with my program. Does this mean my program also has to be free/libre and open source software?
+No. Only the portions based on the Font Software are required to be released under the OFL. The intent of the license is to allow aggregation or bundling with software under restricted licensing as well.
+
+1.6 Can I include the fonts on a CD of freeware or commercial fonts?
+Yes, as long some other font or software is also on the disk, so the OFL font is not sold by itself.
+
+1.7 Can I sell a software package that includes these fonts?
+Yes, you can do this with both the Original Version and a Modified Version. Examples of bundling made possible by the OFL would include: word processors, design and publishing applications, training and educational software, edutainment software, etc.
+
+1.8 Why won't the OFL let me sell the fonts alone?
+The intent is to keep people from making money by simply redistributing the fonts. The only people who ought to profit directly from the fonts should be the original authors, and those authors have kindly given up potential direct income to distribute their fonts under the OFL. Please honor and respect their contribution!
+
+1.9 I've come across a font released under the OFL. How can I easily get more information about the Original Version? How can I know where it stands compared to the Original Version or other Modified Versions?
+Consult the copyright statement(s) in the license for ways to contact the original authors. Consult the FONTLOG for information on how the font differs from the Original Version, and get in touch with the various contributors via the information in the acknowledgment section. Please consider using the Original Versions of the fonts whenever possible.
+
+1.10 What do you mean in condition 4? Can you provide examples of abusive promotion / endorsement / advertisement vs. normal acknowledgement?
+The intent is that the goodwill and reputation of the author(s) should not be used in a way that makes it sound like the original author(s) endorse or approve of a specific Modified Version or software bundle. For example, it would not be right to advertise a word processor by naming the author(s) in a listing of software features, or to promote a Modified Version on a web site by saying "designed by ...". However, it would be appropriate to acknowledge the author(s) if your software package has a list of people who deserve thanks. We realize that this can seem to be a gray area, but the standard used to judge an acknowledgement is that if the acknowledgement benefits the author(s) it is allowed, but if it primarily benefits other parties, or could reflect poorly on the author(s), then it is not.
+
+1.11 Can Font Software released under the OFL be subject to URL-based access restrictions methods or DRM mechanisms?
+Yes, but these issues are out-of-scope for the OFL. The license itself neither encourages their use nor prohibits them since such mechanisms are not implemented in the components of the Font Software but through external software. Such restrictions are put in place for many different purposes corresponding to various usage scenarios. One common example is to limit potentially dangerous cross-site scripting attacks. However, in the spirit of libre/open fonts and unrestricted writing systems, we strongly encourage open sharing and reuse of OFL fonts, and the establishment of an environment where such restrictions are unnecessary. Note that whether you wish to use such mechanisms or you prefer not to, you must still abide by the rules set forth by the OFL when using fonts released by their authors under this license. Derivative fonts must be licensed under the OFL, even if they are part of a service for which you charge fees and/or for which access to source code is restricted!
. You may not sell the fonts on their own - they must be part of a larger software package or bundle. For example, even if the OFL font is distributed in a software package or via an online service using a DRM mechanism, the user would still have the right to extract that font, use, study, modify and redistribute it under the OFL.
+
@@ Diff output truncated at 10240 characters. @@
More information about the Durian-svn
mailing list