If I read the ls output correctly the font file is empty. Such font
can be hardly useful for embedding text into images.
I think that Arial is normally not found on OS X but there are similar
sans-serif fonts that are no worse than Arial.
That’s a lot of empty fonts, and I know I didn’t put them there.
MacOS X follows legacy Macintosh glitches to its detriment,
sometimes. HFS+ supports forked files, and fonts, for legacy
reasons, put their real data in the invisible data fork. eg:
ls -l /Library/Fonts/Arial
-rw-rw-r-- 1 root admin 0 Mar 20 2005 /Library/Fonts/Arial
ls -l /Library/Fonts/Arial/rsrc
-rw-rw-r-- 1 root admin 317313 Mar 20 2005 /Library/Fonts/Arial/
rsrc
MacOS X follows legacy Macintosh glitches to its detriment,
sometimes. HFS+ supports forked files, and fonts, for legacy
reasons, put their real data in the invisible data fork. eg:
ls -l /Library/Fonts/Arial
-rw-rw-r-- 1 root admin 0 Mar 20 2005 /Library/Fonts/Arial
ls -l /Library/Fonts/Arial/rsrc
-rw-rw-r-- 1 root admin 317313 Mar 20 2005 /Library/Fonts/
Arial/rsrc
ah OK, fine thanxs !
but in this case why ls doesn’t see a directory, ie i’d have seen
rather :
drw-rw-r-- 1 root admin 0 Mar 20 2005 /Library/Fonts/Arial
–^---- directory isn’t it ?
-rw-rw-r-- 1 root admin 317313 Mar 20 2005 /Library/Fonts/
Arial/rsrc
ah OK, fine thanxs !
but in this case why ls doesn’t see a directory, ie i’d have seen
rather :
drw-rw-r-- 1 root admin 0 Mar 20 2005 /Library/Fonts/Arial
–^---- directory isn’t it ?
Because it isn’t a directory, it’s a forked file. A file can have
many forks, and rsrc is just some sort of alias to the “resource”
fork. A directory would have rather different behaviour from a
forked file, and overloading the path notation was thought to be the
best way to handle it. It’s a no-win situation when you think about it.
Because it isn’t a directory, it’s a forked file. A file can have
many forks, and rsrc is just some sort of alias to the “resource”
fork. A directory would have rather different behaviour from a
forked file, and overloading the path notation was thought to be the
best way to handle it. It’s a no-win situation when you think about it.
OK, but why Graphiz isn’t aware of that ?
something to do in order to avoid the error message “font Arial not
found” ???
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.