mirror of
https://github.com/YouG-o/YouTube-No-Translation.git
synced 2026-04-25 10:05:54 +03:00
[GH-ISSUE #108] ISSUE: channel name still translated under videos and channel pages #77
Labels
No labels
ToDo
bug
enhancement
enhancement
help wanted
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/YouTube-No-Translation#77
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Originally created by @gut1414 on GitHub (Sep 27, 2025).
Original GitHub issue: https://github.com/YouG-o/YouTube-No-Translation/issues/108
Originally assigned to: @YouG-o on GitHub.
Description
Channel name still tranlated, even inside channel page and inside video page itself (French, German, English tested).
Video for example (Russian origin): https://www.youtube.com/watch?v=y6OtvHwkob8
The channel of this video: https://www.youtube.com/@PeopleAndAnimals777
Tested on all browsers up to date (Edge, Chrome, Firefox, Opera, tested with Franch and German and Librewolf, a Firefox fork like Brave, but browser in English by default for privacy).
But, description, and video title are untranslated.
Other YouTube-related extensions you are using
Ublock origin up to date, Return Youtube dislike, Enhancer For YouTube (on Edge, Opera and Chrome) and Sponsorblock.
@YouG-o commented on GitHub (Oct 1, 2025):
I fixed the Channel name not being original on channel page :
49e1c3b78aBut on video page, I don't have the issue on my side.
I'll have a deeper look later.
@jkfoong commented on GitHub (Oct 3, 2025):
Had the same issue , it happens when refreshing on the channel videos page, not when switching to videos page from channel home page. But if you switch tab, the language become correct again.
@YouG-o commented on GitHub (Oct 3, 2025):
@jkfoong
Like I said above, I fixed it. It will be available in the next update.
@YouG-o commented on GitHub (Oct 3, 2025):
v2.15.1 should fix this issue.
Already available on Chrome Web store.
Waiting for approval on Mozilla & Microsoft (can take a few days)