fix: use vlm_description_localized directly instead of text_content

- Card now shows vlm_description_localized directly (no 【ZH-TW】 label)
- Avoids incorrect language labels from Core API text_content field
- Japanese content now displays correctly without wrong prefix
This commit is contained in:
2026-10-27 15:16:09 +08:00
parent 98161f3ebd
commit ece3747a98

View File

@@ -152,7 +152,8 @@
</span><span v-html="highlightMatch(r._isPerson ? r.file_name : parseSummary(r.summary).text, r.search_query)"></span>
</div>
<div v-if="r._isPerson" class="card-text card-person-stats">{{ r.text_content }}</div>
<div v-if="r.text_content && !r._isPerson" class="card-text" v-html="highlightMatch(r.text_content.slice(0, 120), r.search_query)"></div>
<div v-if="r.vlm_description_localized && !r._isPerson" class="card-text">{{ r.vlm_description_localized.slice(0, 120) }}</div>
<div v-else-if="r.text_content && !r._isPerson && !r.vlm_description_localized" class="card-text" v-html="highlightMatch(r.text_content.slice(0, 120), r.search_query)"></div>
<div v-if="r.vlm_tags && r.vlm_tags.length" class="card-tags">
<span v-for="(tag, i) in r.vlm_tags.slice(0, 5)" :key="i" class="card-tag">{{ tag.local || tag.en }}</span>
</div>