starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

French accented letters showing up as Greek symbols #21908

New Issue
Closed
opened 2026-01-31 07:58:02 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 07:58:02 +00:00
Owner
Copy Link

Originally created by @dEhiN on GitHub (Jun 28, 2024).

Windows Terminal version

1.20.11381.0

Windows build number

10.0.19045

Other Software

No response

Steps to reproduce

I added the Debian WSL app from the Microsoft Store and then I opened it through the Start Menu. That opened a terminal window and triggered the installation, but there was an error in installation due to WSL not being set up. However, within the error message, which is in French since my system language is currently French, I noticed 2 Greek symbols for letters. I realized these letters should be the French accented letters é and è.

I also looked at Settings > Profile > Default > Appearance > Font to see the list of fonts, but none of them appear to be Unicode fonts, that I'm aware of:
image

Expected Behavior

image

The line that starts with Error should read, after the error number: Le sous-système Windows pour Linux n'a pas été activé.

Actual Behavior

In the error message, what should be the French letter è is shown with the Greek letter phi. What should be the French letter é is shown 3 times with the Greek letter theta.

Originally created by @dEhiN on GitHub (Jun 28, 2024). ### Windows Terminal version 1.20.11381.0 ### Windows build number 10.0.19045 ### Other Software _No response_ ### Steps to reproduce I added the Debian WSL app from the Microsoft Store and then I opened it through the Start Menu. That opened a terminal window and triggered the installation, but there was an error in installation due to WSL not being set up. However, within the error message, which is in French since my system language is currently French, I noticed 2 Greek symbols for letters. I realized these letters should be the French accented letters _é_ and _è_. I also looked at Settings > Profile > Default > Appearance > Font to see the list of fonts, but none of them appear to be Unicode fonts, that I'm aware of: <img width="199" alt="image" src="https://github.com/microsoft/terminal/assets/26848686/46b62b2c-1458-4269-b909-a7663041d8ce"> ### Expected Behavior <img width="515" alt="image" src="https://github.com/microsoft/terminal/assets/26848686/44d7646c-f119-424e-9276-2dd4d44bbd04"> The line that starts with _Error_ should read, after the error number: _Le sous-système Windows pour Linux n'a pas été activé._ ### Actual Behavior In the error message, what should be the French letter _è_ is shown with the Greek letter phi. What should be the French letter _é_ is shown 3 times with the Greek letter theta.
claunia added the Needs-TriageIssue-BugNeeds-Attention labels 2026-01-31 07:58:03 +00:00
claunia commented 2026-01-31 07:58:04 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jun 28, 2024):

I think this might be a codepage issue in WSL. Can you report which version of WSL you are using? Did you install it separately, or are you using the one that comes with Windows?

What do you get if you run wsl --upgrade?

@DHowett commented on GitHub (Jun 28, 2024): I think this might be a codepage issue in WSL. Can you report which version of WSL you are using? Did you install it separately, or are you using the one that comes with Windows? What do you get if you run `wsl --upgrade`?
claunia commented 2026-01-31 07:58:04 +00:00
Author
Owner
Copy Link

@dEhiN commented on GitHub (Jul 2, 2024):

Hi @DHowett, thank you for replying. Based on the actual error message, it looks like WSL isn't yet installed. The only thing I did was go to Start Menu > Programs and Features > Turn Windows features on or off, and turned on Windows Subsystem for Linux. I had previously added the Ubuntu WSL app from the Windows store, so I clicked on it to run it. I'm not sure if more was required to actually install or setup WSL. I tried running wsl --upgrade in a Windows PowerShell session in Microsoft Terminal, but apparently that isn't a valid option. However, if you think the problem I submitted is specific to WSL, go ahead and close this issue. Thanks.

@dEhiN commented on GitHub (Jul 2, 2024): Hi @DHowett, thank you for replying. Based on the actual error message, it looks like WSL isn't yet installed. The only thing I did was go to Start Menu > Programs and Features > Turn Windows features on or off, and turned on Windows Subsystem for Linux. I had previously added the Ubuntu WSL app from the Windows store, so I clicked on it to run it. I'm not sure if more was required to actually install or setup WSL. I tried running `wsl --upgrade` in a Windows PowerShell session in Microsoft Terminal, but apparently that isn't a valid option. However, if you think the problem I submitted is specific to WSL, go ahead and close this issue. Thanks.
claunia commented 2026-01-31 07:58:04 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jul 2, 2024):

Ah, sorry, what I mean is that it's associated with wsl.exe whether or not it's actually installed. Since it is a separate exe file it's in control of how its output is formatted for the console.

I recall seeing an issue in our internal tracker for it a few years ago... it's quite possible that the version of WSL in Windows 10.0.19045 just hasn't been updated to fix it.

@DHowett commented on GitHub (Jul 2, 2024): Ah, sorry, what I mean is that it's associated with _wsl.exe_ whether or not it's actually installed. Since it is a separate exe file it's in control of how its output is formatted for the console. I recall seeing an issue in our internal tracker for it a few years ago... it's quite possible that the version of WSL in Windows 10.0.19045 just hasn't been updated to fix it.
claunia commented 2026-01-31 07:58:04 +00:00
Author
Owner
Copy Link

@dEhiN commented on GitHub (Jul 3, 2024):

I understand now. Please go ahead and close this issue. I'll install WSL
from GitHub. Thanks.

On Tue, Jul 2, 2024, 16:08 Dustin L. Howett @.***>
wrote:

Ah, sorry, what I mean is that it's associated with wsl.exe whether or
not it's actually installed. Since it is a separate exe file it's in
control of how its output is formatted for the console.

I recall seeing an issue in our internal tracker for it a few years ago...
it's quite possible that the version of WSL in Windows 10.0.19045 just
hasn't been updated to fix it.

—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/terminal/issues/17483#issuecomment-2204294528,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGM23LW3T5KNCJXLW4PSKELZKMCCDAVCNFSM6AAAAABKCKELLWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBUGI4TINJSHA
.
You are receiving this because you authored the thread.Message ID:
@.***>

@dEhiN commented on GitHub (Jul 3, 2024): I understand now. Please go ahead and close this issue. I'll install WSL from GitHub. Thanks. On Tue, Jul 2, 2024, 16:08 Dustin L. Howett ***@***.***> wrote: > Ah, sorry, what I mean is that it's associated with *wsl.exe* whether or > not it's actually installed. Since it is a separate exe file it's in > control of how its output is formatted for the console. > > I recall seeing an issue in our internal tracker for it a few years ago... > it's quite possible that the version of WSL in Windows 10.0.19045 just > hasn't been updated to fix it. > > — > Reply to this email directly, view it on GitHub > <https://github.com/microsoft/terminal/issues/17483#issuecomment-2204294528>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AGM23LW3T5KNCJXLW4PSKELZKMCCDAVCNFSM6AAAAABKCKELLWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBUGI4TINJSHA> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Issue-Bug Needs-Attention Needs-Triage
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#21908
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?