Fr/FlightGear wiki:Manual of Style: Difference between revisions

Jump to navigation Jump to search

Fr/FlightGear wiki:Manual of Style (view source)

Revision as of 20:50, 21 November 2022

278 bytes added ,  21 November 2022
Traduction partielle
(Traduction partielle)
(Traduction partielle)
Line 1: Line 1:
<small>Version traduite le 21 novembre 2022</small> {{pending}} {{progressbar|20}}
<small>Version traduite le 21 novembre 2022</small> {{pending}} {{progressbar|30}}


{{BeingTranslated}}
{{BeingTranslated}}
Line 49: Line 49:
Mettez une majuscule aux '''noms de régions''' s'ils ont atteint le statut de nom propre, y compris les noms conventionnels informels ({{Xt|Californie du Sud}} ou {{Xt|Sahara Occidental}}). Ne mettez pas de majuscules dans les noms descriptifs des régions qui n'ont pas atteint le statut de noms propres, comme le {{Xt|sud de la Pologne}}.
Mettez une majuscule aux '''noms de régions''' s'ils ont atteint le statut de nom propre, y compris les noms conventionnels informels ({{Xt|Californie du Sud}} ou {{Xt|Sahara Occidental}}). Ne mettez pas de majuscules dans les noms descriptifs des régions qui n'ont pas atteint le statut de noms propres, comme le {{Xt|sud de la Pologne}}.


(Les directions composites peuvent ou non comporter un trait d'union, selon le style adopté dans l'article. L'{{Xt|Asie du Sud-Est}} et le {{Xt|nord-ouest}} sont plus courants en franàais que l'Asie du Sud Est ou le nord ouest. Dans les cas tels que {{Xt|dialogue nord-sud|title=}} et {{Xt|orientation est-ouest}}, un tiret demi-cadratin est utilisé).
(Les directions composites peuvent ou non comporter un trait d'union, selon le style adopté dans l'article. L'{{Xt|Asie du Sud-Est}} et le {{Xt|nord-ouest}} sont plus courants en français que l'Asie du Sud Est ou le nord ouest. Dans les cas tels que {{Xt|dialogue nord-sud|title=}} et {{Xt|orientation est-ouest}}, un tiret demi-cadratin est utilisé).


== Abréviations ==
== Abréviations ==
=== Écrivez à la fois la version complète et l'abréviation à la première occurrence ===
=== Écrivez à la fois la version complète et l'abréviation à la première occurrence ===
* Lorsqu'une abréviation doit être utilisée dans un article, donner d'abord l'expression en entier, suivie immédiatement de l'abréviation entre parenthèses (parenthèses rondes). Dans la suite de l'article l'abréviation peut alors être réemployée seule :
* Lorsqu'une abréviation doit être utilisée dans un article, donner d'abord l'expression en entier, suivie immédiatement de l'abréviation entre parenthèses (parenthèses rondes). Dans la suite de l'article l'abréviation peut alors être réemployée seule :
::{{xt|L'instrument landing system (ILS) est un système d'approche aux instruments au sol.}}, à la première mention du système d'atterrissage aux instruments ; et {{xt|Il existe trois catégories d'ILS}}, lors d'une mention ultérieure.
<blockquote>{{xt|L'instrument landing system (ILS) est un système d'approche aux instruments au sol.}}, à la première mention du système d'atterrissage aux instruments ;
 
et {{xt|Il existe trois catégories d'ILS}}, lors d'une mention ultérieure.</blockquote>
 
* N'appliquez pas de majuscules initiales dans une version complète tout simplement parce que les majuscules sont utilisées dans l'abréviation.
* N'appliquez pas de majuscules initiales dans une version complète tout simplement parce que les majuscules sont utilisées dans l'abréviation.
::{|style="background:transparent"
::{|style="background:transparent"
Line 66: Line 69:
L'esperluette (&) remplace le mot et (c'est une forme du ''et latin''). Dans le texte normal, ''et'' doit être utilisé à la place : ''version 1 et 2'', et non ''version 1 & 2''. Les esperluettes peuvent être utilisées avec cohérence et discrétion dans les tableaux, les infobox et les contextes similaires où l'espace est limité.
L'esperluette (&) remplace le mot et (c'est une forme du ''et latin''). Dans le texte normal, ''et'' doit être utilisé à la place : ''version 1 et 2'', et non ''version 1 & 2''. Les esperluettes peuvent être utilisées avec cohérence et discrétion dans les tableaux, les infobox et les contextes similaires où l'espace est limité.


== Italiques ==
==Italiques==
=== Accentuation ===
===Accentuation===
Italics may be used ''sparingly'' to emphasize words in sentences (whereas boldface is normally not used for this purpose). Generally, the more highlighting in an article, the less its effectiveness.
L'italique peut être utilisé avec parcimonie pour souligner les mots dans les phrases (alors que le gras n'est normalement pas utilisé à cette fin). Généralement, plus un article est mis en avant, moins il est efficace.
 
===Citation en italique===
Les citations doivent toujours être clairement indiqués comme étant des citations. Pour les baliser, utilisez uniquement des guillemets (pour les citations courtes) ou des blocs de citations (pour les longues), et non des italiques. (Voir [[Fr/FlightGear wiki:Manual of Style#Citations|Citations]]) Cela signifie que :


=== <s>Quotations in italics</s> Quotation en italique ===
# une citation n'est pas en italique à l'intérieur de guillemets ou d'un bloc de citation simplement parce qu'il s'agit d'une citation ;
Quotations must always be clearly indicated as being quotations. For quotations, use only quotation marks (for short quotations) or block quoting (for long ones), not italics. (See [[#Quotations|Quotations]] below.) This means that (1) a quotation is not italicized inside quotation marks or a block quote just because it is a quotation, and (2) italics are no substitute for proper quotation formatting.
# les italiques ne remplacent pas la mise en forme approprié des citations.


== Citations ==
==Citations==
Where the same quotation has been used elsewhere in the article, avoid duplicating it, which is regarded as poor style.
Lorsque la même citation a été employée ailleurs dans l'article, évitez de la dupliquer, ce qui est considéré comme un style médiocre.


The quotation should be representative of the whole source document; editors should be very careful to avoid misrepresentation of the argument in the source. Where a quotation presents rhetorical language in place of more neutral, dispassionate tone preferred for encyclopedias, it can be a backdoor method of inserting a non-neutral treatment of a controversial subject into the wiki's narrative on the subject, and should be avoided.
La citation doit être représentative de l'ensemble du document source ; les éditeurs doivent être très prudents pour éviter une fausse représentation de l'argument dans la source. Lorsqu'une citation présente un langage rhétorique à la place d'un ton plus neutre et impartial préféré pour les encyclopédies, cela peut être une méthode détournée pour insérer un traitement non neutre d'un sujet controversé dans le récit du wiki sur le sujet, et doit être évitée.


Quotations should generally be worked into the article text, so as not to inhibit the pace, flow and organization of the article. Longer quotes may need to be set apart, generally through the use of wikitext templates such as {{tl|Quote}} or {{tl|Quotation}}. Longer quotations may also be hidden in the reference (footnote) to facilitate verification by other editors without sacrificing readability. For pull quotes (quotes of the article text used to highlight a section) the {{tl|Cquote}} template can be used. Quotations used only as sources to support statements contained in the article can be added with a <tt><nowiki><ref></nowiki></tt> tag containing a reference formatted with the {{tl|cite web}} template; in that case, add {{tl|Appendix}} at the end of the page so that citations can be displayed in a uniform way.
Les citations doivent généralement être insérées dans le texte de l'article, afin de ne pas entraver le rythme, la fluidité et l'organisation de l'article. Les citations plus longues peuvent avoir besoin d'être mises à part, généralement grâce à l'utilisation de modèles de texte wiki tels que {{tl|Quote}} ou {{tl|Quotation}}. Des citations plus longues peuvent également être masquées dans la référence (note de bas de page) pour faciliter la vérification par d'autres éditeurs sans sacrifier la lisibilité. Pour les guillemets (citations du texte de l'article utilisées pour mettre en évidence une section), le modèle {{tl|Cquote}} peut être appliqué. Les citations utilisées uniquement comme sources pour soutenir les déclarations contenues dans l'article peuvent être ajoutées avec une balise <nowiki><ref> contenant une référence formatée avec le modèle </nowiki>{{tl|cite web}}. Dans ce cas, ajoutez {{tl|Appendix}} à la fin de la page afin que les citations puissent être affichées de manière uniforme.


=== Texte original ===
===Texte original===
Quotations must be verifiably attributed and the wording of the quoted text should be faithfully reproduced. If there is a significant error in the original statement, use {{xt|[''[[sic]]'']}} to show that the error was not made by the wiki editors. However, trivial spelling and typographic errors should simply be corrected without comment (for example, correct {{!xt|basicly}} to {{xt|basically}}), unless the slip is textually important.
Quotations must be verifiably attributed and the wording of the quoted text should be faithfully reproduced. If there is a significant error in the original statement, use {{xt|[''[[sic]]'']}} to show that the error was not made by the wiki editors. However, trivial spelling and typographic errors should simply be corrected without comment (for example, correct {{!xt|basicly}} to {{xt|basically}}), unless the slip is textually important.


Use [[#Ellipses|ellipses]] to indicate omissions from quoted text. Legitimate omissions include extraneous, irrelevant, or parenthetical words. Do not omit text where doing so would remove important context or alter the meaning of the text.  
Use [[#Ellipses|ellipses]] to indicate omissions from quoted text. Legitimate omissions include extraneous, irrelevant, or parenthetical words. Do not omit text where doing so would remove important context or alter the meaning of the text.  


=== Conformité typographique ===
===Conformité typographique===
In most cases it is not desirable to duplicate the original formatting. Formatting and other purely typographical elements of quoted text should be adapted to the wiki's conventions without comment provided that doing so will not change or obscure the meaning of the text. These are alterations which make no difference when the text is read aloud, such as:
In most cases it is not desirable to duplicate the original formatting. Formatting and other purely typographical elements of quoted text should be adapted to the wiki's conventions without comment provided that doing so will not change or obscure the meaning of the text. These are alterations which make no difference when the text is read aloud, such as:
* Changing capitalization so that sentences begin with capital letters.
*Changing capitalization so that sentences begin with capital letters.
* When quoting a quotation that itself contains a quotation, single quotes may be replaced with double quotes, and vice versa. See [[#Quotations within quotations|Quotations within quotations]] below.
*When quoting a quotation that itself contains a quotation, single quotes may be replaced with double quotes, and vice versa. See [[#Quotations within quotations|Quotations within quotations]] below.
* Removing spaces before punctuation such as periods and colons.
*Removing spaces before punctuation such as periods and colons.
* Generally preserve bold and italics (see [[#Italics|Italics]], above), but most other styling should be altered.
*Generally preserve bold and italics (see [[#Italics|Italics]], above), but most other styling should be altered.
* Expanding abbreviations.
*Expanding abbreviations.


=== Citations dans les citations ===
===Citations dans les citations===
For quotations within quotations, use double quote marks outermost and, working inward, alternate single with double quote marks.
For quotations within quotations, use double quote marks outermost and, working inward, alternate single with double quote marks.


=== Attribution ===
===Attribution===
The author of a quote of a full sentence or more should be named; this is done in the main text and not in a footnote. A reader should not have to follow a footnote to learn whose words a quote is.
The author of a quote of a full sentence or more should be named; this is done in the main text and not in a footnote. A reader should not have to follow a footnote to learn whose words a quote is.


=== Liens ===
===Liens===
As much as possible, avoid linking from within quotes, which may clutter the quotation, violate the principle of leaving quotations unchanged, and mislead or confuse the reader.
As much as possible, avoid linking from within quotes, which may clutter the quotation, violate the principle of leaving quotations unchanged, and mislead or confuse the reader.


=== Citations en bloc ===
===Citations en bloc===
Format a long quote (more than about 40 words or a few hundred characters, or consisting of more than one paragraph, regardless of length) as a block quotation, which the wiki's software will indent from both margins. Do not enclose block quotations in quotation marks (and especially avoid decorative quotation marks in normal use, such as those provided by the {{tl|cquote}} template, which are reserved for pull quotes; quoted sections from elsewhere in the same wiki article). Block quotations can be added with {{tl|quote}} or {{tl|quotation}}.
Format a long quote (more than about 40 words or a few hundred characters, or consisting of more than one paragraph, regardless of length) as a block quotation, which the wiki's software will indent from both margins. Do not enclose block quotations in quotation marks (and especially avoid decorative quotation marks in normal use, such as those provided by the {{tl|cquote}} template, which are reserved for pull quotes; quoted sections from elsewhere in the same wiki article). Block quotations can be added with {{tl|quote}} or {{tl|quotation}}.


=== Surutilisation des citations ===
===Surutilisation des citations===
Long quotations crowd the actual article and remove attention from other information. Many direct quotations can be minimized in length by providing an appropriate context in the surrounding text. A summary or paraphrase of a quotation is often better where the original wording could be improved. Consider minimizing the length of a quotation by paraphrasing, by working smaller portions of quotation into the article text, or both.
Long quotations crowd the actual article and remove attention from other information. Many direct quotations can be minimized in length by providing an appropriate context in the surrounding text. A summary or paraphrase of a quotation is often better where the original wording could be improved. Consider minimizing the length of a quotation by paraphrasing, by working smaller portions of quotation into the article text, or both.


Line 114: Line 120:
This means that a quotation is visually on the page, but its relevance is not explained anywhere.
This means that a quotation is visually on the page, but its relevance is not explained anywhere.


==== Recommandations particulières ====
====Recommandations particulières====
* Using too many quotes is incompatible with the encyclopedic writing style.
*Using too many quotes is incompatible with the encyclopedic writing style.
* As a matter of style, quoteboxes should generally be avoided as they draw special attention to the opinion of one source, and present that opinion as though the project endorses it. Instead of using quoteboxes to highlight its notability, explain its importance before introducing the quote or in an introduction to the quote.
*As a matter of style, quoteboxes should generally be avoided as they draw special attention to the opinion of one source, and present that opinion as though the project endorses it. Instead of using quoteboxes to highlight its notability, explain its importance before introducing the quote or in an introduction to the quote.
* The wiki is not a list or repository of loosely associated topics such as quotations.
*The wiki is not a list or repository of loosely associated topics such as quotations.
* Do not insert any number of quotations in a stand-alone quote section.
*Do not insert any number of quotations in a stand-alone quote section.
* A quotation that does not directly relate to the topic of the article or directly support the information as it is presented should not be used.
*A quotation that does not directly relate to the topic of the article or directly support the information as it is presented should not be used.
* Intersperse quotations with original prose that comments on those quotations instead of constructing articles out of quotations with little or no original prose.
*Intersperse quotations with original prose that comments on those quotations instead of constructing articles out of quotations with little or no original prose.
* Longer quotations may be hidden in the reference as a footnote to facilitate verification by other editors without sacrificing readability.
*Longer quotations may be hidden in the reference as a footnote to facilitate verification by other editors without sacrificing readability.


== Ponctuation ==
==Ponctuation==


=== Apostrophes ===
===Apostrophes===
* Consistent use of the straight (or ''typewriter'') apostrophe ({{xt|&nbsp;'&nbsp;}}) is recommended, as opposed to the curly (or ''typographic'') apostrophe ({{!xt|&nbsp;’&nbsp;}}).
*Consistent use of the straight (or ''typewriter'') apostrophe ({{xt|&nbsp;'&nbsp;}}) is recommended, as opposed to the curly (or ''typographic'') apostrophe ({{!xt|&nbsp;’&nbsp;}}).


=== Guillemets ===
===Guillemets===
;Double ou simple
;Double ou simple
: Enclose quotations with double quotation marks ({{xt|Bob said, "Jim ate the apple."}}). Enclose quotations inside quotations with single quotation marks ({{xt|Bob said, "Did Jim say 'I ate the apple' after he left?"}}).
:Enclose quotations with double quotation marks ({{xt|Bob said, "Jim ate the apple."}}). Enclose quotations inside quotations with single quotation marks ({{xt|Bob said, "Did Jim say 'I ate the apple' after he left?"}}).


;Block quotes
;Block quotes
: As already noted [[#Quotations|above]], we use quotation marks or block quotes (not both) to distinguish long quotations from other text. Multiparagraph quotations are always block-quoted. The quotations must be precise and exactly as in the source (except for certain ''allowable typographical changes'', also noted [[#Typographic conformity|above]]). The source should be cited clearly and precisely.
:As already noted [[#Quotations|above]], we use quotation marks or block quotes (not both) to distinguish long quotations from other text. Multiparagraph quotations are always block-quoted. The quotations must be precise and exactly as in the source (except for certain ''allowable typographical changes'', also noted [[#Typographic conformity|above]]). The source should be cited clearly and precisely.


===Crochets et parenthèses===
===Crochets et parenthèses===
Line 149: Line 155:


====Phrases et parenthèses====
====Phrases et parenthèses====
* If any sentence includes material that is enclosed in square or round brackets, it still must end—with a period, or a question or exclamation mark—''after'' those brackets. This principle applies no matter what punctuation is used within the brackets.
*If any sentence includes material that is enclosed in square or round brackets, it still must end—with a period, or a question or exclamation mark—''after'' those brackets. This principle applies no matter what punctuation is used within the brackets.
* However, if the entire sentence is within brackets, the closing punctuation falls within the brackets. (This sentence is an example.) This does not apply to matter that is added (or modified editorially) at the beginning of a sentence for clarity, which is usually in square brackets.
*However, if the entire sentence is within brackets, the closing punctuation falls within the brackets. (This sentence is an example.) This does not apply to matter that is added (or modified editorially) at the beginning of a sentence for clarity, which is usually in square brackets.


=== Ellipses ===
===Ellipses===
An ellipsis (plural ''ellipses'') is used to indicate an omission of material from quoted text or some other omission, perhaps of the end of a sentence, often in a printed record of conversation. The ellipsis is represented by '''ellipsis points''': a set of three unspaced periods, surrounded by square brackets {{xt|[...]}}.
An ellipsis (plural ''ellipses'') is used to indicate an omission of material from quoted text or some other omission, perhaps of the end of a sentence, often in a printed record of conversation. The ellipsis is represented by '''ellipsis points''': a set of three unspaced periods, surrounded by square brackets {{xt|[...]}}.


== Dates et heures ==
==Dates et heures==
=== Moment de la journée ===
===Moment de la journée===
Time of day is normally expressed in figures rather than being spelled out. Context determines whether the 12- or 24-hour clock is used.
Time of day is normally expressed in figures rather than being spelled out. Context determines whether the 12- or 24-hour clock is used.
* 12-hour clock times are written in the form {{xt|11:15&nbsp;a.m.}} and {{xt|2:30&nbsp;p.m.}}, or the form {{xt|11:15&nbsp;am}} and {{xt|2:30&nbsp;pm}}, with a space before the abbreviation.
*12-hour clock times are written in the form {{xt|11:15&nbsp;a.m.}} and {{xt|2:30&nbsp;p.m.}}, or the form {{xt|11:15&nbsp;am}} and {{xt|2:30&nbsp;pm}}, with a space before the abbreviation.
* 24-hour clock times are written in the form {{xt|08:15}}, {{xt|22:55}}, with no suffix. Note that {{xt|00:00}} refers to midnight at the start of a date, and {{xt|24:00}} to midnight at the end of a date.
*24-hour clock times are written in the form {{xt|08:15}}, {{xt|22:55}}, with no suffix. Note that {{xt|00:00}} refers to midnight at the start of a date, and {{xt|24:00}} to midnight at the end of a date.


=== Jours ===
===Jours===
* For full dates, use the format {{xt|10 June 1921}} or the format {{xt|June 10, 1921}}. Similarly, where the year is omitted, use {{xt|10 June}} or {{xt|June 10}}. For choice of format, see below.
*For full dates, use the format {{xt|10 June 1921}} or the format {{xt|June 10, 1921}}. Similarly, where the year is omitted, use {{xt|10 June}} or {{xt|June 10}}. For choice of format, see below.
* Do not use numerical date formats such as {{!xt|03/04/2005}}, as this could refer to 3&nbsp;April or to March&nbsp;4. If a numerical format is required (e.g. for conciseness in long lists and tables), use the YYYY-MM-DD format: {{xt|2005-04-03}}.
*Do not use numerical date formats such as {{!xt|03/04/2005}}, as this could refer to 3&nbsp;April or to March&nbsp;4. If a numerical format is required (e.g. for conciseness in long lists and tables), use the YYYY-MM-DD format: {{xt|2005-04-03}}.


==== Choix du format ====
====Choix du format====
* All the dates in a given article should have the same format (day-month or month-day). These requirements do not apply to dates in quotations or titles.
*All the dates in a given article should have the same format (day-month or month-day). These requirements do not apply to dates in quotations or titles.
* Otherwise, do not change an article from one form to another without good reason.
*Otherwise, do not change an article from one form to another without good reason.


=== Mois ===
===Mois===
* For month and year, write {{xt|June 1921}}, with no comma.
*For month and year, write {{xt|June 1921}}, with no comma.
* Abbreviations for months, such as {{xt|Feb}}, are used only where space is extremely limited. Such abbreviations should use three letters only, and should not be followed by a period (full stop) except at the end of a sentence.
*Abbreviations for months, such as {{xt|Feb}}, are used only where space is extremely limited. Such abbreviations should use three letters only, and should not be followed by a period (full stop) except at the end of a sentence.


=== Années et périodes plus longues ===
===Années et périodes plus longues===
* Do not use ''the year'' before the digits ({{xt|1995}}, not {{!xt|the year 1995}}), unless the meaning would otherwise be unclear.
*Do not use ''the year'' before the digits ({{xt|1995}}, not {{!xt|the year 1995}}), unless the meaning would otherwise be unclear.
* Decades are written in the format {{xt|the 1980s}}, with no apostrophe. Use the two-digit form ('80s) only with an established social or cultural meaning. Avoid forms such as {{!xt|the 1700s}} that could refer to 10 or 100 years.
*Decades are written in the format {{xt|the 1980s}}, with no apostrophe. Use the two-digit form ('80s) only with an established social or cultural meaning. Avoid forms such as {{!xt|the 1700s}} that could refer to 10 or 100 years.


=== Current ===
===Current===
Use of the term "current" should be avoided. What is current today may not be tomorrow; situations change over time. Instead, use date- and time-specific text.
Use of the term "current" should be avoided. What is current today may not be tomorrow; situations change over time. Instead, use date- and time-specific text.
:{|style="background:transparent"
:{| style="background:transparent"
|-
|-
|''Incorrect'':||{{!xt|FlightGear 3.0 is currently the latest version ...}}
|''Incorrect'':||{{!xt|FlightGear 3.0 is currently the latest version ...}}
Line 186: Line 192:
|}
|}


== Nombres ==
==Nombres==
* In general, write whole numbers from one to nine as words, write other numbers that take two words or fewer to say as either figures or words (with consistency within each article), and write all other numbers as figures: {{xt|1/5}} or {{xt|one-fifth}}, {{xt|84}} or {{xt|eighty-four}}, {{xt|200}} or {{xt|two hundred}}, but {{xt|3.75}}, {{xt|544}}, {{xt|21&nbsp;million}}.
*In general, write whole numbers from one to nine as words, write other numbers that take two words or fewer to say as either figures or words (with consistency within each article), and write all other numbers as figures: {{xt|1/5}} or {{xt|one-fifth}}, {{xt|84}} or {{xt|eighty-four}}, {{xt|200}} or {{xt|two hundred}}, but {{xt|3.75}}, {{xt|544}}, {{xt|21&nbsp;million}}.
* In general, use a comma to delimit numbers with five or more digits to the left of the decimal point. Numbers with four digits are at the editor's discretion: {{xt|12,345}}, but either {{xt|1,000}} or {{xt|1000}}.
*In general, use a comma to delimit numbers with five or more digits to the left of the decimal point. Numbers with four digits are at the editor's discretion: {{xt|12,345}}, but either {{xt|1,000}} or {{xt|1000}}.
* In general, use decimals rather than vulgar fractions with measurements.
*In general, use decimals rather than vulgar fractions with measurements.
* Write out "million" and "billion" on the first use. After that, unspaced "M" can be used for millions and "bn" for billions: {{xt|70M}} and {{xt|25bn}}.
*Write out "million" and "billion" on the first use. After that, unspaced "M" can be used for millions and "bn" for billions: {{xt|70M}} and {{xt|25bn}}.
* Write {{xt|3%}}, {{xt|three percent}}, or {{xt|three per cent}}, but not {{!xt|3 %}} (with a space) or {{!xt|three %}}. "Percent" is American usage, and "per cent" is British usage. In ranges of percentages written with an en dash, write only one percent sign: {{xt|3–14%}}.
*Write {{xt|3%}}, {{xt|three percent}}, or {{xt|three per cent}}, but not {{!xt|3 %}} (with a space) or {{!xt|three %}}. "Percent" is American usage, and "per cent" is British usage. In ranges of percentages written with an en dash, write only one percent sign: {{xt|3–14%}}.


==Unités de mesure==
==Unités de mesure==
* The main unit in which a quantity is expressed should generally be an SI unit or non-SI unit officially accepted for use with the SI.
*The main unit in which a quantity is expressed should generally be an SI unit or non-SI unit officially accepted for use with the SI.
* In a direct quotation, always keep the source units. If a conversion is required, it should appear within square brackets in the quote, or else an obscure use of units can be explained in a footnote.
*In a direct quotation, always keep the source units. If a conversion is required, it should appear within square brackets in the quote, or else an obscure use of units can be explained in a footnote.
* Where space is limited (such as tables, infoboxes, parenthetical notes, and mathematical formulas) use unit symbols. In main text it is usually better to spell out unit names, but symbols may also be used when a unit (especially one with a long name) is used repeatedly. However, spell out the first instance of each unit in an article (for example, {{xt|the typical batch is 250 kilograms&nbsp;... and then 15&nbsp;kg of emulsifier is added}}), except for unit names that are hardly ever spelled out (e.g. the degree Celsius). Most unit names are not capitalized. Use "per" when writing out a unit, rather than a slash: {{xt|meter per second}}, not {{!xt|meter/second}}.
*Where space is limited (such as tables, infoboxes, parenthetical notes, and mathematical formulas) use unit symbols. In main text it is usually better to spell out unit names, but symbols may also be used when a unit (especially one with a long name) is used repeatedly. However, spell out the first instance of each unit in an article (for example, {{xt|the typical batch is 250 kilograms&nbsp;... and then 15&nbsp;kg of emulsifier is added}}), except for unit names that are hardly ever spelled out (e.g. the degree Celsius). Most unit names are not capitalized. Use "per" when writing out a unit, rather than a slash: {{xt|meter per second}}, not {{!xt|meter/second}}.
* Potentially unfamiliar unit symbols should be introduced parenthetically at their first occurrence in the article, with the full name given first: for example, {{xt|His initial betatron reached energies of 2.3 megaelectronvolts (MeV), while subsequent betatrons achieved 300&nbsp;MeV.}}
*Potentially unfamiliar unit symbols should be introduced parenthetically at their first occurrence in the article, with the full name given first: for example, {{xt|His initial betatron reached energies of 2.3 megaelectronvolts (MeV), while subsequent betatrons achieved 300&nbsp;MeV.}}
* When dimensions are given, each number should be followed by a unit name or symbol (e.g. write {{xt|1&nbsp;m × 3&nbsp;m × 6&nbsp;m}}, not {{!xt|1 × 3 × 6&nbsp;m}}).
*When dimensions are given, each number should be followed by a unit name or symbol (e.g. write {{xt|1&nbsp;m × 3&nbsp;m × 6&nbsp;m}}, not {{!xt|1 × 3 × 6&nbsp;m}}).
* When they form a compound adjective, values and unit names should be separated by a hyphen: for example, {{xt|a five-day race}}.
*When they form a compound adjective, values and unit names should be separated by a hyphen: for example, {{xt|a five-day race}}.
* Unit symbols are preceded by figures, not by spelled-out numbers. Values and unit symbols are separated by a non-breaking space. For example, {{xt|5&nbsp;min}}. The percent sign, and units of degrees, minutes, and seconds ''for angles and coordinates'', are unspaced.
*Unit symbols are preceded by figures, not by spelled-out numbers. Values and unit symbols are separated by a non-breaking space. For example, {{xt|5&nbsp;min}}. The percent sign, and units of degrees, minutes, and seconds ''for angles and coordinates'', are unspaced.
* Standard unit symbols do not require a full stop (period). However non-standard abbreviations should always be given a full stop.
*Standard unit symbols do not require a full stop (period). However non-standard abbreviations should always be given a full stop.
* No ''s'' is appended, e.g. {{xt|km}}, {{xt|in}}, {{xt|lb}}, not {{!xt|kms}}, {{!xt|ins}}, {{!xt|lbs}}.
*No ''s'' is appended, e.g. {{xt|km}}, {{xt|in}}, {{xt|lb}}, not {{!xt|kms}}, {{!xt|ins}}, {{!xt|lbs}}.
* Write powers of unit symbols with HTML, e.g. {{xt|<nowiki>5&nbsp;km<sup>2</sup></nowiki>}} not Unicode superscripts and subscripts.
*Write powers of unit symbols with HTML, e.g. {{xt|<nowiki>5&nbsp;km<sup>2</sup></nowiki>}} not Unicode superscripts and subscripts.
* For quantities of bytes and bits, specify whether the binary or decimal meanings of K, M, G, etc. are intended.
*For quantities of bytes and bits, specify whether the binary or decimal meanings of K, M, G, etc. are intended.


== Grammaire et usage ==
==Grammaire et usage==
=== First-person pronouns ===
===First-person pronouns===
Wiki articles must not be based on one person's opinions or experiences. The use of ''I'', ''my'', or similar forms is restricted to user pages and quotations. Also avoid ''we'', ''us'', and ''our'': {{!xt|We should note that some critics have argued against our proposal}} (personal rather than encyclopedic).
Wiki articles must not be based on one person's opinions or experiences. The use of ''I'', ''my'', or similar forms is restricted to user pages and quotations. Also avoid ''we'', ''us'', and ''our'': {{!xt|We should note that some critics have argued against our proposal}} (personal rather than encyclopedic).


== Vocabulaire ==
==Vocabulaire==
=== Contractions ===
===Contractions===
Uncontracted forms such as {{xt|do not}} or {{xt|it is}} are the default in encyclopedic style; {{!xt|don't}} and {{!xt|it's}} are too informal.
Uncontracted forms such as {{xt|do not}} or {{xt|it is}} are the default in encyclopedic style; {{!xt|don't}} and {{!xt|it's}} are too informal.


=== Termes étrangers ===
===Termes étrangers===
Foreign words should be used sparingly.
Foreign words should be used sparingly.


==== Pas d'usage courant en anglais ====
====Pas d'usage courant en anglais====
Use italics for phrases in other languages and for isolated foreign words that are not current in English.
Use italics for phrases in other languages and for isolated foreign words that are not current in English.


==== Usage courant en anglais ====
====Usage courant en anglais====
Loanwords and borrowed phrases that have common usage in English ({{xt|vice versa}}) do not require italics. A rule of thumb is not to italicize words that appear unitalicized in major English-language dictionaries.
Loanwords and borrowed phrases that have common usage in English ({{xt|vice versa}}) do not require italics. A rule of thumb is not to italicize words that appear unitalicized in major English-language dictionaries.


=== Langage technique ===
===Langage technique===
Some topics are intrinsically technical, but editors should try to make them understandable to as many readers as possible. Minimize jargon, or at least explain it. For unavoidably technical articles a separate introductory article may be the best solution. Avoid excessive ''wikilinking'' (linking within the wiki) as a substitute for parenthetic explanations such as the one in this sentence. Do not introduce new and specialized words simply to teach them to the reader when more common alternatives will do. When the notions named by jargon are too complex to concisely explain in a few parenthetical words, write one level down. For example, consider adding a brief background section with {{tl|main}} tags pointing to the full treatment article(s) of the prerequisite notions; this approach is practical only when the prerequisite concepts are central to the exposition of the article's main topic, and when such prerequisites aren't too numerous.
Some topics are intrinsically technical, but editors should try to make them understandable to as many readers as possible. Minimize jargon, or at least explain it. For unavoidably technical articles a separate introductory article may be the best solution. Avoid excessive ''wikilinking'' (linking within the wiki) as a substitute for parenthetic explanations such as the one in this sentence. Do not introduce new and specialized words simply to teach them to the reader when more common alternatives will do. When the notions named by jargon are too complex to concisely explain in a few parenthetical words, write one level down. For example, consider adding a brief background section with {{tl|main}} tags pointing to the full treatment article(s) of the prerequisite notions; this approach is practical only when the prerequisite concepts are central to the exposition of the article's main topic, and when such prerequisites aren't too numerous.


=== Éléments géographiques ===
===Éléments géographiques===
Places should generally be referred to consistently by the same name as in the title of their article. Exceptions are made if there is a widely accepted historical English name appropriate to the given context. In cases where such a historical name is used, it should be followed by the modern name in round brackets (parentheses) on the first occurrence of the name in applicable sections of the article. This resembles linking; it should not be done to the detriment of style. On the other hand, it is probably better to provide such a variant too often than too rarely. If more than one historical name is applicable for a given context, the other names should be added after the modern English name, that is: "historical name (modern name, other historical names)".
Places should generally be referred to consistently by the same name as in the title of their article. Exceptions are made if there is a widely accepted historical English name appropriate to the given context. In cases where such a historical name is used, it should be followed by the modern name in round brackets (parentheses) on the first occurrence of the name in applicable sections of the article. This resembles linking; it should not be done to the detriment of style. On the other hand, it is probably better to provide such a variant too often than too rarely. If more than one historical name is applicable for a given context, the other names should be added after the modern English name, that is: "historical name (modern name, other historical names)".


== Images ==
==Images==
* Infoboxes, images, and related content in the lead must be right-aligned.
*Infoboxes, images, and related content in the lead must be right-aligned.
* Use captions to clarify the relevance of the image to the article (see [[#Captions|Captions]], below).
*Use captions to clarify the relevance of the image to the article (see [[#Captions|Captions]], below).
* Each image should be inside the major section to which it relates (within the section defined by the most recent level 2 heading or at the top of the lead), not immediately above the section heading.
*Each image should be inside the major section to which it relates (within the section defined by the most recent level 2 heading or at the top of the lead), not immediately above the section heading.
* Avoid sandwiching text between two images that face each other, and between an image and an infobox or similar.
*Avoid sandwiching text between two images that face each other, and between an image and an infobox or similar.
* The thumbnail option may be used ("<code>thumb</code>"), or another size may be fixed. The default thumbnail width is 220&nbsp;pixels; users can adjust this in their preferences. Lead images should be no wider than "upright=1.35" (by default this is 300 pixels).
*The thumbnail option may be used ("<code>thumb</code>"), or another size may be fixed. The default thumbnail width is 220&nbsp;pixels; users can adjust this in their preferences. Lead images should be no wider than "upright=1.35" (by default this is 300 pixels).
* Avoid referring to images as being on the left or right. Image placement is different for viewers of the mobile version of the wiki and might change in the future. Instead, use captions to identify images.
*Avoid referring to images as being on the left or right. Image placement is different for viewers of the mobile version of the wiki and might change in the future. Instead, use captions to identify images.


=== Évitez de saisir des informations textuelles sous forme d'images ===
===Évitez de saisir des informations textuelles sous forme d'images===
Textual information should almost always be entered as text rather than as an image. True text can be colored and adjusted with CSS tags and templates, but text in images cannot be. Images are not searchable and are slower to download. Any important textual information in an image should also appear in the image's alt text, caption, or other nearby text.
Textual information should almost always be entered as text rather than as an image. True text can be colored and adjusted with CSS tags and templates, but text in images cannot be. Images are not searchable and are slower to download. Any important textual information in an image should also appear in the image's alt text, caption, or other nearby text.


=== Légendes ===
===Légendes===
Photographs and other graphics should always have captions, unless they are "self-captioning" images or when they are unambiguous depictions of the subject of the article.
Photographs and other graphics should always have captions, unless they are "self-captioning" images or when they are unambiguous depictions of the subject of the article.


==== Mise en forme des légendes ====
====Mise en forme des légendes====
* Captions normally start with a capital letter.
*Captions normally start with a capital letter.
* Most captions are not complete sentences, but merely sentence fragments that should not end with a period. If any complete sentence occurs in a caption, all sentences and any sentence fragments in that caption should end with a period.
*Most captions are not complete sentences, but merely sentence fragments that should not end with a period. If any complete sentence occurs in a caption, all sentences and any sentence fragments in that caption should end with a period.
* The text of captions should not be specially formatted (with italics, for example), except in ways that would apply if it occurred in the main text.
*The text of captions should not be specially formatted (with italics, for example), except in ways that would apply if it occurred in the main text.
* Captions should be succinct; more information about the image can be included on its description page, or in the main text.
*Captions should be succinct; more information about the image can be included on its description page, or in the main text.
* Captions for technical charts and diagrams may be substantially longer than those for other images. Captions for technical images should fully describe all the elements of the image, and the image's significance.
*Captions for technical charts and diagrams may be substantially longer than those for other images. Captions for technical images should fully describe all the elements of the image, and the image's significance.


== Listes à puces et numérotées ==
==Listes à puces et numérotées==
* Do not use lists if a passage is read easily as plain paragraphs.
*Do not use lists if a passage is read easily as plain paragraphs.
* Use proper wikimarkup- or template-based list code ''(see [[Help:Formatting#Lists and indentation]])''.
*Use proper wikimarkup- or template-based list code ''(see [[Help:Formatting#Lists and indentation]])''.
* Do not leave blank lines between items in a bulleted or numbered list unless there is a reason to do so, since this causes the wiki software to interpret each item as beginning a new list.
*Do not leave blank lines between items in a bulleted or numbered list unless there is a reason to do so, since this causes the wiki software to interpret each item as beginning a new list.
** Indents (such as this) are permitted if the elements are "Children" items
**Indents (such as this) are permitted if the elements are "Children" items
* Use numbers rather than bullets only if:
*Use numbers rather than bullets only if:
** A need to refer to the elements by number may arise; or
**A need to refer to the elements by number may arise; or
** The sequence of the items is critical.
**The sequence of the items is critical.
* Use the same grammatical form for all elements in a list, and do not mix sentences and sentence fragments as elements.
*Use the same grammatical form for all elements in a list, and do not mix sentences and sentence fragments as elements.
** For example, when the elements are:  
**For example, when the elements are:  
*** ''Complete sentences'', each one is formatted with sentence case (its first letter is capitalized) and a final period (full stop).
***''Complete sentences'', each one is formatted with sentence case (its first letter is capitalized) and a final period (full stop).
*** ''Sentence fragments'', the list is typically introduced by a lead fragment ending with a colon.  
***''Sentence fragments'', the list is typically introduced by a lead fragment ending with a colon.
*** ''Titles of works'', they retain the original capitalization of the titles.
***''Titles of works'', they retain the original capitalization of the titles.
*** ''Other elements'', they are formatted consistently in either sentence case or lower case.
***''Other elements'', they are formatted consistently in either sentence case or lower case.


== Liens ==
==Liens==
=== Wikilinks ===
===Wikilinks===
'''Make [[Help:Formatting#Links|links]] only where they are relevant and helpful in the context:''' Excessive use of hyperlinks can be distracting and may slow the reader down. Redundant links clutter the page and make future maintenance harder. High-value links that ''are'' worth pursuing should stand out clearly.
'''Make [[Help:Formatting#Links|links]] only where they are relevant and helpful in the context:''' Excessive use of hyperlinks can be distracting and may slow the reader down. Redundant links clutter the page and make future maintenance harder. High-value links that ''are'' worth pursuing should stand out clearly.


Line 275: Line 281:
'''Linking in discussion pages:''' When adding a wikilink to a discussion page, it is preferable to use [[Help:Formatting#Permalinks_and_links_to_diffs|permalinks]] instead of ordinary links, since the content may have changed a lot before the next reader reads the comment. To highlight a specific edit, it might also be useful to link to a [[Help:Formatting#Permalinks_and_links_to_diffs|diff]].
'''Linking in discussion pages:''' When adding a wikilink to a discussion page, it is preferable to use [[Help:Formatting#Permalinks_and_links_to_diffs|permalinks]] instead of ordinary links, since the content may have changed a lot before the next reader reads the comment. To highlight a specific edit, it might also be useful to link to a [[Help:Formatting#Permalinks_and_links_to_diffs|diff]].


=== External links ===
===External links===
Do not use external links in the body of an article. Articles can include an ''external links'' section at the end, pointing to further information outside the wiki as distinct from citing sources. The standard format is a primary heading, <code>==External links==</code>, followed by a bulleted list of links. Identify the link and briefly indicate its relevance to the article: avoid linking to commercial and unrelated web sites, in essence ''spam''. For example:
Do not use external links in the body of an article. Articles can include an ''external links'' section at the end, pointing to further information outside the wiki as distinct from citing sources. The standard format is a primary heading, <code>==External links==</code>, followed by a bulleted list of links. Identify the link and briefly indicate its relevance to the article: avoid linking to commercial and unrelated web sites, in essence ''spam''. For example:
:<code><nowiki>* [http://flightgear.org Official website]</nowiki></code>
:<code><nowiki>* [http://flightgear.org Official website]</nowiki></code>
:<code><nowiki>* [https://sourceforge.net/p/flightgear/codetickets/ Bug tracker]</nowiki></code>
:<code><nowiki>* [https://sourceforge.net/p/flightgear/codetickets/ Bug tracker]</nowiki></code>
These will appear as:
These will appear as:
:* [http://flightgear.org Official website]
:*[http://flightgear.org Official website]
:* [https://sourceforge.net/p/flightgear/codetickets/ Bug tracker]
:*[https://sourceforge.net/p/flightgear/codetickets/ Bug tracker]


== Divers ==
==Divers==
=== Gardez le balisage simple ===
===Gardez le balisage simple===
The simplest markup is often the easiest to edit, the most comprehensible, and the most predictable. Markup may appear differently in different browsers. Use HTML and CSS markup sparingly; in particular, do not use the CSS <code>float</code> or <code>line-height</code> properties because they break rendering on some browsers when large fonts are used.
The simplest markup is often the easiest to edit, the most comprehensible, and the most predictable. Markup may appear differently in different browsers. Use HTML and CSS markup sparingly; in particular, do not use the CSS <code>float</code> or <code>line-height</code> properties because they break rendering on some browsers when large fonts are used.


An HTML entity is sometimes better than the equivalent Unicode character, which may be difficult to identify in edit mode; for example, <code>&amp;Alpha;</code> is understood where <code>Α</code> (the upper-case form of Greek <code>α</code>) may not be.
An HTML entity is sometimes better than the equivalent Unicode character, which may be difficult to identify in edit mode; for example, <code>&amp;Alpha;</code> is understood where <code>Α</code> (the upper-case form of Greek <code>α</code>) may not be.


=== Utiliser des modèles ===
===Utiliser des modèles===
Make use of [[:Category:Templates|existing templates]] whenever possible to ensure articles are styled in a uniform way. See [[Help:Templates|the Templates Help page]] for a quick introduction to templates.
Make use of [[:Category:Templates|existing templates]] whenever possible to ensure articles are styled in a uniform way. See [[Help:Templates|the Templates Help page]] for a quick introduction to templates.


=== Problèmes de mise en forme ===
===Problèmes de mise en forme===
Modifications in font size, blank space, and color (see [[#Color coding|Color coding]], below) are an issue for the wiki site-wide style sheet, and should be reserved for special cases only.
Modifications in font size, blank space, and color (see [[#Color coding|Color coding]], below) are an issue for the wiki site-wide style sheet, and should be reserved for special cases only.


Typically, the use of custom font styles will:
Typically, the use of custom font styles will:
* reduce consistency, since the text will no longer look uniform;
*reduce consistency, since the text will no longer look uniform;
* reduce usability, since it might be impossible for people with custom style sheets (for accessibility reasons, for example) to override it, and it might clash with a different skin as well as inconvenience people with color blindness (see below); and
*reduce usability, since it might be impossible for people with custom style sheets (for accessibility reasons, for example) to override it, and it might clash with a different skin as well as inconvenience people with color blindness (see below); and
* cause disputes, since other editors may disagree aesthetically with the choice of style.
*cause disputes, since other editors may disagree aesthetically with the choice of style.


Outside article text, different font sizes are routinely used in navigation templates and infoboxes, tables (especially in larger ones), and some other contexts where alternatives are not available (such as table captions). Specify font sizes ''relatively'' (for example in CSS with <code>font-size: 80%</code>) rather than ''absolutely'' (like <code>font-size: 8pt</code>).
Outside article text, different font sizes are routinely used in navigation templates and infoboxes, tables (especially in larger ones), and some other contexts where alternatives are not available (such as table captions). Specify font sizes ''relatively'' (for example in CSS with <code>font-size: 80%</code>) rather than ''absolutely'' (like <code>font-size: 8pt</code>).


==== Code de couleurs ====
====Code de couleurs====
Information should be accessible to all. Do not use color ''alone'' to mark differences in text: they may be invisible to people with color blindness. Also, black-and-white printouts, older computer displays with fewer colors, and monochrome displays (older PDAs and cell phones) cannot show such distinctions.
Information should be accessible to all. Do not use color ''alone'' to mark differences in text: they may be invisible to people with color blindness. Also, black-and-white printouts, older computer displays with fewer colors, and monochrome displays (older PDAs and cell phones) cannot show such distinctions.


Line 316: Line 322:
To leave an invisible comment, enclose the text you intend to be read only by editors between <code>&lt;!--</code> and <code>--&gt;</code>. For example: {{xt|<code><nowiki><!--If you change this section title, please also change the links to it on the pages ...--></nowiki></code>}}
To leave an invisible comment, enclose the text you intend to be read only by editors between <code>&lt;!--</code> and <code>--&gt;</code>. For example: {{xt|<code><nowiki><!--If you change this section title, please also change the links to it on the pages ...--></nowiki></code>}}


== Référence ==
==Référence==
This document contains a selection of relevant sections from {{wikipedia|Wikipedia:Manual of Style}}.
This document contains a selection of relevant sections from {{wikipedia|Wikipedia:Manual of Style}}.


== Contenu connexe ==
==Contenu connexe==
* [[FlightGear wiki:FlightGear screenshot categories]]
*[[FlightGear wiki:FlightGear screenshot categories]]
* {{tl|informative template}} – ''Template documentation guidelines.''
*{{tl|informative template}} – ''Template documentation guidelines.''


[[Category:Wiki style guides]]
[[Category:Wiki style guides]]
Adaz
482

edits

Retrieved from "https://wiki.flightgear.org/Special:MobileDiff/136257"

Navigation menu