Tune LaTeX formatting to suppress overfull boxes in output.

- Change teletype font from Courier to Computer Modern Typewriter which
  is narrower.
- Be more tolerant when formatting paragraphs, to avoid overfull boxes.
  Do this by increasing \tolerance, \hfuzz, and \emergencystretch.
- Allow line breaks after underscores (but with a large penalty).
- The second column of the "defined variables" table was too narrow.
- Increase the width of margin notes to 40 mm (was about 33 mm before).
- Rename the two longest featurelabels (profile-iuse-injection and
  controllable-compress) because they still didn't fit into the margin.
- I'd rather have avoided explicit \allowbreak commands, but in very few
  cases there is no other way.

1 files changed, 9 insertions, 8 deletions

diff --git a/profiles.tex b/profiles.tex
index 8fb7674..ffdcdec 100644
--- a/profiles.tex
+++ b/profiles.tex
@@ -110,8 +110,8 @@ the forms defined by the directory's EAPI.
 \label{sec:use-masking}
 This section covers the eight files \t{use.mask}, \t{use.force}, \t{use.stable.mask},
 \t{use.stable.force}, \t{package.use.mask}, \t{package.use.force}, \t{package.use.stable.mask},
-and \t{package.use.stable.force}. They are described together because they interact in a non-trivial
-manner.
+and \t{package.use.\allowbreak stable.force}. They are described together because they interact in
+a non-trivial manner.
 
 Simply speaking, \t{use.mask} and \t{use.force} are used to say that a given USE flag must never or
 always, respectively, be enabled when using this profile. \t{package.use.mask} and
@@ -120,9 +120,10 @@ always, respectively, be enabled when using this profile. \t{package.use.mask} a
 \featurelabel{stablemask}
 In profile directories with an EAPI supporting stable masking, as listed in
 table~\ref{tab:profile-stablemask}, the same is true for \t{use.stable.mask}, \t{use.stable.force},
-\t{package.use.stable.mask} and \t{package.use.stable.force}. These files, however, only act on
-packages that are merged due to a stable keyword in the sense of subsection~\ref{sec:keywords}.
-Thus, these files can be used to restrict the feature set deemed stable in a package.
+\t{package.use.stable.mask} and \t{package.use.\allowbreak stable.force}. These files, however,
+only act on packages that are merged due to a stable keyword in the sense of
+subsection~\ref{sec:keywords}. Thus, these files can be used to restrict the feature set deemed
+stable in a package.
 
 \ChangeWhenAddingAnEAPI{5}
 \begin{centertable}{Profile directory support for masking/forcing use flags in stable
@@ -187,9 +188,9 @@ exactly if replacing in \t{KEYWORDS} all stable keywords by the corresponding ti
 keywords (see subsection~\ref{sec:keywords}) would result in the package installation being
 prevented due to the \t{KEYWORDS} setting.
 
-The logic for \t{use.force}, \t{use.stable. force}, \t{package.use.force}, and
-\t{package.use.stable.force} is identical. If a flag is both masked and forced, the mask is
-considered to take precedence.
+The logic for \t{use.force}, \t{use.stable.force}, \t{package.use.force}, and
+\t{package.use.\allowbreak stable.force} is identical. If a flag is both masked and forced, the
+mask is considered to take precedence.
 
 \t{USE\_EXPAND} values may be forced or masked by using \t{expand\_name\_value}.