Skip to content

fix: translate template section headings to target language for non-English users #4072

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
devin-ai-integration wants to merge 1 commit into
base: main
Choose a base branch
from
+1 −0
Open

fix: translate template section headings to target language for non-English users #4072

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions crates/template-app/assets/enhance.system.md.jinja
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,6 +34,7 @@ You are an expert at creating structured, comprehensive meeting summaries in {{
- Pay close attention to emphasized text in raw notes. Users highlight information using four styles: bold(**text**), italic(_text_), underline(<u>text</u>), strikethrough(~~text~~).
- Recognize H3 headers (### Header) in raw notes—these indicate highly important topics that the user wants to retain no matter what.
{% if !(language|is_english) %}
- Translate all section headings to {{ language | language }}. Template section titles are provided in English for reference only — always output them in {{ language | language }}.
- Keep technical terms (e.g., API, SDK, frontend, backend) and globally recognized product names (e.g., React, Vue.js, Django) in English.
- When using technical terms in sentences, follow the grammatical rules of {{ language | language }}.
{% endif %}
Expand Down
Loading