On Thu, Oct 17, 2013 at 8:02 AM, Ryan Ollos <[email protected]> wrote:
> On Thu, Oct 17, 2013 at 2:13 AM, Saint Germain <[email protected]> wrote: > >> Hello, >> >> I am evaluating Bloodhound (current trunk version and on Debian >> Testing) and here are a few feedbacks: >> >> 1) It seems that that we are missing trac/htdocs/js/messages contents >> (typically en_us.js) >> Indeed these javascript files are requested by line 983 of >> trac/web/chrome.py: >> if req.locale is not None: >> add_script(req, 'common/js/messages/%s.js' % req.locale) >> > > I've noticed this as well, but will have to investigate. > This will happen if the message catalogs are not compiled. If that is the case, you'll also likely notice that navigating to /prefs/language and changing the language has no effect. As you've noted already, once the message catalogs are compiled, you should find: ls trac/htdocs/js/messages/ ca.js en_US.js es_MX.js he.js ja.js pt_BR.js tr.js da.js eo.js et.js hu.js ko.js ru.js uk.js de.js es_AR.js fi.js hy.js nb.js sl.js zh_CN.js en_GB.js es.js fr.js it.js nl.js sv.js zh_TW.js If you install in development mode, the message catalogs will not be compiled. To compile them, you can cd to the trac sources directory and run "python setup.py install". If you did not install in development mode, then we need to figure out why the message catalogs are not compiled. I suppose there could be a problem with your Babel install. > > >> 2) When accessing the 'Source' tab, I got a message saying that: >> trac/chrome/theme/css/browser.css is not found >> However I have in my directory: >> trunk/trac/trac/htdocs/css/browser.css >> So I don't see why it is not found. >> I've tried moving browser.css in >> trunk/bloodhound_theme/bhtheme/htdocs/css but then I have thousands of >> errors after that. >> > > I'll see if I can reproduce and get back to you on this one as well. > It looks like we have an open ticket for this issue: https://issues.apache.org/bloodhound/ticket/584 I'll see if it is possible to close out that ticket now.
