On 10/17/13, Ryan Ollos <[email protected]> wrote: > On Thu, Oct 17, 2013 at 10:22 AM, Saint Germain <[email protected]> wrote: > >> On Thu, 17 Oct 2013 10:01:47 -0700, Ryan Ollos >> <[email protected]> wrote : >> [...] >> > Now that you've reminded me, a while back I added a note about the >> > issue to >> > >> https://issues.apache.org/bloodhound/wiki/BloodhoundContributing#GettingTheSource >> > >> > "The message catalogs won't be compiled and therefore language >> > translations won't be available since Trac has been installed in >> > editable/develop mode." >> > >> > The note is probably not too obvious. Maybe we can put it in a box >> > labeled "hint". I can't remember if we have a way to do this already. >> > Olemis, do you know? >> >> Well I _did_ read the first few words but skipped the rest as I didn't >> want localization at first (english is fine for the moment). But it >> seems that somehow in my setup en_US is processed as a local to be >> translated ? > > > I'm not sure why message catalogs are generated for en_US, but I'm going to > guess and say that Babel must not know what the "base" language is. All of > the `msgstr`s in that file are empty, so it appears to have no effect. >
afaict parent lang should be inherited ... > Ideally though, Trac wouldn't try to add the js file when the messages > catalogs aren't available. Presently the Trac codebase acts as if > translations are available when Babel is detected. I think this is behavior is not too bad considering performance . Could be improved by adding a bool config option ? > I've seen situations > where it only shows English as an available language, and others when all > the languages are shown. For the latter, this leads to the confusing > behavior I mentioned earlier, whereby the Language preferences panel > presents a list of languages when the message catalogs are not available, > and changing the active language leaves everything in English. I haven't > sorted out exactly the conditions that lead to each situation, but a > possible improvement to Trac would be to have it behave as if localizations > are available only when the message catalogs are available. > Checking actual availability of translation files may have an impact on performance and , considering the benefits afaict it's not worthy ... especially if a way to work around this requires an efficient bool check . ;) [...] -- Regards, Olemis - @olemislc
