Différences
Ci-dessous, les différences entre deux révisions de la page.
Les deux révisions précédentesRévision précédenteProchaine révision | Révision précédente | ||
composition:texte:lignes:arguments_incorrects_pour_newline [2018/05/25 08:57] – joseph.wright | 3_composition:texte:lignes:arguments_incorrects_pour_newline [2022/11/29 15:52] (Version actuelle) – Usage de ⟨...⟩ dbitouze | ||
---|---|---|---|
Ligne 1: | Ligne 1: | ||
- | --- | + | ====== Pourquoi cette ligne commence-t-elle mal? ====== |
- | section: Why does it _do_ that? | + | |
- | subsection: Common errors | + | |
- | permalink: / | + | |
- | date: 2014-06-10 | + | |
- | --- | + | |
- | # Start of line goes awry | + | Cette réponse concerne deux types de problèmes : |
+ | * ceux où un astérisque au début d'une ligne ne parvient mystérieusement pas à apparaître dans le document final ; | ||
+ | * ceux générant une erreur de la forme : | ||
- | This answer concerns two sorts of problems: errors of the form | + | <code text> |
- | ```latex | + | |
! Missing number, treated as zero. | ! Missing number, treated as zero. | ||
<to be read again> | <to be read again> | ||
p | p | ||
<*> [perhaps] | <*> [perhaps] | ||
- | ``` | + | </ |
- | and errors where a single asterisk at the start of a line mysteriously | + | |
- | fails to appear in the typeset output. | + | |
- | Both problems arise because ` ` takes optional | + | Les deux problèmes surviennent car la commande '' |
- | command ` *` means '' | + | * la commande |
- | following the line break'' | + | * la commande |
- | means '' | + | |
- | afterwards'' | + | |
- | The problem arises because ` ` looks for the next | + | Et ces problèmes arrivent parce que la commande '' |
- | non-blank thing; the test it uses ignores the end of the line in | + | |
- | your input text, so that ` ` comes to imagine that you | + | |
- | were giving it a '' | + | |
- | An obvious solution is to enclose the stuff at the start of the new | + | ===== Dans le texte ===== |
- | line in braces, typing: | + | |
- | <!-- {% raw %} --> | + | Une solution évidente est de mettre l' |
- | ```latex | + | |
+ | < | ||
{\ttfamily | {\ttfamily | ||
- | /* C-language comment\\ | + | /* Commentaire en langage |
- | {[perhaps]} this could be done better\\ | + | {[Important]} à traiter\\ |
{*}/ | {*}/ | ||
} | } | ||
- | ``` | + | </code> |
- | <!-- {% endraw %} --> | + | |
- | This particular example could be coded (without any problems) in | + | |
- | verbatim, but the behaviour does confuse people. | + | |
- | The problem also appears in maths mode, in arrays and so on. In this | + | Cet exemple particulier pourrait être codé (sans aucun problème) en mode verbatim, mais ce mode déroute souvent les utilisateurs. |
- | case, large-scale bracketing of things is _not_ a good idea; the | + | |
- | TeX primitive | + | ===== Dans les mathématiques ===== |
- | searches of this nature) | + | |
- | `comp.text.tex` example: | + | Ce problème apparaît également en mode mathématique, |
- | ```latex | + | |
+ | < | ||
\begin{eqnarray} | \begin{eqnarray} | ||
- | [a] &=& b \\ | + | [a] |
\relax[a] &=& b | \relax[a] &=& b | ||
\end{eqnarray} | \end{eqnarray} | ||
- | ``` | + | </ |
- | which is a usage this FAQ would not recommend, anyway: refer | + | |
- | to the [reason not to use `eqnarray`](FAQ-eqnarray.md). | + | Cet exemple n'est toutefois pas recommandé par cette FAQ, comme indiqué à la question « [[4_domaines_specialises:mathematiques: |
+ | |||
+ | Notez que l' | ||
+ | |||
+ | ----- | ||
- | Note that the [`amsmath`](https: | + | //Source:// [[faquk> |
- | ` ` in maths. | + | |
- | `eqnarray` example doesn' | + | |
- | (`\relax` or braces). | + | |
+ | {{htmlmetatags> | ||
+ | metatag-og: | ||
+ | metatag-og: | ||
+ | }} | ||