mirror of
https://github.com/deepseek-ai/DeepSeek-V3.git
synced 2026-11-05 00:47:48 +00:00
[GH-ISSUE #294] [BUG] RTL Arabic Direction #112
Labels
No labels
closed-as-stale
enhancement
question
spam
stale
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
deepseek-ai/DeepSeek-V3#112
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 @abdo-ibrahim on GitHub (Jan 16, 2025).
Original GitHub issue: https://github.com/deepseek-ai/DeepSeek-V3/issues/294
Describe the bug
we need deepseek be compatible with The direction of text generated in the Arabic language
as the default direction is ltr but in arabic is rtl, this makes the text difficult to read at some time
@mowentian commented on GitHub (Jan 17, 2025):
you mean app? ios ver 1.0.2 is rtl
@mowentian commented on GitHub (Jan 17, 2025):
o，i get，this vresion remains some problem，we will make it better at next version
@Morrigan-Ship commented on GitHub (Jan 17, 2025):
i know how to fix it:
just need to detect type of first character in text box
if first character is Arabic or Persian:
document.body.dir='rtl'if fist character is english:
document.body.dir='ltr'just like Telegram messenger
@JohnBrayden commented on GitHub (Jan 20, 2025):
Also, if we edit the direction to RTL via DevTools, the generated code looks like this:
@Ndegwadavid commented on GitHub (Jan 29, 2025):
mmmh! interesting direction 🏷
@abdo-ibrahim commented on GitHub (Jan 29, 2025):
i made a script that fix the Direction you can use it until Deepseek fix this problem
-open the link and install tampermonkey extension based on the browser that you use
-then install script
https://greasyfork.org/en/scripts/525186-dynamic-rtl-ltr-direction
@Morrigan-Ship commented on GitHub (Jan 29, 2025):
is it open source?
@abdo-ibrahim commented on GitHub (Jan 29, 2025):
yes, actually u can find the script when u install it
@JohnBrayden commented on GitHub (Feb 19, 2025):
@Morrigan-Ship You will find a collection of open-source repositories here for browser extensions to fix the RTL issue in DeepSeek.
@mowentian I would also like to emphasize the critical necessity of resolving this issue, as it actively prevents a wide range of DeepSeek users from continuing to utilize the platform effectively. Any responses generated by DeepSeek are rendered unreadable due to the RTL problem, which underscores the urgency of fixing this. This is not merely a cosmetic or superficial issue but a significant practical obstacle that consistently hinders our ability to proceed.
@github-actions[bot] commented on GitHub (Mar 25, 2025):
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you believe this issue is still relevant, please leave a comment to keep it open. Thank you for your contributions!
@DevalGarg129 commented on GitHub (Mar 27, 2025):
Possible Fix
Implement bidirectional text support based on language detection.
Automatically set dir="rtl" for Arabic output in web-based applications.
Use Unicode Right-to-Left Mark (RLM) characters for proper rendering.
@github-actions[bot] commented on GitHub (Apr 29, 2025):
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you believe this issue is still relevant, please leave a comment to keep it open. Thank you for your contributions!
@github-actions[bot] commented on GitHub (May 13, 2025):
false
@MohammedGalal-IT commented on GitHub (May 22, 2026):
Please fix this problem
@qingkong66 commented on GitHub (May 22, 2026):
@MohammedGalal-IT @abdo-ibrahim
This issue (#294) has been closed by a bot, but the problem persists.
Arabic RTL text direction is not a cosmetic preference. It's a functional barrier for a significant group of users. When generated text is unreadable without workarounds (Tampermonkey scripts), the product is not serving its audience properly.
Other language/region issues have been raised more recently:
This is not an isolated complaint. It's a pattern.
Re-opening this issue may not help, but the signal should not be lost. The team should consider language/region rendering as part of core UX, not an enhancement.