Is There a Better Way?

Contents
8A Better Macro Structure
7A Better Font Structure

=Defining the TDS required many compromises. Both the overallEstructure and the names of the individual directories were arrived atFby finding common ground among many opinions. The driving forces wereBachievability (in terms of what could technically be done and what=could reasonably be expected from developers) and regularity ?(files grouped together in an arrangement that ``made sense'').

FThe arrangement actually adopted tends to spread files out into two orGthree places (macros, documentation, and fonts, for example, are spread<into different sections of the tree right at the top level).>

A Better Macro Structure

The TWG settled on the &format/package ;arrangement after long discussion about how best to arrange the files.

GThe primary alternative to this arrangement was a scheme which reversed the order of these directories: &package/format.HThis reversed arrangement has a strong appeal: it keeps all of the files4related to a particular package in a single place.

6In the end, the format/package &structure won for a couple of reasons:

It is closer in spirit to the arrangements that are actually in use already. D The fact that several members of the TWG already have arrangementsC that are similar to the TDS demonstrates that this arrangement isF usable (proof by example). The alternative arrangement is not in useC at any known site, and the TWG felt it wrong to mandate something. with which there is no practical experience.O
The alternative arrangement spreads out the files needed by the system.I The files that must be found using subdirectory searching may be spread5 out in a wide, shallow tree. This spreading effectK could have a profound impact on the efficiency of subdirectory searching.