This guide adapts rules and examples from Microsoft’s Localization Style Guide for French (Canada) (originally written for software/UI localization). The underlying linguistic rules apply universally — to legal contracts, medical documents, marketing copy, and any Canadian French translation work. Restructured and reformatted as a general Canadian French translator reference by ChatsControl.

French (Canada) Translation Style Guide — Voice, Word Choice & Common Pitfalls (Legal, Medical, Marketing, IT)¶

TL;DR¶

• Canadian French translation prefers full forms over shortenings — write “application” (not “app”), “synchroniser” (not “sync”), and “information” (not “info” in running text); shortened forms are tolerated only when source UI space is constrained.
• Modern Canadian French register replaces formal vocabulary with everyday words — pour (not afin de), toujours (not invariablement), baisse (not diminution); applies to marketing copy, patient instructions, software UI, and consumer-facing legal documents.
• Use gender-inclusive constructions — prefer collective nouns (le lectorat), plurals (les journalistes), epicene adjectives (spécialiste), and impersonal phrasing; avoid il/elle in generic references.
• Address users with “vous” (masculine singular form) in standard content; switch to “tu” only in Copilot predefined prompts where users model casual conversation with AI.
• Canadian French punctuation differs from European French — no leading nonbreaking space before semicolon, exclamation mark, or question mark; leading space before colon; em dash usually replaced by comma, period, or parentheses.

Register and tone for modern Canadian French translation¶

Register is the level of formality, warmth, and conversational ease the target text projects. Modern Canadian French readers across consumer-facing spheres expect a register that feels clear, friendly, and concise — language that resembles conversation observed in everyday settings, as opposed to the formal, technical language that has traditionally dominated commercial and technical content.

Three principles define the modern Canadian French register for consumer-facing content:

• Warm and relaxed. Sounds natural — less formal, more grounded in honest conversation. Occasionally playful when context permits, but never forced.
• Crisp and clear. Written for scanning first, reading second. Sentences short enough to parse on a phone screen. Simplicity is the default.
• Ready to help. Anticipates what the reader needs and offers it at the right moment, rather than burying it under qualifications.

Why this matters: Formal Canadian French is the default in legacy commercial and technical writing, and it carries an institutional distance that damages outcomes across spheres. In marketing copy it kills conversion — readers disengage when text sounds like a government circular. In patient-facing medical materials it reduces comprehension and treatment compliance. In software UI it creates friction at every interaction. In consumer-facing legal documents (terms of service, privacy notices) Quebec consumer-protection legislation increasingly favors plain language. Only sworn legal translation and pure technical specifications retain the older formal register.

Audience targeting: technical vs. consumer vocabulary¶

The same source text requires different vocabulary depending on who reads the translation. Use technical terms for technical audiences; for consumers use common words and phrases. A clinical drug monograph for prescribers uses precise pharmacological terminology; the patient leaflet for the same drug uses everyday Canadian French. A software API reference uses developer jargon; the end-user help article uses plain Canadian French.

This applies in every sphere. Legal translation for corporate counsel uses Latinisms and procedural shorthand; consumer-facing versions need plain-French framing. Medical translation for clinicians keeps Greek/Latin nomenclature; for patients it switches to common terms. IT translation uses developer jargon in engineer-facing docs, natural Canadian French in end-user help.

Flexibility: when to translate literally vs. when to rewrite¶

Flexibility is the translator’s discretion to depart from literal source structure when the literal rendering produces unnatural Canadian French. The rule: consider the intent of the text and what the reader needs to know to successfully complete the task, then compose Canadian French sentences that carry the same meaning naturally. Feel free to choose words that aren’t standard literal translations if those choices stay truer to the source intent.

Because conversational style departs from source-faithful translation, literally rendering the English text frequently produces target text that is not relevant or natural to Canadian French readers.

Why this matters: Source-faithful translation produces translatorese — text that reads as translated. Required in sworn legal translation and certified document translation (birth certificates, court rulings, disputed contracts) where literal accuracy is mandated. Harmful in marketing translation (lost conversion), patient-facing healthcare materials (lost clarity), and software UX (lost engagement). Knowing where the boundary sits is core translator judgment.

Word choice: terminology, short forms, and everyday vocabulary¶

Approved terminology¶

Use approved terminology from project glossaries and termbases where applicable — for key terms, technical terms, and product names. Every serious translation project has a terminology bank, explicit (glossary, termbase) or implicit (translator’s accumulated decisions). Consistency within the bank matters more than the individual choice.

Why this matters: Terminology consistency is non-negotiable in legal translation (a defined term in a contract must render identically across all 200 pages — variant renderings create ambiguity opposing counsel will exploit), medical translation (drug names, dosage units, anatomical terms must be invariant — a synonym swap can produce a dispensing error), and IT/software translation (UI labels, menu items, error codes must match help documentation word-for-word or users can’t find what they need).

Short word forms¶

In Canadian French, full forms are preferred and the use of shortened words is the exception. Where English casually shortens words (“app,” “info,” “sync”), Canadian French keeps the full form unless the source UI imposes a hard space constraint.

en-US source term	en-US word usage	fr-CA word usage
App	Short word “app” is used instead of application or program	Do not use “app” in Canadian French. Use “application” instead as this is the approved translation. Note that when used in the source string and if space is limited, then the use of the short form « appli » is acceptable.
Info	Used in most situations unless information fits the context. Used to point the reader elsewhere (“for more info, see “)	Try to avoid using “infos” in running text and use the full form instead (“informations” or “information”). Note that when used in the source string and if space is limited, then the use of the short form is acceptable. Use “infos” in the context of data related to a contact, personal details, more info, etc.
PC	Used for personal computing devices (computer for situations about PCs and Macs)	Use “PC” as per source as this is the approved translation.
Sync	—	Do not use “sync” or “synchro,” even if used in the source, and use the full form instead: synchroniser/synchronisation.

Everyday words over formal alternatives¶

For modern Canadian French, everyday words convey meaning in a more concise and direct way. Target audiences are often reluctant to read and understand long text, especially when it contains obscure or formal vocabulary. The following table contains formal target terms and their simpler everyday alternatives.

fr-CA existing term	fr-CA new voice term
invariablement	toujours
il est (fort) probable que	sans doute, probablement
pléthore	trop (excès is less-used, and depends on context)
diminution	baisse
afin de, dans le but de	pour
avoir la possibilité de, avoir l’opportunité de	pouvoir
réaliser	faire, effectuer
requérir, exiger	demander, nécessiter
faire une recommandation	recommander, conseiller

Why this matters: Formal vocabulary signals institutional distance. In marketing translation, “afin de bénéficier de” reads as paperwork; “pour profiter de” reads as someone talking to the reader. In medical patient materials, “il est fort probable que vous ressentiez” delays comprehension; “vous ressentirez probablement” lands immediately. In software UI, “réaliser la sauvegarde” is longer and stiffer than “faire la sauvegarde.” These substitutions are among the highest-leverage edits a translator can make.

Words and phrases to avoid in modern Canadian French¶

Avoid an unnecessarily formal tone. The following words and phrases express a very formal register and have simpler equivalents that work better in consumer-facing contexts.

Canadian French old word/phrase	Canadian French new word/phrase
avoir la possibilité de, avoir l’opportunité de	pouvoir
Réaliser	faire, effectuer
requérir	demander
faire une recommandation	recommander, conseiller
nécessiter	devoir
Impossible de…	When source is using forms such as “We were unable to” or “We could not,” try to avoid using impersonal forms such as “impossible de.” Instead, match the source and use forms such as “Nous n’avons pas pu.”

Why this matters: The impersonal “impossible de” pattern is one of the most common Canadian French translation defects. In error messages it sounds passive and machine-like; “Nous n’avons pas pu télécharger le fichier” tells the user what happened in a more human voice. In legal correspondence the choice between “Nous n’avons pas pu” and “Il n’a pas été possible de” changes who bears responsibility in the text. In medical advice content, “nous vous recommandons” connects more directly than “il est recommandé.”

Sample translations: applying voice principles in context¶

Focusing on the user action¶

US English	Canadian French target	Explanation
The password isn’t correct, so try again. Passwords are case-sensitive.	Le mot de passe est incorrect, réessayez. Les mots de passe respectent la casse.	The user has entered an incorrect password so provide the user with a short and friendly message with the action to try again.
This product key didn’t work. Check it and try again.	Cette clé de produit ne fonctionne pas. Vérifiez-la et recommencez.	The user has entered an incorrect product key. The message casually and politely asks the user to check it and try again.
All ready to go	Tout est prêt.	Casual and short message to inform user that setup has completed, ready to start using the system.
Give your PC a name–any name you want. If you want to change the background color, turn high contrast off in PC settings.	Donnez un nom à votre PC (celui que vous voulez). Pour modifier la couleur d’arrière-plan, désactivez le contraste élevé dans les paramètres du PC.	Address the user directly using second person pronoun to take the necessary action.

Explanatory text and providing support¶

US English	Canadian French target	Explanation
The updates are installed, but Windows Setup needs to restart for them to work. After it restarts, we’ll keep going from where we left off.	Les mises à jour sont installées, mais le programme d’installation de Windows doit redémarrer pour qu’elles puissent fonctionner. Une fois le redémarrage effectué, l’installation pourra reprendre.	The language is natural, the way people talk. In this case voice is reassuring, letting the user know that we’re doing the work. Use of “we” provides a more personal feel.
If you restart now, you and any other people using this PC could lose unsaved work.	Si vous redémarrez le PC maintenant, vous et les autres personnes en train d’utiliser ce PC risquez de perdre le travail non enregistré.	Voice is clear and natural informing the user what will happen if this action is taken.
This document will be automatically moved to the right library and folder after you correct invalid or missing properties.	Ce document sera automatiquement déplacé vers la bibliothèque et le dossier appropriés dès que vous aurez corrigé les propriétés non valides ou manquantes.	Voice talks to the user informatively and directly on the action that will be taken.
Something bad happened! Unable to locate downloaded files to create your bootable USB flash drive.	Il y a eu un problème : impossible de trouver les fichiers téléchargés pour créer votre clé USB de démarrage.	Without complexity and using short sentences inform the user what has happened.

Promoting a feature¶

US English	Canadian French target	Explanation
Picture password is a new way to help you protect your touchscreen PC. You choose the picture—and the gestures you use with it—to create a password that’s uniquely yours.	Le mot de passe image est une nouvelle méthode de protection de votre PC à écran tactile. Vous choisissez l’image (ainsi que les mouvements nécessaires à sa réalisation) pour créer un mot de passe réellement personnalisé.	Promoting a specific feature.
Let apps give you personalized content based on your PC’s location, name, account picture, and other domain info.	Permettre aux applications de vous donner du contenu personnalisé en fonction de l’emplacement, du nom et de l’avatar de compte de votre PC, ainsi que d’autres informations de domaine.	Promoting the use of apps.

Providing how-to guidelines¶

US English	Canadian French target	Explanation
To go back and save your work, click Cancel and finish what you need to.	Pour revenir en arrière et enregistrer votre travail, cliquez sur Annuler et terminez vos tâches.	Short and clear action using second person pronoun.
To confirm your current picture password, just watch the replay and trace the example gestures shown on your picture.	Pour confirmer votre mot de passe image actuel, regardez simplement la relecture de la séquence enregistrée et tracez les exemples de mouvements indiqués sur votre image.	Voice is simple and natural. The user isn’t overloaded with information; we tell them only what they need to know to make a decision.
It’s time to enter the product key. When you connect to the Internet, we’ll activate Windows for you.	Il est temps d’entrer la clé de produit (Product Key). Quand vous vous connecterez à Internet, nous activerons Windows pour vous.	Speak to the user directly and naturally using second person pronoun “vous” on clear actions to enter the product key.

Inclusive language¶

All communications should be inclusive and diverse. The following guidelines provide examples on how to use inclusive language and avoid habits that may unintentionally lead to marginalization, offense, misrepresentation, or the perpetuation of stereotypes.

General guidelines:

• Comply with local language laws.
• Use plain language — straightforward, concrete, familiar words. Plain and accessible language helps people of all learning levels and abilities. Prefer a two-syllable word over a three-syllable word, or several clear words instead of one complicated term.
• Be mindful when referring to various parts of the world. If you name cities, countries, or regions in examples, make sure they’re not politically disputed. In examples that refer to several regions, use equivalent references — don’t mix countries with states or continents.
• In text and images, represent diverse perspectives and circumstances. Depict a variety of people from all walks of life participating fully in activities.
• Don’t generalize or stereotype people by region, culture, age, or gender — not even if the stereotype is positive.
• Don’t use profane, derogatory, or slang terms that could be considered cultural appropriation.
• Don’t use terms that may carry unconscious racial bias or terms associated with military actions, politics, or controversial historical events.

Use this (English)	Not this (English)	Use this (French Canada)	Not this (French Canada)
primary/subordinate	master/slave	principal/secondaire; instructeur/exécutant	maître/esclave
perimeter network	demilitarized zone (DMZ)	réseau de périmètre	zone démilitarisée
expert	guru	expert	gourou
meeting	pow wow	réunion	pow wow
colleagues; everyone; all	guys; ladies and gentlemen	collègues, tout le monde, tous	mesdames et messieurs
parent	mother or father	parent	père ou mère

Why this matters: Inclusive language is now mandated or expected across government and public-sector translation (federal Canadian guidelines explicitly require it), corporate communications (most large employers have inclusive-language policies), healthcare materials (patient-centric inclusive language improves access for marginalized communities), and marketing copy (audience-broadening signals brand modernity). Translators who default to legacy gendered constructions or culturally-loaded metaphors create rework downstream.

Avoid gender bias¶

Use gender-neutral alternatives for common terms. Avoid compounds containing gender-specific terms (homme, femme, etc.).

Use this	Not this	Comments
êtres humains, humanité, l’humain	l’homme, les hommes	Replace gendered humanity term with neutral form
le lectorat	les lecteurs	Replacing the masculine “le lecteur” with the neutral “le lectorat”
les journalistes	le ou la journaliste	Using the plural “les” instead of the gendered articles “le” and “la”
spécialiste	spécialisé or spécialisée	Using an epicene adjective instead of a gendered one
Êtes-vous de citoyenneté canadienne?	Êtes-vous citoyen canadien?	Using impersonal phrasing instead of gendered phrasing
gestion de l’approvisionnement	il ou elle devra gérer l’approvisionnement	Using a noun phrase instead of a gendered phrase

Strategies for generalization:

• Use plural noun forms (personnes, individus, étudiants, etc.).
• Don’t use gendered pronouns (elle, il, etc.) in generic references. Rewrite to use the indefinite pronoun “on” or the plural first or second person “nous,” “vous.”
• Rewrite the sentence to have a plural noun and pronoun.
• Use “la personne” or “l’individu.”

Use this (English)	Not this (English)	Use this (French Canada)	Not this (French Canada)
A user with the appropriate rights can set other users’ passwords.	If the user has the appropriate rights, he can set other users’ passwords.	Les utilisateurs ayant le niveau d’accès approprié peuvent modifier les mots de passe d’autres utilisateurs.	Si l’utilisateur a le niveau d’accès approprié, il a la capacité de modifier les mots de passe d’autres utilisateurs.
Developers need access to servers in their development environments, but they don’t need access to the servers in Azure.	A developer needs access to servers in his development environment, but he doesn’t need access to the servers in Azure.	Les développeurs doivent avoir accès aux serveurs dans leurs environnements de développement, mais n’ont pas besoin d’accéder aux serveurs dans Azure.	Un développeur doit avoir accès aux serveurs dans son environnement de développement, mais il n’a pas besoin d’accéder aux serveurs dans Azure.
When the author opens the document….	When the author opens her document….	Lorsque la personne qui rédige ouvre le document…	Lorsque le rédacteur ouvre son document…
To call someone, select the person’s name, select Make a phone call, and then choose the number you’d like to dial.	To call someone, select his name, select Make a phone call, and then select his number.	Pour appeler quelqu’un, sélectionner le nom de la personne, sélectionnez Passer un appel téléphonique, puis choisissez le numéro que vous souhaitez composer.	Pour appeler quelqu’un, sélectionnez son nom, sélectionnez Passer un appel téléphonique, puis sélectionnez son numéro.

When writing about a real person, use the pronouns the person prefers — il, elle, iel, or another pronoun. It’s OK to use gendered pronouns when writing about real people who use those pronouns themselves.

When the subject of a sentence is a product, brand, or company, avoid using a specific gender:

en-US source	fr-CA source
Benefits for Microsoft?	(+) Quels seraient les avantages pour Microsoft? (-) Quels avantages Microsoft pourrait-elle en tirer?

Note: Gender-neutral language should be used in new products and content going forward, but it’s acceptable not to update all existing or legacy material.

Accessibility¶

Focus on people, not disabilities. Don’t use words that imply pity, such as “victime de” or “souffrant de.” The preferred option is not to mention a disability unless it’s relevant.

Use this (English)	Not this (English)	Use this (French Canada)	Not this (French Canada)
person with a disability	handicapped	personne en situation de handicap, personne vivant avec un handicap	un handicapé, une handicapée
person without a disability	normal person; healthy person	personne n’ayant aucune déficience, personne non handicapée	personne normale, un non-handicapé or une non-handicapé

Use generic verbs that apply to all input methods and devices. In procedures and instructions, avoid verbs that don’t make sense with alternative input methods used for accessibility.

Use this (English)	Not this (English)	Use this (French Canada)	Not this (French Canada)
Select	Click	Sélectionnez	Cliquez

Keep paragraphs short and sentence structure simple — aim for one verb per sentence. Read text aloud and imagine it spoken by a screen reader.

Spell out words like “et,” “plus,” and “environ.” Screen readers can misread text that uses special characters like the ampersand (&), plus sign (+), and tilde (~).

Why this matters: Accessible translation directly affects healthcare equity (screen-reader-friendly patient materials reach visually-impaired patients), corporate compliance (most large clients now require WCAG conformance for translated content), legal accessibility (consumer-facing legal documents must be navigable by assistive tech in Canada), and government translation (federal accessibility standards apply across all bilingual content).

Language-specific standards¶

Abbreviations¶

You might need to abbreviate some words in the UI (mainly button or option names) due to lack of space. Rules:

• Regular abbreviations shorten a word by three or more letters and end with periods (see below for exceptions). Abbreviate only after a consonant or cluster of consonants. Example: supplement > suppl.
• Plural abbreviations do not take an “s” in Canadian French. Example: des URL, 200 Mo

List of common abbreviations:

Expression	Acceptable abbreviation
article	art.
bits par seconde	bps
chapitre	chap.
deuxième, troisième	2e, 3e
exemple	ex.
gigaoctet	Go
heure	h
kilobits par seconde	kbps
kilohertz	kHz
kilo-octet	Ko
mégabits par seconde	mbps
mégahertz	MHz
mégaoctet	Mo
monsieur	M.
million	Mio*
minute	min
numéro	no
premier, première	1er, 1re
reportez-vous à	cf.
référence numéro	réf. no

* It is recommended to use the abbreviation M when it is used with another symbol (M$) and to not use an abbreviation otherwise. If Mio must be used, then it would be necessary to write it next to the long form of million before using it alone. Example: million (Mio).

Don’t abbreviate such words as pouce, pica, point, pied, and pixel.

Acronyms¶

Acronyms are words made up of the initial letters of major parts of a compound term — WYSIWYG, DNS, HTML.

• Write acronyms in capital letters, without periods or spaces.
• Acronyms do not agree in number.
• In Canadian French, do not capitalize a spelled-out term beyond the first substantive.
• When the acronym can be pronounced as a proper name, it is permissible to write it in lower case with an initial capital (e.g. Unesco, Opep).
• Some acronyms, having become common nouns, are treated as such (e.g. ovni, laser).

Localized acronyms — when acronyms are localized, which does not happen often, they take the gender of the first substantive.

en-US source	fr-CA target
DTP	la PAO (Publication assistée par ordinateur)
DBMS	le SGBD (Système de gestion de base de données)

Unlocalized acronyms — if an acronym must remain in English throughout a manual, write its full name in Canadian French in normal style the first time it occurs, followed in parentheses by the acronym and its full spelling in English in italics.

Example: Si cette application gère l’échange dynamique de données (DDE, Dynamic Data Exchange) ou la liaison et l’incorporation d’objets (OLE, Object Linking and Embedding), vous pouvez également y coller avec liaison un document graphique.

Why this matters: In technical/IT translation acronym handling determines whether downstream readers can search for terms — DDE must remain searchable for technical users while still being introduced in French for general readers. In medical translation, acronyms like ECG, IRM, IV must follow Canadian French conventions distinct from European French (e.g., RM vs. IRM). In legal translation acronyms in contracts are often defined terms with binding meaning — wrong gender or wrong introduction can render a defined-term clause ambiguous.

Adjectives¶

In Canadian French, adjectives take masculine/feminine and singular/plural forms according to the noun they relate to. They are commonly placed after this noun. Be careful not to use too many adjectives in a row.

Articles¶

Definite articles are far more often used in Canadian French than in English. Avoid indefinite articles whenever possible.

Possessive adjectives: The frequent use of possessives is a feature of English. In Canadian French, possessive adjectives should be avoided whenever possible. Prefer definite forms.

en-US source	fr-CA target
Select a file to convert.	(+) Sélectionnez le fichier à convertir.

Unlocalized feature names: Microsoft product names and non-translated feature names are used without definite or indefinite articles in English. Treat them this way in Canadian French as well.

en-US source	fr-CA target
Download Microsoft Office	Télécharger Microsoft Office

Localized feature names: Translated feature names are handled like any Canadian French name — with the appropriate article.

en-US source	fr-CA target
About Calculator	À propos de la Calculatrice

Articles for English borrowed terms: When faced with an English loan word previously used in products, consider:

• Motivation. Does the English word have any formally motivated features that allow integration into the noun class system? Is the word derived from another word that is kept in English and whose article is already adopted? Is there a part of the word that already exists in Canadian French?
• Analogy. Is there an equivalent Canadian French term whose article could be used?
• Frequency. Is the term used in other technical documentation? If so, what article is used most often?

en-US source	fr-CA target
Enter a valid URL.	Entrez une URL valide.

Capitalization¶

As a general rule, only proper nouns and the first word of a sentence are capitalized. Exceptions exist (e.g., legal terms in a contract). The first word of a title or compound noun must also be capitalized.

Compounds¶

Compounds should be understandable and clear. Avoid overly long or complex compounds — they diminish usability.

Plural rules for compounds:

1. When two nouns are in apposition, both nouns must be plural. - des lettres types - des fenêtres parentes / des fenêtres enfants - des applications clientes - des fichiers sources / des fichiers cibles

2. If the two nouns are complements, only the first one is plural. - des serveurs passerelle - des tables système - des imprimantes couleur - des raccourcis clavier - des fichiers système - des fichiers texte - des connexions réseau - des installations réseau

Conjunctions¶

Some specific conjunctions in modern Canadian French translation can be used rather than others to help convey a conversational tone. Some others are too formal and should be avoided.

Old use of conjunctions	New use of conjunctions
de même que	comme
lors de	durant/pendant
auquel cas	avoid using this conjunction
lorsque/une fois que	quand
de sorte que / de (telle) façon que	pour, afin de
sitôt que	dès que
par conséquent / d’où	ainsi
parce que / vu que / à cause de	car
jusqu’au moment où	jusqu’à ce que
en dépit de	malgré
sauf que	sauf si
si jamais	si
après que / maintenant que	une fois…, une fois que
sans ça / sans cela	sinon

Why this matters: Stiff conjunctions are one of the most common indicators of “translated French.” In marketing translation, “lorsque” reads as a manual; “quand” reads as conversation. In medical patient instructions, “par conséquent” reads as legalese; “ainsi” lands naturally. In software UI strings, “sitôt que” is dated; “dès que” matches contemporary usage. These swaps cost nothing and visibly improve register.

Localizing colloquialism, idioms, and metaphors¶

Modern Canadian French translation allows for the use of culture-centric colloquialisms, idioms, and metaphors. Choose from the following options to express the intent of the source text appropriately:

• Do not attempt to replace the source colloquialism with a Canadian French colloquialism that fits the same meaning unless it is a perfect and natural fit for the context.
• Translate the intended meaning of the colloquialism (as opposed to literally translating the original), but only if the meaning is integral to the text and can’t be omitted.
• If the colloquialism can be omitted without affecting the meaning of the text, omit it.

en-US source	fr-CA target
We’ve hit a snag…	Not casual, and no slang: Nous avons rencontré un problème…
Uploads are limited to 100MB. Got something smaller?	Les téléchargements étant limités à 100 Mo, merci d’utiliser une taille de fichier plus petite.
Bummer…	Do not translate and delete.
Working on it… Bear with us. Note: This generic string is displayed when there is something happening on SharePoint that takes longer than a second.	Cette tâche est presque terminée… / Nous avons bientôt terminé… Merci de patienter.
Warm up your fingers—it’s time to enter the product key.	Entrez maintenant la clé de produit.
Drum roll…	Fin de l’installation
Yay! The wait is over.	Vous pouvez passer à l’étape suivante.

Nouns¶

Canadian French tends to use more nouns than English.

en-US source	fr-CA target
How to use Microsoft Office	Utilisation de Microsoft Office

Plural formation: Unlike English, adjectives in Canadian French take plural forms according to the noun. Compound plural rules are inconsistent — check your dictionary if in doubt.

Numbers¶

When to use numerals vs. spell out numbers:

• Numbers below 10 should usually be written out in Canadian French, except if there are other numbers in the same sentence.

Examples:

• “La mise à niveau vers la version 10.1 prendra 4 à 9 minutes.” (mixed with numerals → keep as numerals)
• “Le temps de chargement est estimé à neuf secondes.” (no other numerals → spell out)

Prepositions¶

Be aware of proper preposition use in translations. Many translators, influenced by English, omit them or change the word order. For modern conversational tone, starting or ending a sentence with a preposition is acceptable practice.

Source text expression	Canadian French expression	Comment
Due to…	En raison de…	Using “Dû à” at the beginning of a sentence is incorrect.
Specific to	Propre à / Spécifique de	“Spécifique à” is incorrect.
Log in / Log out	Se connecter / Se déconnecter	Always pay attention to prepositions like “in” and “out,” “to” and “from,” because a misreading can lead to the opposite meaning.

Pronouns¶

When addressing users, avoid using “on” and always use the masculine singular form of “vous.”

en-US source	fr-CA target
Do you want to delete this file?	Voulez-vous supprimer ce fichier?

Punctuation¶

Punctuation plays a supportive role; it isn’t a substitute for good word choice.

Basic rules:

• Do not use semicolons. Two shorter sentences are better and easier to read.
• Don’t systematically reuse exclamation marks as in the source. Use stronger words instead.
• Question marks — use judiciously. They work well when a link is phrased as a customer question.
• Parentheses give a noticeable whisper.

An em dash is used to demarcate an isolated element or to introduce an item that is not essential to the meaning of the sentence. In Canadian French, replace the em dash with a period, comma, or parentheses.

Bulleted lists¶

If the bulleted items are complete sentences, each begins with a capital and ends with a period.

Example:

Vous pouvez obtenir plus d’informations dans les chapitres suivants de cette deuxième partie. - Le chapitre 6 traite des lettres types. - Le chapitre 7 traite des étiquettes et autres documents à fusionner.

If the bulleted items continue an introductory clause, each begins with a lower case letter and ends with a semicolon, except the last, which ends with a period.

Example:

Vous avez le choix entre les options suivantes : - alignement contre la marge gauche; - alignement contre la marge droite; - centrage entre les deux marges.

Comma¶

In a series of three or more elements with similar grammatical function, separate the elements with commas. When one of the conjunctions et, ou, or ni joins the last two elements in a series, do not use a comma before the conjunction.

Example: (+) Le chapitre 5 traite des fichiers, dossiers et répertoires.

If the elements do not have the same grammatical function, a comma precedes et, ou, or ni.

Example: (+) J’ai acheté un ordinateur, et un système d’exploitation y était déjà installé.

Use commas to set off explanatory clauses and appositives.

Example: (+) Vous devez ouvrir le fichier principal, c’est-à-dire le premier de la liste.

Colon¶

Use colons to introduce lists and explanations. You may use a colon at the end of an introductory phrase even if it is not a complete sentence.

Do not capitalize the word following a colon unless (1) the colon is at the end of a heading or (2) the text following the colon is a complete quotation.

Examples: - (+) Vous avez ouvert deux fichiers : le fichier source et le fichier cible. - (+) Le logiciel est offert sur plusieurs appareils : Mac, PC, tablette et téléphone. - (+) Microsoft déclare : « Le succès est au rendez-vous! ».

Do not use colons to introduce only one idea.

US English	Canadian French target
Click on: File	(+) Cliquez sur Fichier. / (-) Cliquez sur : Fichier.

Dashes and hyphens¶

Three different dash characters exist:

Hyphen (trait d’union) — divides words between syllables, links parts of a compound word, and connects the parts of an inverted or imperative verb form.

Example: des fonctionnalités-clés, voulez-vous…

When a hyphenated compound should not be divided between lines (e.g., MS-DOS), use a non-breaking hyphen (CTRL+SHIFT+HYPHEN).

En dash (tiret demi-cadratin, ANSI 0150) — used as a minus sign, usually with spaces before and after.

Example: Salaire – 1 000 = 2 000

Also used in number ranges (page numbers). No spaces around the en dash in this case.

Em dash (tiret cadratin, ANSI 0151) — should only be used to emphasize an isolated element or introduce a non-essential element. In most cases where English uses dashes, commas or parentheses suffice in Canadian French.

US English	Canadian French target
Each table in your database should store facts about a single subject—about customers, for example, or products.	Chacune des tables de votre base de données devrait se limiter à un seul sujet, tel que clients ou produits, par exemple.

Ellipses (Suspension points)¶

Do not use three periods for suspension points in printed documentation. Use the ellipsis character … (ANSI 0133).

Rules:

• Omitted word — spaces before and after the ellipsis. Example: Je vous présente Monsieur … qui est agent secret.
• Omitted string of words — enclose the ellipsis in square brackets. Example: Il n’est pas nécessaire de lire tous les chapitres, […] pour comprendre le système.
• Beginning of a sentence — one space before the first word. Example: … PowerPoint aura tout fait pour vous.
• End of a word within a sentence with no words deleted (rare in documentation, more common in tutorials and callouts) — no space before the points, one space after. Example: Cliquez maintenant sur Suivant… … pour voir la suite de l’exercice.
• End of a sentence or paragraph — they also serve as the final period.
• Do not use suspension points after the word “etc.”

Period¶

Insert only one space after a period.

Use a period in all complete sentences — sentences with a conjugated verb. Do not use a period in a software string without a conjugated verb.

US English	Canadian French target
Deleting files.	Suppression de fichiers

Quotation marks¶

Use Canadian French quotation marks « », guillemets ouvrants and fermants, in both software and documentation.

Non-breaking spaces (CTRL+SHIFT+SPACEBAR or Alt+0160) should be used between the chevrons and the quoted text. Punctuation marks that do not belong to the quoted text are always placed outside the quotation marks in Canadian French.

Examples: - (+) Vider le dossier « <0s#25> » - (+) Pour plus d’informations sur les états, voir le chapitre 7, « États, bilans et rapports », dans lequel vous trouverez tous les détails nécessaires. - (+) Pour plus d’informations, voir le chapitre 2, « Notions de base de l’application ».

English quotation marks are used only in:

1. When needed to match software functionality (code).
2. In developer documentation and software (e.g. Visual Studio) per SPM request.
3. For nested quotations — a quotation within a quotation uses English double quotation marks (‘’…’‘).

Example: Le commandant poursuit alors : « Je n’irai pas jusqu’à vous promettre comme Churchill ‘’du sang, de la sueur et des larmes’‘, mais je dois vous convier plutôt à l’effort qu’à la facilité. »

In US source strings, software references may be surrounded by English quotation marks. Do not copy this US practice — in Canadian French, just remove the quotation marks.

US English	Canadian French target
Click the “Delete” button to delete the selected item.	Cliquez sur le bouton Supprimer pour supprimer l’élément sélectionné.

Parentheses¶

In both English and Canadian French, there is no space between the parentheses and the text inside them.

Spaces¶

Unlike European French, semi-colons, exclamation marks, and question marks are not preceded by a nonbreaking leading space. Use a leading space before colon.

Why this matters: Punctuation differences between Canadian and European French are subtle but identity-marking. In government and legal Canadian French the absence of leading space before “?” / “!” / “;” is a hallmark of authentic Canadian usage; copying European French spacing flags translations as foreign. In marketing brand voice, punctuation consistency is a baseline quality signal. In software UI, mixed spacing rules within one product create visible inconsistency.

Split infinitive¶

Do not translate split infinitives literally. Use periphrases or explicit verbs to express the meaning.

US English	Canadian French target
We expect our output to more than double this year.	Cette année, nos résultats devraient doubler, au minimum.

Subjunctive¶

Subjunctive constructions in Canadian French are complicated. Avoid them as much as possible. Use active voice and indicative or imperative instead.

US English	Canadian French target
Click here so that you can view this page.	Cliquez ici pour visualiser cette page.

Symbols and nonbreaking spaces¶

Whenever there is a symbol in English, keep it in Canadian French, particularly when dealing with statements.

Example: Tapez un signe moins (–) après la parenthèse.

Use non-breaking spaces:

• Between chapitre or annexe and its number or letter.
• As a thousand separator.
• Between a unit of measure or currency and the number that goes with it.
• Between any items that should not be divided onto separate lines.

Examples: - (+) Chapitre 1 : Installation (nbsp before “1” and before “:”) - (+) 5 000 € (nbsp after “5” and before “€”)

Note: Nonbreaking spaces sometimes cause problems in the generation of the final documents. Nonbreaking spaces should not be used in online help and documentation live content.

Syntax¶

Anacoluthon — when the structure of a sentence is broken such that the sentence begins with one subject and unexpectedly ends with another. In standard French it is a grammar mistake but more common in English, so the translator must adjust the structure.

Language	Example
English	Please install the latest Skype version on your computer. Once installed, the user will have access to the newly added features
French	Veuillez installer la dernière version de Skype sur votre ordinateur. Une fois celle-ci installée, l’utilisateur peut accéder aux nouvelles fonctions.

(Note: a subject must be introduced in the second sentence to show the past participle is not related to the second subject “l’utilisateur.”)

According to / Depending on — a common mistake is translating « according to / depending on » as « selon » at the beginning of a sentence and keeping the same structure afterwards. In French, when a sentence is introduced by « selon », you expect at least two choices.

Variant	Sentence
English	According to/Depending on your user rights, you might be able to access those files
Wrong	Selon vos droits d’accès, vous pouvez accéder à ces fichiers
Right	Si vous disposez des droits d’accès adéquats, vous pourrez accéder à ces fichiers

If keeping « selon », say: « Selon vos droits d’accès, vous pouvez accéder ou non à ces fichiers. » — but the first solution flows better.

Verbs¶

Verb tense helps convey clarity. Simple tenses are easiest to understand — the simple present is the default. Avoid future tense unless describing something that will really happen in the future and simple present is inapplicable. Use simple past tense when describing events that have already happened.

Use simple past tense (passé composé) when describing events that already happened, and only use complex tenses (plus-que-parfait, futur antérieur) when required by basic grammar rules.

Avoid tenses that sound too formal — passé simple, past subjunctive, etc. Use verb tenses you would use in normal conversation while still applying basic rules of concordance des temps.

Localization considerations¶

Accessibility programs¶

Accessibility options are designed to make the computer usable by people with cognitive, hearing, physical, or visual disabilities. Some accessible products may not be available in French-speaking markets — double-check with appropriate resources. General accessibility information: https://www.microsoft.com/fr-ca/accessibility/.

Applications, products, and features¶

Application/product names are often trademarked or may be trademarked in the future, so they are rarely translated. Occasionally feature names are trademarked too (e.g. IntelliSense™). Before translating any application, product, or feature name, verify it is in fact translatable and not protected.

Version numbers always contain a period (e.g. Version 4.2). Version numbers are usually part of version strings, but technically they are not the same.

Translation of version strings — version strings containing copyright information should always be translated.

US English	Canadian French target
© 2024 Microsoft Corporation. All rights reserved.	Refer to authoritative terminology to check the correct translations of “All rights reserved” and “Microsoft Corporation.”

Copilot predefined prompts¶

Copilot prompts are the instructions or questions used to tell Copilot what to do — create or edit content, ask questions, summarize information, catch up on things. Across products, predefined prompts guide users in creating, learning, and using Copilot.

Best practices for the localization of Copilot predefined prompts:

Copilot prompts are functional — translations must be accurate, consistent, concise, natural, and use the appropriate tone of voice. Translation quality significantly influences Copilot responses.

• Be clear and specific. English prompts are generally questions or requests starting with an action verb. Make sure target prompts are natural questions or requests. Avoid vague language. Use clear and specific phrases or keywords.
• Keep it conversational. Be consistent with voice principles. Use simple, natural language. Avoid adopting a machine-like tone. Use “Tu” and not “Vous” as the prompts model the tone users are expected to use in their requests to Copilot.
• Be polite and professional. Use kind and respectful language — this fosters collaboration and improves AI responsiveness. Don’t use slang and jargon.
• Use quotation marks. Helps Copilot know what to write, modify, or replace.
• Pay attention to punctuation, grammar, and capitalization. Clear communication helps collaboration.
• Pay attention to placement of entity tokens. An entity token is a placeholder that triggers a pop-up menu in the UI for the customer to choose an entity (file, contact, meeting). The position of the entity token should make sense in the target text syntax.
• Entity token localization exception. Some prompts may be a display text (an example) — in such cases the entity token needs to be translated. Read the Dev comment carefully. Example: Source string: List key points from [file], DevComment=Translate [file].
• Be consistent. Some English prompts are remarkably similar. Translate them consistently.

Source prompt	Target prompt
List ideas for a fun remote team building event	Donne-moi des idées pour un événement de consolidation d’équipe distanciel amusant
What are the goals and topics from the meeting? Format each section with a bolded heading, a bulleted list, and bolded names	Quels sont les objectifs et les sujets de la réunion ? Mets en forme chaque section avec un titre en gras, une liste à puces et des noms en gras.
Propose a new introduction to <entity type='file'>file</entity>	Propose une nouvelle introduction pour le <entity type='file'>fichier</entity>
What were the open issues from <entity type='meeting'>meeting</entity>?	Quels étaient les problèmes en suspens dans la <entity type='meeting'>réunion</entity>?
Give me ideas for icebreaker activities for a new team	Donne-moi des idées d’activités brise-glace pour une nouvelle équipe
Create a list of <placeholder>color names inspired by the ocean</placeholder>	Crée une liste de <placeholder>noms de couleurs inspirés de l'océan</placeholder>

Why this matters: Copilot prompt translation is a new and growing translation specialty. Unlike standard UI strings, prompts are functional — they shape downstream LLM behavior. A poorly-translated prompt produces poorer Copilot output for that locale. This affects enterprise productivity (Copilot is now embedded in Office, Teams, Windows), healthcare AI deployments (clinical documentation copilots increasingly use predefined prompts), and legal AI tools (drafting assistants use prompt scaffolding). Translators working in this space need to understand prompt engineering basics, not just linguistic equivalence.

Trademarks¶

Trademarked names and the name Microsoft Corporation should not be localized unless local laws require translation and an approved translated form is available. Microsoft trademark list: https://www.microsoft.com/en-us/legal/intellectualproperty/trademarks.

Software considerations¶

General guidelines:

• Clarity and simplicity are key.
• Be as short as possible. Avoid unnecessary words.
• Keep in mind different devices, sizes, and formats are used, and UI should fit all of them.
• Try to achieve cross-platform consistency in products used on desktop, mobile, and cloud.

Every principle below may have an exception based on the product, specific experience, and customer. Interpret guidelines for the best customer experience.

Arrow keys¶

The arrow keys move input focus among controls within a group. Pressing the right arrow key moves input focus to the next control in tab order; left arrow moves to the previous control. Home, End, Up, Down also have expected behavior within a group. Users can’t navigate out of a control group using arrow keys.

Error messages¶

Error messages inform the user of an error that must be corrected for the program to continue. Apply voice principles to ensure target translation is natural, empathetic, and not robot-like.

English term	Correct Canadian French translation
That can’t be blank…	Ce champ ne peut pas être vide.
Not enough memory to process this command.	Mémoire insuffisante pour traiter cette commande.

Style rules for error messages:

• Use consistent terminology and language style — don’t just translate as they appear in the US product.
• Always use a period after an error message, regardless of whether it has a conjugated verb. Exception: strings ending with a placeholder follow US punctuation if you don’t know what will replace the placeholder at runtime.
• Avoid parentheses as much as possible.

Standard phrases in error messages:

English	Translation	Example	Comment
Cannot … / Could not …	Impossible de	Impossible de télécharger le fichier.	Avoid “Le fichier ne peut pas être téléchargé.”
Failed to … / Failure of …	Échec du / Échec de	Échec du téléchargement du fichier.	Avoid “Le téléchargement du fichier a échoué.”
Cannot find … / Could not find … / Unable to find … / Unable to locate …	…introuvable	Fichier introuvable.	Avoid “Impossible de trouver le fichier.”
Not enough memory / Insufficient memory / There is not enough memory / There is not enough memory available	Mémoire insuffisante	Mémoire insuffisante.	Avoid “Pas assez de mémoire disponible.”
… is not available / … is unavailable	n’est pas disponible	Le fichier n’est pas disponible.	Avoid “Le fichier est indisponible.”

Error messages containing placeholders: When localizing, try to find out what will replace the placeholder. This is necessary for the sentence to be grammatically correct.

• %d, %ld, %u, %lu means
• %c means
• %s means

Examples: - “Checking Web %1!d! of %2!d!” means “Checking Web of .” - “INI file “%1!-.200s!” section” means “INI file “” section.”

Why this matters: Error messages are read at moments of user frustration. A bureaucratic error message (“Le fichier ne peut pas être téléchargé”) sounds blame-shifting; “Impossible de télécharger le fichier” sounds factual. In medical software error message quality affects clinician decisions in time-pressured workflows. In financial software error messages have audit and compliance implications. In consumer software they are the highest-friction text the user reads.

Keyboard shortcuts¶

Some menu options, commands, or dialog boxes have underlined or highlighted letters — keyboard shortcuts that help users perform tasks more quickly.

Keyboard shortcuts special options	Usage: is it allowed?	Notes
“Slim characters,” such as I, l, t, r, f, can be used as keyboard shortcuts	yes	n/a
Characters with downstrokes (g, j, y, p, q) can be used as keyboard shortcuts	yes	Avoid setting keyboard shortcuts on letters with downstrokes like q and g. Only use them if no other letter is available.
Extended characters can be used as keyboard shortcuts	yes	Avoid setting keyboard shortcuts on letters with accents like é è ë ê à â and î. Only use them if no other letter is available.
An additional letter between brackets after item name can be used as a keyboard shortcut	yes	n/a
A number between brackets after item name can be used as a keyboard shortcut	yes	n/a
A punctuation sign between brackets after item name can be used as a keyboard shortcut	yes	n/a
Duplicate keyboard shortcuts when no other character is available	yes	This may need to be checked with SPM.
No keyboard shortcut when no more characters are available (minor options only)	yes	This may need to be checked with SPM.

Terminology:

Term	Usage
Access key	A letter or number the user types to access UI controls with text labels. Assigned to top-level controls so the user can use the keyboard to move through the UI quickly. Example: F in Alt+F. Most access keys are used with the Alt key.
Key tip	The letter or number that appears in the ribbon when the Alt key is pressed. In UI localization, the key tip is the last character after the “" character. Example: Home\H
Shortcut key	A key the user types to perform a common action without going through the UI. Shortcut keys are not available for every command. Example: Ctrl+N, Ctrl+V. Most shortcut keys use Ctrl. Ctrl+letter combinations and function keys (F1-F12) are usually the best choices.

Duplicate keyboard shortcuts are acceptable to avoid accessibility issues, but may need double-check with the subsidiary.

Keys¶

In English, references to key names appear in normal text (not in small caps).

Key names (English → Canadian French):

English key name	Canadian French key name
Alt	Alt
Backspace	Retour arrière
Break	Attn
Caps Lock	Verr maj
Ctrl	Control
Delete	Suppr
Down Arrow	Bas
End	Fin
Enter	Entrée
Esc	Échap
Home	Origine
Insert	Inser
Left Arrow	Gauche
Num Lock	Verr Num

Voice video considerations¶

For voice work, follow standard French pronunciation rules with Canadian phonological norms. Match the tone to context — instructional content uses a clear, helpful register; promotional content can be warmer.

Video voice checklist considerations:

• Pronunciation of English brand names — generally keep English pronunciation for product names (Microsoft, Windows, Office).
• Pace — Canadian French dubbing tends to run slightly slower than European French; budget time accordingly.
• Tone — should match content. Tutorials are friendly and patient; error/recovery content is reassuring; promotional content is energetic.

Reference materials¶

Use these references for orthography, grammar, and terminology when this guide doesn’t specify.

Normative references — adhere to these. When more than one solution is possible, consult other topics in this guide.

1. Le Trésor de la Langue Française Informatisé — atilf.atilf.fr. Free online comprehensive French dictionary.
2. Le Petit Robert — ROBERT, Paul, Paris: Dictionnaire Le Robert. Standard contemporary French dictionary.
3. Le Petit Larousse — Éditions Larousse. Standard contemporary French dictionary.
4. Le bon usage — GREVISSE, Maurice, Paris-Gembloux: Duculot. Standard French grammar reference.

Informative references — supplementary information, background, comparison.

1. Termium Plus — btb.termiumplus.gc.ca. Government of Canada terminology and linguistic data bank. Authoritative for Canadian government and legal terminology.
2. Le Grand Dictionnaire Terminologique — granddictionnaire.com. Office québécois de la langue française terminology bank.
3. Le Dictionnaire de l’Informatique — Microsoft Press, Paris. IT/computing terminology reference.

FAQ¶

Should I use ‘app’ or ‘application’ in Canadian French?¶

Always use “application” in running text — “app” is not standard in Canadian French. The short form “appli” is acceptable only when the source uses “app” and screen space is limited. The same rule applies to “info” (use “information” or “informations”) and “sync” (use “synchroniser” or “synchronisation” even when source uses the short form).

How do I address users in Canadian French translation?¶

Use “vous” (masculine singular form) for standard product, marketing, and documentation content. Never use the impersonal “on” when addressing users. The only exception is Copilot predefined prompts, where “tu” is preferred because prompts model how users speak to AI conversationally.

What’s the difference between Canadian and European French punctuation?¶

Canadian French does not put a nonbreaking space before semicolons, exclamation marks, or question marks — European French does. Canadian French does keep a leading space before a colon. Quotation marks « » still use nonbreaking spaces between the chevrons and the quoted text. The em dash is generally avoided in favor of comma, period, or parentheses.

How should I handle gendered language in Canadian French?¶

Default to gender-inclusive constructions: collective nouns (“le lectorat” instead of “les lecteurs”), epicene adjectives (“spécialiste” instead of “spécialisé/spécialisée”), plural articles (“les journalistes” instead of “le ou la journaliste”), and impersonal phrasing (“Êtes-vous de citoyenneté canadienne?” instead of “Êtes-vous citoyen canadien?”). Use il/elle only when writing about a specific real person who uses those pronouns. New content should be gender-neutral; legacy content may retain older forms.

Which authoritative references should I use for Canadian French translation?¶

Normative: Le Trésor de la Langue Française Informatisé (atilf.atilf.fr), Le Petit Robert, Le Petit Larousse, and Le bon usage by Grevisse. Informative supplements: Termium Plus (the Canadian government terminology bank), Le Grand Dictionnaire Terminologique (from OQLF), and Le Dictionnaire de l’Informatique by Microsoft Press.

How do I translate English colloquialisms like “We’ve hit a snag” or “Bummer”?¶

Don’t replace with a Canadian French colloquialism unless it’s a perfect natural fit. Translate the intended meaning (“Nous avons rencontré un problème” for “We’ve hit a snag”). If the colloquialism can be omitted without affecting meaning, omit it (“Bummer” is typically deleted). Avoid forced informality — overly casual French translations of English slang usually read as awkward.

What’s the rule for Canadian French keyboard shortcuts?¶

Avoid setting shortcuts on letters with downstrokes (g, j, y, p, q) and accented letters (é, è, ë, ê, à, â, î) when possible — use them only if no other letter is available. Duplicate shortcuts are acceptable when no other character is available but should be confirmed with the subsidiary. Most access keys use Alt; most shortcut keys use Ctrl. Ctrl+letter combinations and function keys (F1-F12) are best for shortcut keys.

Sources¶

• Microsoft Localization Style Guide for French (Canada) (PDF)
• Microsoft Globalization Style Guides hub
• Le Trésor de la Langue Française Informatisé
• Termium Plus — Government of Canada terminology bank
• Le Grand Dictionnaire Terminologique (OQLF)
• Microsoft Accessibility (Canada)