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
I hope this message finds you well. I am a user of your platform (Web-UI: https://chat.qwenlm.ai/) and would like to suggest a small but meaningful improvement regarding the file-saving feature.
Currently, when saving dialogues or conversations, the platform offers the option to download files in .txt format. However, upon inspection, the content of these files includes Markdown syntax (.md). This can be slightly misleading for users who expect plain text without any formatting.
To improve clarity and usability, I propose renaming the option from "Save as .txt" to "Save as .md" (Markdown). Alternatively, you could provide both options:
Save as .txt (plain text without Markdown syntax)
Save as .md (with Markdown formatting preserved)
This change would:
Make the file format more transparent for users.
Align with the actual content being saved.
Enhance the user experience for those familiar with Markdown, as they could directly use the files in editors or platforms that support Markdown.
Thank you for considering this suggestion. I believe it would make the platform even more user-friendly and intuitive. Please let me know if you need further clarification or additional details.
基本示例 | Basic Example
I choose "Download -> Save as .txt" option in a dialogue '...' menu, but have to rename downloaded file to .md since the file actually contains Markdown formatting.
And I'd like to use this format as is by several MD viewers.
缺陷 | Drawbacks
未解决问题 | Unresolved questions
There are redundant user actions on downloading dialogues.
The text was updated successfully, but these errors were encountered:
Manually Rename the File
After downloading, rename the file from .txt to .md. (This allows Markdown viewers to recognize the file properly.)
Open the Markdown file on GitHub.
Click the "Raw" button to view the file in pure text format.
Right-click and select "Save As".
Change the file extension to .md before saving.
Use a Browser Extension or Script
Some browser extensions allow you to force .md downloads instead of .txt.
You can also create a small JavaScript bookmarklet to automatically rename .txt to .md when downloading.
起始日期 | Start Date
No response
实现PR | Implementation PR
No response
相关Issues | Reference Issues
No response
摘要 | Summary
Dear [Team/Support/Developer],
I hope this message finds you well. I am a user of your platform (Web-UI: https://chat.qwenlm.ai/) and would like to suggest a small but meaningful improvement regarding the file-saving feature.
Currently, when saving dialogues or conversations, the platform offers the option to download files in .txt format. However, upon inspection, the content of these files includes Markdown syntax (.md). This can be slightly misleading for users who expect plain text without any formatting.
To improve clarity and usability, I propose renaming the option from "Save as .txt" to "Save as .md" (Markdown). Alternatively, you could provide both options:
Save as .txt (plain text without Markdown syntax)
Save as .md (with Markdown formatting preserved)
This change would:
Make the file format more transparent for users.
Align with the actual content being saved.
Enhance the user experience for those familiar with Markdown, as they could directly use the files in editors or platforms that support Markdown.
Thank you for considering this suggestion. I believe it would make the platform even more user-friendly and intuitive. Please let me know if you need further clarification or additional details.
基本示例 | Basic Example
I choose "Download -> Save as .txt" option in a dialogue '...' menu, but have to rename downloaded file to .md since the file actually contains Markdown formatting.
And I'd like to use this format as is by several MD viewers.
缺陷 | Drawbacks
未解决问题 | Unresolved questions
There are redundant user actions on downloading dialogues.
The text was updated successfully, but these errors were encountered: