[vim/vim] Add French translation for Chapter 2 of the Vimtutor (PR #17546)

Damien Lejay

unread,

Jun 14, 2025, 7:33:04 AM6/14/25

to vim/vim, Subscribed

This PR does two things :

It fixes some small things in the tutor2 file (like >= that will appear funny when ligatures are turned on)
It provides a French translation for tutor2

You can view, comment on, or merge this pull request online at:

https://github.com/vim/vim/pull/17546

Commit Summary

a74c565 Fix some minor issues in tutor2
7918c29 Add French translation for tutor2

File Changes

(3 files)

Patch Links:

—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.

Christian Brabandt

unread,

Jun 15, 2025, 9:59:57 AM6/15/25

to vim/vim, Subscribed

@chrisbra commented on this pull request.

In runtime/tutor/tutor2:

> @@ -6,7 +6,7 @@
 
      Hic Sunt Dracones: if this is your first exposure to vim and you
      intended to avail yourself of the introductory chapter, kindly type
-     :q<enter> and try again.
+     :q<Enter> and try again.

Hm, tutor1 uses <ENTER>. I think we should stick to it. Also, the try again is a bit unhelpful. How about this instead:

⬇️ Suggested change

-     :q<Enter> and try again.
+     :q! <ENTER> and run vimtutor for Chapter 1 instead.

In runtime/tutor/tutor2:

> @@ -23,14 +23,14 @@
 
 MNEMONIC: into register(") named (a) (y)ank (i)nner (w)ord
 
-  3. Navigate forward to the word 'cookie' (fk or 2fc or $2b or /co<enter>)
+  3. Navigate forward to the word 'cookie' (fk or 2fc or $2b or /co<Enter>)

⬇️ Suggested change

-  3. Navigate forward to the word 'cookie' (fk or 2fc or $2b or /co<Enter>)
+  3. Navigate forward to the word 'cookie' (fk or 2fc or $2b or /co<ENTER>)

In runtime/tutor/tutor2:

>       and type   "byiw
 
-  4. Navigate to any point on the word 'Vince' and type   ciw<C-r>a<ESC>
+  4. Navigate to any point on the word 'Vince' and type   ciw<Ctrl-r>a<ESC>

⬇️ Suggested change

-  4. Navigate to any point on the word 'Vince' and type   ciw<Ctrl-r>a<ESC>
+  4. Navigate to any point on the word 'Vince' and type:   ciw<CTRL-R>a<ESC>

In runtime/tutor/tutor2:

>  
 MNEMONIC: (c)hange (i)nner (w)ord with <contents of (r)egister> named (a)
 
-  5. Navigate to any point on the word 'cake' and type   ciw<C-r>b<ESC>
+  5. Navigate to any point on the word 'cake' and type   ciw<Ctrl-r>b<ESC>

⬇️ Suggested change

-  5. Navigate to any point on the word 'cake' and type   ciw<Ctrl-r>b<ESC>
+  5. Navigate to any point on the word 'cake' and type:   ciw<CTRL-R>b<ESC>

In runtime/tutor/tutor2:

> @@ -40,8 +40,8 @@ NOTE: Delete also works into registers, i.e. "sdiw will delete the word under
 
 REFERENCE: 	Registers 	:h registers
 		Named Registers :h quotea
-		Motion 		:h motion.txt<enter> /inner<enter>
-		CTRL-R		:h insert<enter> /CTRL-R<enter>
+		Motion 		:h motion.txt<Enter> /inner<Enter>
+		CTRL-R		:h insert<Enter> /CTRL-R<Enter>

Similar here

In runtime/tutor/tutor2:

> @@ -54,10 +54,10 @@ REFERENCE: 	Registers 	:h registers
 
   2. Navigate to any point on the supplied number
 
-  3. Type ciw<C-r>=60*60*24<enter>
+  3. Type ciw<Ctrl-r> followed by  =60*60*24<Enter>

⬇️ Suggested change

-  3. Type ciw<Ctrl-r> followed by  =60*60*24<Enter>
+  3. Type ciw<CTRL-R> followed by:  =60*60*24<ENTER>

In runtime/tutor/tutor2:

>  
   4. On the next line, enter insert mode and add today's date with 
-     <C-r>=system('date')<enter>
+     <Ctrl-r> followed by  =system('date')<Enter>

same here and below

In runtime/tutor/tutor2:

>  
   1. Move the cursor to the line below marked --->
 
-  2. Go to the first line of the function and mark it with   ma
+  2. Go to the first line of the function and set mark (a) it with   ma

⬇️ Suggested change

-  2. Go to the first line of the function and set mark (a) it with   ma
+  2. Go to the first line of the function and set mark (a) with   ma

In runtime/tutor/tutor2:

>       in insert mode
 
   7. Inspect registers with   :reg
-  8. Learn the final destination of whole line deletions: dd in the numbered
-     registers, i.e. descending from register 1 - 9.  Appreciate that whole
-     line deletions are preserved in the numbered registers longer than any
-     other operation
+  8. Understand that whole-line deletions (with dd) are specially preserved in

⬇️ Suggested change

-  8. Understand that whole-line deletions (with dd) are specially preserved in
+  8. Understand that whole-line deletions (with dd) are preserved in

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.

Gabriel Dupras

unread,

Jun 15, 2025, 10:40:13 AM6/15/25

to vim/vim, Subscribed

gdupras left a comment (vim/vim#17546)

Bonjour,

tutor1, tutor2, and tutor1.fr all use the typewriter apostrophe '. For consistency, I think tutor2.fr should also use that apostrophe instead of the typographic apostrophe ’ that you have used.

https://en.wikipedia.org/wiki/Apostrophe

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.

Damien Lejay

unread,

Jun 15, 2025, 1:06:43 PM6/15/25

to vim/vim, Subscribed

@dlejay commented on this pull request.

In runtime/tutor/tutor2:

> @@ -6,7 +6,7 @@
 
      Hic Sunt Dracones: if this is your first exposure to vim and you
      intended to avail yourself of the introductory chapter, kindly type
-     :q<enter> and try again.
+     :q<Enter> and try again.

So... tutor1 uses <ENTER>, tutor2 uses <enter> and the help files use <Enter>?

Let's choose one standard and apply it everywhere.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.

Damien Lejay

unread,

Jun 15, 2025, 1:10:50 PM6/15/25

to vim/vim, Push

@dlejay pushed 1 commit.

7dc132d Update runtime/tutor/tutor2

—
View it on GitHub or unsubscribe.
You are receiving this because you are subscribed to this thread.

Gabriel Dupras

unread,

Jun 15, 2025, 2:18:17 PM6/15/25

to vim/vim, Subscribed

@gdupras commented on this pull request.

In runtime/tutor/tutor2.fr.utf-8:

> +  6. Insérer le résultat d’un appel système : <Ctrl-r>=system('ls -1')
+     en mode Insertion
+
+  7. Inspecter les registres avec   :reg
+  8. Apprendre pourquoi les suppressions de lignes entières (dd) sont préservées
+     plus longtemps : elles bénéficient des registres 1 à 9 et sont préservées
+     plus longtemps que toute autre opération
+  9. Apprendre la destination finale de toutes les copies dans les registres
+     numérotés et à quel point elles sont éphémères
+
+ 10. Placer des marques depuis le mode Normal   m[a-zA-Z0-9]
+ 11. Se déplacer ligne par ligne jusqu’à une marque avec   '
+
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+  Voilà, vous êtes arrivé à la find du chapitre deux du tutoriel de Vim. Il est

⬇️ Suggested change

-  Voilà, vous êtes arrivé à la find du chapitre deux du tutoriel de Vim. Il est
+  Voilà, vous êtes arrivés à la fin du chapitre deux du tutoriel de Vim. Il est

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.

Gabriel Dupras

unread,

Jun 15, 2025, 2:22:04 PM6/15/25

to vim/vim, Subscribed

@gdupras commented on this pull request.

In runtime/tutor/tutor2.fr.utf-8:

> +     c, 7, 4, 2, 8. i.e collez avec  "cp puis "7p puis etc. 
+
+---> 0. Ceci
+     9. zigzag
+     8. secret
+     7. est
+     6. on
+     5. axe
+     4. un
+     3. guerre
+     2. message
+     1. hommage 
+
+NOTE : Les lignes entièrement supprimées (via dd) restent beaucoup plus
+       longtemps dans les registres numérotés que les lignes copiées (via yy)
+       ou les suppressions impliquants des mouvements plus courts.

⬇️ Suggested change

-       ou les suppressions impliquants des mouvements plus courts.
+       ou les suppressions impliquant des mouvements plus courts.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.

Gabriel Dupras

unread,

Jun 15, 2025, 2:54:36 PM6/15/25

to vim/vim, Subscribed

@gdupras commented on this pull request.

In runtime/tutor/tutor2.fr.utf-8:

> +RÉFÉRENCES: 	Registers 	:h registers
+		Named Registers :h quotea
+		Motion 		:h motion.txt<Enter> /inner<Enter>
+		CTRL-R		:h insert<Enter> /CTRL-R<Enter>

Si on veut aussi traduire les sections « RÉFÉRENCES » :

⬇️ Suggested change

-RÉFÉRENCES: 	Registers 	:h registers
-		Named Registers :h quotea
-		Motion 		:h motion.txt<Enter> /inner<Enter>
-		CTRL-R		:h insert<Enter> /CTRL-R<Enter>
+RÉFÉRENCES: 	Registres 	 :h registers
+		Registres nommés :h quotea
+		Déplacements 	 :h motion.txt<Enter> /inner<Enter>
+		CTRL-R		 :h insert<Enter> /CTRL-R<Enter>

J’hésite entre « Déplacements » et « Mouvements ». Je crois que je préfère le premier.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.

Gabriel Dupras

unread,

Jun 15, 2025, 2:58:01 PM6/15/25

to vim/vim, Subscribed

@gdupras commented on this pull request.

In runtime/tutor/tutor2.fr.utf-8:

> +  3. Tapez  ciw<Ctr-r> suivi de  =60*60*24<Enter>
+
+  4. Sur la ligne suivante, en mode Insertion, ajoutez la date du jour avec
+     <Ctrl-r> suivi de  =system('date')<Enter>
+
+NOTE : Tous les appels système dépendent de votre système d’exploitation. Par
+      exemple sur MS-Windows, utilisez plutôt
+      system('date /t')   ou  :r!date /t
+
+---> Dans une journée, il y a 100 secondes.
+     Aujourd’hui, nous sommes :
+
+NOTE: on arrive au même résultat avec  :pu=system('date')
+      ou, plus court  :r!date
+
+RÉFÉRENCE : 	Expression Register 	:h quote=

⬇️ Suggested change

-RÉFÉRENCE : 	Expression Register 	:h quote=
+RÉFÉRENCE : 	Registre d'expressions 	:h quote=

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.

Gabriel Dupras

unread,

Jun 15, 2025, 2:59:36 PM6/15/25

to vim/vim, Subscribed

@gdupras commented on this pull request.

In runtime/tutor/tutor2.fr.utf-8:

> +---> 0. Ceci
+     9. zigzag
+     8. secret
+     7. est
+     6. on
+     5. axe
+     4. un
+     3. guerre
+     2. message
+     1. hommage 
+
+NOTE : Les lignes entièrement supprimées (via dd) restent beaucoup plus
+       longtemps dans les registres numérotés que les lignes copiées (via yy)
+       ou les suppressions impliquants des mouvements plus courts.
+
+RÉFÉRENCE : 	Numbered Registers 	:h quote0

⬇️ Suggested change

-RÉFÉRENCE : 	Numbered Registers 	:h quote0
+RÉFÉRENCE : 	Registres numérotés 	:h quote0

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.

Gabriel Dupras

unread,

Jun 15, 2025, 3:12:57 PM6/15/25

to vim/vim, Subscribed

@gdupras commented on this pull request.

In runtime/tutor/tutor2.fr.utf-8:

> +RÉFÉRENCE: 	Marks 		:h marks
+		Mark Motions 	:h mark-motions  (difference between ' and `)

⬇️ Suggested change

-RÉFÉRENCE: 	Marks 		:h marks
-		Mark Motions 	:h mark-motions  (difference between ' and `)
+RÉFÉRENCE: 	Marques 			 :h marks
+		Déplacements avec les marques	 :h mark-motions
+						 (différence entre ' et `)

Peut-être un peu long…

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.

Damien Lejay

unread,

Jun 16, 2025, 5:47:50 AM6/16/25

to vim/vim, Push

@dlejay pushed 1 commit.

5481eeb Fix typo

—
View it on GitHub or unsubscribe.

You are receiving this because you are subscribed to this thread.

Damien Lejay

unread,

Jun 16, 2025, 5:49:11 AM6/16/25

to vim/vim, Subscribed

@dlejay commented on this pull request.

In runtime/tutor/tutor2.fr.utf-8:

> +  6. Insérer le résultat d’un appel système : <Ctrl-r>=system('ls -1')
+     en mode Insertion
+
+  7. Inspecter les registres avec   :reg
+  8. Apprendre pourquoi les suppressions de lignes entières (dd) sont préservées
+     plus longtemps : elles bénéficient des registres 1 à 9 et sont préservées
+     plus longtemps que toute autre opération
+  9. Apprendre la destination finale de toutes les copies dans les registres
+     numérotés et à quel point elles sont éphémères
+
+ 10. Placer des marques depuis le mode Normal   m[a-zA-Z0-9]
+ 11. Se déplacer ligne par ligne jusqu’à une marque avec   '
+
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+  Voilà, vous êtes arrivé à la find du chapitre deux du tutoriel de Vim. Il est

Thanks for spotting the typo find.

For arrivé, I believe there will be only be one person going through the Vimtutor

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.

Damien Lejay

unread,

Jun 16, 2025, 5:51:00 AM6/16/25

to vim/vim, Push

@dlejay pushed 1 commit.

ee83edc Apply suggestions from code review

—
View it on GitHub or unsubscribe.

You are receiving this because you are subscribed to this thread.

Damien Lejay

unread,

Jun 16, 2025, 6:01:43 AM6/16/25

to vim/vim, Subscribed

@dlejay commented on this pull request.

In runtime/tutor/tutor2.fr.utf-8:

> +RÉFÉRENCES: 	Registers 	:h registers
+		Named Registers :h quotea
+		Motion 		:h motion.txt<Enter> /inner<Enter>
+		CTRL-R		:h insert<Enter> /CTRL-R<Enter>

J'aurais bien aimé traduire les sections « RÉFÉRENCES », mais vu que tous ces :h vont vers des pages en anglais, autant annoncer la couleur dès le départ et laisser le mot-clé en anglais.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.

Gabriel Dupras

unread,

Jun 16, 2025, 7:17:30 AM6/16/25

to vim/vim, Subscribed

@gdupras commented on this pull request.

In runtime/tutor/tutor2.fr.utf-8:

> +RÉFÉRENCES: 	Registers 	:h registers
+		Named Registers :h quotea
+		Motion 		:h motion.txt<Enter> /inner<Enter>
+		CTRL-R		:h insert<Enter> /CTRL-R<Enter>

Ces sections ont été traduites dans les autres langues (gl, it, ru et sr). Je ne vois pas pourquoi elles ne seraient pas traduites en français aussi. C’est la commande (p. ex. :h registers) qui annonce que la documentation sera en anglais.

Les autres versions ont même traduit les « MNEMONIC » !

D’ailleurs la documentation n’est pas forcément en anglais. Il y a plusieurs traduction sur la page ci-dessous mais la version française n’est plus disponible malheureusement. Peut-être qu’un jour quelqu’un la mettra à jour…

https://www.vim.org/translations.php

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.

Damien Lejay

unread,

Jun 16, 2025, 7:30:52 AM6/16/25

to vim/vim, Subscribed

dlejay left a comment (vim/vim#17546)

Bonjour,

tutor1, tutor2, and tutor1.fr all use the typewriter apostrophe '. For consistency, I think tutor2.fr should also use that apostrophe instead of the typographic apostrophe ’ that you have used.

https://en.wikipedia.org/wiki/Apostrophe

Bonjour,

While I was doing my due diligence to give a detailed answer, I updated my knowledge on the matter and I now have a new settled opinion. I will try to make this as easy to understand as possible for everybody.

This blog post from Ted Clancy (and the discussions) made me change my mind on the matter.

The vimtutor `tutor` files

The vimtutor tutor files are available in several encodings. The Makefile says :

# Use the UTF-8 version as the original and create the others with conversion..

So we need to discuss apostrophes within Unicode.

Apostrophes in encodings

We need to start with a little history, because legacy problems explain the messy state that we are in today.

The ASCII apostrophe

Because the ASCII table had limited available space, the ASCII char number 0x27 has historically had the role of :

the apostrophe ;
the opening single quote ;
the closing single quote.

Latin1

ASCII is a 7-bit encoding. To help write some Western Europe languages, it was extended into 8-bit encodings... by several people.

ISO/IEC 8859-1

The official latin1 famously fails to provide the French characters œ, Œ and Ÿ (here is an article from Jacques André that explains the whole historical drama).

It does not impact the usage of apostrophes.

Windows-1252 and Mac Roman

Microsoft and Apple also extended the 7-bit ASCII table into their own latin1 8-bit encoding, in an incompatible way with each other and with ISO.

Both added to the list both the opening single quote character and the closing single quote character.

Crucially, the famous MS-Word software started to do “smart” replacement of the character 0x27 with the closing single quote character on each platform :

on Windows-1252 with character 0x92 ;
on Mac Roman with character 0xD5.

because the typographic apostrophe has the same shape as a comma. The character 0x27 was rendered as straight, while the closing single quote war curly. So this trick achieved the desired visual result.

Unicode

Unicode extends ISO/IEC 8859-1 and is now the default encoding.
The standard introduced :

U+0027 named Apostrophe;
U+02BC named Modifier Letter Apostrophe ;
U+2019 named Right Single Quotation Mark.

The standard was explicitly designed so that ASCII 0x27 maps to U+0027 and so that both Windows-1252 0x92 and Mac Roman 0xD5 map to U+2019.

The recommended apostrophe character in Unicode

Now that historical facts have been recalled, we can delve into the politics. At first Unicode recommended the use of character U+02BC to represent the apostrophe. In version 2.1, the official recommendation was changed to U+2019.

Let's see why that is and what it means.

Orthographic words

Unicode characters can be assembled into words. Here a word is understood as an orthographic word instead of a grammatical one. For example the text :

Let's make America great again.

had 5 orthographic words, but 6 grammatical words.

Why Unicode recommended `U+02BC`

Unicode splits its characters general categories. For example, the character U+2019 is in the general category Pe (Punctuation, close).
Any character in that category is understood as characters that cannot make up words.
So when one writes “can’t” in Unicode, it is understood that there are two orthographic words.

Similarly, the character U+0027 is in the general category Po (Punctuation, other) so “can't” will also be understood as two orthographic words.

On the contrary, U+02BC is in the category Lm (Letter, modifier) and will be understood as a word character.

Why Unicode changed its recommendation to `U+2019`

The official documentation states that U+2019 is now recommended to make mapping from Windows and Mac systems easier. So it's basically because the software people use outputs U+2019 by default, that it becomes the recommended choice.

Effect on Vim and the Vimtutor

The difference between those three characters is probably most visible in Vim and especially in the Vim tutor.
Have a try at Vim motions w or e on the following file :

It won't work (U+0027)
It won’t work (U+2019)
It wonʼt work (U+02BC)

they will work “intuitively” only with U+02BC.

Actions and suggestions

For the tutor2.fr

I had the French tutor2 file filed with U+2019 because I simply followed the modern Unicode recommendation. I now believe the better choice is U+02BC, especially for the Vimtutor.

For the tutor1.fr

@RestorerZ commented on this pull request.

In runtime/tutor/tutor2:

> @@ -6,7 +6,7 @@
 
      Hic Sunt Dracones: if this is your first exposure to vim and you
      intended to avail yourself of the introductory chapter, kindly type
-     :q<enter> and try again.
+     :q<Enter> and try again.

So... tutor1 uses , tutor2 uses and the help files use ?

In the tutorial, I think it is better to capitalize key names.

It would also be nice to standardise on whether <Enter> (and all the other <...>) refer to the physical key or to a Unicode character.

:h key-notation
Although... it's not so clear-cut either.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.

Christian Brabandt

unread,

Jun 16, 2025, 2:32:23 PM6/16/25

to vim/vim, Subscribed

@chrisbra commented on this pull request.

In runtime/tutor/tutor2:

> @@ -6,7 +6,7 @@
 
      Hic Sunt Dracones: if this is your first exposure to vim and you
      intended to avail yourself of the introductory chapter, kindly type
-     :q<enter> and try again.
+     :q<Enter> and try again.

yes, I agree on this.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.

Damien Lejay

unread,

Jun 16, 2025, 4:26:43 PM6/16/25

to vim/vim, Subscribed

@dlejay commented on this pull request.

In runtime/tutor/tutor2:

> @@ -6,7 +6,7 @@
 
      Hic Sunt Dracones: if this is your first exposure to vim and you
      intended to avail yourself of the introductory chapter, kindly type
-     :q<enter> and try again.
+     :q<Enter> and try again.

So... tutor1 uses , tutor2 uses and the help files use ?

In the tutorial, I think it is better to capitalize key names.

It would also be nice to standardise on whether (and all the other <...>) refer to the physical key or to a Unicode character.

:h key-notation Although... it's not so clear-cut either.

Yes I have tried to find an answer in h key-notation and it was not very clear.

When you say that it is better to capitalize key names, which version are you referring to ? <ENTER> or <Enter> ?

And outside of the Vimtutor, what should one do ?

The lack of a standard bothers me more than any of the choices.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.

Christian Brabandt

unread,

Jun 17, 2025, 3:12:52 AM6/17/25

to vim/vim, Subscribed

@chrisbra commented on this pull request.

In runtime/tutor/tutor2:

> @@ -6,7 +6,7 @@
 
      Hic Sunt Dracones: if this is your first exposure to vim and you
      intended to avail yourself of the introductory chapter, kindly type
-     :q<enter> and try again.
+     :q<Enter> and try again.

Let's leave the help files out for now and just use a consistent naming between tutor 1 and tutor2, so use <ENTER>.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.

Restorer

unread,

Jun 17, 2025, 12:00:04 PM6/17/25

to vim/vim, Subscribed

@RestorerZ commented on this pull request.

In runtime/tutor/tutor2:

> @@ -6,7 +6,7 @@
 
      Hic Sunt Dracones: if this is your first exposure to vim and you
      intended to avail yourself of the introductory chapter, kindly type
-     :q<enter> and try again.
+     :q<Enter> and try again.

When you say that it is better to capitalize key names, which version are you referring to ? <ENTER> or <Enter> ?

<ENTER> in tutor*

And outside of the Vimtutor, what should one do ?

An existing style in the Vim documentation <Enter>

The lack of a standard bothers me more than any of the choices.

This is a long-known weakness and at the same time a strength of open source.
If in the Enterprise sphere someone writes procedures first, and then everyone does everything according to these procedures without deviating a step. But in a community it is often the opposite.
On the other hand, you have a unique opportunity to create this standard right now.
Describe that tutorials like “vimtutor” use the <ENTER> style for key names, and the <Enter> style in the program documentation. And the community, if it accepts that, will follow that standard.

—
Reply to this email directly, view it on GitHub, or unsubscribe.

You are receiving this because you are subscribed to this thread.

Damien Lejay

unread,

Jun 17, 2025, 12:26:20 PM6/17/25

to vim/vim, Subscribed

@dlejay commented on this pull request.

In runtime/tutor/tutor2:

> @@ -6,7 +6,7 @@
 
      Hic Sunt Dracones: if this is your first exposure to vim and you
      intended to avail yourself of the introductory chapter, kindly type
-     :q<enter> and try again.
+     :q<Enter> and try again.

Thanks, it's now much more clear which end result is suggested.

@RestorerZ May I now ask why you prefer <ENTER> for the tutor ?

—
Reply to this email directly, view it on GitHub, or unsubscribe.

You are receiving this because you are subscribed to this thread.

D. Ben Knoble

unread,

Jun 17, 2025, 12:50:08 PM6/17/25

to vim/vim, Subscribed

@benknoble commented on this pull request.

In runtime/tutor/tutor2.fr.utf-8:

> +RÉFÉRENCES: 	Registers 	:h registers
+		Named Registers :h quotea
+		Motion 		:h motion.txt<Enter> /inner<Enter>
+		CTRL-R		:h insert<Enter> /CTRL-R<Enter>

À voire/MàJ aussi Where are the French help files?

—
Reply to this email directly, view it on GitHub, or unsubscribe.

You are receiving this because you are subscribed to this thread.

Restorer

unread,

Jun 17, 2025, 1:11:07 PM6/17/25

to vim/vim, Subscribed

@RestorerZ commented on this pull request.

In runtime/tutor/tutor2:

> @@ -6,7 +6,7 @@
 
      Hic Sunt Dracones: if this is your first exposure to vim and you
      intended to avail yourself of the introductory chapter, kindly type
-     :q<enter> and try again.
+     :q<Enter> and try again.

Neither you nor I know what kind of training the person taking the training course has. It could be an experienced user or a complete beginner.
And writing keys in uppercase is more visual and makes you realize that it is not part of the previous command you were asked to type on the keyboard.
Note that it is suggested to use uppercase only for the so-called "gray keys", i.e. <Enter>, <Ctrl>, <Shift> and so on. Since there is a difference between <a> and <A> in the Vim editor. Which is, however, explained here: :h CTRL-{char}

—
Reply to this email directly, view it on GitHub, or unsubscribe.

You are receiving this because you are subscribed to this thread.

Damien Lejay

unread,

Jun 17, 2025, 1:29:12 PM6/17/25

to vim/vim, Subscribed

@dlejay commented on this pull request.

In runtime/tutor/tutor2:

> @@ -6,7 +6,7 @@
 
      Hic Sunt Dracones: if this is your first exposure to vim and you
      intended to avail yourself of the introductory chapter, kindly type
-     :q<enter> and try again.
+     :q<Enter> and try again.

As an additional note, the greeting message that most people see the very first time they use Vim, tells them how to quit Vim with

type  :q<Enter>               to exit

—
Reply to this email directly, view it on GitHub, or unsubscribe.

You are receiving this because you are subscribed to this thread.

Restorer

unread,

Jun 17, 2025, 1:44:12 PM6/17/25

to vim/vim, Subscribed

@RestorerZ commented on this pull request.

In runtime/tutor/tutor2:

> @@ -6,7 +6,7 @@
 
      Hic Sunt Dracones: if this is your first exposure to vim and you
      intended to avail yourself of the introductory chapter, kindly type
-     :q<enter> and try again.
+     :q<Enter> and try again.

That's right. Program messages are a kind of part of documentation. And that is why, to make it clear to any user, it is described in lesson 1.1.2. how to exit the program.

—
Reply to this email directly, view it on GitHub, or unsubscribe.

You are receiving this because you are subscribed to this thread.

Christian Brabandt

unread,

Jun 17, 2025, 2:42:05 PM6/17/25

to vim/vim, Subscribed

@chrisbra commented on this pull request.

In runtime/tutor/tutor2:

> @@ -6,7 +6,7 @@
 
      Hic Sunt Dracones: if this is your first exposure to vim and you
      intended to avail yourself of the introductory chapter, kindly type
-     :q<enter> and try again.
+     :q<Enter> and try again.

I have one small personal grievance with the all-caps version : when I see I always think instinctively ctrl+shift+r

Traditionally, this did not make a difference at least from where vim originates. Only recently xterm and kitty (and other more modern terminal emulators) are able to distinguish Ctrl-r from Ctrl-R using the xterm-modify-keys and kitty terminal protocol. But on a serial console like terminal, there is still no difference.

—
Reply to this email directly, view it on GitHub, or unsubscribe.

You are receiving this because you are subscribed to this thread.

Damien Lejay

unread,

Jun 18, 2025, 11:57:58 AM6/18/25

to vim/vim, Push

@dlejay pushed 1 commit.

e35c1b8 Add suggestions by reviewers

—
View it on GitHub or unsubscribe.
You are receiving this because you are subscribed to this thread.

Damien Lejay

unread,

Jun 18, 2025, 12:07:54 PM6/18/25

to vim/vim, Push

@dlejay pushed 1 commit.

c85e448 Apply changes of the previous commit to .fr accordingly

—
View it on GitHub or unsubscribe.

You are receiving this because you are subscribed to this thread.

Gabriel Dupras

unread,

Jun 18, 2025, 1:14:54 PM6/18/25

to vim/vim, Subscribed

gdupras left a comment (vim/vim#17546)

I disagree. I think we should use the usual typewriter apostrophe ' U+0027 instead of the letter apostrophe ʼ U+02BC. Here’s why, in no specific order.

To be consistent with the English vimtutor.
To be consistent with the rest of Vim’s documentation. U+0027 is used everywhere. There is not a single instance of U+02BC in runtime/doc.
To jump to the end of an orthographic word—or WORD, to use Vim’s terminology—you can use E. Similarly you can jump to the next orthographic word with W. There is no point forcing every word into a WORD.
People learning Vim will be confused as to why the behavior of e and w is different in vimtutor compared to everywhere else. “Why does e jumps to the end of the word instead of the apostrophe?”
U+02BC breaks spell checking. For example, “lʼavion” is marked wrong even though it is not actually a mistake. Spell checking works fine with U+0027.
If other contributors modify the French vimtutor, they will probably be unaware it uses the letter apostrophe so we will most likely end up with a mix of U+0027 and U+02BC.
U+02BC is not available on most keyboard layouts. Even if it is, most people don’t know how to type it.
U+02BC is not even in :h digraph-table so people who don’t have this character on their keyboard can’t use digraphs as an alternate way to type it.
Most people have never even heard of letter apostrophe.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.

Gabriel Dupras

unread,

Jun 18, 2025, 1:37:05 PM6/18/25

to vim/vim, Subscribed

@gdupras commented on this pull request.

In runtime/tutor/tutor2.fr.utf-8:

> +RÉFÉRENCES: 	Registers 	:h registers
+		Named Registers :h quotea
+		Motion 		:h motion.txt<Enter> /inner<Enter>
+		CTRL-R		:h insert<Enter> /CTRL-R<Enter>

Merci benknoble. J’ai finalement trouvé une copie de la documentation en français. Voir le lien ci-dessous. Malheureusement la dernière mise-à-jour date de plus de 13 ans. On pourrait au moins mettre à jour le lien sur vim.org.

Thank you benknoble. I’ve finally found an archive of the French documentation. See the link below. Unfortunately, it hasn’t been updated in more than 13 years. At least we could update the link on vim.org.

https://github.com/dblanchet/vim-help-fr

—
Reply to this email directly, view it on GitHub, or unsubscribe.

You are receiving this because you are subscribed to this thread.

Christian Brabandt

unread,

Jun 18, 2025, 1:44:28 PM6/18/25

to vim/vim, Subscribed

@chrisbra commented on this pull request.

In runtime/tutor/tutor2.fr.utf-8:

> +RÉFÉRENCES: 	Registers 	:h registers
+		Named Registers :h quotea
+		Motion 		:h motion.txt<Enter> /inner<Enter>
+		CTRL-R		:h insert<Enter> /CTRL-R<Enter>

done

—
Reply to this email directly, view it on GitHub, or unsubscribe.

You are receiving this because you are subscribed to this thread.

Gabriel Dupras

unread,

Jun 18, 2025, 1:46:39 PM6/18/25

to vim/vim, Subscribed

@gdupras commented on this pull request.

In runtime/tutor/tutor2.fr.utf-8:

> +RÉFÉRENCES: 	Registers 	:h registers
+		Named Registers :h quotea
+		Motion 		:h motion.txt<Enter> /inner<Enter>
+		CTRL-R		:h insert<Enter> /CTRL-R<Enter>

Super, merci !

Great, thanks !

—
Reply to this email directly, view it on GitHub, or unsubscribe.

You are receiving this because you are subscribed to this thread.

Damien Lejay

unread,

Jun 19, 2025, 3:29:34 AM6/19/25

to vim/vim, Subscribed

dlejay left a comment (vim/vim#17546)

1 & 2 → If someone starts vimtutor in French, they will likely never consult the English version. The tutor and the docs already follow different conventions : the keys are labelled all caps <ENTER> in the tutor instead of <Enter> in the docs. As Chris said in another comment, letʼs focus on the vimtutor and weʼll address the docs in a second time.

3 → e and w are supposed to work with orthographic words. E and W are meant to include punctuation alongside orthographic words.
Example :

The sentence 'Iʼm a fan of apostrophes.' has five words between two ASCII quotes.

4 → Some level of confusion is inevitable, as multiple apostrophe characters exist in Unicode. My view is that U+02BC makes the experience smoother within the tutor, which is a text-based, controlled environment where users first explore motions like e and w.

5 → The spell checker issue is valid. Iʼm happy to explore ways to improve this.

6 → I agree consistency matters. We can add a note for contributors about the use of U+02BC and if an occasional U+0027 slips in, I think thatʼs not a big deal as it will not be too difficult to normalize.

7 & 8 & 9 → Input should not be a concern, as the tutor does not require users to type a textual apostrophe. Moreover, Vim allows input of Unicode characters with <CTRL-V>u. I can review the tutor to confirm this and propose adding U+02BC to the digraph table.

Proposal : letʼs focus at the perspective of a new user, that has limited knowledge (never opened a man page, knows nothing about apostrophes etc.), that starts vimtutor and that lands automatically in the French version because their locale is set to fr.

My hypothesis is that for this user :

the tutor is a sandboxed, controlled environment, where Vim is run in Vi-compatible mode ;
using U+02BC will make their experience smoother with Vim motions e and w while playing around in the tutor ;
Which means they are (marginally) more likely to continue to the end of the tutor and to be a happy Vim user ;
if they later use Vim to edit text that contains U+0027, any frustration with word motions will arise regardless ;
when coding, U+0027 functions as a quotation mark and will not create confusion.

—
Reply to this email directly, view it on GitHub, or unsubscribe.

You are receiving this because you are subscribed to this thread.

Damien Lejay

unread,

Jun 19, 2025, 3:41:13 PM6/19/25

to vim/vim, Push

@dlejay pushed 1 commit.

cc8d100 Add translation of references and mnemonics

—
View it on GitHub or unsubscribe.
You are receiving this because you are subscribed to this thread.

Damien Lejay

unread,

Jun 19, 2025, 3:42:18 PM6/19/25

to vim/vim, Subscribed

@dlejay commented on this pull request.

In runtime/tutor/tutor2.fr.utf-8:

> +RÉFÉRENCES: 	Registers 	:h registers
+		Named Registers :h quotea
+		Motion 		:h motion.txt<Enter> /inner<Enter>
+		CTRL-R		:h insert<Enter> /CTRL-R<Enter>

I am now convinced you are correct, translating as much as possible is the better option.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.

Damien Lejay

unread,

Jun 19, 2025, 3:44:00 PM6/19/25

to vim/vim, Push

@dlejay pushed 1 commit.

6cfe6b0 Replace astuce with aide

—
View it on GitHub or unsubscribe.
You are receiving this because you are subscribed to this thread.

Damien Lejay

unread,

Jun 19, 2025, 3:46:34 PM6/19/25

to vim/vim, Push

@dlejay pushed 1 commit.

de7b740 Replace one last <C-r> with <CTRL-R>

—
View it on GitHub or unsubscribe.

You are receiving this because you are subscribed to this thread.

Damien Lejay

unread,

Jun 19, 2025, 3:47:45 PM6/19/25

to vim/vim, Push

@dlejay pushed 1 commit.

79e8615 fix: readd tutor2

—
View it on GitHub or unsubscribe.

You are receiving this because you are subscribed to this thread.

Gabriel Dupras

unread,

Jun 20, 2025, 12:19:26 PM6/20/25

to vim/vim, Subscribed

gdupras left a comment (vim/vim#17546)

1 & 2 → You’re mixing up two different things. There may not be a convention for <ENTER>/<Enter> but there is a clear convention for apostrophes. That convention is to use U+0027.

3 →

e and w are supposed to work with orthographic words.

The documentation doesn’t say that anywhere. Vim doesn’t operate on grammatical and orthographic words. It doesn’t understand those concepts. It operates on “words” and “WORDS”, as defined in the documentation.

:h word:

A word consists of a sequence of letters, digits and underscores, or a
sequence of other non-blank characters, separated with white space (spaces,
tabs, <EOL>).  This can be changed with the 'iskeyword' option.  An empty line
is also considered to be a word.

:h WORD:

A WORD consists of a sequence of non-blank characters, separated with white
space.  An empty line is also considered to be a WORD.

So, for example, “I'm a fan of apostrophes.” (with U+0027) is eight words (' and . are both words) and five WORDS.

4 → Sure but we can reduce the level of confusion by using the much more common typewriter apostrophe. The user may not even run into an other kind of apostrophe in a very long time. Why sneakily introduce a very unusual one right at the beginning of their Vim journey, especially if they likely won’t ever see this apostrophe anywhere else?

The experience is not smoother if e and w don’t behave like you would expect them to based on documentation (official one or not). It’s not obvious at all that U+02BC is actually a letter, not a punctuation mark.

Also, if the user experiments and types a U+0027, they will wonder why e and w appear to have an inconsistent behaviour, even within Vimtutor. Visually the difference between U+0027 and U+02BC is not immediately obvious.

5 → OK. Still, it’s a problem that could easily be avoided by using the regular apostrophe.

6 → Fair enough. But we would avoid this extra trouble by using the conventional U+0027 instead.

7 & 8 & 9 → Same as 6.

Sure. Vimtutor doesn’t run in Vi-compatible mode though. You can check for yourself with :set compatible?. Anyway, that’s not relevant to this discussion.
This is debatable. I don’t think it’s necessarily smoother. See “4 →” above.
That seems to be your own frustration with e and w that you’re projecting on new users. They may not agree. Especially if they know about E and W.
OK but Vim is not only used for coding. For example, I’m writing this in Vim. Like I said before new users will wonder why e and w do not behave the same in Vimtutor as everywhere else. Even when coding, strings often contain apostrophes.

I still think we should stick with U+0027. Using U+02BC causes more problems than it solves.

To alleviate some of the “frustration” with e and w, instead of tricking the user with a fake apostrophe, how about we include a section on E and W somewhere in Vimtutor instead? Maybe a new lesson 1.7 with w, e, b, W, E, and B in tutor1. It would make sense to learn about motions before using them with operators in 2.1. Or those motions could be added to lesson 2.3.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.

D. Ben Knoble

unread,

Jun 20, 2025, 4:15:31 PM6/20/25

to vim/vim, Subscribed

benknoble left a comment (vim/vim#17546)

A note: when replying, it is helpful to the reader to quote (portions) of the replied-to text so they can follow the discussion. Otherwise much scrolling is required.

(This is also known as "don't top post" in mailing list circles).

—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.

Gabriel Dupras

unread,

Jun 20, 2025, 4:21:49 PM6/20/25

to vim/vim, Subscribed

gdupras left a comment (vim/vim#17546)

when replying, it is helpful to the reader to quote (portions) of the replied-to text

Got it. Sorry about that.

—
Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.

Damien Lejay

unread,

Jun 21, 2025, 9:48:32 AM6/21/25

to vim/vim, Subscribed

dlejay left a comment (vim/vim#17546)

1 & 2 → You’re mixing up two different things.

What I am saying is : the vimtutor is its own environment and can have itʼs own set of standard practices. As an example, it uses a different capitalization for the keys.

You are correct, it seems that :h word and :h WORD were written for ASCII text. They probably need some update to reflect more modern usage scenarios with Unicode. Thanks for pointing it out.

Having a dedicated section about E and W could make sense. Maybe one could take it also as an opportunity to introduce the existence of different apostrophes ?

It’s not obvious at all that U+02BC is actually a letter, not a punctuation mark.

It is clear to everybody that apostrophes in French (and in English) are not punctuation marks, independently from any documentation, encoding etc.
From Cecil Hartley :

The stop point out, with truth, the time of pause
A sentence doth require at evʼry clause.
At evʼry comma, stop while one you count;
At semicolon, two is the amount;
A colon doth require the time of three;
The period four, as learned men agree.

U+0027 is a punctuation mark (in the Unicode classification) because it used to be the quantum typewriter superposition ½ <opening single quote + closing single quote + top part of exclamation mark + apostrophe>, so it had to be classified that way.

Vimtutor doesn’t run in Vi-compatible mode though.

You might have discovered a bug. The man page says : Vim is always started in Vi compatible mode.

That seems to be your own frustration with e and w that you’re projecting on new users.

[…] instead of tricking the user with a fake apostrophe […]

I see where this is heading, and I prefer not to go down that path.

I do notice though that you chose to use U+2019 as your default apostrophe character in your comments.

Conclusion

I happened to write the Chapter 2 of the French vimtutor naturally using U+2019 (in the same way that I naturally use narrow non-break spaces before double punctuations), as you do. Following your first comment and after having done quite a bit of research, I realized U+02BC is objectively better, so thank you for that.

I believe using U+02BC in the vimtutor is a net positive. I understand you see it as a net negative. Since the difference is minuscule and no argument from the perspective of a new user within vimtutor convinced me otherwise, weʼll keep it as is and move on.

In the meantime, thanks to this discussion we have a valuable list of improvements to be made :

Improve spellchecking ;
Improve the documentation on word and WORD ;
Write a tutor section on E and W ;
Introduce a digraph for U+02BC ;
Check the vimtutor script and the man page for Vi-compatible inconsistencies.

which I think is really great.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.

Christian Brabandt

unread,

Jun 22, 2025, 2:05:54 PM6/22/25

to vim/vim, Subscribed

chrisbra left a comment (vim/vim#17546)

Okay, not sure I follow everything. I don't really have an opinion regarding the use of apostrophes in the French tutor translation. So I'd leave the decision to the community. So are you all fine with the current approach here? Also pinging @DominiquePelle-TomTom and Tony Mechelynck for their opinion.

—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.

Damien Lejay

unread,

Jun 23, 2025, 4:59:12 AM6/23/25

to vim/vim, Push

@dlejay pushed 16 commits.

e054709 Fix some minor issues in tutor2
eb66e38 Add French translation for tutor2
cbd3d17 Update runtime/tutor/tutor2
e6abc45 Fix typo
8086c74 Apply suggestions from code review
c43dd99 Change U+2019 to U+02BC
d03b003 Apply suggestions from code review
7ba55f8 Refer to Chapter 2 in tutor1.fr
1d51c8e Add vimtutor translation
63709e7 Add suggestions by reviewers
a4fcca1 Apply changes of the previous commit to .fr accordingly
a2430b9 Add translation of references and mnemonics
1f569e0 Replace astuce with aide
5a52fc8 Replace one last <C-r> with <CTRL-R>
d12244d fix: readd tutor2
466bb25 Rename tutor2.fr

—
View it on GitHub or unsubscribe.

You are receiving this because you are subscribed to this thread.

Damien Lejay

unread,

Jun 23, 2025, 5:08:49 AM6/23/25

to vim/vim, Subscribed

dlejay left a comment (vim/vim#17546)

@chrisbra Yes great idea, Iʼd love to have their perspective.

The apostrophe question is not specific to French, so you could have an opinion on the same topic for the English version of the tutor : what would be your reaction if somebody wrote a new tutor chapter using U+02BC as the apostrophe there ?

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.

Damien Lejay

unread,

Jun 23, 2025, 5:13:07 AM6/23/25

to vim/vim, Push

@dlejay pushed 1 commit.

536a07f fix <CTRL-R>

—
View it on GitHub or unsubscribe.
You are receiving this because you are subscribed to this thread.

Damien Lejay

unread,

Jun 28, 2025, 8:39:17 AM6/28/25

to vim/vim, Push

@dlejay pushed 1 commit.

d6d6be8 Update MAINTAINERS file

—
View it on GitHub or unsubscribe.

You are receiving this because you are subscribed to this thread.

Damien Lejay

unread,

Jun 28, 2025, 8:41:00 AM6/28/25

to vim/vim, Push

@dlejay pushed 1 commit.

8575292 Update MAINTAINERS file

—
View it on GitHub or unsubscribe.

You are receiving this because you are subscribed to this thread.

Christian Brabandt

unread,

Jun 28, 2025, 2:51:25 PM6/28/25

to vim/vim, Subscribed

chrisbra left a comment (vim/vim#17546)

can you squash and split up the commits into 2? One for cleanup of chapter2 and one for the French translation?

—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.

Damien Lejay

unread,

Jun 29, 2025, 6:45:46 AM6/29/25

to vim/vim, Push

@dlejay pushed 2 commits.

7f52c34 cleanup: apply fixes to runtime/tutor/tutor2
f301de4 feat: add and refine French translation of tutor2

—
View it on GitHub or unsubscribe.

You are receiving this because you are subscribed to this thread.

Damien Lejay

unread,

Jun 29, 2025, 6:48:29 AM6/29/25

to vim/vim, Subscribed

dlejay left a comment (vim/vim#17546)

Now 2 commits: cleanup + FR translation. Let me know if anything else.

—
Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.

Christian Brabandt

unread,

Jun 29, 2025, 11:48:56 AM6/29/25

to vim/vim, Subscribed

chrisbra left a comment (vim/vim#17546)

Thanks. I'll include it now. As I said before, I don't have much of a preference of the used apostrophe. If using U+02BC is the convention in France and it works fine with Vim, then why not stick with it. If it causes too much trouble, we can re-consider. I assume French users will complain (or not) :)

Thanks all.

—
Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.

Christian Brabandt

unread,

Jun 29, 2025, 11:56:02 AM6/29/25

to vim/vim, Subscribed

Closed #17546 via d419fa2.

—
Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.

Damien Lejay

unread,

Jun 30, 2025, 3:49:18 AM6/30/25

to vim/vim, Subscribed

dlejay left a comment (vim/vim#17546)

As a French person, you can count on the French to complain 😉

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.

Reply all

Reply to author

Forward

[vim/vim] Add French translation for Chapter 2 of the Vimtutor (PR #17546)

Damien Lejay

You can view, comment on, or merge this pull request online at:

Commit Summary

File Changes

Patch Links:

Christian Brabandt

Gabriel Dupras

Damien Lejay

Damien Lejay

Gabriel Dupras

Gabriel Dupras

Gabriel Dupras

Gabriel Dupras

Gabriel Dupras

Gabriel Dupras

Damien Lejay

Damien Lejay

Damien Lejay

Damien Lejay

Gabriel Dupras

Damien Lejay

The vimtutor tutor files

Apostrophes in encodings

The ASCII apostrophe

Latin1

ISO/IEC 8859-1

Windows-1252 and Mac Roman

Unicode

The recommended apostrophe character in Unicode

Orthographic words

Why Unicode recommended U+02BC

Why Unicode changed its recommendation to U+2019

Effect on Vim and the Vimtutor

Actions and suggestions

For the tutor2.fr

For the tutor1.fr

For the English tutor file

Damien Lejay

Damien Lejay

Damien Lejay

Damien Lejay

Damien Lejay

Restorer

Christian Brabandt

Damien Lejay

Christian Brabandt

Restorer

Damien Lejay

D. Ben Knoble

Restorer

Damien Lejay

Restorer

Christian Brabandt

Damien Lejay

Damien Lejay

Gabriel Dupras

Gabriel Dupras

Christian Brabandt

Gabriel Dupras

Damien Lejay

Damien Lejay

Damien Lejay

Damien Lejay

Damien Lejay

Damien Lejay

Gabriel Dupras

D. Ben Knoble

Gabriel Dupras

Damien Lejay

Conclusion

Christian Brabandt

Damien Lejay

Damien Lejay

Damien Lejay

Damien Lejay

Damien Lejay

Christian Brabandt

Damien Lejay

Damien Lejay

The vimtutor `tutor` files

Why Unicode recommended `U+02BC`

Why Unicode changed its recommendation to `U+2019`