From 1d3d8d704c30ad1e69f01cb0548560023c47dd77 Mon Sep 17 00:00:00 2001 From: Aidan Lister Date: Sat, 18 Dec 2004 03:49:03 +0000 Subject: [PATCH] Refined a couple of comments git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@175007 c90b9560-bf6c-de11-be94-00142212c4b1 --- reference/image/functions/imagettftext.xml | 28 +++++++++++++++++----- 1 file changed, 22 insertions(+), 6 deletions(-) diff --git a/reference/image/functions/imagettftext.xml b/reference/image/functions/imagettftext.xml index 84d580ef9b..8654191c92 100644 --- a/reference/image/functions/imagettftext.xml +++ b/reference/image/functions/imagettftext.xml @@ -1,5 +1,5 @@ - + @@ -88,18 +88,34 @@ The path to the TrueType font you wish to use. - Depending on which version of the GD library that PHP is using, when + Depending on which version of the GD library PHP is using, when fontfile does not begin with a leading - / then .ttf will be appended + / then .ttf will be appended to the filename and the library will attempt to search for that filename along a library-defined font path. - When using versions of the GD library lower than 2.0.18, a "space" character, - rather than a semicolon, was used to define alternate paths to the font files. + When using versions of the GD library lower than 2.0.18, a space character, + rather than a semicolon, was used as the 'path separator' for different font files. Unintentional use of this feature will result in the warning message: - Warning: Could not find/open font. + Warning: Could not find/open font. For these affected versions, the + only solution is moving the font to a path which does not contain spaces. + + In many cases where a font resides in the same directory as the script using it + the following trick will alleviate any include problems. + + +]]> + +