Don Spaulding wrote: > > > On Tue, Sep 16, 2008 at 2:20 PM, Don Spaulding > <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote: > > > Hope it's useful! > > > > and of course it isn't. I forgot my lambdas. Doh! > That's a great start. I noticed that many Google links are to fragments, and wondered if we could do some sort of recognition on them. It turned out to be interesting, as I was hadn't realised the documentation doesn't implement fragment references in the expected way.
I pulled down the current documentation and the 0.96 stuff with websucker - I think it broke before it got quite all the old stuff, but the majority is present. The work I have done would really best be done on the final version of the pre-1.0 documentation before it was converted to the new organization, but I couldn't find that. So far I've only looked at the section headings, which can be located easily as <div class="section" id="...">. There are 119 sections like general-questions genericsitemap specialities-of-django-translation definitive-urls creating-models installation-questions template-inheritance overriding-default-model-methods less-code and serialization-formats which don't seem to appear (as sections) in the new documentation. So it's goodbye to them unless they appear as other structures in the new documentation. There are apparently 678 newly-minted sections like module-django.forms.fields using-generic-relations-as-an-inline inherited-models onetoonefield extra-methods-on-managers-when-used-in-a-foreignkey-context post-delete inlinemodeladmin-objects module-django.test module-django.http and the-file-object that never appeared (as sections) in the old documentation, so we don't need to worry about them unless they appeared as tags on some other type of object. The *good* news is that there appear to be 789 sections that can be redirected (hopefully with 301s, so Google and pals will pick up the new locations), of which a few examples are: Tag requesting-features was: ./contributing/index.html now: dev/internals/contributing/index.html Tag font-sizes was: ./admin_css/index.html now: dev/obsolete/admin-css/index.html Tag relationships was: ./model-api/index.html now: dev/topics/db/models/index.html Tag phone2numeric was: ./templates/index.html now: dev/ref/templates/builtins/index.html Tag pprint was: ./templates/index.html now: dev/ref/templates/builtins/index.html Tag restarting-the-spawned-server was: ./fastcgi/index.html now: dev/howto/deployment/fastcgi/index.html Tag basics was: ./templates_python/index.html now: dev/ref/templates/api/index.html Tag how-to-add-change-and-delete-redirects was: ./redirects/index.html now: dev/ref/contrib/redirects/index.html Tag seeing-which-settings-you-ve-changed was: ./settings/index.html now: dev/topics/settings/index.html Tag custom-default-settings was: ./settings/index.html now: dev/topics/settings/index.html Sorry that the old and new references aren't strictly comparable: this has been a spare time project in a rather busy week. I'm sure it's fairly obvious where they can be found. The question is: is it worth continuing this web-scraping and analysis and potentially extending it to other reference mechanisms I am unaware of? I don't know whether the current redirection will eventually cause the web search engines to throw away the old references, but it would be nice to be able to move them forward if possible. regards Steve --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
