Danny, All, Sure. I think status quo is important. Luckily, (and thanks to all the infrastructure team members and board) I got an account on daedalus, I am now *exploring* under the /x2/www/ directory. If I do not have basic knowledge on daedalus, my *imaginary-best-idea* might be meaningless...
There might be the best solution for putting the translation efforts, but I am just wondering how to implement. Please give me more time. cf. James Website Translation into Korean: http://jakarta.apache-korea.org/james/ Sincerely, -- Tetsuya ([EMAIL PROTECTED]) P.S. If I describe the condition of /x2/www/jakarta.apache.org/ in one word which came to my mind, it might be .. *CreteLabylinth* , big spectacle :D --------------------------------------------------------------------- On Mon, 21 Jul 2003 14:27:41 +0100 (Subject: RE: [l10n] localisation infrastructure) "Danny Angus" <[EMAIL PROTECTED]> wrote: > > (a) keeping translations up-to-date, > > This is why I'd prefer the status quo, currently we have a Japanese > translation of James site and docs which is "unofficial" but linked from the > James site. > > What this means is that the Japanese is available but is not authoritative. > If we publish Japanese on james.apache.org this would be seen as > authoritative and MUST therefore to be up-to-date and accurate. > > We have no-one among the James commiters who writes a word of Japanese, and > we couldn't necessarily rely upon Tetsuya being available to translate when > we want him to. > > I'm very much in favour of having translations, but concerned about the > resources required not to create them but to maintain them. > > d.
