Re: Path problem with jsi18n - internationalization

Did you try to access it like http:jsi18n/ ? I have http:///jsi18n/ 404 too, but it's okay with locale. It's not good, but at least it's something On Tuesday, January 13, 2009 12:02:47 PM UTC+3, Tipan wrote: > > > > > That's strange, are you succesfully using another component of Django

Re: Path problem with jsi18n - internationalization

> > That's strange, are you succesfully using another component of Django > i18n infrastructure in the same application?. De you have USE_I18N set to > True in the settings file you are using? > Yes. The use_i18n is set to true and I've successfully translated most of my pages, created the .po

Re: Path problem with jsi18n - internationalization

On Sun, Jan 11, 2009 at 6:43 PM, Tipan wrote: > > Hi Ramiro, > > I'm using the latest development version of Django. Apache web server. > MySqL/Mod_python, all served from same apache on my laptop. > > I get a 404 error when I put http:///jsi18n/ into the browser > URL. >

Re: Path problem with jsi18n - internationalization

Hi Ramiro, I'm using the latest development version of Django. Apache web server. MySqL/Mod_python, all served from same apache on my laptop. I get a 404 error when I put http:///jsi18n/ into the browser URL. Rgds, Tim --~--~-~--~~~---~--~~ You received this

Re: Path problem with jsi18n - internationalization

On Sun, Jan 11, 2009 at 2:48 PM, Tipan wrote: > > I'm having a problem accessing Javascript Translation catalog whilst > converting my site to multi-language. As suggested in the docs, I have > added the following to my applications top level urls file. > > > js_info_dict = {

Path problem with jsi18n - internationalization

I'm having a problem accessing Javascript Translation catalog whilst converting my site to multi-language. As suggested in the docs, I have added the following to my applications top level urls file. js_info_dict = { 'packages': ( 'myapp.myproject',), } (r'^jsi18n/$',