Hey Karen, Thanks for your fast reply.
Well, I searched around and it seems that a lot of people aren't too happy with Python's default title() functionality. ( http://muffinresearch.co.uk/archives/2008/05/27/titlecasepy-titlecase-in-python/ ) >From a publishing point of view, I don't know for sure Python's method is correct. Personally, I don't think so. It is logical to put a capitalized letter after a semicolon, but that's certainly not the case if it's in a word ( Like Foo;bar, from my example ). > 1 - the existing behavior mirrors Python so is unsurprising in a > Python-based framework Ok, but then you would to actually change the documentation accordingly. It now states that it converts a string to title case and what Python title method does is not what it "should" do. ( I already discussed that ). > 2 - changing it at this point is backwards-incompatible True, maybe put this patch to 2.0? > 3 - you can easily write your own filter to title case in whatever manner > you want That's also true, but you can almost override any component that is in Django, thus saying this sounds like "Yeah, you can override everything anyway." So, in conclusion, I think this should be put into 2.0, under the condition that we can confirm Python's title method isn't publishing- friendly. We need someone in publishing to back us up on this one. Another solution would be to change the documentation, because what we do now probably isn't "proper" title casing. Greets, Henk. On 4 nov, 14:44, "Karen Tracey" <[EMAIL PROTECTED]> wrote: > On Tue, Nov 4, 2008 at 8:08 AM, H. de Vries <[EMAIL PROTECTED]> wrote: > > > > > > > Hey all, > > > I pretty new to developing for Django itself and for that reason I > > have question. > > > 4 days ago I submitted a bug and I wrote a patch and tests for it. I > > noticed through the timeline that there are people that review > > tickets. > > > Problem is, I haven't had any response on my ticket yet. How long does > > it usually take for someone to review a ticket that has a patch and > > tests? > > > I know in open source projects things can sometimes take a while. It > > would awesome if my patch would make it into 1.0.X ( if that isn't too > > late, I just read on the blog today about the beta and the 1.0.X > > branch ). > > > This is the ticket I'm talking about: > >http://code.djangoproject.com/ticket/9483 > > Four days is not very long. I personally have not responded on that ticket > because I have no background in publishing or editing to know what the > correct behavior is for converting to "title case". You assert that the > current behavior is wrong, but to me it actually looks correct; I was hoping > someone connected to publishing with more of a clue in this area than I > would chime in, but four days has not been long enough for any such > qualified people to have the time. > > Regardless of what is technically correct for title casing, I'd be leery of > changing the existing title filter at this point. It seems like there may > be people using it who expect the current behavior, and to suddenly change > the behavior would be backwards-incompatible for them. So my inclination > would be to close that ticket as wontfix based on the fact that: > > 1 - the existing behavior mirrors Python so is unsurprising in a > Python-based framework > 2 - changing it at this point is backwards-incompatible > 3 - you can easily write your own filter to title case in whatever manner > you want > > But like I said I don't know what is technically "correct" for title casing, > so if what you are proposing is the generally accepted way than perhaps > there is a case to be made for including in Django a filter that does casing > that way. > > Karen --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
