From Eloy Lafuente (stronk7 at moodle.org) Monday, 9 May 2005, 11:52 PM:
Yeah, I know!
The problem was that, after testing it, the number of changes required to make course names multilang is really big (hundreds).
I'll retake it after finishing other prioritised tasks (at least, for the global community) 
For a complete list about the multilang degree of implementation, you can take a look to:
http://moodle.org/mod/wiki/view.php?id=2935&page=CFGFilterAllSupport
(I try to maintain it updated)
Ciao 
From Robert (rjb at robelko.com) Tuesday, 31 May 2005, 09:47 PM:
IMHO, multilang filter should be used for inline translation but not for wholesale multilingual course setup. I think that courses and activities should use a model parallel to language packs for full multilingual implementations. May be each language should have a setting [monolingual/multilingual] which would trigger using private language files.
Even some of the moodle pages itself would benefit. For example, I am providing custom instructions for login (using pop3 authentication). The text box for entering/editing it is kinda small for one language and becomes quite messy if I enter it in several languages. If would be simpler if I could say use such-and-such string from language pack and define these using language editing interface for any language I wish.
From Eloy Lafuente (stronk7 at moodle.org) Wednesday, 6 July 2005, 08:25 PM:
Uhm,
I agree that the multilang filter isn't the correct solution for all the situations. The DB approach sounds really nice (although it'll imply a huge modification of current code at 'introduction' level to support it).
Anyway, in the long term, it could be implemented because it provides some interesting features, sure (perhaps we could add this as a MUST feature for the 'everything-is-a-post' implementation when such work was started?).
From Eloy Lafuente (stronk7 at moodle.org) Monday, 9 May 2005, 11:52 PM:
Yeah, I know!
The problem was that, after testing it, the number of changes required to make course names multilang is really big (hundreds).
I'll retake it after finishing other prioritised tasks (at least, for the global community)
For a complete list about the multilang degree of implementation, you can take a look to:
http://moodle.org/mod/wiki/view.php?id=2935&page=CFGFilterAllSupport
(I try to maintain it updated)
Ciao
From Robert (rjb at robelko.com) Tuesday, 31 May 2005, 09:47 PM:
IMHO, multilang filter should be used for inline translation but not for wholesale multilingual course setup. I think that courses and activities should use a model parallel to language packs for full multilingual implementations. May be each language should have a setting [monolingual/multilingual] which would trigger using private language files.
Even some of the moodle pages itself would benefit. For example, I am providing custom instructions for login (using pop3 authentication). The text box for entering/editing it is kinda small for one language and becomes quite messy if I enter it in several languages. If would be simpler if I could say use such-and-such string from language pack and define these using language editing interface for any language I wish.
From Eloy Lafuente (stronk7 at moodle.org) Wednesday, 6 July 2005, 08:25 PM:
Uhm,
I agree that the multilang filter isn't the correct solution for all the situations. The DB approach sounds really nice (although it'll imply a huge modification of current code at 'introduction' level to support it).
Anyway, in the long term, it could be implemented because it provides some interesting features, sure (perhaps we could add this as a MUST feature for the 'everything-is-a-post' implementation when such work was started?).