Qt wiki will be updated on October 12th 2023 starting at 11:30 AM (EEST) and the maintenance will last around 2-3 hours. During the maintenance the site will be unavailable.

Language Guidelines: Difference between revisions

From Qt Wiki
Jump to navigation Jump to search
No edit summary
m (Removed reference to broken link. Fixed a spelling error and typo.)
 
(11 intermediate revisions by 6 users not shown)
Line 1: Line 1:
h1. Language Guidelines
[[Category:Writing Guidelines]]
TODO: Check whether all these rules are listed in the [https://learn.microsoft.com/en-us/style-guide/welcome/ Microsoft Style Guide] and then remove this page.  
 
QUESTION: Should we add these as links into the appropriate sections in the MS Style Guide on the [[Developing Qt Documentation]] page?


This page is part of the [[QtWritingGuidelines | Qt Writing Guidelines]].
This page is part of the [[QtWritingGuidelines | Qt Writing Guidelines]].


== Idioms and usage ==
==Idioms and usage==


=== Since/as/because and ambiguity ===
===Point of view (POV)===


According to MSTP both "since" and "as" need to be avoided because they can lead to ambiguous interpretations (causal meaning or temporal meaning). MSTP recommends using "because".
Use second person point of view with the personal pronoun '''you''' in technical communication. This is also known as direct address, and helps you write in active voice.


The Canadian Writer's Handbook also recommends not using "since" and "as".
===Since/as/because and ambiguity===
 
According to MSTP both "since" and "as" need to be avoided because they can lead to ambiguous interpretations (causal meaning or temporal meaning). MSTP recommends using "because".
 
The Canadian Writer's Handbook also recommends not using "since" and "as".


The Chicago Manual of Style doesn't mention this issue.
The Chicago Manual of Style doesn't mention this issue.


A very good article in this respect is Grammar Girl's discussion of this topic:<br />http://grammar.quickanddirtytips.com/although-versus-while.aspx .
==Spelling==


== Spelling ==
Qt documentation follows American English spelling.


Qt documentation follows the American spelling.
===Latin expressions commonly used in English===


=== Latin expressions commonly used in English ===
i.e. (that is)
e.g. (for example)
cf. (compare)
etc. (and so forth)
vs.(versus)
et al. (and others)


i.e. (that is)<br />e.g. (for example)<br />cf. (compare)<br />etc. (and so forth)<br />vs.(versus)<br />et al. (and others)
It is advisable to use the English equivalent for better readability.


It is advisable to use the English equivalent for better readibility.
==Punctuation==


== Punctuation ==
===Oxford comma===


=== Oxford comma ===
In punctuation, a serial comma (also called Oxford comma) needs to be placed immediately before the conjunction (often "and" or "or") in a series of three or more terms.
 
In punctuation, a serial comma (also called Oxford comma) needs to be placed immediately before the conjunction (often &quot;and&amp;quot; or &quot;or&amp;quot;) in a series of three or more terms.


Example:
Example:
Line 35: Line 45:
I would like crackers, cheese, and garlic.
I would like crackers, cheese, and garlic.


=== The comma as a separator between compound sentences. ===
===The comma as a separator between compound sentences.===


Use commas to separate independent clauses when they are joined by any of these seven coordinating conjunctions: and, but, for, or, nor, so, yet.
Use commas to separate independent clauses when they are joined by any of these seven coordinating conjunctions: and, but, for, or, nor, so, yet.
Line 41: Line 51:
However, the comma can be dropped in the following cases:
However, the comma can be dropped in the following cases:


* if both independent clauses are quite short, especially if the two clauses are very closely related, and even more so if the subject of both clauses is the same, or
*When both independent clauses are quite short, especially if the two clauses are very closely related, and even more so if the subject of both clauses is the same.


* if only the first clause is quite short, especially if the two clauses are very closely related, and even more so if the subject of both clauses is the same.
*If only the first clause is quite short, especially if the two clauses are very closely related, and even more so if the subject of both clauses is the same.


=== Periods and spaces ===
===Periods and spaces===


The period ending a sentence should be followed by 1 space.
The period ending a sentence should be followed by 1 space.
Line 51: Line 61:
An exception to this rule is the legal text in the beginning of Qt code, which can have 2 spaces after a period.
An exception to this rule is the legal text in the beginning of Qt code, which can have 2 spaces after a period.


== Grammar issues ==
==Grammar issues==
 
===Genitive===


=== Genitive ===
Can we use the possessive's if the owner is not a person ?


Can we use the possessive 's if the owner is not a person ?
Example:


Example:<br />* the item's width<br />* the width of the item
*the item's width
*the width of the item


Both are correct. There is presently no rule stating that the owner cannot be an inanimate object.
Both are correct. There is presently no rule stating that the owner cannot be an inanimate object.


=== An URL or a URL ? ===
===An URL or a URL ?===


A URL.
A URL.


If the &quot;u&amp;quot; is long, the article is &quot;a&amp;quot;. For example, a uniform, a university, a Ugandan man.
If the "u" is long, the article is "a". For example, a uniform, a university, a Ugandan man.
 
If it is short, the article is &quot;an&amp;quot;. For example, an understatement, an undermining comment, an underdog team.
 
== Usage and idioms ==
 
=== Using the second personal pronoun in manuals ===
 
Avoid using &quot;you&amp;quot; in technical documents.


When correcting this, use the passive voice, an imperative, and/or rephrase the sentence.
If it is short, the article is "an". For example, an understatement, an undermining comment, an underdog team.


For example:<br />You can override this function for your delegate if you need extra logic to decide which transition to return.<br />==&gt; This function can be overridden for the delegate if extra logic is required to decide which transition to return.
==Sources==


== Sources ==
Microsoft Manual of Style, Fourth Edition. Microsoft Press
https://www.microsoftpressstore.com/store/microsoft-manual-of-style-9780735648715


The Chicago Manual of Style, 14th edition. The University of Chicago Press.<br />&quot;English Language &amp; Usage&amp;quot;: http://english.stackexchange.com/about.
The Chicago Manual of Style, 14th edition. The University of Chicago Press.
"English Language & Usage": http://english.stackexchange.com/about.

Latest revision as of 11:54, 18 April 2023

TODO: Check whether all these rules are listed in the Microsoft Style Guide and then remove this page.

QUESTION: Should we add these as links into the appropriate sections in the MS Style Guide on the Developing Qt Documentation page?

This page is part of the Qt Writing Guidelines.

Idioms and usage

Point of view (POV)

Use second person point of view with the personal pronoun you in technical communication. This is also known as direct address, and helps you write in active voice.

Since/as/because and ambiguity

According to MSTP both "since" and "as" need to be avoided because they can lead to ambiguous interpretations (causal meaning or temporal meaning). MSTP recommends using "because".

The Canadian Writer's Handbook also recommends not using "since" and "as".

The Chicago Manual of Style doesn't mention this issue.

Spelling

Qt documentation follows American English spelling.

Latin expressions commonly used in English

i.e. (that is) e.g. (for example) cf. (compare) etc. (and so forth) vs.(versus) et al. (and others)

It is advisable to use the English equivalent for better readability.

Punctuation

Oxford comma

In punctuation, a serial comma (also called Oxford comma) needs to be placed immediately before the conjunction (often "and" or "or") in a series of three or more terms.

Example:

I would like crackers, cheese, and garlic.

The comma as a separator between compound sentences.

Use commas to separate independent clauses when they are joined by any of these seven coordinating conjunctions: and, but, for, or, nor, so, yet.

However, the comma can be dropped in the following cases:

  • When both independent clauses are quite short, especially if the two clauses are very closely related, and even more so if the subject of both clauses is the same.
  • If only the first clause is quite short, especially if the two clauses are very closely related, and even more so if the subject of both clauses is the same.

Periods and spaces

The period ending a sentence should be followed by 1 space.

An exception to this rule is the legal text in the beginning of Qt code, which can have 2 spaces after a period.

Grammar issues

Genitive

Can we use the possessive's if the owner is not a person ?

Example:

  • the item's width
  • the width of the item

Both are correct. There is presently no rule stating that the owner cannot be an inanimate object.

An URL or a URL ?

A URL.

If the "u" is long, the article is "a". For example, a uniform, a university, a Ugandan man.

If it is short, the article is "an". For example, an understatement, an undermining comment, an underdog team.

Sources

Microsoft Manual of Style, Fourth Edition. Microsoft Press https://www.microsoftpressstore.com/store/microsoft-manual-of-style-9780735648715

The Chicago Manual of Style, 14th edition. The University of Chicago Press. "English Language & Usage": http://english.stackexchange.com/about.