>From ba0af5ad755ab4e175b07abb71890077e4d54a20 Mon Sep 17 00:00:00 2001
From: Akira Yokosawa <akiyks@xxxxxxxxx>
Date: Sat, 5 Aug 2017 12:20:00 +0900
Subject: [PATCH 3/3] styleguide: Remove references to 'floatrow' and adjust context
Also fix a typo (and -> nor).
Signed-off-by: Akira Yokosawa <akiyks@xxxxxxxxx>
---
appendix/styleguide/styleguide.tex | 28 ++++++++++++++--------------
1 file changed, 14 insertions(+), 14 deletions(-)
diff --git a/appendix/styleguide/styleguide.tex b/appendix/styleguide/styleguide.tex
index 72b8ca0..22ff2f4 100644
--- a/appendix/styleguide/styleguide.tex
+++ b/appendix/styleguide/styleguide.tex
@@ -128,7 +128,7 @@ be used as a prefix. An improper example:
\label{sec:app:styleguide:Non-SI Unit Symbol}
Although NIST style guide does not cover non-SI unit symbols
-such as ``KB'', ``MB'', and ``GB'', the same rule should be followed.
+such as ``KB'', ``MB'', nor ``GB'', the same rule should be followed.
Example:
@@ -320,9 +320,9 @@ Line numbers are manually placed for ease of referencing them within
number counter and the count can be displayed in the resulting
listing. Leftmost line numbers in
Figure~\ref{fig:app:styleguide:LaTeX Source of Sample Code Snippet}
- are output by the feature. See the source of this Section
- in \path{appendix/styleguide/styleguide.tex}
- if you are interested.}
+ are output by the feature. The litmus tests in
+ Section~\ref{sec:advsync:Memory Barriers}
+ has been converted to use the auto-numbering feature.}
The verbatim environment is used for listings with too many lines
to fit in a column. It is also used to avoid overwhelming
@@ -411,8 +411,7 @@ The \qco{\\verb} macro can be used in running text if you
need to use monospace font for a string which contains
many characters to escape.\footnote{
\co{\\verb} is not almighty though. For example, you can't use it
- within a footnote nor table inside ``floatrow'' environment mentioned
- later. If you do so, you will see a fatal latex error.
+ within a footnote. If you do so, you will see a fatal latex error.
There are several workarounds of this problem, but as for perfbook,
\co{\\co\{\}} should suffice.}
@@ -588,7 +587,10 @@ This section lists up such candidates.
Strictly speaking, code snippets are \emph{not} figures.
They deserve their own floating environment.
-The ``floatrow'' package would be of help.
+The ``float'' package would be of help.\footnote{
+ The ``floatrow'' package provides us even more flexible
+ control of floating objects. However, because of an issue
+ in two-column layout, we can not use it at the moment.}
% TODO: Add example
@@ -602,7 +604,7 @@ top. You naturally look at the top of a table at first. Captions at
the bottom of tables disturb this flow.
The same can be said of code snippets, which are read from
top to bottom.
-The floatrow package mentioned above also has the capability
+The float package mentioned above also has the capability
to adjust layout of caption.
% TODO: Add example
@@ -617,13 +619,11 @@ as the default for the environment.
To prevent a pair of closely related figures or listings
from being placed in different pages, it is desirable to group
them into a single floating environment.
-The floatrow package provides the features to do so.\footnote{
+The ``subfig'' package provides the features to do so.\footnote{
Note that the ``subfigure'' package currently declared in the
- preamble is not used any more.
- The floatrow package is the choice to group floating environments
- these days.
- One problem of grouping figures might be the learning curve
- to do so.}
+ preamble is obsoleted by subfig package.
+ One problem of grouping figures might be the complexity in
+ \LaTeX\ source.}
% TODO: Add example
--
2.7.4
--
To unsubscribe from this list: send the line "unsubscribe perfbook" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
