With lang_to_table, the thing is that we want to be able to create any source
and target language. Actually we want to be able to use the source code as a
'project identifier'. I.e. we can have multiple projects for one language pair
and want to be able to use different TM'S (while only running one tm server)
for each. Like this: /tmserver//
Ok, then we maybe need to talk about this a bit more. If you change the source
language code, you also affect the way the indexing happens, which can affect
the results you get when querying the server, and might make things a bit
slower even. If we get this into a separate bug that might help us discuss this
a bit more, but maybe an IRC meeting or dedicated mail session is even better
to work out exactly how you want to use this.
(split from bug #1960 which contains multiple issues)
transl8bzimport
commented
13 years ago
Originally posted by Marce van Velden:
Ok, then we maybe need to talk about this a bit more. If you change the source language code, you also affect the way the indexing happens, which can affect the results you get when querying the server, and might make things a bit slower even. If we get this into a separate bug that might help us discuss this a bit more, but maybe an IRC meeting or dedicated mail session is even better to work out exactly how you want to use this.
(split from bug #1960 which contains multiple issues)