i've used rdoc with the option -d, i get the graphviz output images
howver i get this message also :
Diagrams: .Error: Could not find/open font : Arial
.Error: Could not find/open font : Arial
this font is on my computer :
%> ls -al /Library/Fonts gives :
-rw-rw-r-- 1 root admin 0 Mar 21 2005 Arial
then i wonder if their is a env var to setup for ruby ??? and/or for
Graphviz about fonts directory "Library/Fonts" ???
--
une bévue
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.
Thanks
Michal
On 9/4/06, Une bévue <pere.noel@laponie.com.invalid> wrote:
i've used rdoc with the option -d, i get the graphviz output images
howver i get this message also :Diagrams: .Error: Could not find/open font : Arial
.Error: Could not find/open font : Arialthis font is on my computer :
%> ls -al /Library/Fonts gives :
-rw-rw-r-- 1 root admin 0 Mar 21 2005 Arial
right ))
Le 4 sept. 06 à 13:41, Michal Suchanek a écrit :
If I read the ls output correctly the font file is empty. Such font
can be hardly useful for embedding text into images.
Hmm I think OS X does something funky with it's fonts:
logan:/Library/Fonts% ls -l | grep Arial
-rw-rw-r-- 1 root admin 0 Mar 20 2005 Arial
-rw-rw-r-- 1 root admin 0 Mar 20 2005 Arial Black
-rw-rw-r-- 1 root admin 0 Mar 20 2005 Arial Narrow
-rw-rw-r-- 1 root admin 0 Mar 20 2005 Arial Rounded Bold
-rw-rw-r-- 1 root admin 38476 Mar 1 2005 ArialHB.ttf
-rw-rw-r-- 1 root admin 38136 Mar 1 2005 ArialHBBold.ttf
logan:/Library/Fonts% ls -l | awk '$5 ~ /^0$/ { print }'
-rw-rw-r-- 1 root admin 0 Mar 20 2005 Andale Mono
-rw-rw-r-- 1 root admin 0 Mar 20 2005 Arial
-rw-rw-r-- 1 root admin 0 Mar 20 2005 Arial Black
-rw-rw-r-- 1 root admin 0 Mar 20 2005 Arial Narrow
-rw-rw-r-- 1 root admin 0 Mar 20 2005 Arial Rounded Bold
-rw-rw-r-- 1 root admin 0 Mar 20 2005 Brush Script
-rw-rw-r-- 1 root admin 0 Mar 20 2005 Comic Sans MS
-rw-rw-r-- 1 root admin 0 Mar 20 2005 Courier New
-rw-rw-r-- 1 root admin 0 Mar 20 2005 Georgia
-rw-rw-r-- 1 root admin 0 Mar 20 2005 Impact
-rw-rw-r-- 1 root admin 0 Mar 20 2005 Times New Roman
-rw-rw-r-- 1 root admin 0 Mar 20 2005 Trebuchet MS
-rw-rw-r-- 1 root admin 0 Mar 20 2005 Verdana
-rw-rw-r-- 1 root admin 0 Mar 20 2005 Webdings
-rw-r--r-- 1 root admin 0 Nov 6 2005 fonts.cache-1
That's a lot of empty fonts, and I know I didn't put them there.
On Sep 4, 2006, at 12:57 PM, Yvon Thoraval wrote:
Le 4 sept. 06 à 13:41, Michal Suchanek a écrit :
If I read the ls output correctly the font file is empty. Such font
can be hardly useful for embedding text into images.right ))
same prob by me )))
Le 4 sept. 06 à 20:10, Logan Capaldo a écrit :
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
Paul
On 4 Sep 2006, at 19:10, Logan Capaldo wrote:
Hmm I think OS X does something funky with it's fonts:
logan:/Library/Fonts% ls -l | grep Arial
-rw-rw-r-- 1 root admin 0 Mar 20 2005 Arial
-rw-rw-r-- 1 root admin 0 Mar 20 2005 Arial Black
-rw-rw-r-- 1 root admin 0 Mar 20 2005 Arial Narrow
-rw-rw-r-- 1 root admin 0 Mar 20 2005 Arial Rounded Bold
-rw-rw-r-- 1 root admin 38476 Mar 1 2005 ArialHB.ttf
-rw-rw-r-- 1 root admin 38136 Mar 1 2005 ArialHBBold.ttfThat'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/Arialls -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 ?
Le 4 sept. 06 à 20:43, Paul Lynch a écrit :
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.
Paul
On 5 Sep 2006, at 07:47, Yvon Thoraval wrote:
Le 4 sept. 06 à 20:43, Paul Lynch a écrit :
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/Arialls -l /Library/Fonts/Arial/rsrc
-rw-rw-r-- 1 root admin 317313 Mar 20 2005 /Library/Fonts/Arial/rsrcah 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 ?
OK, but why Graphiz isn't aware of that ?
something to do in order to avoid the error message "font Arial not
found" ???
Paul Lynch <paul@plsys.co.uk> wrote:
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.
--
une bévue
Perhaps make a copy of the resource fork somewhere?
It should not break anything if you do cat Arial/rsrc >> Arial
Thanks
Michal
On 9/7/06, Une bévue <pere.noel@laponie.com.invalid> wrote:
Paul Lynch <paul@plsys.co.uk> wrote:
>
> 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" ???
OK thanks, i'll try that when time permit, thanxs !
Le 7 sept. 06 à 21:44, Michal Suchanek a écrit :
Perhaps make a copy of the resource fork somewhere?
It should not break anything if you do cat Arial/rsrc >> Arial