You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem Description
As an Arabic-speaking power user and a dedicated tester of the DeepSeek platform, I have identified three critical gaps that severely hinder the experience for millions of potential Arabic-speaking users. These issues are not just inconveniences; they are major barriers to entry and effective utilization.
Critical RTL (Right-to-Left) Display Bug
The most urgent issue is that the interface does not properly support RTL languages. When I type in Arabic, the text is rendered from left to right (LTR), making it nearly unreadable and causing severe formatting errors, especially when mixing Arabic with English or numbers.
This bug is well-documented by multiple users in the official repository with critical issues like #933, #326, #294, and #546. All point to the same core problem of text direction and alignment.
The issue persists in both user input and AI-generated responses.
No Arabic UI Localization
The entire user interface, including menus, buttons, settings, and system prompts, is exclusively in English and Chinese (on mobile). There is currently no option to switch the platform's language to Arabic, making it inaccessible to users who are not comfortable navigating complex technical interfaces in English.
No Integrated Virtual Arabic Keyboard
As previously requested in my earlier feature request Integrated Pop-up Virtual Arabic Keyboard with Essential Editing Buttons #617, there is no built-in virtual Arabic keyboard within the chat interface. This is especially problematic for users on devices without a physical Arabic keyboard or in case of hardware failure. For a platform aiming for global reach, this is a significant oversight.
Proposed Solution
I propose a comprehensive "Full Arabic Language Support" package, which integrates and expands upon community requests to solve this issue holistically. This package would consist of three core components, and a fourth optional one.
Immediate RTL Rendering Fix (The Foundation)
This is the most critical technical bug to fix. As outlined in Issue feat: add OfoxAI to Providers #546, the solution is simple and effective.
Proposed Fix: Add the CSS property direction: rtl; to the main content block (identified by the class ds-markdown ds-markdown--block) to ensure correct right-to-left alignment.
For Mixed Text: To handle both RTL and LTR content dynamically, the dir="auto" HTML attribute should be set on the parent container. This allows the browser to automatically detect the direction of the input text.
Cross-Platform: This fix must be applied to both the web and mobile applications.
Full UI Localization (The Identity)
Add Arabic as a selectable language in the platform's settings. The entire interface should be professionally translated into Arabic, including:
Navigation menus and all buttons.
Settings panels and configuration options.
All system prompts and error messages.
The layout itself should be mirrored to a true RTL format.
This is a common practice for all major global platforms. As one community member noted, issues #326 specifically calls for this full localization to make the platform inclusive and accessible to RTL language users.
Integrated Virtual Arabic Keyboard (The Accessibility Feature)
Implement the virtual Arabic keyboard I requested in Issue Integrated Pop-up Virtual Arabic Keyboard with Essential Editing Buttons #617. This ensures that users can type in Arabic without needing a physical keyboard, serving as an essential accessibility feature.
Optional: Platform-Wide RTL Layout (The Premium Experience)
Long-term, the entire layout should support proper RTL mirroring. This means not just text direction, but also the positioning of UI elements. The sidebar, the send button, and the alignment of lists should all be mirrored for a truly native Arabic experience.
Community Validation (Supporting Evidence)
This request is not mine alone. It is a community demand that has been pending for months, and in some cases, over a year. It consolidates several critical issues raised by the community:
Issue #933: [BUG] RTL text display issue (Reported on Jul 15, 2025).
Issue #326: Fix Critical Bug in Right-to-Left Language Support and Add Persian, Arabic, and Hebrew Languages (Reported on Jan 23, 2025).
Issue #294: [BUG] RTL Arabic Direction (Reported on Jan 16, 2025).
Issue #546: Improve RTL Text Display (Reported on Feb 3, 2025).
Issue #617: My previous request for the virtual Arabic keyboard.
The existence of community-developed browser extensions and Tampermonkey scripts like "Dynamic RTL/LTR Direction" and various Chrome extensions to fix this issue (as noted in issues #326 and #294) is a clear testament to the high demand for this feature and the community's frustration with its absence.
Additional Context
I am an active power user and have been rigorously testing the platform, as evidenced by my four other feature requests (#615, #616, #617, and #618). Fixing the Arabic language support is not just a matter of adding another language; it is about providing equal access and a professional user experience to the hundreds of millions of Arabic speakers worldwide. It is about making DeepSeek a truly global and inclusive platform, not just a product of the English-speaking world.
Once this is implemented, DeepSeek would set a new standard for AI platforms in the Middle East, significantly expanding its market reach and user base.
Problem Description
As an Arabic-speaking power user and a dedicated tester of the DeepSeek platform, I have identified three critical gaps that severely hinder the experience for millions of potential Arabic-speaking users. These issues are not just inconveniences; they are major barriers to entry and effective utilization.
The most urgent issue is that the interface does not properly support RTL languages. When I type in Arabic, the text is rendered from left to right (LTR), making it nearly unreadable and causing severe formatting errors, especially when mixing Arabic with English or numbers.
This bug is well-documented by multiple users in the official repository with critical issues like #933, #326, #294, and #546. All point to the same core problem of text direction and alignment.
The issue persists in both user input and AI-generated responses.
No Arabic UI Localization
The entire user interface, including menus, buttons, settings, and system prompts, is exclusively in English and Chinese (on mobile). There is currently no option to switch the platform's language to Arabic, making it inaccessible to users who are not comfortable navigating complex technical interfaces in English.
No Integrated Virtual Arabic Keyboard
As previously requested in my earlier feature request Integrated Pop-up Virtual Arabic Keyboard with Essential Editing Buttons #617, there is no built-in virtual Arabic keyboard within the chat interface. This is especially problematic for users on devices without a physical Arabic keyboard or in case of hardware failure. For a platform aiming for global reach, this is a significant oversight.
Proposed Solution
I propose a comprehensive "Full Arabic Language Support" package, which integrates and expands upon community requests to solve this issue holistically. This package would consist of three core components, and a fourth optional one.
This is the most critical technical bug to fix. As outlined in Issue feat: add OfoxAI to Providers #546, the solution is simple and effective.
Proposed Fix: Add the CSS property direction: rtl; to the main content block (identified by the class ds-markdown ds-markdown--block) to ensure correct right-to-left alignment.
For Mixed Text: To handle both RTL and LTR content dynamically, the dir="auto" HTML attribute should be set on the parent container. This allows the browser to automatically detect the direction of the input text.
Cross-Platform: This fix must be applied to both the web and mobile applications.
Add Arabic as a selectable language in the platform's settings. The entire interface should be professionally translated into Arabic, including:
Navigation menus and all buttons.
Settings panels and configuration options.
All system prompts and error messages.
The layout itself should be mirrored to a true RTL format.
This is a common practice for all major global platforms. As one community member noted, issues #326 specifically calls for this full localization to make the platform inclusive and accessible to RTL language users.
Integrated Virtual Arabic Keyboard (The Accessibility Feature)
Implement the virtual Arabic keyboard I requested in Issue Integrated Pop-up Virtual Arabic Keyboard with Essential Editing Buttons #617. This ensures that users can type in Arabic without needing a physical keyboard, serving as an essential accessibility feature.
Optional: Platform-Wide RTL Layout (The Premium Experience)
Long-term, the entire layout should support proper RTL mirroring. This means not just text direction, but also the positioning of UI elements. The sidebar, the send button, and the alignment of lists should all be mirrored for a truly native Arabic experience.
Community Validation (Supporting Evidence)
This request is not mine alone. It is a community demand that has been pending for months, and in some cases, over a year. It consolidates several critical issues raised by the community:
Issue #933: [BUG] RTL text display issue (Reported on Jul 15, 2025).
Issue #326: Fix Critical Bug in Right-to-Left Language Support and Add Persian, Arabic, and Hebrew Languages (Reported on Jan 23, 2025).
Issue #294: [BUG] RTL Arabic Direction (Reported on Jan 16, 2025).
Issue #546: Improve RTL Text Display (Reported on Feb 3, 2025).
Issue #617: My previous request for the virtual Arabic keyboard.
The existence of community-developed browser extensions and Tampermonkey scripts like "Dynamic RTL/LTR Direction" and various Chrome extensions to fix this issue (as noted in issues #326 and #294) is a clear testament to the high demand for this feature and the community's frustration with its absence.
Additional Context
I am an active power user and have been rigorously testing the platform, as evidenced by my four other feature requests (#615, #616, #617, and #618). Fixing the Arabic language support is not just a matter of adding another language; it is about providing equal access and a professional user experience to the hundreds of millions of Arabic speakers worldwide. It is about making DeepSeek a truly global and inclusive platform, not just a product of the English-speaking world.
Once this is implemented, DeepSeek would set a new standard for AI platforms in the Middle East, significantly expanding its market reach and user base.