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

BUG: Text Encoding issues (backgroundImage path, tabTitle) #3185

New Issue
Closed
opened 2026-01-30 23:15:00 +00:00 by claunia · 3 comments
claunia commented 2026-01-30 23:15:00 +00:00
Owner
Copy Link

Originally created by @kfarmer-msft on GitHub (Aug 6, 2019).

Environment

Windows build number: 
Microsoft Windows [Version 10.0.18362.267]

Windows Terminal version (if applicable):
Windows Terminal (Preview)
Version: 0.3.2142.0

Any other software?
VS 2019, latest build

Steps to reproduce

These profile settings cause the specified background image to display. Each of these images is viewable via File Explorer and in use as desktop background images.

  "backgroundImage": "C:\\Users\\kfarm\\OneDrive\\Backgrounds\\Characters (Landscape)\\Oddr [Vizsla] - desktop.png",
  "backgroundImageAlignment": "bottomRight",
  "backgroundImageOpacity": 0.5,
  "backgroundImagesStretchMode": "fill"

These backgroundImage paths fail to render:

  "backgroundImage": "C:\\Users\\kfarm\\OneDrive\\Backgrounds\\Characters (Landscape)\\Þiálfi [Vizsla] - desktop.png",

  "backgroundImage": "C:\\Users\\kfarm\\OneDrive\\Backgrounds\\Characters (Landscape)\\Fálki [Vizsla] - desktop.png",

Additionally, adding these characters to tab name causes them to display the bad-encoding diamond.

Expected behavior

Background image renders for any valid NTFS path or URI

Tab title renders without encoding issues

Actual behavior

No background image shown, bad characters, great sadness.

... Given the rash of other character issues, I think it's a failure to interpret UTF-8, perhaps?

... Further investigation showed that switching the encoding of the file in VS would fix the tab issue, but Terminal would rewrite the background image paths with \uxxxx codes which I'd have to re-type.

Originally created by @kfarmer-msft on GitHub (Aug 6, 2019). # Environment ```none Windows build number: Microsoft Windows [Version 10.0.18362.267] Windows Terminal version (if applicable): Windows Terminal (Preview) Version: 0.3.2142.0 Any other software? VS 2019, latest build ``` # Steps to reproduce These profile settings cause the specified background image to display. Each of these images is viewable via File Explorer and in use as desktop background images. "backgroundImage": "C:\\Users\\kfarm\\OneDrive\\Backgrounds\\Characters (Landscape)\\Oddr [Vizsla] - desktop.png", "backgroundImageAlignment": "bottomRight", "backgroundImageOpacity": 0.5, "backgroundImagesStretchMode": "fill" These backgroundImage paths fail to render: "backgroundImage": "C:\\Users\\kfarm\\OneDrive\\Backgrounds\\Characters (Landscape)\\Þiálfi [Vizsla] - desktop.png", "backgroundImage": "C:\\Users\\kfarm\\OneDrive\\Backgrounds\\Characters (Landscape)\\Fálki [Vizsla] - desktop.png", Additionally, adding these characters to tab name causes them to display the bad-encoding diamond. # Expected behavior Background image renders for any valid NTFS path or URI Tab title renders without encoding issues # Actual behavior No background image shown, bad characters, great sadness. ... Given the rash of other character issues, I think it's a failure to interpret UTF-8, perhaps? ... Further investigation showed that switching the encoding of the file in VS would fix the tab issue, but Terminal would rewrite the background image paths with \uxxxx codes which I'd have to re-type.
claunia added the Help WantedArea-SettingsIssue-BugNeeds-Tag-FixProduct-Terminal labels 2026-01-30 23:15:00 +00:00
claunia commented 2026-01-30 23:15:02 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 8, 2019):

Yea I'd concur that this is a utf-8 roundtripping problem. This could be on either end of serializing or deserializing, impossible to know four sure without debugging further.

@zadjii-msft commented on GitHub (Aug 8, 2019): Yea I'd concur that this is a utf-8 roundtripping problem. This could be on either end of serializing or deserializing, impossible to know four sure without debugging further.
claunia commented 2026-01-30 23:15:02 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Aug 26, 2019):

Gut: deserializing issue

@DHowett-MSFT commented on GitHub (Aug 26, 2019): Gut: deserializing issue
claunia commented 2026-01-30 23:15:03 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Sep 24, 2019):

I can't repro this with a JSON file saved in codepage 65001.
image

image

@DHowett-MSFT commented on GitHub (Sep 24, 2019): I can't repro this with a JSON file saved in codepage 65001. ![image](https://user-images.githubusercontent.com/14316954/65552844-4c8c2300-deda-11e9-862c-e3a838b8c432.png) ![image](https://user-images.githubusercontent.com/14316954/65552848-52820400-deda-11e9-831a-6aa0c1af53c8.png)
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 Area-Settings Help Wanted Issue-Bug Needs-Tag-Fix Product-Terminal
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#3185
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?