How to Answer
"Four areas change:
- (1)Embeddings — switch to multilingual model (e.g., multilingual-e5-large). Test retrieval quality per language — it degrades for low-resource languages.
- (2)Chunking — sentence boundaries differ. Use language-aware tokenizers. Arabic is RTL — ensure your pipeline handles it.
- (3)Evaluation — build golden sets per language. LLM-as-judge must be multilingual or use per-language judges.
- (4)Tool schemas — keep in English (models handle English schemas best). But response generation should be in the user's language. Add 'Respond in {detected_language}' to the system prompt. Cost implication: multilingual embeddings are larger; retrieval quality is usually 10-15% lower for non-English."