Merge pull request #31 from jejust/main

Corrections and updates found during translation to French.

Author: josephwright

AUTHORS.md

@@ -47,6 +47,7 @@ The following people are _known_ to have contributed to the FAQ:
 - David Jansen
 - Alan Jeffrey
 - Regnor Jernsletten
+- Jérémy Just
 - David Kastrup
 - Oleg Katsitadze
 - Isaac Khabaza

CHANGELOG.md

@@ -7,9 +7,32 @@ file. Changes prior to the switch to Markdown format are available from
 The format is based on [Keep a
 Changelog](https://keepachangelog.com/en/1.0.0/).
 
+## 2021-04-18
+
+### Added
+
+- Q-prevlig: New question.
+
+### Renammed
+
+- Q-texcad to Q-texdraw: Added other drawing packages.
+
+### 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`.
+- Q-typo-style: Added two documents.
+- Q-uploads: Added details about version identifiers.
+- Q-useMF: Correction of typos.
+- Q-whereFAQ: Correction of links.
+- Q-xspace: Correction of punctuation.
+
 ## 2021-04-01
 
 ### Added
+
 - Q-arraytab: New question
 - Q-rule: New question
 

FAQ-2colfloat.md

@@ -8,30 +8,29 @@ permalink: /FAQ-2colfloat
 date: 2018-05-18
 ---
 
-You specified placement `[htbp]` for your full-width figure or
-table, but they always get placed at the top of the page…  Well,
+You specified placement `[htbp]` for your full-width figure or table,
+but they always get placed at the top of the page…  Well,
 it _is_ what the documentation says: LaTeX, unadorned, only
 allows full-width floats at the top of a page, or occupying (part of) a
 float page.
 
 The package [`nidanfloat`](https://ctan.org/pkg/nidanfloat) supports `[b]` placement of a
-full-width figure in a two-column document even on the first page of a
-document.
+full-width figure in a two-column document even on the first page of a document.
 
 Barbara Beeton's article
 [Placing a full-width insert at the bottom of two columns](https://tug.org/TUGboat/tb35-3/tb111beet-banner.pdf) in TUGboat 35(3)
 gives a manual method for doing the same.
 
-The [`stfloats`](https://ctan.org/pkg/stfloats) package also ameliorates the situation somewhat, and
-makes LaTeX honour "[b]" placement as well.
+The [`stfloats`](https://ctan.org/pkg/stfloats) package also ameliorates
+the situation somewhat, and makes LaTeX honour "[b]" placement as well.
 
-A particular problem with [`stfloats`](https://ctan.org/pkg/stfloats) and [`dblfloatfix`](https://ctan.org/pkg/dblfloatfix)
-is that the float will appear, at its earliest, on the page after it
-is specified.  This has two undesirable side-effects: first, there may
-be no bottom float on the first page of a document, and second, float
-numbers may become "entangled" (particularly if you're using
-[`dblfloatfix`](https://ctan.org/pkg/dblfloatfix) that ensures that the early-specified bottom
-float is set _before_ any single column floats).
+A particular problem with [`stfloats`](https://ctan.org/pkg/stfloats) and
+[`dblfloatfix`](https://ctan.org/pkg/dblfloatfix) is that the float will appear,
+at its earliest, on the page after it is specified.  This has two undesirable
+side-effects: first, there may be no bottom float on the first page of a
+document, and second, float numbers may become "entangled" (particularly
+if you're using [`dblfloatfix`](https://ctan.org/pkg/dblfloatfix) that ensures
+that the early-specified bottom float is set _before_ any single column floats).
 
 (The FAQ team doesn't know of any package that will make
 LaTeX honour "[h]" placement of double-column floats, but the
@@ -40,7 +39,8 @@ something approximating the effect it would have.)
 
 Prior to the LaTeX2e 2015 release, double and single column floats were maintained
 in separate lists and could be output in the wrong order. For these older releases
-[`dblfloatfix`](https://ctan.org/pkg/dblfloatfix) package combines a tidied version of the changes
-made in [`stfloats`](https://ctan.org/pkg/stfloats) with the
-  [float ordering corrections](FAQ-2colfltorder) defined in
-  [`fixltx2e`](https://ctan.org/pkg/fixltx2e).
+[`dblfloatfix`](https://ctan.org/pkg/dblfloatfix) package combines a tidied version
+of the changes made in [`stfloats`](https://ctan.org/pkg/stfloats) with the
+[float ordering corrections](FAQ-2colfltorder) defined in
+[`fixltx2e`](https://ctan.org/pkg/fixltx2e).
+

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-hyphen.md

@@ -49,8 +49,7 @@ hyphenation: `\language` (which selects a hyphenation style), and
 engine, overriding the effect of the patterns).
 
 The ordinary LaTeX user need not worry about `\language`, since
-it is very thoroughly managed by the [`babel`](https://ctan.org/pkg/babel) package; use of
-`\hyphenation` is discussed in
-  the context of
+it is very thoroughly managed by the [`babel`](https://ctan.org/pkg/babel)
+package; use of `\hyphenation` is discussed in the context of
 [hyphenation failure](FAQ-nohyph).
 

FAQ-letterspace.md

@@ -20,15 +20,15 @@ text is less awful a crime; the technique used also to be used for
 emphasis of text set in Fraktur (or similar) fonts.
 
 Straightforward macros (usable, in principle, with any TeX macro
-package) may be found in [`letterspacing`](https://ctan.org/pkg/letterspacing) (which is the name of
-the `tex` file).
+package) may be found in [`letterspacing`](https://ctan.org/pkg/letterspacing)
+(which is the name of the `tex` file).
 
 A more comprehensive solution is to be found in the [`soul`](https://ctan.org/pkg/soul)
 package (which is optimised for use with LaTeX, but also works with
 Plain TeX).  Soul also permits hyphenation of letterspaced text;
 Gill's view of such an activity is not (even apocryphally) recorded.
-(Spacing-out forms part of the name of [`soul`](https://ctan.org/pkg/soul); the other half
-is described in [another question](FAQ-underline).)
+(Spacing-out forms part of the name of [`soul`](https://ctan.org/pkg/soul);
+the other half is described in [another question](FAQ-underline).)
 
 Possibly the "ultimate" in this field is the [`microtype`](https://ctan.org/pkg/microtype),
 which uses the micro-typography capabilities of current pdfTeX to
@@ -37,7 +37,6 @@ declared in a `\SetTracking` command.  [`Microtype`](https://ctan.org/pkg/Microt
 "tracking" facility expands the natural spacing of the font itself,
 rather than inserting space between characters.  Ordinarily,
 letter-spacing will destroy ligatures; however, this is _wrong_
-for some font styles (for example, `fraktur`), and the
-package provides a means of protecting the ligatures in a
-letter-spaced text.
+for some font styles (for example, `fraktur`), and the package provides
+a means of protecting the ligatures in a letter-spaced text.
 

FAQ-parmoderr.md

@@ -14,10 +14,10 @@ For example:
 ```
 The error comes when you try to build something movable inside a box.
 Movable things, in this context, are floating environments
-(`figure` and `table`, for example), and
-`\marginpar`s.  LaTeX simply doesn't have the mechanisms for
-floating out of boxes.  In fact, floats and `\marginpar`s
-themselves are built out of boxes, so that they can't be nested.
+(`figure` and `table`, for example), and `\marginpar`s.  LaTeX simply
+doesn't have the mechanisms for floating out of boxes.  In fact, floats
+and `\marginpar`s themselves are built out of boxes, so that they
+can't be nested.
 
 If your error arises from `\marginpar`, you simply have to think of
 an alternative way of placing the command; there is no slick solution.
@@ -37,8 +37,8 @@ the `H` placement option, provided (for example) by the
 <!-- {% endraw %} -->
 This example makes little sense as it stands; however, it is
 conceivable that sane uses could be found (for example, using a
-package such as [`algorithm2e`](https://ctan.org/pkg/algorithm2e) to place two algorithms
-side-by-side).
+package such as [`algorithm2e`](https://ctan.org/pkg/algorithm2e) to place
+two algorithms side-by-side).
 
 
 Another common occurrence is when the user wants a figure somewhere
@@ -64,8 +64,7 @@ The problem is, that the `tabular` environment, and the
 `\framebox` command restrain the `figure` environment
 from its natural métier, which is to float around the document.
 
-The solution is simply not to use the `figure` environment
-here:
+The solution is simply not to use the `figure` environment here:
 ```latex
 \begin{tabular}{|l|}
   \hline
@@ -78,8 +77,7 @@ serves no useful purpose; but perhaps you actually wanted a diagram
 and its caption framed, in a float.
 
 It's simple to achieve this&nbsp;&mdash; just reverse the order of the
-environments (or of the `figure` environment and the
-command):
+environments (or of the `figure` environment and the command):
 ```latex
 \begin{figure}
   \begin{tabular}{|l|}

FAQ-prevlig.md

@@ -0,0 +1,71 @@
+---
+title: Preventing a ligature
+category: formatting
+permalink: /FAQ-prevlig
+date: 2021-04-18
+---
+
+This is a strength of TeX: some pairs of letters are automatically replaced
+by a single glyph, for aesthetic reasons, as is done in letterpress.  For example,
+when an `f` and an `i` are placed next to each other, the hood of the `f` would
+normally tend collide with the tittle of the `i`, which wouldn't look very nice.
+TeX therefore replaces them with a new, prettier glyph: fi.
+This merging of glyphs is called a ligature.
+
+The same mechanism is used to obtain the Spanish characters ¡ and ¿, which are
+typed in as `` !` `` and `` ?` ``.
+
+In Cyrillic fonts used with OT2 encoding, the letter pair `sh` will produce the
+glyph ш (the _sha_ letter).
+
+But in some cases, one may want to prevent ligatures from occurring.
+
+
+To prevent a single ligature, just separate the letters in the (La)TeX code
+with something that will produce nothing in the output file. For example:
+`\/`, `{}`, `\mbox{}`, `\null`.  The T1 and OT1 font encodings also provide
+the `\textcompwordmark` command, which has the same purpose.
+
+```latex
+% With the automatic ligature:
+offence
+
+% Without it:
+of\/fence
+of{}fence
+of\null fence
+of\mbox{}fence
+of\textcompwordmark fence
+```
+
+Note that, in some cases, `{}` seems to have no effect, and the ligature
+occurs in spite of it.  This is apparently a side effect of some packages, such
+as [`multicol`](https://ctan.org/pkg/multicol).  The other solutions may
+therefore be preferred.
+In all cases, [hyphenation](FAQ-hyphen) of the word is no longer performed
+automatically by TeX, and you have to [take care of it manually](FAQ-hyphexcept),
+if needed.
+
+
+The same solution prevents kerning between consecutive characters.
+Compare for example the rendering of `AV` and `A\/V`.
+
+
+In case you want to prevent ligature in you whole document,
+have a look at [`fontspec`](https://ctan.org/pkg/fontspec) options.
+It can disable all aesthetic ligatures, or disable them on a type by type basis:
+
+```latex
+\usepackage{fontspec}
+ 
+\defaultfontfeatures{
+  Ligatures={
+    NoCommon,
+    NoRequired,
+    NoContextual,
+    NoHistoric,
+    NoDiscretionary
+  }
+}
+```
+