Re:RAG Is Simpler Than You Think
by jon-wood on Wednesday August 26, 2026 @07:04AM
(#49446902)
Instinctively this feels like a two phase problem - start with some machine translation into a single spoken language and index that, then when people are querying do the same thing. When returning search results show them in the original language.
[ Parent
| on HN ]
Re:RAG Is Simpler Than You Think
by whilenot-dev on Wednesday August 26, 2026 @07:27AM
(#49447106)
Why not create indexes for multiple languages, as that would also avoid double translation issues (e.g. GER [query] → ENG [index] → GER [document])?
you would also need to maintain multiple indexes in multiple languages. I never had to do that - but I assume it's a pain
Re:RAG Is Simpler Than You Think
by whilenot-dev on Saturday August 29, 2026 @04:47AM
(#49488132)
It's a matter of running a for-loop. You'd get faster response times (no query→index translation), but the storage requirements for the indexes would be larger.
Yes we've tried. It works. But jargon is hard. RAG with embeddings works all the same. The LLM doesn't mind receiving sources in Italian, french and German, and then outputting the answer in Japanese while providing the verbatim German jargon term in brackets
Embedding search is effectively machine translation into a single common ‘language’ - embedding space - and then searching that; cleaner and less lossy than translating everything into English for searching, but harder to debug when it goes wrong.