Really Simple CAPTCHA - Version 1.6

Version Description

  • Bundled font changed to Gentium Basic 1.1.
  • Some workarounds for infrequently reported problems on Windows server.
  • Do temp file cleanup every time before generating CAPTCHA image.
Download this release

Release Info

Developer takayukister
Plugin Icon 128x128 Really Simple CAPTCHA
Version 1.6
Comparing to
See all releases

Code changes from version 1.5 to 1.6

Files changed (22) hide show
  1. gentium/FONTLOG.txt +114 -138
  2. gentium/GENTIUM-FAQ.txt +61 -19
  3. gentium/GenAI102.TTF +0 -0
  4. gentium/GenAR102.TTF +0 -0
  5. gentium/GenBasB.ttf +0 -0
  6. gentium/GenBasBI.ttf +0 -0
  7. gentium/GenBasI.ttf +0 -0
  8. gentium/GenBasR.ttf +0 -0
  9. gentium/GenBkBasB.ttf +0 -0
  10. gentium/GenBkBasBI.ttf +0 -0
  11. gentium/GenBkBasI.ttf +0 -0
  12. gentium/GenBkBasR.ttf +0 -0
  13. gentium/GenI102.TTF +0 -0
  14. gentium/GenR102.TTF +0 -0
  15. gentium/GentiumDesignSource.vfb +0 -0
  16. gentium/GentiumIDesignSource.vfb +0 -0
  17. gentium/OFL-FAQ.txt +66 -32
  18. gentium/OFL.txt +35 -40
  19. gentium/QUOTES.txt +0 -76
  20. gentium/README.txt +0 -2
  21. readme.txt +8 -2
  22. really-simple-captcha.php +71 -31
gentium/FONTLOG.txt CHANGED
@@ -1,58 +1,83 @@
1
  FONTLOG
2
- Gentium font family
3
- ========================
4
 
5
 
6
- This file provides detailed information on the Gentium family of fonts. This
7
- information should be distributed along with the Gentium fonts and any
8
- derivative works.
9
 
10
 
11
  Basic Font Information
12
  ----------------------
13
 
14
- Gentium ("belonging to the nations" in Latin) is a Unicode typeface family
15
- designed to enable the many diverse ethnic groups around the world who use
16
- the Latin script to produce readable, high-quality publications. The design
17
- is intended to be highly readable, reasonably compact, and visually
18
- attractive. Gentium has won a "Certificate of Excellence in Typeface Design"
19
- in two major international typeface design competitions: bukva:raz! (2001),
20
- TDC2003 (2003).
21
-
22
- Gentium provides glyphs for a wide range of Latin and Greek characters. The
23
- additional 'extended' Latin letters are designed to naturally harmonize with
24
- the traditional 26 ones. Diacritics are treated with careful thought and
25
- attention to their use. Gentium also supports both ancient and modern Greek,
26
- including a number of alternate forms. It currently supports the following
27
- ranges of Unicode 3.0 (completely unless noted):
28
-
29
- Range Description
30
- U+0020-U+007F Basic Latin
31
- U+00A0-U+00FF Latin-1 Supplement
32
- U+0100-U+017F Latin Extended-A
33
- U+0180-U+021F Latin Extended-B
34
- U+0222-U+0233 Latin Extended-B (continued)
35
- U+0250-U+02AD IPA Extensions
36
- U+02B0-U+02FF Spacing Modifier Letters
37
- U+0300-U+036F Combining Diacritical Marks
38
- U+0370-U+03D5 Greek (not including archaic or Coptic)
39
- U+1E00-U+1EFF Latin Extended Additional
40
- U+1F00-U+1FFF Greek Extended
41
- U+2000-U+203A General Punctuation (partial)
42
- U+2070-U+209F Superscripts and Subscripts
43
- U+20A0-U+20CF Currency Symbols (partial)
44
- U+2100-U+214F Letterlike Symbols (only a couple)
45
-
46
- Gentium Regular also includes some Cyrillic glyphs, but they are only early
47
- drafts. A future version will include a completely revised set, including
48
- italic, and will expand the support for Latin, Greek and Cyrillic to Unicode
49
- 4.1.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
50
 
51
 
52
  ChangeLog
53
  ---------
54
  (This should list both major and minor changes, most recent first.)
55
 
 
 
 
 
 
 
 
 
56
  28 Nov 2005 (Victor Gaultney) Gentium version 1.02
57
  - Changed licensing to the SIL Open Font License
58
  - Included FontLab source files
@@ -62,116 +87,67 @@ ChangeLog
62
  19 Sep 2003 (Victor Gaultney) Gentium version 1.01
63
  - Maintenance release focused on changing internal font
64
  - Information to reflect the changeover to an SIL project
65
- - There is only one bug fix - the Greek mu PS name was changed to try and fix
66
- a display/printing problem. There is still no manual hinting
67
 
68
  16 Sep 2002 (Victor Gaultney) Gentium version 1.00
69
  - First public release
70
- - No manual hinting is included in this version. Some has been done - with
71
- good results - but is not yet complete enough.
72
-
73
-
74
- Information for Contributors
75
- ----------------------------
76
-
77
- The main point of version 1.02 is to enable modification via the OFL and to
78
- establish a means for people to contribute to the project. For information
79
- on what you're allowed to change or modify, consult the OFL and OFL-FAQ. The
80
- OFL-FAQ also gives a very general rationale regarding why you would want to
81
- contribute to the project.
82
-
83
- Anyone can make their own modified version of Gentium (using a different
84
- name), but SIL International will continue to maintain and develop the
85
- canonical version of the Gentium fonts. As the package maintainer, we warmly
86
- welcome contributions. Here are some things to keep in mind:
87
-
88
- Format: We are open to contributions in various formats, but if you want to
89
- maximise the chances of us including your work, please make it available to
90
- us (via email or a URL) as either a FontLab database (preferred) or a
91
- PostScript Type 1 (or OT-CFF) font.
92
-
93
- Source files: For the first time, we're including FontLab databases used in
94
- developing the fonts. The current fonts, however, were not solely built from
95
- this FontLab database, so a simple "Generate Font" will not give you an
96
- identical result. These databases are provided not as canonical source but
97
- as an aid to anyone who might find it useful to have access to the
98
- PostScript-style curves before they were turned into TrueType ones. BTW -
99
- although only two databases are provided, they contain all the Alt glyphs.
100
- In the future we may be making our 'source' available in three formats:
101
- OpenType (TrueType), OT-CFF, and FontLab.
102
-
103
- Copyright attribution: If you submit something for inclusion in the main
104
- Gentium fonts, we will ask you to affirm that it is your original work, and
105
- ask you to assign the copyright of your work to SIL International. This is
106
- to ensure that future releases can be made under improved versions of the
107
- OFL without needing to track you down for further permission. This follows
108
- the same principle used by the FSF. Keep in mind that we are a
109
- not-for-profit organization committed to free/libre and open source
110
- software, and that any contributions incorporated in the fonts will always
111
- be available under the OFL or a similar license.
112
-
113
- Quality: Because we want to be able to guarantee a high level of quality for
114
- the primary Gentium fonts, we will review submissions carefully. Please
115
- don't be discouraged if we do not include a submission for this reason, or
116
- ask you to make specific revisions.
117
-
118
- What types of contributions are welcomed now (some more than others):
119
- - Old style figures
120
- - Small caps (although we would want such done for *all* caps, not just A-Z)
121
- - Specifications for smart Greek code (write us about this)
122
- - Coptic
123
- - Historic/Archaic Cyrillic
124
- - Glyphs used for ancient Greek text study (but not alphabetic ones, like
125
- the digamma)
126
- - Mathematical glyphs
127
- - OpenType code and glyphs for on-the-fly fraction creation
128
- - Additional scripts (Armenian, etc.?), and any needed OT/Graphite/AAT code
129
- - Other things that we may have once told you we didn't have time to do :-)
130
-
131
- What is not needed at this point:
132
- - Revisions to the basic letters or their spacing
133
- - Cyrillic revisions or additions. These are already in process
134
- - Other weights (Bold, Bold italic). We already have some work done on this
135
- - Alphabetic Ancient Greek glyphs (digamma, etc.). These are done and are
136
- waiting for the next release
137
- - Unicode 4.1 additions for Latin. We have these already in the pipeline
138
- - General Latin/Cyrillic OpenType/Graphite/AAT code - we already have this
139
- (see our Doulos SIL project)
140
- - Kerning - there is some in place
141
- - Hinting - although if you could offer to do some hinting, let us know :-)
142
-
143
- So why didn't we include some of this in this release? The only change for
144
- 1.02 is the new licensing model. We thought that it was important to get a
145
- revised font out before we had completed the next big revision. We also
146
- didn't want to hold up release until we had everything neat and tidy :-)
147
-
148
- When submissions will be included: We hope to have a revised version of the
149
- Regular and Italic fonts (including full Cyrillic) completed by mid-2006. To
150
- do this we will need submissions early in the year. Other weights will
151
- follow after that.
152
-
153
- WARNINGS: The details of the source files and build procedures will be
154
- changing radically before the next release, so do not spend too much time
155
- working on systems that depend on the current FontLab database information.
156
- Also - the Cyrillic glyphs in the regular font are very early prototypes and
157
- will be changing completely. So don't bother to modify them!
158
 
159
 
160
  Acknowledgements
161
  ----------------
162
- (Here is where contributors can be acknowledged. If you make modifications
163
- be sure to add your name (N), email (E), web-address (W) and description
164
- (D). This list is sorted by last name in alphabetical order.)
165
 
166
  N: Victor Gaultney
167
  E: victor_gaultney@sil.org
168
  W: http://www.sil.org/~gaultney/
169
- D: Original Designer of Latin, Greek and Cyrillic glyphs
 
 
 
 
 
170
 
171
- The Gentium project is maintained by SIL International.
 
 
 
172
 
173
- For more information please visit the Gentium page on SIL International's
174
- Computers and Writing systems website:
 
175
  http://scripts.sil.org/gentium
176
 
177
  Or send an email to <gentium AT sil DOT org>
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
  FONTLOG
2
+ Gentium Basic and Gentium Book Basic v1.1
3
+ ==========================================================
4
 
5
 
6
+ This file provides detailed information on the Gentium Basic and Gentium Book Basic font families. This information should be distributed along with the Gentium Basic and Gentium Book Basic fonts and any derivative works.
 
 
7
 
8
 
9
  Basic Font Information
10
  ----------------------
11
 
12
+ Gentium ("belonging to the nations" in Latin) is a Unicode typeface family designed to enable the many diverse ethnic groups around the world who use the Latin script to produce readable, high-quality publications. The design is intended to be highly readable, reasonably compact, and visually attractive. Gentium has won a "Certificate of Excellence in Typeface Design" in two major international typeface design competitions: bukva:raz! (2001), TDC2003 (2003).
13
+
14
+ The Gentium Basic and Gentium Book Basic font famililes are based on the original design, but with additional weights. The "Book" family is slightly heavier. Both families come with a complete regular, bold, italic and bold italic set of fonts.
15
+
16
+ The supported character set, however, is much smaller than for the main Gentium fonts. These "Basic" fonts support only the Basic Latin and Latin-1 Supplement Unicode ranges, plus a selection of the more commonly used extended Latin characters, with miscellaneous diacritical marks, symbols and punctuation. For a complete list of supported characters see the list at the end of this document.
17
+
18
+ In particular, these fonts do not support:
19
+
20
+ - Full extended Latin IPA
21
+ - Complete support for Central European languages
22
+ - Greek
23
+ - Cyrillic
24
+
25
+ A much more complete character set will be supported in a future version of the complete Gentium fonts. These "Basic" fonts are intended as a way to provide additional weights for basic font users without waiting until the complete Gentium character set is finished. So please don't request additional glyphs or characters to be supported in the Basic fonts - such support will become available in the main Gentium family in the future.
26
+
27
+ There are also some other limitations of the Basic fonts:
28
+
29
+ - They are not completely metric-compatible with the full Gentium family
30
+ (some glyphs may have different widths, although changes have been minimal)
31
+ - There is no kerning
32
+ - There are no "Alt" versions, or ones with low-profile diacritics
33
+ - The default stacking style for some diacritic combinations does not match Vietnamese-style conventions (although this is available through a OpenType/Graphite feature)
34
+ - No support for TypeTuner
35
+
36
+ There are, however, some wonderful new features that are still missing from the main Gentium family:
37
+
38
+ - Bold!
39
+ - Bold Italic!
40
+ - The slightly-heavier Book family!
41
+ - OpenType and Graphite smart code for diacritic placement!
42
+ - A few useful OpenType and Graphite features
43
+ - Support for a few more recent additions to Unicode and the SIL PUA (http://scripts.sil.org/UnicodePUA)
44
+ - Character assignments are updated to conform to Unicode 5.1
45
+
46
+ In particular, the Basic fonts support a subset of the smart font features that the Doulos SIL font supports. Those features are:
47
+
48
+ - Capital Eng alternates
49
+ - Literacy alternates
50
+ - Capital Y-hook alternate
51
+ - Capital N-left-hook alternate
52
+ - Modifier apostrophe alternate
53
+ - Modifier colon alternate
54
+ - Open o alternate
55
+ - Vietnamese-style diacritics
56
+
57
+ More detail on the features can be seen in the Doulos SIL Technical Documentation (http://scripts.sil.org/DoulosSIL_Technical).
58
+
59
+
60
+ Known Problems
61
+ --------------
62
+
63
+ We know of the following problems. Please report any other problems you encounter.
64
+
65
+ - logicalnot (U+00AC) appears distorted in Bold Italic and Book Italic.
66
+ - Opening the fonts with FontLab 5.0.x, then closing them, crashes FontLab. We are working to get this bug fixed in the next version of FontLab. A workaround is to open the font, save as a .vfb file, close (which still causes a crash). Then restart FontLab and open the .vfb file.
67
 
68
 
69
  ChangeLog
70
  ---------
71
  (This should list both major and minor changes, most recent first.)
72
 
73
+ 4 Apr 2008 (Victor Gaultney) Gentium Basic/Gentium Book Basic version 1.1
74
+ - Final release
75
+
76
+ 12 Nov 2007 (Victor Gaultney) Gentium Basic/Gentium Book Basic version 1.1b1
77
+ - trimmed character set down to Basic
78
+ - added additional weights
79
+ - no FontLab source files
80
+
81
  28 Nov 2005 (Victor Gaultney) Gentium version 1.02
82
  - Changed licensing to the SIL Open Font License
83
  - Included FontLab source files
87
  19 Sep 2003 (Victor Gaultney) Gentium version 1.01
88
  - Maintenance release focused on changing internal font
89
  - Information to reflect the changeover to an SIL project
90
+ - There is only one bug fix - the Greek mu PS name was changed to try and fix a display/printing problem. There is still no manual hinting
 
91
 
92
  16 Sep 2002 (Victor Gaultney) Gentium version 1.00
93
  - First public release
94
+ - No manual hinting is included in this version. Some has been done - with good results - but is not yet complete enough.
95
+
96
+
97
+ Information for Developers/Contributors
98
+ ---------------------------------------
99
+
100
+ The source release contains FontLab source files for the eight fonts, but those files do not include the OpenType and Graphite code, as those are inserted after the fonts are generated from FontLab. The files are included as a source for the PostScript-style cubic curves. You are welcome, however, to open the font files themselves to gain access to the smart font code, although most editors will not let you edit that code directly. We will provide a richer set of sources for the full Gentium fonts at a later time.
101
+
102
+ SIL will remain as maintainers of this font project, but we do not intend any further major releases. Our primary efforts will be going into the full Gentium package. Any contributions should be directed toward that project.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
103
 
104
 
105
  Acknowledgements
106
  ----------------
107
+ (Here is where contributors can be acknowledged. 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.)
 
 
108
 
109
  N: Victor Gaultney
110
  E: victor_gaultney@sil.org
111
  W: http://www.sil.org/~gaultney/
112
+ D: Original Designer
113
+
114
+ N: Annie Olsen
115
+ E: nrsi@sil.org
116
+ W: http://scripts.sil.org/
117
+ D: Contributed some extended Latin glyphs
118
 
119
+ N: SIL font engineers
120
+ E: nrsi@sil.org
121
+ W: http://scripts.sil.org/
122
+ D: OpenType code and build support
123
 
124
+ The Gentium project, and the Gentium Basic and Gentium Book Basic fonts, are maintained by SIL International.
125
+
126
+ For more information please visit the Gentium page on SIL International's Computers and Writing systems website:
127
  http://scripts.sil.org/gentium
128
 
129
  Or send an email to <gentium AT sil DOT org>
130
+
131
+
132
+ Character Range Coverage
133
+ ------------------------
134
+
135
+ C0 Controls and Basic Latin (U+0020..U+007E)
136
+ C1 Controls and Latin-1 Supplement (U+00A0..U+00FF)
137
+ Latin Extended-A (U+0100..U+0103, U+0106..U+010E, U+011A..U+0121, U+0124..U+0125, U+0128..U+012D, U+0130..U+0133, U+0139..U+013A, U+0141..U+0144, U+0147..U+0148, U+014A..U+0155, U+0158..U+015D, U+0160..U+0161, U+0164, U+0168..U+0171, U+00174..U+017E)
138
+ Latin Extended-B (U+0181, U+0186, U+0189..U+018A, U+018E, U+0190, U+0192, U+0197..U+019A, U+019D, U+019F..U+01A1, U+01A9..U+01AA, U+01AF..U+01B0, U+01B3..U+01B4, U+01B7, U+01CD..U+01E3, U+01E6..U+01E9, U+01EE..U+01EF, U+01F4..U+01F5, U+01F8..U+01FF, U+021E..U+021F, U+0226..U+0233, U+0237, U+023D, U+0241..U+0242, U+0244..U+0245, U+024A..U+024B)
139
+ IPA Extensions (U+0251, U+0253..U+0254, U+0256..U+0257, U+0259, U+025B, U+0263, U+0268..U+0269, U+026B, U+0272, U+0275, U+0283, U+0289..U+028A, U+028C, U+0292, U+0294, U+02A0)
140
+ Spacing Modifier Letters (U+02BC, U+02C0, U+02C6..U+02C7, U+02C9..U+02CB, U+02CD, U+02D7..U+02DD)
141
+ Combining Diacritical Marks (U+0300..U+0304,U+0306..U+030C, U+031B, U+0323, U+0327..U+0328, U+0331, U+033F, U+035F)
142
+ Greek and Coptic (U+03A0, U+03A9, U+03C0)
143
+ Latin Extended Additional (U+1E02..U+1E0F, U+1E14..U+1E17, U+1E1C..U+1E27, U+1E2E..U+1E3B, U+1E3E..U+1E49, U+1E4C..U+1E6F, U+1E78..U+1E99, U+1EA0..U+1EF9)
144
+ General Punctuation (U+2011, U+2013..U+2014, U+2018..U+201A, U+201C..U+201E, U+2020..U+2022, U+2026, U+2030, U+2039..U+203A, U+2044)
145
+ Currency Symbols (U+20AC)
146
+ Letterlike Symbols (U+2122..U+2123, U+2126)
147
+ Mathematical Operators (U+2202, U+2205..U+2206, U+220F, U+2211..U+2212, U+2219..U+221A, U+221E, U+222B, U+2248, U+2260, U+2264..U+2265)
148
+ Geometric Shapes (U+25CA, U+25CC)
149
+ Latin Extended-C (U+2C60..U+2C62)
150
+ Modifier Tone Letters (U+A700..U+A71A)
151
+ Latin Extended-D (U+A789..U+A78C)
152
+ Alphabetic Presentation Forms (U+FB01..U+FB02)
153
+ SIL PUA (U+F130..U+F131, U+F195, U+F197, U+F1C8, U+F1E9..U+F1EA, U+F20E..U+F20F, U+F211..U+F212, U+F218..U+F219, U+F21D..U+F21F, U+F242, U+F26A)
gentium/GENTIUM-FAQ.txt CHANGED
@@ -1,6 +1,6 @@
1
  GENTIUM-FAQ
2
- Gentium Release 1.02
3
- 28 November 2005
4
  ========================
5
 
6
  Here are some answers to frequently asked questions about the Gentium fonts:
@@ -19,11 +19,11 @@ What is GentiumAlt?
19
  It is a version of the font with redesigned diacritics (flatter
20
  ones) to make it more suitable for use with stacking diacritics, and
21
  for languages such as Vietnamese. The Greek glyphs also use the
22
- Porsonic (single-curve) design for the circumflex. Since Gentium
23
- does not currently include any 'smart' rendering routines, there is
24
- no easy way to access these alternate diacritic shapes from within
25
- the regular Gentium font. The encoding of the fonts are the same, so
26
- the same text can be viewed with either one. There is also no
27
  problem with having both font families installed at the same time.
28
 
29
 
@@ -119,13 +119,16 @@ I can't find the 'o with right hook' in the font. Where is it?
119
  cases, we're not able to anticipate every possible combination.
120
  Future versions of Gentium will include 'smart font' support for
121
  technologies such as OpenType and SIL's Graphite. This will make
122
- diacritic positioning much better.
 
 
123
 
124
  Some diacritics are not aligning well with base glyphs, and if I type more
125
  than one diacritic, they run into each other. Why is that?
126
 
127
  Gentium currently has no 'smart font' code for automatic diacritic
128
- positioning, but will in the near future.
 
129
 
130
  How do I type the Greek letters?
131
 
@@ -141,6 +144,49 @@ I'm having problems making PDFs -- why won't my document distill?
141
  reduce the size of your files.
142
 
143
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
144
  Future
145
  ======
146
 
@@ -156,7 +202,7 @@ designer?
156
  Do you plan to include other typographic enhancements (small caps, old style
157
  figures, etc.)?
158
 
159
- Those would be nice, wouldn't they. From a design point of view,
160
  it would be great to have these refinements, and we haven't ruled
161
  them out. But there are other needs that are much higher priority
162
  (Bold, Cyrillic, etc.). If you think you could contribute some of
@@ -165,21 +211,18 @@ figures, etc.)?
165
 
166
  What about bold?
167
 
168
- We hope to make a prototype of a Bold weight (and a few others,
169
- including italic) available soon, but it will only cover basic Latin
170
- glyphs at first. Once we are confident that the basic design is solid,
171
- we will begin to design the bold versions of the other hundreds of
172
- glyphs. Be patient, though, as Gentium has lots of glyphs!
173
 
174
  Sans-serif?
175
 
176
  There is a definite need for a sans-serif font that shares some of
177
- Gentium�s strengths -- high readability, economy of space, etc. It
178
  would also be great if that font also harmonized well with Gentium.
179
  We don't currently have any plans for a companion face, although one
180
  of our other projects - Andika - may be useful. Andika is a sans-serif
181
  font designed specifically for use in literacy programs around the
182
- world. A prototype should be available in a few months.
183
 
184
  Will you be extending Gentium to cover other scripts, and Hebrew in
185
  particular?
@@ -195,8 +238,7 @@ When will Cyrillic be completed?
195
  I need a couple of ancient Greek glyphs, such as the digamma. When will
196
  those be ready?
197
 
198
- These have already been designed and will be in the next release
199
- (mid-2006).
200
 
201
  Will there be a Type 1 version? What about OpenType?
202
 
1
  GENTIUM-FAQ
2
+ Gentium Basic Release 1.1
3
+ 4 April 2008
4
  ========================
5
 
6
  Here are some answers to frequently asked questions about the Gentium fonts:
19
  It is a version of the font with redesigned diacritics (flatter
20
  ones) to make it more suitable for use with stacking diacritics, and
21
  for languages such as Vietnamese. The Greek glyphs also use the
22
+ Porsonic (single-curve) design for the circumflex. Since the main
23
+ Gentium fonts do not currently include any 'smart' rendering routines,
24
+ there is no easy way to access these alternate diacritic shapes from
25
+ within the regular Gentium font. The encoding of the fonts are the same,
26
+ so the same text can be viewed with either one. There is also no
27
  problem with having both font families installed at the same time.
28
 
29
 
119
  cases, we're not able to anticipate every possible combination.
120
  Future versions of Gentium will include 'smart font' support for
121
  technologies such as OpenType and SIL's Graphite. This will make
122
+ diacritic positioning much better. The Gentium Basic fonts do,
123
+ however, include limited support for both OpenType and Graphite,
124
+ and demonstrate the type of support that will eventually be provided.
125
 
126
  Some diacritics are not aligning well with base glyphs, and if I type more
127
  than one diacritic, they run into each other. Why is that?
128
 
129
  Gentium currently has no 'smart font' code for automatic diacritic
130
+ positioning, but the Gentium Basic fonts do, and similar support will
131
+ appear in the main fonts in the near future.
132
 
133
  How do I type the Greek letters?
134
 
144
  reduce the size of your files.
145
 
146
 
147
+ Basic
148
+ =====
149
+
150
+ How are the Basic fonts (Gentium Basic, Gentium Book Basic) different
151
+ from Gentium?
152
+
153
+ These font families are based on the original Gentium design, but with
154
+ additional weights. Both families come with a complete regular, bold,
155
+ italic and bold italic set of fonts. The supported character set,
156
+ however, is much smaller than for the main Gentium fonts. These
157
+ 'Basic' fonts support only the Basic Latin and Latin-1 Supplement
158
+ Unicode ranges, plus a selection of the more commonly used extended
159
+ Latin characters, with miscellaneous diacritical marks, symbols and
160
+ punctuation. In particular, these fonts do not support full extended
161
+ Latin IPA, complete support for Central European languages, Greek and
162
+ Cyrillic.
163
+
164
+ What is the Book weight?
165
+
166
+ It is a complete second font family that is slightly heavier overall,
167
+ and more useful for some purposes. The main Gentium family will
168
+ eventually have a complete matching Book weight, along with matching
169
+ italics.
170
+
171
+ Why is the line spacing greater for the Basic fonts?
172
+
173
+ In some environments, stacked diacritics in Gentium could display as
174
+ 'chopped-off'. Gentium Basic has slightly wider default line spacing
175
+ in order to avoid this problem. Most applications do, however, let you
176
+ set the line spacing explicitly, so you can have the lines spaced
177
+ precisely as you wish.
178
+
179
+ Will you be accepting requests for additions to the Basic character set?
180
+
181
+ No. We are now focusing our development efforts on the main Gentium
182
+ fonts, which already provide richer character set support.
183
+
184
+ Is there an Alt version of the Basic fonts?
185
+
186
+ No, although you may notice that capitals and some tall lowercase
187
+ letters do use 'low-profile' versions.
188
+
189
+
190
  Future
191
  ======
192
 
202
  Do you plan to include other typographic enhancements (small caps, old style
203
  figures, etc.)?
204
 
205
+ Those would be nice, wouldn't they? From a design point of view,
206
  it would be great to have these refinements, and we haven't ruled
207
  them out. But there are other needs that are much higher priority
208
  (Bold, Cyrillic, etc.). If you think you could contribute some of
211
 
212
  What about bold?
213
 
214
+ The Gentium Basic fonts include Bold and Bold Italic versions. The
215
+ main Gentium fonts will also include them in the future.
 
 
 
216
 
217
  Sans-serif?
218
 
219
  There is a definite need for a sans-serif font that shares some of
220
+ Gentium�s strengths -- high readability, economy of space, etc. It
221
  would also be great if that font also harmonized well with Gentium.
222
  We don't currently have any plans for a companion face, although one
223
  of our other projects - Andika - may be useful. Andika is a sans-serif
224
  font designed specifically for use in literacy programs around the
225
+ world, and is available from our web site.
226
 
227
  Will you be extending Gentium to cover other scripts, and Hebrew in
228
  particular?
238
  I need a couple of ancient Greek glyphs, such as the digamma. When will
239
  those be ready?
240
 
241
+ These have already been designed and will be in the next main release.
 
242
 
243
  Will there be a Type 1 version? What about OpenType?
244
 
gentium/GenAI102.TTF DELETED
Binary file
gentium/GenAR102.TTF DELETED
Binary file
gentium/GenBasB.ttf ADDED
Binary file
gentium/GenBasBI.ttf ADDED
Binary file
gentium/GenBasI.ttf ADDED
Binary file
gentium/GenBasR.ttf ADDED
Binary file
gentium/GenBkBasB.ttf ADDED
Binary file
gentium/GenBkBasBI.ttf ADDED
Binary file
gentium/GenBkBasI.ttf ADDED
Binary file
gentium/GenBkBasR.ttf ADDED
Binary file
gentium/GenI102.TTF DELETED
Binary file
gentium/GenR102.TTF DELETED
Binary file
gentium/GentiumDesignSource.vfb DELETED
Binary file
gentium/GentiumIDesignSource.vfb DELETED
Binary file
gentium/OFL-FAQ.txt CHANGED
@@ -1,45 +1,45 @@
1
  OFL FAQ - Frequently Asked Questions about the SIL Open Font License (OFL)
2
- Version 1.0 - 22 November 2005
3
  (See http://scripts.sil.org/OFL for updates)
4
 
5
 
6
  1 ABOUT USING AND DISTRIBUTING FONTS LICENSED UNDER THE OFL
7
 
8
  1.1 Can I use the fonts in any publication, even embedded in the file?
9
- 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 resulting document is not a derivative anymore than a compiled program is a derivative of a compiler. Similarly, creating a graphic using an OFL font does not make the resulting artwork subject to the OFL.
10
 
11
  1.2 Can I make web pages using these fonts?
12
  Yes! Go ahead! Using CSS (Cascading Style Sheets) is recommended.
13
 
14
  1.3 Can I make the fonts available to others from my web site?
15
- Yes, as long as you meet the conditions for use (include the necessary files, don't abuse the Author(s)' names, rename Modified Versions, do not sublicense and do not sell by itself).
16
 
17
- 1.4 Can the fonts be included with free and open source software distributions (such as GNU/Linux and BSD distributions)?
18
- Yes! The OFL is compatible with most FLOSS (Free/Libre and Open Source Software) licenses. 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.
19
 
20
  1.5 I want to distribute the fonts with my program. Does this mean my program also has to be free and open source software?
21
- 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 also with software under restricted licensing.
22
 
23
  1.6 Can I include the fonts on a CD of freeware or commercial fonts?
24
  Yes, as long some other font or software is also on the disk, so the OFL font is not sold by itself.
25
 
26
  1.7 Can I sell a software package that includes these fonts?
27
- Yes, you can do this with both the Standard 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.
28
 
29
  1.8 Why won't the OFL let me sell the fonts alone?
30
- 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 income to distribute their fonts under the OFL. Please honor and respect their contribution!
31
 
32
- 1.9 I've come across a font released under the OFL. How can I easily get more information about the Standard Version? How can I know where it stands compared to the Standard Version or other Modified Versions?
33
- Consult the copyright statement in the license for how to contact the original authors. Consult the FONTLOG for information on if and how the font differs from the Standard Version, and get in touch with the various contributors via the information in the acknowledgment section. Please consider using the Standard Versions of the fonts whenever possible.
34
 
35
  1.10 What do you mean in condition 4? Can you provide examples of abusive promotion / endorsement / advertisement vs. normal acknowledgement?
36
- The intent is that the goodwill and reputation of the authors should not be used in a way that makes it sound like the original authors 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 authors 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 authors 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 authors it is allowed, but if it primarily benefits other parties, or could reflect poorly on the authors, then it is not.
37
 
38
 
39
  2 ABOUT MODIFYING OFL LICENSED FONTS
40
 
41
  2.1 Can I change the fonts? Are there any limitations to what things I can and cannot change?
42
- You are allowed to change anything, as long as such changes do not violate the terms of the license. In other words, you could not remove the copyright statement from the font, but you could add additional information into it that covers your contribution.
43
 
44
  2.2 I have a font that needs a few extra glyphs - can I take them from an OFL licensed font and copy them into mine?
45
  Yes, but if you distribute that font to others it must be under the OFL, and include the information mentioned in condition 2 of the license.
@@ -53,19 +53,31 @@ Yes. This is a good way to fund the further development of the fonts. Keep in mi
53
  2.5 I need to make substantial revisions to the font to make it work with my program. It will be a lot of work, and a big investment, and I want to be sure that it can only be distributed with my program. Can I restrict its use?
54
  No. If you redistribute a Modified Version of the font it must be under the OFL. You may not restrict it in any way. This is intended to ensure that all released improvements to the fonts become available to everyone. But you will likely get an edge over competitors by being the first to distribute a bundle with the enhancements. Again, please remember how you have benefitted from the contributions of others.
55
 
56
- 2.6 Do I have to make any derivative fonts (including source code, build scripts, documentation, etc.) publicly available?
57
  No, but please do share your improvements with others. You may find that you receive more than what you gave in return.
58
 
59
  2.7 Why can't I use the Reserved Font Name(s) in my derivative font names? I'd like people to know where the design came from.
60
- The best way to acknowledge the source of the design is to thank the original authors and any other contributors in the files that are distributed with your revised font (although no acknowledgement is required). The FONTLOG is a natural place to do this. Reserved Font Name(s) ensure that the only fonts that have the original names are the unmodified Standard Versions. This eliminates potential confusion and name conflicts. When choosing a name be creative and try to avoid names that sound like the original. Keep in mind that the copyright holder can allow a specific trusted partner to use Reserved Font Name(s) through a separate written agreement.
61
 
62
- 2.8 What do you mean by "references stored in the Font Software"? Do I have to delete every reference to the Reserved Font Name(s) from inside every file I modify?
63
- No, not every reference. It would be fine, for example, to keep a text reference to the original fonts in your modified source code, as long as no one could be confused that your modified source is the original. But you cannot use the Reserved Font Names in any way to identify the font to the user (unless the Copyright Holder allows it through a separate agreement, see section 2.7). Users who install derivatives ("Modified Versions") on their systems should not see any of the original names ("Reserved Font Names") in their font menus, font properties dialogs, PostScript streams, documents that refer to a particular font name, etc. Again, this is to ensure that users are not confused and do not mistake a font for another and so expect features only another derivative or the Standard Version can actually offer. Ultimately, creating name conflicts will cause many problems for the users as well as for the designer of both the Standard and derivative versions, so please think ahead and find a good name for your own derivative. Font substitution systems like fontconfig, OpenOffice.org or Scribus will also get very confused if the name of the font they are configured to substitute to actually refers to another physical font on the user's hard drive. It will help everyone if Standard and derivative fonts can easily be distinguished from one another, and from other derivatives.
64
 
65
- 2.9 What is this FONTLOG thing exactly?
 
 
 
 
 
 
 
 
 
 
 
 
66
  It has three purposes: 1) to provide basic information on the font to users and other developers, 2) to document changes that have been made to the font or accompanying files, either by the original authors or others, and 3) to provide a place to acknowledge the authors and other contributors. Please use it! See below for details on how changes should be noted.
67
 
68
- 2.10 Am I required to update the FONTLOG?
69
  No, but users, designers and other developers might get very frustrated at you if you don't! People need to know how derivative fonts differ from the originals, and how to take advantage of the changes, or build on them.
70
 
71
 
@@ -77,7 +89,7 @@ The FONTLOG can take a variety of formats, but should include these four section
77
  This file provides detailed information on the <FontFamilyName> font software. This information should be distributed along with the <FontFamilyName> fonts and any derivative works.
78
 
79
  3.2 Basic Font Information
80
- (Here is where you would describe the purpose and brief specifications for the font project, and where users can find more detailed documentation. It can also include references to how changes can be contributed back to the Standard Version. You may also wish to include a short guide to the design, or a reference to such a document.)
81
 
82
  3.3 ChangeLog
83
  (This should list both major and minor changes, most recent first. Here are some examples:)
@@ -95,7 +107,9 @@ This file provides detailed information on the <FontFamilyName> font software. T
95
  - Initial release of font "<FontFamilyName>"
96
 
97
  3.4 Acknowledgements
98
- (Here is where contributors can be acknowledged. 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.)
 
 
99
 
100
  N: Jane Doe
101
  E: jane@university.edu
@@ -128,29 +142,49 @@ D: Designer - original Roman glyphs
128
  4 ABOUT MAKING CONTRIBUTIONS
129
 
130
  4.1 Why should I contribute my changes back to the original authors?
131
- It would benefit many people if you contributed back to what you've received. Providing your contributions and improvements to the fonts and other components (data files, source code, build scripts, documentation, etc.) could be a tremendous help and would encourage others to contribute as well and 'give back', which means you will have an opportunity to benefit from other people's contributions as well. Sometimes maintaining your own separate version takes more effort than merging back with the original. Be aware that any contributions, however, must be either your own original creation or work that you own, and you may be asked to affirm that when you contribute.
132
 
133
- 4.2 I've made some very nice improvements to the font, will you consider adopting them and putting them into future Standard Versions?
134
- Most authors would be very happy to receive such contributions. Keep in mind that it is unlikely that they would want to incorporate major changes that would require additional work on their end. Any contributions would likely need to be made for all the fonts in a family and match the overall design and style. Authors are encouraged to include a guide to the design with the fonts. It would also help to have contributions submitted as patches or clearly marked changes (the use of a centralized or distributed source revision control system like subversion or arch is a good idea). Examples of useful contributions are bug fixes, additional glyphs, stylistic alternates (and the smart font code to access them).
135
 
136
  4.3 How can I financially support the development of OFL fonts?
137
- It is likely that most authors of OFL fonts would accept financial contributions - contact them for instructions on how to do this. Such contributions would support future development. You can also pay for others to enhance the fonts and contribute the results back to the original authors for inclusion in the Standard Versions.
138
 
139
 
140
  5 ABOUT THE LICENSE
141
 
142
- 5.1 I see that this is version 1.0 of the license. Will there be later changes?
143
- We hope that version 1.0 will meet most needs, but are open to future improvements. Any revisions would be for future font releases, and previously existing licenses would remain in effect. No retroactive changes are possible, although the Copyright Holder can re-release the font under a revised OFL. All versions will be available on our web site: http://scripts.sil.org/OFL.
144
 
145
  5.2 Can I use the SIL Open Font License for my own fonts?
146
- Yes! We heartily encourage anyone to use the OFL to distribute their own original fonts. It is a carefully constructed license that allows great freedom with some protection for the original authors and clear rules for other contributors. Some additional information is included at the end of this FAQ.
147
 
148
- 5.3 Does this license restrict the rights of the Copyright Holder?
149
- No. The Copyright Holder still retains all rights to their creation; they are only releasing a portion of it for use in a specific way. For example, the Copyright Holder may choose to release a 'basic' version of their font under the OFL, but sell a restricted 'enhanced' version. Only the Copyright Holder can do this.
150
 
151
  5.4 Is the OFL a contract or a license?
152
  The OFL is a license and not a contract and so does not require you to sign it to have legal validity. By using, modifying and redistributing components under the OFL you indicate that you accept the license.
153
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
154
 
155
  6 ABOUT SIL INTERNATIONAL
156
 
@@ -158,7 +192,7 @@ The OFL is a license and not a contract and so does not require you to sign it t
158
  SIL International is a worldwide faith-based education and development organization (NGO) that studies, documents, and assists in developing the world's lesser-known languages through literacy, linguistics, translation, and other academic disciplines. SIL makes its services available to all without regard to religious belief, political ideology, gender, race, or ethnic background. SIL's members and volunteers share a Christian commitment.
159
 
160
  6.2 What does this have to do with font licensing?
161
- The ability to read, write, type and publish in one's own language is one of the most critical needs for millions of people around the world. This requires fonts that are widely available and support lesser-known languages. SIL develops - and encourages others to develop - a complete stack of writing systems implementation components available under open licenses. This open stack includes input methods, smart fonts, smart rendering libraries and smart applications. There has been a need for a common open license that is specifically applicable to fonts and related software (a crucial component of this stack) so SIL developed the SIL Open Font License.
162
 
163
  6.3 How can I contact SIL?
164
  Our main web site is: http://www.sil.org/
@@ -170,8 +204,8 @@ Information about this license (including contact email information) is at: http
170
 
171
  If you want to release your fonts under the OFL, you only need to do the following:
172
 
173
- 7.1 Put your copyright and reserved names information in the beginning of the main OFL file.
174
- 7.2 Put your copyright and the OFL references in your various font files (such as in TrueType name, description and license fields) and in your other components (build scripts, glyph databases, documentation, keyboard, samples, etc).
175
  7.3 Write an initial FONTLOG for your font and include it in the release package.
176
  7.4 Include the OFL in your release package.
177
  7.5 We also highly recommend you include the relevant practical documentation on the license by putting the OFL-FAQ in your package.
1
  OFL FAQ - Frequently Asked Questions about the SIL Open Font License (OFL)
2
+ Version 1.1 - 1 February 2007
3
  (See http://scripts.sil.org/OFL for updates)
4
 
5
 
6
  1 ABOUT USING AND DISTRIBUTING FONTS LICENSED UNDER THE OFL
7
 
8
  1.1 Can I use the fonts in any publication, even embedded in the file?
9
+ 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.
10
 
11
  1.2 Can I make web pages using these fonts?
12
  Yes! Go ahead! Using CSS (Cascading Style Sheets) is recommended.
13
 
14
  1.3 Can I make the fonts available to others from my web site?
15
+ Yes, as long as you meet the conditions of the license (do not sell by itself, include the necessary files, rename Modified Versions, do not abuse the Author(s)' name(s) and do not sublicense).
16
 
17
+ 1.4 Can the fonts be included with Free/Libre and Open Source Software collections such as GNU/Linux and BSD distributions?
18
+ Yes! Fonts licensed under the OFL can be freely agreggated 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.
19
 
20
  1.5 I want to distribute the fonts with my program. Does this mean my program also has to be free and open source software?
21
+ 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.
22
 
23
  1.6 Can I include the fonts on a CD of freeware or commercial fonts?
24
  Yes, as long some other font or software is also on the disk, so the OFL font is not sold by itself.
25
 
26
  1.7 Can I sell a software package that includes these fonts?
27
+ 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.
28
 
29
  1.8 Why won't the OFL let me sell the fonts alone?
30
+ 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!
31
 
32
+ 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?
33
+ Consult the copyright statement 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.
34
 
35
  1.10 What do you mean in condition 4? Can you provide examples of abusive promotion / endorsement / advertisement vs. normal acknowledgement?
36
+ 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.
37
 
38
 
39
  2 ABOUT MODIFYING OFL LICENSED FONTS
40
 
41
  2.1 Can I change the fonts? Are there any limitations to what things I can and cannot change?
42
+ You are allowed to change anything, as long as such changes do not violate the terms of the license. In other words, you are not allowed to remove the copyright statement(s) from the font, but you could add additional information into it that covers your contribution.
43
 
44
  2.2 I have a font that needs a few extra glyphs - can I take them from an OFL licensed font and copy them into mine?
45
  Yes, but if you distribute that font to others it must be under the OFL, and include the information mentioned in condition 2 of the license.
53
  2.5 I need to make substantial revisions to the font to make it work with my program. It will be a lot of work, and a big investment, and I want to be sure that it can only be distributed with my program. Can I restrict its use?
54
  No. If you redistribute a Modified Version of the font it must be under the OFL. You may not restrict it in any way. This is intended to ensure that all released improvements to the fonts become available to everyone. But you will likely get an edge over competitors by being the first to distribute a bundle with the enhancements. Again, please remember how you have benefitted from the contributions of others.
55
 
56
+ 2.6 Do I have to make any derivative fonts (including source files, build scripts, documentation, etc.) publicly available?
57
  No, but please do share your improvements with others. You may find that you receive more than what you gave in return.
58
 
59
  2.7 Why can't I use the Reserved Font Name(s) in my derivative font names? I'd like people to know where the design came from.
60
+ The best way to acknowledge the source of the design is to thank the original authors and any other contributors in the files that are distributed with your revised font (although no acknowledgement is required). The FONTLOG is a natural place to do this. Reserved Font Name(s) ensure that the only fonts that have the original names are the unmodified Original Versions. This allows designers to maintain artistic integrity while allowing collaboration to happen. It eliminates potential confusion and name conflicts. When choosing a name be creative and avoid names that reuse almost all the same letters in the same order or sound like the original. Keep in mind that the Copyright Holder(s) can allow a specific trusted partner to use Reserved Font Name(s) through a separate written agreement.
61
 
62
+ 2.8 What do you mean by "primary name as presented to the user"? Are you are referring to the font menu name?
63
+ Yes, the requirement to change the visible name used to differentiate the font from others applies to the font menu name and other mechanisms to specify a font in a document. It would be fine, for example, to keep a text reference to the original fonts in the description field, in your modified source file or in documentation provided alongside your derivative as long as no one could be confused that your modified source is the original. But you cannot use the Reserved Font Names in any way to identify the font to the user (unless the Copyright Holder(s) allow(s) it through a separate agreement, see section 2.7). Users who install derivatives ("Modified Versions") on their systems should not see any of the original names ("Reserved Font Names") in their font menus, for example. Again, this is to ensure that users are not confused and do not mistake a font for another and so expect features only another derivative or the Original Version can actually offer. Ultimately, creating name conflicts will cause many problems for the users as well as for the designer of both the Original and Modified versions, so please think ahead and find a good name for your own derivative. Font substitution systems like fontconfig, or application-level font fallback configuration within OpenOffice.org or Scribus, will also get very confused if the name of the font they are configured to substitute to actually refers to another physical font on the user's hard drive. It will help everyone if Original Versions and Modified Versions can easily be distinguished from one another and from other derivatives. The substitution mechanism itself is outside the scope of the license. Users can always manually change a font reference in a document or set up some kind of substitution at a higher level but at the lower level the fonts themselves have to respect the Reserved Font Name(s) requirement to prevent ambiguity. If a substitution is currently active the user should be aware of it.
64
 
65
+ 2.9 Am I not allowed to use any part of the Reserved Font Names?
66
+ You may not use the words of the font names, but you would be allowed to use parts of words, as long as you do not use any word from the Reserved Font Names entirely. We do not recommend using parts of words because of potential confusion, but it is allowed. For example, if "Foobar" was a Reserved Font Name, you would be allowed to use "Foo" or "bar", although we would not recommend it. Such an unfortunate choice would confuse the users of your fonts as well as make it harder for other designers to contribute.
67
+
68
+ 2.10 So what should I, as an author, identify as Reserved Font Names?
69
+ Original authors are encouraged to name their fonts using clear, distinct names, and only declare the unique parts of the name as Reserved Font Names. For example, the author of a font called "Foobar Sans" would declare "Foobar" as a Reserved Font Name, but not "Sans", as that is a common typographical term, and may be a useful word to use in a derivative font name. Reserved Font Names should also be single words. A font called "Flowing River" should have Reserved Font Names "Flowing" and "River", not "Flowing River".
70
+
71
+ 2.11 Do I, as an author, have to identify and Reserved Font Names?
72
+ No, but we strongly encourage you to do so. This is to avoid confusion between your work and Modified versions. You may, however, give certain trusted parties the right to use any of your Reserved Font Names through separate written agreements. For example, even if "Foobar" is a RFN, you could write up an agreement to give company "XYZ" the right to distribute a modified version with a name that includes "Foobar". This allows for freedom without confusion.
73
+
74
+ 2.12 Are any names (such as the main font name) reserved by default?
75
+ No. That is a change to the license as of version 1.1. If you want any names to be Reserved Font Names, they must be specified after the copyright statement.
76
+
77
+ 2.13 What is this FONTLOG thing exactly?
78
  It has three purposes: 1) to provide basic information on the font to users and other developers, 2) to document changes that have been made to the font or accompanying files, either by the original authors or others, and 3) to provide a place to acknowledge the authors and other contributors. Please use it! See below for details on how changes should be noted.
79
 
80
+ 2.14 Am I required to update the FONTLOG?
81
  No, but users, designers and other developers might get very frustrated at you if you don't! People need to know how derivative fonts differ from the originals, and how to take advantage of the changes, or build on them.
82
 
83
 
89
  This file provides detailed information on the <FontFamilyName> font software. This information should be distributed along with the <FontFamilyName> fonts and any derivative works.
90
 
91
  3.2 Basic Font Information
92
+ (Here is where you would describe the purpose and brief specifications for the font project, and where users can find more detailed documentation. It can also include references to how changes can be contributed back to the Original Version. You may also wish to include a short guide to the design, or a reference to such a document.)
93
 
94
  3.3 ChangeLog
95
  (This should list both major and minor changes, most recent first. Here are some examples:)
107
  - Initial release of font "<FontFamilyName>"
108
 
109
  3.4 Acknowledgements
110
+ (Here is where contributors can be acknowledged.
111
+
112
+ 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.)
113
 
114
  N: Jane Doe
115
  E: jane@university.edu
142
  4 ABOUT MAKING CONTRIBUTIONS
143
 
144
  4.1 Why should I contribute my changes back to the original authors?
145
+ It would benefit many people if you contributed back to what you've received. Providing your contributions and improvements to the fonts and other components (data files, source code, build scripts, documentation, etc.) could be a tremendous help and would encourage others to contribute as well and 'give back', which means you will have an opportunity to benefit from other people's contributions as well. Sometimes maintaining your own separate version takes more effort than merging back with the original. Be aware that any contributions, however, must be either your own original creation or work that you own, and you may be asked to affirm that clearly when you contribute.
146
 
147
+ 4.2 I've made some very nice improvements to the font, will you consider adopting them and putting them into future Original Versions?
148
+ Most authors would be very happy to receive such contributions. Keep in mind that it is unlikely that they would want to incorporate major changes that would require additional work on their end. Any contributions would likely need to be made for all the fonts in a family and match the overall design and style. Authors are encouraged to include a guide to the design with the fonts. It would also help to have contributions submitted as patches or clearly marked changes (the use of smart source revision control systems like subversion, svk or bzr is a good idea). Examples of useful contributions are bug fixes, additional glyphs, stylistic alternates (and the smart font code to access them) or improved hinting.
149
 
150
  4.3 How can I financially support the development of OFL fonts?
151
+ It is likely that most authors of OFL fonts would accept financial contributions - contact them for instructions on how to do this. Such contributions would support future development. You can also pay for others to enhance the fonts and contribute the results back to the original authors for inclusion in the Original Version.
152
 
153
 
154
  5 ABOUT THE LICENSE
155
 
156
+ 5.1 I see that this is version 1.1 of the license. Will there be later changes?
157
+ Version 1.1 is the first minor revision of the OFL. We are confident that version 1.1 will meet most needs, but are open to future improvements. Any revisions would be for future font releases, and previously existing licenses would remain in effect. No retroactive changes are possible, although the Copyright Holder(s) can re-release the font under a revised OFL. All versions will be available on our web site: http://scripts.sil.org/OFL.
158
 
159
  5.2 Can I use the SIL Open Font License for my own fonts?
160
+ Yes! We heartily encourage anyone to use the OFL to distribute their own original fonts. It is a carefully constructed license that allows great freedom along with enough artistic integrity protection for the work of the authors as well as clear rules for other contributors and those who redistribute the fonts. Some additional information about using the OFL is included at the end of this FAQ.
161
 
162
+ 5.3 Does this license restrict the rights of the Copyright Holder(s)?
163
+ No. The Copyright Holder(s) still retains all the rights to their creation; they are only releasing a portion of it for use in a specific way. For example, the Copyright Holder(s) may choose to release a 'basic' version of their font under the OFL, but sell a restricted 'enhanced' version. Only the Copyright Holder(s) can do this.
164
 
165
  5.4 Is the OFL a contract or a license?
166
  The OFL is a license and not a contract and so does not require you to sign it to have legal validity. By using, modifying and redistributing components under the OFL you indicate that you accept the license.
167
 
168
+ 5.5 How about translating the license and the FAQ into other languages?
169
+ SIL certainly recognises the need for people who are not familiar with English to be able to understand the OFL and this FAQ better in their own language. Making the license very clear and readable is a key goal of the OFL.
170
+
171
+ If you are an experienced translator, you are very welcome to help translating the OFL and its FAQ so that designers and users in your language community can understand the license better. But only the original English version of the license has legal value and has been approved by the community. Translations do not count as legal substitutes and should only serve as a way to explain the original license. SIL - as the author and steward of the license for the community at large - does not approve any translation of the OFL as legally valid because even small translations ambiguities could be abused and create problems.
172
+
173
+ We give permission to publish unofficial translations into other languages provided that they comply with the following guidelines:
174
+
175
+ - put the following disclaimer in both English and the target language stating clearly that the translation is unofficial:
176
+
177
+ "This is an unofficial translation of the SIL Open Font License into $language. It was not published by SIL International, and does not legally state the distribution terms for fonts that use the OFL. A release under the OFL is only valid when using the original English text.
178
+
179
+ However, we recognize that this unofficial translation will help users and designers not familiar with English to understand the SIL OFL better and make it easier to use and release font families under this collaborative font design model. We encourage designers who consider releasing their creation under the OFL to read the FAQ in their own language if it is available.
180
+
181
+ Please go to http://scripts.sil.org/OFL for the official version of the license and the accompanying FAQ."
182
+ "
183
+
184
+ - keep your unofficial translation current and update it at our request if needed, for example if there is any ambiguity which could lead to confusion.
185
+
186
+ If you start such a unofficial translation effort of the OFL and its accompanying FAQ please let us know, thank you.
187
+
188
 
189
  6 ABOUT SIL INTERNATIONAL
190
 
192
  SIL International is a worldwide faith-based education and development organization (NGO) that studies, documents, and assists in developing the world's lesser-known languages through literacy, linguistics, translation, and other academic disciplines. SIL makes its services available to all without regard to religious belief, political ideology, gender, race, or ethnic background. SIL's members and volunteers share a Christian commitment.
193
 
194
  6.2 What does this have to do with font licensing?
195
+ The ability to read, write, type and publish in one's own language is one of the most critical needs for millions of people around the world. This requires fonts that are widely available and support lesser-known languages. SIL develops - and encourages others to develop - a complete stack of writing systems implementation components available under open licenses. This open stack includes input methods, smart fonts, smart rendering libraries and smart applications. There has been a need for a common open license that is specifically applicable to fonts and related software (a crucial component of this stack) so SIL developed the SIL Open Font License with the help of the FLOSS community.
196
 
197
  6.3 How can I contact SIL?
198
  Our main web site is: http://www.sil.org/
204
 
205
  If you want to release your fonts under the OFL, you only need to do the following:
206
 
207
+ 7.1 Put your copyright and reserved font names information in the beginning of the main OFL file.
208
+ 7.2 Put your copyright and the OFL references in your various font files (such as in the copyright, license and description fields) and in your other components (build scripts, glyph databases, documentation, rendering samples, etc).
209
  7.3 Write an initial FONTLOG for your font and include it in the release package.
210
  7.4 Include the OFL in your release package.
211
  7.5 We also highly recommend you include the relevant practical documentation on the license by putting the OFL-FAQ in your package.
gentium/OFL.txt CHANGED
@@ -1,51 +1,46 @@
1
- This Font Software is Copyright (c) 2003-2005, SIL International (http://scripts.sil.org/).
2
- All Rights Reserved.
3
 
4
- "Gentium" is a Reserved Font Name for this Font Software.
5
- "SIL" is a Reserved Font Name for this Font Software.
6
-
7
- This Font Software is licensed under the SIL Open Font License, Version 1.0.
8
- No modification of the license is permitted, only verbatim copy is allowed.
9
  This license is copied below, and is also available with a FAQ at:
10
  http://scripts.sil.org/OFL
11
 
12
 
13
  -----------------------------------------------------------
14
- SIL OPEN FONT LICENSE Version 1.0 - 22 November 2005
15
  -----------------------------------------------------------
16
 
17
  PREAMBLE
18
  The goals of the Open Font License (OFL) are to stimulate worldwide
19
- development of cooperative font projects, to support the font creation
20
- efforts of academic and linguistic communities, and to provide an open
21
- framework in which fonts may be shared and improved in partnership with
22
- others.
23
 
24
  The OFL allows the licensed fonts to be used, studied, modified and
25
  redistributed freely as long as they are not sold by themselves. The
26
  fonts, including any derivative works, can be bundled, embedded,
27
- redistributed and sold with any software provided that the font
28
  names of derivative works are changed. The fonts and derivatives,
29
- however, cannot be released under any other type of license.
 
 
30
 
31
  DEFINITIONS
32
- "Font Software" refers to any and all of the following:
33
- - font files
34
- - data files
35
- - source code
36
- - build scripts
37
- - documentation
38
 
39
- "Reserved Font Name" refers to the Font Software name as seen by
40
- users and any other names as specified after the copyright statement.
41
 
42
- "Standard Version" refers to the collection of Font Software
43
- components as distributed by the Copyright Holder.
44
 
45
- "Modified Version" refers to any derivative font software made by
46
- adding to, deleting, or substituting -- in part or in whole --
47
- any of the components of the Standard Version, by changing formats
48
- or by porting the Font Software to a new environment.
49
 
50
  "Author" refers to any designer, engineer, programmer, technical
51
  writer or other person who contributed to the Font Software.
@@ -57,31 +52,31 @@ redistribute, and sell modified and unmodified copies of the Font
57
  Software, subject to the following conditions:
58
 
59
  1) Neither the Font Software nor any of its individual components,
60
- in Standard or Modified Versions, may be sold by itself.
61
 
62
- 2) Standard or Modified Versions of the Font Software may be bundled,
63
- redistributed and sold with any software, provided that each copy
64
  contains the above copyright notice and this license. These can be
65
  included either as stand-alone text files, human-readable headers or
66
  in the appropriate machine-readable metadata fields within text or
67
  binary files as long as those fields can be easily viewed by the user.
68
 
69
  3) No Modified Version of the Font Software may use the Reserved Font
70
- Name(s), in part or in whole, unless explicit written permission is
71
- granted by the Copyright Holder. This restriction applies to all
72
- references stored in the Font Software, such as the font menu name and
73
- other font description fields, which are used to differentiate the
74
- font from others.
75
 
76
- 4) The name(s) of the Copyright Holder or the Author(s) of the Font
77
  Software shall not be used to promote, endorse or advertise any
78
  Modified Version, except to acknowledge the contribution(s) of the
79
- Copyright Holder and the Author(s) or with their explicit written
80
  permission.
81
 
82
  5) The Font Software, modified or unmodified, in part or in whole,
83
- must be distributed using this license, and may not be distributed
84
- under any other license.
 
 
85
 
86
  TERMINATION
87
  This license becomes null and void if any of the above conditions are
1
+ Copyright (c) 2003-2008 SIL International (http://www.sil.org/),
2
+ with Reserved Font Names "Gentium" and "SIL".
3
 
4
+ This Font Software is licensed under the SIL Open Font License, Version 1.1.
 
 
 
 
5
  This license is copied below, and is also available with a FAQ at:
6
  http://scripts.sil.org/OFL
7
 
8
 
9
  -----------------------------------------------------------
10
+ SIL OPEN FONT LICENSE Version 1.1 - 1 February 2007
11
  -----------------------------------------------------------
12
 
13
  PREAMBLE
14
  The goals of the Open Font License (OFL) are to stimulate worldwide
15
+ development of collaborative font projects, to support the font creation
16
+ efforts of academic and linguistic communities, and to provide a free and
17
+ open framework in which fonts may be shared and improved in partnership
18
+ with others.
19
 
20
  The OFL allows the licensed fonts to be used, studied, modified and
21
  redistributed freely as long as they are not sold by themselves. The
22
  fonts, including any derivative works, can be bundled, embedded,
23
+ redistributed and/or sold with any software provided that the font
24
  names of derivative works are changed. The fonts and derivatives,
25
+ however, cannot be released under any other type of license. The
26
+ requirement for fonts to remain under this license does not apply
27
+ to any document created using the fonts or their derivatives.
28
 
29
  DEFINITIONS
30
+ "Font Software" refers to the set of files released by the Copyright
31
+ Holder(s) under this license and clearly marked as such. This may
32
+ include source files, build scripts and documentation.
 
 
 
33
 
34
+ "Reserved Font Name" refers to any names specified as such after the
35
+ copyright statement(s).
36
 
37
+ "Original Version" refers to the collection of Font Software components as
38
+ distributed by the Copyright Holder(s).
39
 
40
+ "Modified Version" refers to any derivative made by adding to, deleting,
41
+ or substituting -- in part or in whole -- any of the components of the
42
+ Original Version, by changing formats or by porting the Font Software to a
43
+ new environment.
44
 
45
  "Author" refers to any designer, engineer, programmer, technical
46
  writer or other person who contributed to the Font Software.
52
  Software, subject to the following conditions:
53
 
54
  1) Neither the Font Software nor any of its individual components,
55
+ in Original or Modified Versions, may be sold by itself.
56
 
57
+ 2) Original or Modified Versions of the Font Software may be bundled,
58
+ redistributed and/or sold with any software, provided that each copy
59
  contains the above copyright notice and this license. These can be
60
  included either as stand-alone text files, human-readable headers or
61
  in the appropriate machine-readable metadata fields within text or
62
  binary files as long as those fields can be easily viewed by the user.
63
 
64
  3) No Modified Version of the Font Software may use the Reserved Font
65
+ Name(s) unless explicit written permission is granted by the corresponding
66
+ Copyright Holder. This restriction only applies to the primary font name as
67
+ presented to the users.
 
 
68
 
69
+ 4) The name(s) of the Copyright Holder(s) or the Author(s) of the Font
70
  Software shall not be used to promote, endorse or advertise any
71
  Modified Version, except to acknowledge the contribution(s) of the
72
+ Copyright Holder(s) and the Author(s) or with their explicit written
73
  permission.
74
 
75
  5) The Font Software, modified or unmodified, in part or in whole,
76
+ must be distributed entirely under this license, and must not be
77
+ distributed under any other license. The requirement for fonts to
78
+ remain under this license does not apply to any document created
79
+ using the Font Software.
80
 
81
  TERMINATION
82
  This license becomes null and void if any of the above conditions are
gentium/QUOTES.txt DELETED
@@ -1,76 +0,0 @@
1
- QUOTES
2
- Gentium Release 1.02
3
- 28 November 2005
4
- ========================
5
-
6
-
7
- Read some of the comments sent to us by various grateful Gentium users:
8
-
9
-
10
- 'Purpose: to build a free multilingual font to bring better typography to
11
- thousands of languages around the globe. I can think of no higher calling.'
12
-
13
- '...an interesting blend of economical use of space, a serious tone of voice
14
- and a modern informal dress code.'
15
-
16
- 'Thank you for this fantastic font set -- fantastic both in its purpose and
17
- in its appearance and usability!'
18
-
19
- 'Finally I can include Greek characters in my English papers without looking
20
- typographically schizophrenic!'
21
-
22
- 'Thank you so much for sharing this amazing work. I do love the vision you
23
- have for "written word empowering". This is ethical science at its best.'
24
-
25
- 'Our language restoration project thanks you.'
26
-
27
- 'distinctive, elegant and readable'
28
-
29
- 'a very warm look'
30
-
31
- 'great consistency and legibility'
32
-
33
- 'lotion for the eyes'
34
-
35
- 'Your typeface Gentium is a "friendly" font to me. It's easy to read and its
36
- lines and visual connections flow gently.'
37
-
38
- 'I needed a nice serif font with haceks and other diacriticals... and was
39
- very happy to find your Gentium. Thank you for making this available to us
40
- poorer academic perfectionists!'
41
-
42
- 'Your font is definitely the most complete and good-looking I've found for
43
- my uses in Classical Greek.'
44
-
45
- '...the various letters in the Extended-Latin and IPA ranges look "native"
46
- to the font.'
47
-
48
- '...diacritic Nirvana...'
49
-
50
- 'Thank you very much for this excellent font. It is the most readable I have
51
- ever seen.'
52
-
53
- 'Officina Gentium: The workshop of the world.'
54
-
55
- 'Commercial quality for free! That's the best free font that I see.'
56
-
57
- 'May I congratulate you on what seems to be an outstanding effort matched
58
- only by your generosity.'
59
-
60
- 'I will be using this font regularly and will be recommending it strongly to
61
- others. This is a very beautiful typeface. What you have done is a most
62
- generous gift to the world.'
63
-
64
- 'Many thanks. I have an esthetic dislike of "Times" fonts and a scholar's
65
- budget. Now I have Gentium and I'm pleased as punch.'
66
-
67
- 'I appreciate your project, that of making a font suitable for many
68
- languages, including smaller ones.'
69
-
70
- 'I am not sure where in the world I will end up, so I need something all
71
- inclusive. Thanks so much!'
72
-
73
- 'Thanks for such a beautiful and mind-bogglingly useful typeface!'
74
-
75
- ...
76
-
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
gentium/README.txt DELETED
@@ -1 +0,0 @@
1
- README - WINDOWS
2
- --------------------------
 
 
readme.txt CHANGED
@@ -3,8 +3,8 @@ Contributors: takayukister
3
  Donate link: http://contactform7.com/donate/
4
  Tags: captcha
5
  Requires at least: 3.2
6
- Tested up to: 3.3.1
7
- Stable tag: 1.5
8
 
9
  Really Simple CAPTCHA is a CAPTCHA module intended to be called from other plugins. It is originally created for my Contact Form 7 plugin.
10
 
@@ -89,6 +89,12 @@ If you have any further questions, please submit them [to the support forum](htt
89
 
90
  == Changelog ==
91
 
 
 
 
 
 
 
92
  = 1.5 =
93
 
94
  * The required WordPress version changed to 3.2 and higher.
3
  Donate link: http://contactform7.com/donate/
4
  Tags: captcha
5
  Requires at least: 3.2
6
+ Tested up to: 3.5.1
7
+ Stable tag: 1.6
8
 
9
  Really Simple CAPTCHA is a CAPTCHA module intended to be called from other plugins. It is originally created for my Contact Form 7 plugin.
10
 
89
 
90
  == Changelog ==
91
 
92
+ = 1.6 =
93
+
94
+ * Bundled font changed to Gentium Basic 1.1.
95
+ * Some workarounds for infrequently reported problems on Windows server.
96
+ * Do temp file cleanup every time before generating CAPTCHA image.
97
+
98
  = 1.5 =
99
 
100
  * The required WordPress version changed to 3.2 and higher.
really-simple-captcha.php CHANGED
@@ -1,14 +1,14 @@
1
  <?php
2
  /*
3
  Plugin Name: Really Simple CAPTCHA
4
- Plugin URI: http://ideasilo.wordpress.com/2009/03/14/really-simple-captcha/
5
  Description: Really Simple CAPTCHA is a CAPTCHA module intended to be called from other plugins. It is originally created for my Contact Form 7 plugin.
6
  Author: Takayuki Miyoshi
7
- Version: 1.5
8
  Author URI: http://ideasilo.wordpress.com/
9
  */
10
 
11
- /* Copyright 2007-2012 Takayuki Miyoshi (email: takayukister at gmail.com)
12
 
13
  This program is free software; you can redistribute it and/or modify
14
  it under the terms of the GNU General Public License as published by
@@ -25,6 +25,8 @@ Author URI: http://ideasilo.wordpress.com/
25
  Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
26
  */
27
 
 
 
28
  class ReallySimpleCaptcha {
29
 
30
  function ReallySimpleCaptcha() {
@@ -37,13 +39,13 @@ class ReallySimpleCaptcha {
37
 
38
  /* Array of fonts. Randomly picked up per character */
39
  $this->fonts = array(
40
- dirname( __FILE__ ) . '/gentium/GenAI102.TTF',
41
- dirname( __FILE__ ) . '/gentium/GenAR102.TTF',
42
- dirname( __FILE__ ) . '/gentium/GenI102.TTF',
43
- dirname( __FILE__ ) . '/gentium/GenR102.TTF' );
44
 
45
  /* Directory temporary keeping CAPTCHA images and corresponding text files */
46
- $this->tmp_dir = dirname( __FILE__ ) . '/tmp/';
47
 
48
  /* Array of CAPTCHA image size. Width and height */
49
  $this->img_size = array( 72, 24 );
@@ -73,8 +75,11 @@ class ReallySimpleCaptcha {
73
  $this->answer_file_mode = 0440;
74
  }
75
 
76
- /* Generate and return random word with $chars characters x $char_length length */
77
-
 
 
 
78
  function generate_random_word() {
79
  $word = '';
80
 
@@ -87,12 +92,19 @@ class ReallySimpleCaptcha {
87
  return $word;
88
  }
89
 
90
- /* Generate CAPTCHA code and corresponding code and save them into $tmp_dir directory.
91
- $prefix is file prefix for both files.
92
- $captcha is a random word usually generated by generate_random_word()
93
- This function returns the filename of the CAPTCHA image temporary file */
94
-
 
 
95
  function generate_image( $prefix, $word ) {
 
 
 
 
 
96
  $dir = trailingslashit( $this->tmp_dir );
97
  $filename = null;
98
 
@@ -106,7 +118,12 @@ class ReallySimpleCaptcha {
106
 
107
  for ( $i = 0; $i < strlen( $word ); $i++ ) {
108
  $font = $this->fonts[array_rand( $this->fonts )];
109
- imagettftext( $im, $this->font_size, mt_rand( -2, 2 ), $x,
 
 
 
 
 
110
  $this->base[1] + mt_rand( -2, 2 ), $fg, $font, $word[$i] );
111
  $x += $this->font_char_width;
112
  }
@@ -135,13 +152,17 @@ class ReallySimpleCaptcha {
135
  return $filename;
136
  }
137
 
138
- /* Generate answer file corresponding to CAPTCHA image. */
139
-
 
 
 
 
140
  function generate_answer_file( $prefix, $word ) {
141
  $dir = trailingslashit( $this->tmp_dir );
142
  $answer_file = $dir . sanitize_file_name( $prefix . '.txt' );
143
 
144
- if ( $fh = fopen( $answer_file, 'w' ) ) {
145
  $word = strtoupper( $word );
146
  $salt = wp_generate_password( 64 );
147
  $hash = hash_hmac( 'md5', $word, $salt );
@@ -155,9 +176,13 @@ class ReallySimpleCaptcha {
155
  @chmod( $answer_file, $this->answer_file_mode );
156
  }
157
 
158
- /* Check a $response against the code kept in the temporary file with $prefix
159
- Return true if the two match, otherwise return false. */
160
-
 
 
 
 
161
  function check( $prefix, $response ) {
162
  $response = strtoupper( $response );
163
 
@@ -165,7 +190,7 @@ class ReallySimpleCaptcha {
165
  $filename = sanitize_file_name( $prefix . '.txt' );
166
  $file = $dir . $filename;
167
 
168
- if ( is_readable( $file ) && ( $code = file_get_contents( $file ) ) ) {
169
  $code = explode( '|', $code, 2 );
170
 
171
  $salt = $code[0];
@@ -178,25 +203,37 @@ class ReallySimpleCaptcha {
178
  return false;
179
  }
180
 
181
- /* Remove temporary files with $prefix */
182
-
 
 
 
183
  function remove( $prefix ) {
184
  $suffixes = array( '.jpeg', '.gif', '.png', '.php', '.txt' );
185
 
186
  foreach ( $suffixes as $suffix ) {
187
  $filename = sanitize_file_name( $prefix . $suffix );
188
  $file = trailingslashit( $this->tmp_dir ) . $filename;
189
- if ( is_file( $file ) )
190
  unlink( $file );
191
  }
192
  }
193
 
194
- /* Clean up dead files older than $minutes in the tmp folder */
195
-
 
 
 
 
196
  function cleanup( $minutes = 60 ) {
197
  $dir = trailingslashit( $this->tmp_dir );
198
 
199
- if ( ! is_dir( $dir ) || ! is_readable( $dir ) || ! is_writable( $dir ) )
 
 
 
 
 
200
  return false;
201
 
202
  $count = 0;
@@ -221,8 +258,11 @@ class ReallySimpleCaptcha {
221
  return $count;
222
  }
223
 
224
- /* Make a temporary directory and generate .htaccess file in it */
225
-
 
 
 
226
  function make_tmp_dir() {
227
  $dir = trailingslashit( $this->tmp_dir );
228
 
1
  <?php
2
  /*
3
  Plugin Name: Really Simple CAPTCHA
4
+ Plugin URI: http://contactform7.com/captcha/
5
  Description: Really Simple CAPTCHA is a CAPTCHA module intended to be called from other plugins. It is originally created for my Contact Form 7 plugin.
6
  Author: Takayuki Miyoshi
7
+ Version: 1.6
8
  Author URI: http://ideasilo.wordpress.com/
9
  */
10
 
11
+ /* Copyright 2007-2013 Takayuki Miyoshi (email: takayukister at gmail.com)
12
 
13
  This program is free software; you can redistribute it and/or modify
14
  it under the terms of the GNU General Public License as published by
25
  Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
26
  */
27
 
28
+ define( 'REALLYSIMPLECAPTCHA_VERSION', '1.6' );
29
+
30
  class ReallySimpleCaptcha {
31
 
32
  function ReallySimpleCaptcha() {
39
 
40
  /* Array of fonts. Randomly picked up per character */
41
  $this->fonts = array(
42
+ dirname( __FILE__ ) . '/gentium/GenBkBasR.ttf',
43
+ dirname( __FILE__ ) . '/gentium/GenBkBasI.ttf',
44
+ dirname( __FILE__ ) . '/gentium/GenBkBasBI.ttf',
45
+ dirname( __FILE__ ) . '/gentium/GenBkBasB.ttf' );
46
 
47
  /* Directory temporary keeping CAPTCHA images and corresponding text files */
48
+ $this->tmp_dir = path_join( dirname( __FILE__ ), 'tmp' );
49
 
50
  /* Array of CAPTCHA image size. Width and height */
51
  $this->img_size = array( 72, 24 );
75
  $this->answer_file_mode = 0440;
76
  }
77
 
78
+ /**
79
+ * Generate and return a random word.
80
+ *
81
+ * @return string Random word with $chars characters x $char_length length
82
+ */
83
  function generate_random_word() {
84
  $word = '';
85
 
92
  return $word;
93
  }
94
 
95
+ /**
96
+ * Generate CAPTCHA image and corresponding answer file.
97
+ *
98
+ * @param string $prefix File prefix used for both files
99
+ * @param string $word Random word generated by generate_random_word()
100
+ * @return string|bool The file name of the CAPTCHA image. Return false if temp directory is not available.
101
+ */
102
  function generate_image( $prefix, $word ) {
103
+ if ( ! $this->make_tmp_dir() )
104
+ return false;
105
+
106
+ $this->cleanup();
107
+
108
  $dir = trailingslashit( $this->tmp_dir );
109
  $filename = null;
110
 
118
 
119
  for ( $i = 0; $i < strlen( $word ); $i++ ) {
120
  $font = $this->fonts[array_rand( $this->fonts )];
121
+
122
+ // sanitize for Win32 installs
123
+ $font = str_replace( '\\', '/', $font );
124
+ $font = preg_replace( '|/+|', '/', $font );
125
+
126
+ imagettftext( $im, $this->font_size, mt_rand( -12, 12 ), $x,
127
  $this->base[1] + mt_rand( -2, 2 ), $fg, $font, $word[$i] );
128
  $x += $this->font_char_width;
129
  }
152
  return $filename;
153
  }
154
 
155
+ /**
156
+ * Generate answer file corresponding to CAPTCHA image.
157
+ *
158
+ * @param string $prefix File prefix used for answer file
159
+ * @param string $word Random word generated by generate_random_word()
160
+ */
161
  function generate_answer_file( $prefix, $word ) {
162
  $dir = trailingslashit( $this->tmp_dir );
163
  $answer_file = $dir . sanitize_file_name( $prefix . '.txt' );
164
 
165
+ if ( $fh = @fopen( $answer_file, 'w' ) ) {
166
  $word = strtoupper( $word );
167
  $salt = wp_generate_password( 64 );
168
  $hash = hash_hmac( 'md5', $word, $salt );
176
  @chmod( $answer_file, $this->answer_file_mode );
177
  }
178
 
179
+ /**
180
+ * Check a response against the code kept in the temporary file.
181
+ *
182
+ * @param string $prefix File prefix used for both files
183
+ * @param string $response CAPTCHA response
184
+ * @return bool Return true if the two match, otherwise return false.
185
+ */
186
  function check( $prefix, $response ) {
187
  $response = strtoupper( $response );
188
 
190
  $filename = sanitize_file_name( $prefix . '.txt' );
191
  $file = $dir . $filename;
192
 
193
+ if ( @is_readable( $file ) && ( $code = file_get_contents( $file ) ) ) {
194
  $code = explode( '|', $code, 2 );
195
 
196
  $salt = $code[0];
203
  return false;
204
  }
205
 
206
+ /**
207
+ * Remove temporary files with given prefix.
208
+ *
209
+ * @param string $prefix File prefix
210
+ */
211
  function remove( $prefix ) {
212
  $suffixes = array( '.jpeg', '.gif', '.png', '.php', '.txt' );
213
 
214
  foreach ( $suffixes as $suffix ) {
215
  $filename = sanitize_file_name( $prefix . $suffix );
216
  $file = trailingslashit( $this->tmp_dir ) . $filename;
217
+ if ( @is_file( $file ) )
218
  unlink( $file );
219
  }
220
  }
221
 
222
+ /**
223
+ * Clean up dead files older than given length of time.
224
+ *
225
+ * @param int $minutes Consider older files than this time as dead files
226
+ * @return int|bool The number of removed files. Return false if error occurred.
227
+ */
228
  function cleanup( $minutes = 60 ) {
229
  $dir = trailingslashit( $this->tmp_dir );
230
 
231
+ if ( ! @is_dir( $dir ) || ! @is_readable( $dir ) )
232
+ return false;
233
+
234
+ $is_win = ( 'WIN' === strtoupper( substr( PHP_OS, 0, 3 ) ) );
235
+
236
+ if ( ! ( $is_win ? win_is_writable( $dir ) : @is_writable( $dir ) ) )
237
  return false;
238
 
239
  $count = 0;
258
  return $count;
259
  }
260
 
261
+ /**
262
+ * Make a temporary directory and generate .htaccess file in it.
263
+ *
264
+ * @return bool True on successful create, false on failure.
265
+ */
266
  function make_tmp_dir() {
267
  $dir = trailingslashit( $this->tmp_dir );
268