482
edits
(Page creation) |
(Traduction partielle) |
||
| Line 1: | Line 1: | ||
<small>Version traduite le 14 novembre 2022</small> {{pending}} {{progressbar| | <small>Version traduite le 14 novembre 2022</small> {{pending}} {{progressbar|10}} | ||
{{BeingTranslated}} | {{BeingTranslated}} | ||
| Line 6: | Line 6: | ||
{{shortcut|FGW:MOS}} | {{shortcut|FGW:MOS}} | ||
Le '''manuel de style''' est un guide pour tous les articles du wiki FlightGear. Il aide les éditeurs à rédiger des articles avec un langage clairs et précis, une mise en page et un formatage homogènes. Le but est de rendre l'utilisation de ce wiki plus facile et plus intuitive. Un langage, un style et une mise en forme homogènes favorisent la clarté et la cohésion. La rédaction doit être claire et concise. Le style direct et simple fonctionne mieux; évitez l'ambiguïté, le jargon et les formulations vagues ou inutilement complexes. | |||
Débattez des problèmes de style sur [[FlightGear wiki talk:Manual of Style|la page de discussion]]. | |||
== | == Titres, en-têtes et sections des articles == | ||
=== | === Titres des articles === | ||
* Use sentence case, not title case. The initial letter of a title is capitalized (except in rare cases, such as eBay), but otherwise, capital letters are used only where they would be used in a normal sentence ({{xt|List of developed airports}}, not {{!xt|List of Developed Airports}}). Also, keep in mind that the wiki software automatically capitalizes the initial letter of a namespace/page title in its address. | * Use sentence case, not title case. The initial letter of a title is capitalized (except in rare cases, such as eBay), but otherwise, capital letters are used only where they would be used in a normal sentence ({{xt|List of developed airports}}, not {{!xt|List of Developed Airports}}). Also, keep in mind that the wiki software automatically capitalizes the initial letter of a namespace/page title in its address. | ||
* Titles should be precise enough to unambiguously define the topical scope of the article ({{xt|Boeing 747}}, not {{!xt|747}}). | * Titles should be precise enough to unambiguously define the topical scope of the article ({{xt|Boeing 747}}, not {{!xt|747}}). | ||
* The characters <code># < > [ ] | { }</code> are reserved by the wiki software and can not be used. | * The characters <code># < > [ ] | { }</code> are reserved by the wiki software and can not be used. | ||
=== | === Organisation des sections === | ||
An article should begin with an introductory lead section, which should not contain section headings. The remainder may be divided into sections, each with a section heading (see below) that can be nested in a hierarchy. If there are at least four section headings in the article, a navigable table of contents is generated automatically and displayed between the lead and the first heading. | An article should begin with an introductory lead section, which should not contain section headings. The remainder may be divided into sections, each with a section heading (see below) that can be nested in a hierarchy. If there are at least four section headings in the article, a navigable table of contents is generated automatically and displayed between the lead and the first heading. | ||
=== | === Titres de section === | ||
Equal signs are used to mark the enclosed text as a section heading: <code>== Title ==</code> for a primary section; <code>=== Title ===</code> for the next level (a subsection); and so on to the lowest-level subsection, with <code>===== Title =====</code>. (The highest heading level technically possible is <code>= Title =</code>; but do not use it in articles, because it is reserved for the automatically generated top-level heading at the top of the page containing the title of the whole article.) Spaces between the equal signs and the heading text are optional, and will not affect the way the heading is displayed. The heading must be typed on a separate line. Include one blank line above the heading, and optionally one blank line below it, for readability in the edit window (but not two or more consecutive blank lines, which will add unnecessary visible white space in the rendered page.) | Equal signs are used to mark the enclosed text as a section heading: <code>== Title ==</code> for a primary section; <code>=== Title ===</code> for the next level (a subsection); and so on to the lowest-level subsection, with <code>===== Title =====</code>. (The highest heading level technically possible is <code>= Title =</code>; but do not use it in articles, because it is reserved for the automatically generated top-level heading at the top of the page containing the title of the whole article.) Spaces between the equal signs and the heading text are optional, and will not affect the way the heading is displayed. The heading must be typed on a separate line. Include one blank line above the heading, and optionally one blank line below it, for readability in the edit window (but not two or more consecutive blank lines, which will add unnecessary visible white space in the rendered page.) | ||
| Line 28: | Line 28: | ||
* Headings should not contain images. | * Headings should not contain images. | ||
== | == Les majuscules == | ||
Sentence case rather than title case is used in wiki article titles and section headings; see [[#Article titles|Article titles]] and [[#Section headings|Section headings]] above. For capitalization of list items, see [[#Bulleted and numbered lists|Bulleted and numbered lists]]. Other points concerning capitalization are summarized below. | Sentence case rather than title case is used in wiki article titles and section headings; see [[#Article titles|Article titles]] and [[#Section headings|Section headings]] above. For capitalization of list items, see [[#Bulleted and numbered lists|Bulleted and numbered lists]]. Other points concerning capitalization are summarized below. | ||
=== | ===N'utilisez pas de majuscules pour accentuer=== | ||
Use italics, not capitals, to denote emphasis. | Use italics, not capitals, to denote emphasis. | ||
:''Incorrect'': {{!xt|It is not only a LITTLE learning that is dangerous}}. | :''Incorrect'': {{!xt|It is not only a LITTLE learning that is dangerous}}. | ||
:''Correct'': {{xt|It is not only a ''little'' learning that is dangerous}}. | :''Correct'': {{xt|It is not only a ''little'' learning that is dangerous}}. | ||
=== | ===Objets de calendrier=== | ||
* '''Months, days of the week, and holidays''' start with a capital letter ({{xt|June}}, {{xt|Monday}}). | * '''Months, days of the week, and holidays''' start with a capital letter ({{xt|June}}, {{xt|Monday}}). | ||
=== | ===Corps célestes=== | ||
* When used generally, the words '''<nowiki />''sun'', ''earth'', and ''moon''<nowiki />''' do not take capitals ({{xt|The sun was peeking over the mountain top}}), except when the term names a specific astronomical body ({{xt|The Moon orbits the Earth}}). | * When used generally, the words '''<nowiki/>''sun'', ''earth'', and ''moon''<nowiki/>''' do not take capitals ({{xt|The sun was peeking over the mountain top}}), except when the term names a specific astronomical body ({{xt|The Moon orbits the Earth}}). | ||
=== | ===Points cardinaux=== | ||
Do not capitalize '''directions''' such as ''north'', nor their related forms ({{xt|Follow the northern road}}), except where they are parts of proper names (such as {{xt|South Pole}}). | Do not capitalize '''directions''' such as ''north'', nor their related forms ({{xt|Follow the northern road}}), except where they are parts of proper names (such as {{xt|South Pole}}). | ||
| Line 49: | Line 49: | ||
(Composite directions may or may not be hyphenated, depending on the style adopted in the article. {{xt|Southeast Asia}} and {{xt|northwest}} are more common in American English; but {{xt|South-East Asia}} and {{xt|north-west}} in British English. In cases such as {{xt|north–south dialogue}} and {{xt|east–west orientation}} an en dash is used.) | (Composite directions may or may not be hyphenated, depending on the style adopted in the article. {{xt|Southeast Asia}} and {{xt|northwest}} are more common in American English; but {{xt|South-East Asia}} and {{xt|north-west}} in British English. In cases such as {{xt|north–south dialogue}} and {{xt|east–west orientation}} an en dash is used.) | ||
== | == Abréviations == | ||
=== Write out both the full version and the abbreviation at first occurrence === | === Write out both the full version and the abbreviation at first occurrence === | ||
* When an abbreviation is to be used in an article, give the expression in full at first, followed immediately by the abbreviation in parentheses (round brackets). In the rest of the article the abbreviation can then be used by itself: | * When an abbreviation is to be used in an article, give the expression in full at first, followed immediately by the abbreviation in parentheses (round brackets). In the rest of the article the abbreviation can then be used by itself: | ||
edits