It is indeed U+2019. Keyboard typing is not affected by this problem because in this case it is U+0027 that is used. The problem with U+2019 concerns txt files imported from another device. I will look into the solution of configuring a different font. Thank you
Le mar. 13 mai 2025, 13:01, Benno Schulenberg <bensb...@telfort.nl> a écrit : > > [Please respond only to the list, not to me.] > > Op 12-05-2025 om 12:28 schreef Pascal DEVEAUX: > > Using archlinux without X11 with locale set to fr_FR.UTF-8, nano can't > > display "apostrophe" and put □ instead. Nano display : can□t instead > can't > > When you say "apostrophe", you mean U+2019, not U+0027, right? > > (To check, run `nano --mini --constant` and type your "apostrophe". > Then move the cursor back onto the character, and check what it says > in the mini bar at the bottom.) > > I can confirm that, on an up-to-date Manjaro, on a Linux console > the character U+2019 is displayed as ￭ instead of as ’. > > When I run `showconsolefont` on Manjaro, it shows just four blocks > of 64 characters. On my Mint install, it shows eight blocks, and > there U+2019 is shown as a ’ just fine. > > So you need to configure a different font for the console. How to > do that... I don't know. Better refer to the Arch Linux docs: > > https://wiki.archlinux.org/title/Linux_console#Fonts > > > On Ubuntu and derivatives, this report may be of some use: > > https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1569964 > > > Benno >
