summaryrefslogtreecommitdiff
path: root/include/freetype/config/ftstdlib.h
diff options
context:
space:
mode:
authorNikhil Ramakrishnan <ramakrishnan.nikhil@gmail.com>2018-08-24 22:22:30 +0530
committerNikhil Ramakrishnan <ramakrishnan.nikhil@gmail.com>2018-08-25 16:16:56 +0530
commitae5d1a4cec37557f31aec270332cfe886a62f9a0 (patch)
treecf8f4ad5e1ccd82897b36e2cc41adc62de1ef6b2 /include/freetype/config/ftstdlib.h
parent77f0814a3162a945d6d6704f545827f883e451e5 (diff)
downloadfreetype2-ae5d1a4cec37557f31aec270332cfe886a62f9a0.tar.gz
* include/*.*: Convert comments to markdown.
This commit was created by applying scripts `markify.py' and `markdown-format.bash' to all C header files, followed by minor clean-up. No change in functionality, of course. Scripts used: https://github.com/nikramakrishnan/freetype-docs.git: Commit dfce31e. http://lists.nongnu.org/archive/html/freetype-devel/2018-08/msg00013.html: With patches applied.
Diffstat (limited to 'include/freetype/config/ftstdlib.h')
-rw-r--r--include/freetype/config/ftstdlib.h18
1 files changed, 9 insertions, 9 deletions
diff --git a/include/freetype/config/ftstdlib.h b/include/freetype/config/ftstdlib.h
index a744d0d05..a11db25f8 100644
--- a/include/freetype/config/ftstdlib.h
+++ b/include/freetype/config/ftstdlib.h
@@ -41,17 +41,17 @@
*
* integer limits
*
- * UINT_MAX and ULONG_MAX are used to automatically compute the size
- * of `int' and `long' in bytes at compile-time. So far, this works
- * for all platforms the library has been tested on.
+ * UINT_MAX and ULONG_MAX are used to automatically compute the size of
+ * 'int' and 'long' in bytes at compile-time. So far, this works for all
+ * platforms the library has been tested on.
*
- * Note that on the extremely rare platforms that do not provide
- * integer types that are _exactly_ 16 and 32 bits wide (e.g. some
- * old Crays where `int' is 36 bits), we do not make any guarantee
- * about the correct behaviour of FT2 with all fonts.
+ * Note that on the extremely rare platforms that do not provide integer
+ * types that are _exactly_ 16 and 32 bits wide (e.g. some old Crays where
+ * 'int' is 36 bits), we do not make any guarantee about the correct
+ * behaviour of FT2 with all fonts.
*
- * In these case, `ftconfig.h' will refuse to compile anyway with a
- * message like `couldn't find 32-bit type' or something similar.
+ * In these case, `ftconfig.h` will refuse to compile anyway with a message
+ * like 'couldn't find 32-bit type' or something similar.
*
*/