Some URLs updated or added.

Attempt to format error messages as `raw` instead of `latex` code.

Author: jejust

CHANGELOG.md

@@ -19,6 +19,7 @@ Changelog](https://keepachangelog.com/en/1.0.0/).
 
 ### Changed
 
+- Q-erroradvice: Added link.
 - Q-spell: Removed information about VMS and MS-DOS programs. Added `Antidote` as a LaTeX-aware spell checker.
 - Q-recovertex: Links added.
 - Q-time.md: Added `datetime2`.

FAQ-RCS.md

@@ -5,8 +5,7 @@ permalink: /FAQ-RCS
 redirect_from: /FAQ-rcs
 ---
 
-If you use RCS, CVS, `Subversion`,
-`Bazaar` or `Git` to maintain
+If you use RCS, CVS, `Subversion`, `Bazaar` or `Git` to maintain
 your (La)TeX documents under version control, you may need some
 mechanism for including the version details in your document, in such
 a way that they can be typeset (that is, rather than just hiding them
@@ -69,8 +68,7 @@ documentation to see which suits you best.
 An alternative script-based approach to version control has been taken
 by the [`vc`](https://ctan.org/pkg/vc) bundle, that in certain situations might work more
 reliably than any of the packages mentioned above.  The [`vc`](https://ctan.org/pkg/vc)
-bundle supports `Bazaar`, `Git` and
-`Subversion` usage and works with both LaTeX and
+bundle supports `Bazaar`, `Git` and `Subversion` usage and works with both LaTeX and
 Plain TeX.  Note that [`vc`](https://ctan.org/pkg/vc) is the only option that
 currently claims to support `Bazaar`-controlled repositories.
 

FAQ-errmissitem.md

@@ -5,7 +5,7 @@ permalink: /FAQ-errmissitem
 ---
 
 Sometimes, the error
-```latex
+```raw
 Something's wrong--perhaps a missing \item
 ```
 actually means what it says:
@@ -99,9 +99,8 @@ modification of the above _does_ work:
 ```
 <!-- {% endraw %} -->
 The code above produces a box that's far too wide for the text.  One
-may want to use something that allows 
-[variable size boxes](FAQ-varwidth) in place of the
-`minipage` environment.
+may want to use something that allows [variable size boxes](FAQ-varwidth)
+in place of the `minipage` environment.
 
 Oddly, although the `verbatim` environment wouldn't work
 inside a `\fbox` command argument (see 
@@ -118,6 +117,5 @@ error:
 This is a case where you've simply got to be more subtle; you should
 either write your own macros to replace the insides of LaTeX's
 sectioning macros, or  look for some alternative in the packages
-discussed in 
-"[The style of section headings](FAQ-secthead)".
+discussed in "[The style of section headings](FAQ-secthead)".
 

FAQ-erroradvice.md

@@ -10,17 +10,16 @@ macroprocessors.  Knuth makes light of the problem in the TeXbook,
 suggesting that you acquire the sleuthing skills of a latter-day
 Sherlock Holmes; while this approach has a certain romantic charm to
 it, it's not good for the "production" user of (La)TeX.  This
-answer (derived, in part, from an article by Sebastian Rahtz in
-TUGboat 16(4)) offers some general guidance in dealing with TeX
+answer (derived, in part, from an [article by Sebastian Rahtz](http://tug.org/TUGboat/tb16-4/tb49rahtz.pdf)
+in TUGboat 16(4)) offers some general guidance in dealing with TeX
 error reports, and other answers in this section deal with common (but
 perplexing) errors that you may encounter.  There's a long list of
 "hints" in Sebastian's article, including the following:
-  
+
 
 -  Look at TeX errors; those messages may seem cryptic at first,
     but they often contain a straightforward clue to the problem.  See
-    [the structure of errors](FAQ-errstruct) for further
-    details. 
+    [the structure of errors](FAQ-errstruct) for further details.
 -  Read the `log` file; it contains hints to things you may
     not understand, often things that have not even presented as error
     messages.
@@ -40,16 +39,15 @@ perplexing) errors that you may encounter.  There's a long list of
 -  As a last resort, tracing can be a useful tool; reading a full
     (La)TeX trace takes a strong constitution, but once you know how,
     the trace can lead you quickly to the source of a problem.  You need
-    to have read the TeXbook (see
-    [books about TeX](FAQ-tex-books)) in some detail, fully
-    to understand the trace.
-  
+    to have read the TeXbook (see [books about TeX](FAQ-tex-books))
+    in some detail, fully to understand the trace.
+
 
     The command `\tracingall` sets up maximum tracing; it also sets
     the output to come to the interactive terminal, which is somewhat of
     a mixed blessing (since the output tends to be so vast — all but
     the simplest traces are best examined in a text editor after the event).
-  
+
 
     The LaTeX [`trace`](https://ctan.org/pkg/trace) package (first distributed with the
     2001 release of LaTeX) provides more manageable tracing.  Its
@@ -65,7 +63,6 @@ most of the common errors are plain to the eye when you go back to the
 source line that TeX tells you of.  If that approach doesn't work,
 the remaining answers in this section deal with some of the odder
 error messages you may encounter.  You should not ordinarily need to
-appeal to the [wider public](FAQ-gethelp)
-for assistance, but if you do, be sure to
-report full backtraces (see `errorcontextlines` above) and so on.
+appeal to the [wider public](FAQ-gethelp) for assistance, but if you do,
+be sure to report full backtraces (see `errorcontextlines` above) and so on.
 

FAQ-errstruct.md

@@ -37,7 +37,7 @@ is after all the arguments have been scanned.)  For example:
 \blah and so on
 ```
 produces the error report
-```latex
+```raw
 ! Undefined control sequence.
 l.4 \blah
           and so on
@@ -48,7 +48,7 @@ while:
 \blah{to you}, folks
 ```
 produces the error report
-```latex
+```raw
 ! Undefined control sequence.
 \blah #1->\bleah 
                  #1
@@ -61,7 +61,7 @@ If the argument itself is in error, we will see things such as
 \blah{\bleah}, folks
 ```
 producing
-```latex
+```raw
 ! Undefined control sequence.
 <argument> \bleah 
                   
@@ -70,7 +70,7 @@ l.5 \blah{\bleah}
 ```
 
 The prompt accepts single-character commands: the list of what's
-available may be had by typing `?`.  One immediately valuable
+available may be obtained by typing `?`.  One immediately valuable
 command is `h`, which gives you an expansion of TeXs original
 précis message, sometimes accompanied by a hint on what to do to
 work round the problem in the short term.  If you simply type "return"

FAQ-tmupfl.md

@@ -6,7 +6,7 @@ permalink: /FAQ-tmupfl
 
 If LaTeX responds to a `\begin{figure}` or
 `\begin{table}` command with the error message
-```latex
+```raw
 ! LaTeX Error: Too many unprocessed floats.
 
 See the LaTeX manual or LaTeX Companion for explanation.

FAQ-verbwithin.md

@@ -24,11 +24,11 @@ which simply regurgitates its argument, and use it as:
 ```latex
 \unbrace{\verb+\error+}
 ```
-the combinartion will not (it will attempt to execute `\error`).
+the combination will not (it will attempt to execute `\error`).
 Other errors one
 may encounter are "`\verb` ended by end of line", or even the
 rather more helpful "`\verb` illegal in command argument".  The
-same sorts of thing happen with `\begin{verbatim}` …
+same sort of thing happen with `\begin{verbatim}` …
 `\end{verbatim}`:
 <!-- {% raw %} -->
 ```latex
@@ -50,15 +50,13 @@ matching `\end{verbatim}`.
 This is why the LaTeX book insists that verbatim
 commands must not appear in the argument of any other command; they
 aren't just fragile, they're quite unusable in any "normal" command
-parameter, 
-regardless of [`\protect`ion](FAQ-protect).  (The `\verb`
+parameter, regardless of [`\protect`ion](FAQ-protect).  (The `\verb`
 command tries hard to detect if you're misusing it; unfortunately, it
 can't always do so, and the error message is therefore not reliable as an
 indication of problems.)
 
-The first question to ask yourself is: "is `\verb` actually
-necessary?".
-  
+The first question to ask yourself is: "is `\verb` actually necessary?".
+
 
 -  If `\texttt{_your text_}` produces the same result
     as `\verb+_your text_+`, then there's no need of
@@ -99,14 +97,15 @@ Another way out is to use one of "argument types" of the
 \cmd{Command }|\furble|{ isn't defined}
 ```
 Which gives us:
-  Command `\furble` isn't defined
+```raw
+Command `\furble` isn't defined
+```
 The `m` tag argument specifies a normal mandatory argument,
 and the `v` specifies one of these verbatim arguments.
 As you see, it's implanting a `\verb`-style command argument in the
-argument sequence of an otherwise "normal" sort of command; that
-  `|` 
-may be any old character that doesn't
-conflict with the content of the argument.
+argument sequence of an otherwise "normal" sort of command; that `|`
+may be any old character that doesn't conflict with the content of
+the argument.
 
 This is pretty neat (even if the verbatim is in an argument of its
 own) but the downside is that [`xparse`](https://ctan.org/pkg/xparse) pulls in
@@ -115,7 +114,7 @@ the experimental LaTeX3 programming environment
 
 Other than the [`cprotect`](https://ctan.org/pkg/cprotect) package, there are four partial
 solutions to the problem:
-  
+
 
 -  Some packages have macros which are designed to be responsive
     to verbatim text in their arguments.  For example,
@@ -127,15 +126,15 @@ solutions to the problem:
     arguments of other commands, but it can clash with other packages:
     for example, `\VerbatimFootnotes` interacts poorly with the
     `para` option of the [`footmisc`](https://ctan.org/pkg/footmisc) package.
-  
+
 
     The [`memoir`](https://ctan.org/pkg/memoir) class defines its `\footnote` command so that
     it will accept verbatim in its arguments, without any supporting package.
 -  The [`fancyvrb`](https://ctan.org/pkg/fancyvrb) package defines a command `\SaveVerb`,
     with a corresponding `\UseVerb` command, that allow you to save
     and then to reuse the content of its argument; for details of this
     extremely powerful facility, see the package documentation.
-  
+
 
     Rather simpler is the [`verbdef`](https://ctan.org/pkg/verbdef) package, whose `\verbdef`
     command defines a (robust) command which expands to the verbatim
@@ -156,13 +155,11 @@ solutions to the problem:
 -  The [`tcolorbox`](https://ctan.org/pkg/tcolorbox) package provides a similar facility
 -  If you have a single character that is giving trouble (in
     its absence you could simply use `\texttt`), consider using
-    `\string`.  `\texttt{my`\string`_name}`
-    typesets the same as 
+    `\string`.  `\texttt{my`\string`_name}` typesets the same as 
     `\verb+my_name+`, and will work in the argument of a command.  It
     won't, however, work in a moving argument, and no amount of
-    [`\protect`ion](FAQ-protect) will make it work in
-    such a case.
-  
+    [`\protect`ion](FAQ-protect) will make it work in such a case.
+
 
     A robust alternative is:
     ```latex
@@ -175,7 +172,7 @@ solutions to the problem:
     troublesome character (though it's plainly not necessary for things
     like percent signs for which (La)TeX already provides
     robust macros).
-  
+
 
 -  One may also consider putting verbatim material in an external
     file; this is somewhat more tedious, but the file may be reused
@@ -188,7 +185,7 @@ solutions to the problem:
     ```
     which (as one might guess) writes to the named file; load the saved
     contents using `\input{<file name>}`
-  
+
 
     A second environment puts your verbatim material in an (apparently)
     anonymous temporary file:
@@ -200,14 +197,14 @@ solutions to the problem:
     In this case, you use the anonymous file with the `\tcbusetemp`
     macro.  (You can change the name used for the "anonymous" file, if
     its default proves troublesome.)
-  
+
 
     The [`moreverb`](https://ctan.org/pkg/moreverb) package provides a `\verbatimwrite`
     command, which doesn't provide an anonynous file.
-  
+
 
     Macros, to achieve the same effect, are outlined in the
-    documentation of the [`verbatim`](https://ctan.org/pkg/verbatim) package; the macros use the
-    facilities of the package, but the user has to write a mini-package
-    actually to use them.
+    documentation of the [`verbatim`](https://ctan.org/pkg/verbatim) package;
+    the macros use the facilities of the package, but the user has to write
+    a mini-package actually to use them.
 

FAQ-webpkgs.md

@@ -14,7 +14,7 @@ outlining the programming techniques, may be had from CTAN.
 `CWEB`, by Silvio Levy, is a WEB for C programs.
 
 `FWEB`, by John Krommes, is a version for Fortran,
-Ratfor,C, C++, working with LaTeX; it was derived
+Ratfor, C, C++, working with LaTeX; it was derived
 from `CWEB`.
 
 Spidery WEB, by Norman Ramsey, supports many 

FAQ-whereFAQ.md

@@ -15,7 +15,7 @@ The sources of the present FAQ are available from CTAN.
 
 This FAQ and others are regularly mentioned, on `comp.text.tex` and elsewhere,
 in a "pointer FAQ" which is also saved at
-[https://tug.org/tex-ptr-faq](https://tug.org/tex-ptr-faq).
+[http://tug.org/interest.html](http://tug.org/interest.html#doc).
 
 A 2006 innovation from Scott Pakin is the "visual" LaTeX FAQ.
 This is a document with (mostly rubbish) text formatted so as to
@@ -36,17 +36,18 @@ user group CS-TUG have published translations of this FAQ in the past,
 with extensions appropriate to their languages.
 
 The French FAQ is currently hosted on an open wiki at
-[https://faq.gutenberg.eu.org/](https://faq.gutenberg.eu.org/)
+[https://faq.gutenberg.eu.org](https://faq.gutenberg.eu.org/)
 and is [actively updated](https://www.gutenberg.eu.org/faq).
 Its contributors have gathered material from the French historical FAQ
-from `fr.comp.text.tex` and from this FAQ. Feel free to contribute! 
+from `fr.comp.text.tex` and from [this FAQ](http://faq.tug.org/).
+Feel free to contribute!
 
 
 Other non-English FAQs are available (off-CTAN):
 
 - German: Posted regularly to `de.comp.tex`, and [archived on CTAN](https://www.ctan.org/pkg/faq-de);
   another version is maintained on a wiki:
-  [https://texfragen.de/]([https://texfragen.de/);
+  [https://texfragen.de](https://texfragen.de/);
 - Italian: See [https://www.guitex.org/home/it/faq](https://www.guitex.org/home/it/faq);
 - Spanish: A FAQ is [published by CervanTeX](http://www.aq.upm.es/Departamentos/Fisica/agmartin/webpublico/latex/FAQ-CervanTeX/FAQ-CervanTeX.html),
   the Spanish TeX user group.