nextcloud / nextcloud/assistant
Markdown support of translations
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 88
- Forks
- 43
- Avg merge
- 18h 49m
- Merged PRs (30d)
- 3
Description
(I'm not sure that this issue belongs here but I think so. – Nextcloud 31.0.8, Assistant 2.6.1, AI configured with mistral-large by Le platforme)
May be related to #56.
When I use the "translation" function, the model usually returns Markdown. However the result is displayed
- as plain text (instead of Markdown), and
- without line breaks.
This makes it really hard to understand. Example:
I suggest to handle Markdown either by default, or at least make it an option.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named. Start at the translation function's result-rendering entry point and reproduce the issue with a Markdown response from the configured model. Done means translation output is rendered as Markdown with preserved line breaks, either by default or through a user-visible option.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100