Hi all, I'll just keep patiently bumping my own bugreport, i.e. http://code.djangoproject.com/ticket/14924
I also do have something new to add & request since last time on this list. I'd like to have some discussion on my own comment below: I'd like to have some input on the most desirable order of looking for localization sources. Having looked at the original tests the most desirable order appeared to be: 1. Project path locale 2. Apps (in correct order) 3. Locale- path 4. Django's own translations I made a patch (submitted in the bugreport) which I have running in some production code now, and I'm feeling this is not the most logical order. (The order was originally established by looking at the existing tests and code, and matching that order as closely as possible while making sure the apps are evaluated in the correct, not reverse, order). However, in my mind, locale path should be the first to be evaluated. The reason someone would put up a specific path for locales pretty much has to be to override the existing behavior (which would be found in project and apps). At least, that is how I use and want to use the explicit locale path. Input (discussion) on this is much appreciated. I'll gladly put in a new patch once a decision is reached. If this is a separate issue, I'm also fine on opening a separate ticket. (it could be argued that we can move forward on the original bug report as a separate issue more easily, since it's "obviously broken") ciao, Klaas On Dec 23 2010, 5:00 pm, Klaas van Schelven <[email protected]> wrote: > Thanks for the notification! > > On Dec 23, 2:24 pm, Ramiro Morales <[email protected]> wrote: > > > > > > > > > Klaas, > > > On Thu, Dec 23, 2010 at 7:43 AM, KlaasvanSchelven > > > <[email protected]> wrote: > > > Hi all, > > > > Thanks for checking in 14910! > > > > Could anyone take a serious look at > > >http://code.djangoproject.com/ticket/14924 > > > > It has a test that proves the problem and a relatively simple patch. > > > > I'm doing a lot of "app overriding" and this bug is extremely annoying > > > in that case. It would be great if the fix could still make it to 1.3 > > > I'm pretty sure a design decision will be made about it before 1.3 gets > > released. It is in the list of tickets I want to look at, and I know it is > > in > > the radar of at least one core developer. > > > Just bear with us, we have a lot of tickets (some of them older > > and/or uglier) to review and fix and one almost seven weeks to work on > > bug killing before 1.3 goes gold. > > > Thanks for reporting, following and contributing to the solution of > > this old issue, and for your patience. > > > -- > > Ramiro Morales -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
