F
filthy-mcnasty
Posted by it's author, Al Jones, in alt.binaries.fonts on Sunday 12th
March. Size zipped 74,123 bytes, plus documentation file of 83,456 bytes
included in the same post
The present version handles TrueType (TTF), OpenType (OTF) and
PostScript Type 1 (AFM/INF/PFB/PFM) font files. Later versions will
handle raster .FON files too. Operations are presently limited to
copy/move. It has the ability to sort fonts by foundry, designer, alpha,
family or a combination of these according to the user's preferences
It comes with 2 TXTFiles, one each for foundries and designers. These
are tab-delimited files which can be modified/extended by the user.
However, while the program is still in development, Al would prefer that
users modify the start link for the application with it's /l (for log)
switch - ie "FontOrg.EXE /l" (no quotes). This will produce a file named
Unknown.LOG, containing as much identification as can be extracted from
otherwise unidentifiable fontfiles - Those posted to a folder named
_unknown\unknown. The logfile should be posted to Al in
alt.binaries.fonts, and gradually the information contained therein will
be incorporated in the 2 TXTFiles
Installation is of the good old-fashioned variety. Copy it to a folder
of choice, make a link. That's it. Easy to get rid of too, though you'll
not be doing that
At present there is no helpfile, but basic instructions are in the
accompanying documentation file
To run Font Organiser you will need to have the Microsoft DotNet version
2.0 runtimes installed. Many new applications require these, so there is
a good chance many of you will already have them. Otherwise they are
easily found on the Microsoft recommended downloads pages. Presently one
as yet unresolved, but entirely harmless, issue remains regarding
FontOrg's use of DotNet. It is flagged by ZoneAlarm's firewall. It makes
no attempt to access the external net, but rather "listens" passively to
the internal net, ie the local machine. ET most definitely does NOT
phone home, or collect data of any kind. This anomoly is currently being
tackled by Al
As a beta tester I have experienced no problems with FontOrg. Even in
the earliest incarnations the few errors that occurred were trapped
without even necessitating closure of the program
To satisfy yourselves of it's capabilities you would probably initially
prefer to try it on copies of your font files, and to restrict it to
copy operations rather than moves. I have tested it on tens of thousands
of files without losing or damaging any. It will NOT mismatch your
PostScript font sets. In fact, as far as I know, it is unique in that it
maintains links between the AFM/INF and PFB/PFM pairs. I have too many
times had to manually clear up the orphans and other detritus left
behind by some other very expensive commercial utilities
The cons? It's NOT a font manager. Just a sorter. It won't necessarily
sort exactly to every individual's notions of perfection. I own up to
being one of those anal retentives who subsorts the sorts. Some of my
font folder trees are seven or eight levels deep. Get a life. One day.
It will however remove almost all of the drudgery from the job. And for
those who DO have a life, it'll probably suit you pretty well as it is
Any quibbles with the above are down to me. I've probably forgotten
something. Read the documentation. I'm biased. I was going to say that
for it's size it's the best sorter I've ever had the pleasure of using.
But we all know that size doesn't matter. So, I'm just going to have to
settle for saying it's the best
And don't forget that /l switch. Your feedback is valuable to Al and the
user-base alike, so post those Unknown.LOG files to alt.binaries.fonts,
and maybe a thankyou or three to Al
March. Size zipped 74,123 bytes, plus documentation file of 83,456 bytes
included in the same post
The present version handles TrueType (TTF), OpenType (OTF) and
PostScript Type 1 (AFM/INF/PFB/PFM) font files. Later versions will
handle raster .FON files too. Operations are presently limited to
copy/move. It has the ability to sort fonts by foundry, designer, alpha,
family or a combination of these according to the user's preferences
It comes with 2 TXTFiles, one each for foundries and designers. These
are tab-delimited files which can be modified/extended by the user.
However, while the program is still in development, Al would prefer that
users modify the start link for the application with it's /l (for log)
switch - ie "FontOrg.EXE /l" (no quotes). This will produce a file named
Unknown.LOG, containing as much identification as can be extracted from
otherwise unidentifiable fontfiles - Those posted to a folder named
_unknown\unknown. The logfile should be posted to Al in
alt.binaries.fonts, and gradually the information contained therein will
be incorporated in the 2 TXTFiles
Installation is of the good old-fashioned variety. Copy it to a folder
of choice, make a link. That's it. Easy to get rid of too, though you'll
not be doing that
At present there is no helpfile, but basic instructions are in the
accompanying documentation file
To run Font Organiser you will need to have the Microsoft DotNet version
2.0 runtimes installed. Many new applications require these, so there is
a good chance many of you will already have them. Otherwise they are
easily found on the Microsoft recommended downloads pages. Presently one
as yet unresolved, but entirely harmless, issue remains regarding
FontOrg's use of DotNet. It is flagged by ZoneAlarm's firewall. It makes
no attempt to access the external net, but rather "listens" passively to
the internal net, ie the local machine. ET most definitely does NOT
phone home, or collect data of any kind. This anomoly is currently being
tackled by Al
As a beta tester I have experienced no problems with FontOrg. Even in
the earliest incarnations the few errors that occurred were trapped
without even necessitating closure of the program
To satisfy yourselves of it's capabilities you would probably initially
prefer to try it on copies of your font files, and to restrict it to
copy operations rather than moves. I have tested it on tens of thousands
of files without losing or damaging any. It will NOT mismatch your
PostScript font sets. In fact, as far as I know, it is unique in that it
maintains links between the AFM/INF and PFB/PFM pairs. I have too many
times had to manually clear up the orphans and other detritus left
behind by some other very expensive commercial utilities
The cons? It's NOT a font manager. Just a sorter. It won't necessarily
sort exactly to every individual's notions of perfection. I own up to
being one of those anal retentives who subsorts the sorts. Some of my
font folder trees are seven or eight levels deep. Get a life. One day.
It will however remove almost all of the drudgery from the job. And for
those who DO have a life, it'll probably suit you pretty well as it is
Any quibbles with the above are down to me. I've probably forgotten
something. Read the documentation. I'm biased. I was going to say that
for it's size it's the best sorter I've ever had the pleasure of using.
But we all know that size doesn't matter. So, I'm just going to have to
settle for saying it's the best
And don't forget that /l switch. Your feedback is valuable to Al and the
user-base alike, so post those Unknown.LOG files to alt.binaries.fonts,
and maybe a thankyou or three to Al