.otf file extension support and foreign characters
dfletcher - October 10, 2006 - 16:54
| Project: | Signwriter |
| Version: | 6.x-2.0-beta1 |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
First let me just say thanks for a great module!
Signwriter (well TrueType) supports .otf fonts just fine but because of the way Signwriter looks for fonts, the path must be a full hard coded path. This would be fine but I have several profiles and am in the process of moving my server and I have to change each one when I move.
It would be nice if signwriter could just look for .otf in addition to .ttf and then I could just specify the base name and put the path in the global configuration.
#1
Hi dfletcher,
I've had a look at this, but Signwriter uses php's GD image library to draw the fonts, and GD is the one that automatically looks for extensions of .ttf. It would be possible to add a function which searches through your GDFONTPATH and looks for files ending in .otf as well, but that seems like a bit of a hack.
Maybe you could just rename your .otf files to .ttf?
Alex
#2
This issue has been inactive for some time and is not actually a bug.
Closing this ticket.
#3
Renaming an .otf file to .ttf worked for me.
-Steve
#4
Hi,
I changed the .otf extension to .tff, but foreign characters are not rendering properly. Do you think there is a workaround, or is this a limitation of the system?
I also updated the issue title to reflect the problem with foreign characters.
Albert.
#5
...reopening the issue and setting to 6.x-2.0. Thanks.