diff --git a/ChangeLog b/ChangeLog
index c9629a882..8d8aacf24 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -582,7 +582,7 @@
Reported as
- http://lists.nongnu.org/archive/html/freetype-devel/2018-08/msg00124.html
+ https://lists.nongnu.org/archive/html/freetype-devel/2018-08/msg00124.html
* docs/reference/markdown/stylesheets/extra.css (.md-typeset code):
Add rule `white-space'.
@@ -735,7 +735,7 @@
Reported as
- http://lists.nongnu.org/archive/html/freetype-devel/2018-08/msg00083.html
+ https://lists.nongnu.org/archive/html/freetype-devel/2018-08/msg00083.html
2018-08-26 Werner Lemberg
To configure library dependencies like zlib and libpng, edit the freetype.users.props file in this directory. It also simplifies automated (command-line) builds using msbuild.
+href="https://msdn.microsoft.com/library/dd393574%28v=vs.100%29.aspx">msbuild.To link your executable with FreeType DLL, you may want to define DLL_IMPORT so that the imported functions are appropriately diff --git a/builds/windows/visualc/index.html b/builds/windows/visualc/index.html index 3a77f36a4..2eefbdced 100644 --- a/builds/windows/visualc/index.html +++ b/builds/windows/visualc/index.html @@ -26,7 +26,7 @@ It compiles the following libraries from the FreeType 2.9.1 sources:
archives are already stored this way, so no further action is required. If you use some .tar.*z archives, be sure to configure your extracting tool to convert the line endings. For example, with WinZip, you should activate the TAR +href="https://www.winzip.com">WinZip, you should activate the TAR file smart CR/LF Conversion option. Alternatively, you may consider using the unix2dos or u2d utilities that are floating around, which specifically deal with this particular problem. diff --git a/builds/windows/visualce/index.html b/builds/windows/visualce/index.html index d5a3ca3e3..4be4bc8c1 100644 --- a/builds/windows/visualce/index.html +++ b/builds/windows/visualce/index.html @@ -35,7 +35,7 @@ It compiles the following libraries from the FreeType 2.9.1 sources: archives are already stored this way, so no further action is required. If you use some .tar.*z archives, be sure to configure your extracting tool to convert the line endings. For example, with WinZip, you should activate the TAR +href="https://www.winzip.com">WinZip, you should activate the TAR file smart CR/LF Conversion option. Alternatively, you may consider using the unix2dos or u2d utilities that are floating around, which specifically deal with this particular problem. diff --git a/docs/CHANGES b/docs/CHANGES index c90cf546b..30156006d 100644 --- a/docs/CHANGES +++ b/docs/CHANGES @@ -76,7 +76,7 @@ CHANGES BETWEEN 2.9 and 2.9.1 - CVE-2018-6942: Older FreeType versions can crash with certain malformed variation fonts. - http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6942 + https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6942 II. MISCELLANEOUS @@ -1393,7 +1393,7 @@ CHANGES BETWEEN 2.4.10 and 2.4.11 Originally, it was a separate patch available from - http://www.infinality.net/blog/ + https://web.archive.org/web/20150710073951/http://www.infinality.net:80/blog/ and which has been integrated. @@ -4115,7 +4115,7 @@ CHANGES BETWEEN beta8 and 2.0 untested for now. - Updated `docs/docmaker.py', a draft API reference is available at - http://www.freetype.org/ft2api.html. + https://web.archive.org/web/20001215173400/http://www.freetype.org:80/ft2api.html. - Changed `type1' to use `psaux'. diff --git a/docs/INSTALL b/docs/INSTALL index 71d4a0553..73d1d6a68 100644 --- a/docs/INSTALL +++ b/docs/INSTALL @@ -70,7 +70,7 @@ II. Custom builds of the library [1] make++, a make tool written in Perl, has sufficient support of GNU make extensions to build FreeType. See - http://makepp.sourceforge.net + https://makepp.sourceforge.net for more information; you need version 2.0 or newer, and you must pass option `--norc-substitution'. diff --git a/docs/INSTALL.GNU b/docs/INSTALL.GNU index e314ecfdd..b15e0b5ef 100644 --- a/docs/INSTALL.GNU +++ b/docs/INSTALL.GNU @@ -23,7 +23,7 @@ instructions in the file `INSTALL.UNIX' instead. Note that make++, a make tool written in Perl, supports enough features of GNU make to compile FreeType. See - http://makepp.sourceforge.net + https://makepp.sourceforge.net for more information; you need version 2.0 or newer, and you must pass option `--norc-substitution'. diff --git a/docs/MAKEPP b/docs/MAKEPP index a4d44b78e..4450e4770 100644 --- a/docs/MAKEPP +++ b/docs/MAKEPP @@ -1,5 +1,5 @@ As a special exception, FreeType can also be built with the 'makepp' -build tool, available from http://makepp.sourceforge.net. +build tool, available from https://makepp.sourceforge.net. Note, however, that you will need at least version 2.0 and pass the option --norc-substitution to have it work correctly. diff --git a/docs/formats.txt b/docs/formats.txt index 75aba92e3..e4acf979d 100644 --- a/docs/formats.txt +++ b/docs/formats.txt @@ -165,8 +165,8 @@ which isn't supported yet please send a mail too. partially defined in MHP 1.0.3 (also called ETSI TS 101812 V1.3.1) section 7.4. - http://www.etsi.org/ - http://webapp.etsi.org/workprogram/Report_WorkItem.asp?WKI_ID=18799 + https://www.etsi.org/ + https://webapp.etsi.org/workprogram/Report_WorkItem.asp?WKI_ID=18799 [3] Support is rudimentary currently; some tables or data are not loaded yet. diff --git a/include/freetype/ftdriver.h b/include/freetype/ftdriver.h index 1e6835d69..779ee450c 100644 --- a/include/freetype/ftdriver.h +++ b/include/freetype/ftdriver.h @@ -249,7 +249,7 @@ FT_BEGIN_HEADER * of improving symmetry in glyphs through hinting the right-side bearing * were no longer necessary. This lead to what GDI calls 'natural * widths' ClearType, see - * http://www.beatstamm.com/typography/RTRCh4.htm#Sec21. Since hinting + * http://rastertragedy.com/RTRCh4.htm#Sec21. Since hinting * has extra resolution, most non-linearity went away, but it is still * possible for hints to change the advance widths in this mode. * @@ -262,7 +262,7 @@ FT_BEGIN_HEADER * to determine the width in bi-level rendering, and then re-run in * ClearType, with the difference in widths being absorbed in the font * hints for ClearType (mostly in the white space of hints); see - * http://www.beatstamm.com/typography/RTRCh4.htm#Sec20. Somewhat by + * http://rastertragedy.com/RTRCh4.htm#Sec20. Somewhat by * definition, compatible width ClearType allows for non-linear widths, * but only when the bi-level version has non-linear widths. * @@ -275,7 +275,7 @@ FT_BEGIN_HEADER * mode', not to be confused with GDI's 'natural widths'. Subpixel * positioning, in the current implementation of Direct Write, * unfortunately does not support hinted advance widths, see - * http://www.beatstamm.com/typography/RTRCh4.htm#Sec22. Note that the + * http://rastertragedy.com/RTRCh4.htm#Sec22. Note that the * TrueType interpreter fully allows the advance width to be adjusted in * this mode, just the DWrite client will ignore those changes. * @@ -284,7 +284,7 @@ FT_BEGIN_HEADER * This is a set of exceptions made in the TrueType interpreter to * minimize hinting techniques that were problematic with the extra * resolution of ClearType; see - * http://www.beatstamm.com/typography/RTRCh4.htm#Sec1 and + * http://rastertragedy.com/RTRCh4.htm#Sec1 and * https://www.microsoft.com/typography/cleartype/truetypecleartype.aspx. * This technique is not to be confused with ClearType compatible widths. * ClearType backward compatibility has no direct impact on changing diff --git a/src/psaux/pshints.c b/src/psaux/pshints.c index 6b2bd7e5d..1cbecd2b1 100644 --- a/src/psaux/pshints.c +++ b/src/psaux/pshints.c @@ -1212,7 +1212,7 @@ * (`u'). * * See notation in - * http://softsurfer.com/Archive/algorithm_0104/algorithm_0104B.htm. + * http://geomalgorithms.com/a05-_intersect-1.html. * Calculations are done in 16.16, but must handle the squaring of * line lengths in character space. We scale all vectors by 1/32 to * avoid overflow. This allows values up to 4095 to be squared. The diff --git a/src/smooth/ftgrays.c b/src/smooth/ftgrays.c index 871e98136..7029e590a 100644 --- a/src/smooth/ftgrays.c +++ b/src/smooth/ftgrays.c @@ -48,7 +48,7 @@ * coverage of the outline on each pixel cell. * * It is based on ideas that I initially found in Raph Levien's - * excellent LibArt graphics library (see http://www.levien.com/libart + * excellent LibArt graphics library (see https://www.levien.com/libart * for more information, though the web pages do not tell anything * about the renderer; you'll have to dive into the source code to * understand how it works). diff --git a/src/truetype/ttinterp.h b/src/truetype/ttinterp.h index 172cdd028..eb2db75a5 100644 --- a/src/truetype/ttinterp.h +++ b/src/truetype/ttinterp.h @@ -352,7 +352,7 @@ FT_BEGIN_HEADER * https://www.microsoft.com/typography/cleartype/truetypecleartype.aspx * * [3] Beat Stamm describes it in more detail: - * http://www.beatstamm.com/typography/RTRCh4.htm#Sec12 + * http://rastertragedy.com/RTRCh4.htm#Sec12. * * [4] The list of `native ClearType' fonts is small at the time of this * writing; I found the following on a Windows 10 Update 1511