#3308: Escaped documentation in admin site
-----------------------------------------------+----------------------------
   Reporter:  Noah Slater <[EMAIL PROTECTED]>  |                Owner:  adrian  
       
     Status:  new                              |            Component:  Admin 
interface
    Version:                                   |           Resolution:          
       
   Keywords:                                   |                Stage:  
Accepted       
  Has_patch:  0                                |           Needs_docs:  0       
       
Needs_tests:  0                                |   Needs_better_patch:  0       
       
-----------------------------------------------+----------------------------
Changes (by mtredinnick):

  * stage:  Design decision needed => Accepted

Comment:

 Well, the above example looks wrong, but a fix is going to need careful
 thought: any raw text should be escaped before being dumped into the doc
 pages, just so that you can write "3 < 5" in your docstrings and not have
 it break on output. Anything that has gone through docutils, though,
 should not be escaped, since it's already HTML. I used to remember which
 parts were which, but I do remember it's not too hard to work out.
 
 However, the bug also shows another problem: the "bar" string really
 doesn't want to be in paragraph tags in the first place. So we may need to
 look at that as well. May be multiple problems here, or all handled by one
 simple fix. Not sure.

-- 
Ticket URL: <http://code.djangoproject.com/ticket/3308#comment:3>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django updates" 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-updates?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to