From 9ab166c31e2f109f76311eafc94995e331b47c20 Mon Sep 17 00:00:00 2001 From: sepehr Date: Sun, 31 May 2026 23:48:48 +0200 Subject: [PATCH] fix: glossaries page support for multilingual (target_language='multi') MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The /dashboard/glossaries page had two issues: 1. SUPPORTED_LANGUAGES had no 'multi' code, so multilingual glossaries showed '🌐 undefined' instead of '🌐 Multilingue' 2. The Compatible/Autre cible badge compared target_language directly with currentTargetLang, so 'multi' never matched → always showed 'Autre cible'. Now 'multi' is treated as compatible with any target. Co-Authored-By: Claude Opus 4.8 --- frontend/src/app/dashboard/glossaries/page.tsx | 5 +++-- frontend/src/app/dashboard/glossaries/types.ts | 1 + 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/frontend/src/app/dashboard/glossaries/page.tsx b/frontend/src/app/dashboard/glossaries/page.tsx index c9c883e..5d1f195 100644 --- a/frontend/src/app/dashboard/glossaries/page.tsx +++ b/frontend/src/app/dashboard/glossaries/page.tsx @@ -493,9 +493,10 @@ export default function GlossariesPage() { const termCount = glossary.terms_count ?? 0; const srcInfo = SUPPORTED_LANGUAGES.find(l => l.code === glossary.source_language); const tgtInfo = SUPPORTED_LANGUAGES.find(l => l.code === glossary.target_language); + const isMultilingual = glossary.target_language === 'multi'; // Does this glossary match the current translation target? - const matchesTarget = currentTargetLang && glossary.target_language === currentTargetLang; - const mismatch = currentTargetLang && glossary.target_language && glossary.target_language !== currentTargetLang; + const matchesTarget = currentTargetLang && (isMultilingual || glossary.target_language === currentTargetLang); + const mismatch = currentTargetLang && !isMultilingual && glossary.target_language && glossary.target_language !== currentTargetLang; return (