tes with it.
On Tue, Aug 24, 2010 at 8:41 PM, Yo-Yo Ma wrote:
> @Josh - really helpful. Thanks. So, if Django had a bug pertaining to
> character encoding, it wouldn't be appropriate for me to report it
> here because I discovered it while I was developing a site.
--
Josh Ouris
uot;Django developers" group.
> To post to this group, send email to django-develop...@googlegroups.com.
> To unsubscribe from this group, send email to
> django-developers+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.co
possibility of reusing some of the rework done
there? If nothing else it certainly provides a good, working proof of
concept.
Cheers,
Josh
--
Josh Ourisman
j...@joshourisman.com
301-244-9674
--
You received this message because you are subscribed to the Google Groups
"Django developers&quo
ived this message because you are subscribed to the Google Groups
> "Django developers" group.
> To post to this group, send email to django-develop...@googlegroups.com.
> To unsubscribe from this group, send email to
> django-developers+unsubscr...@googlegroups.com
> .
>
ions, visit this group at
>> http://groups.google.com/group/django-developers?hl=en.
>>
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers" group.
> To post to this group, send email to django-develop...@goo
Why not just type the opening {%, then the stuff that goes inside, then the
closing %}. Seems like that would be easier for everybody (baring using a
reasonable editor or learning how to use yours properly).
--
Josh Ourisman
j...@joshourisman.com
301-244-9674
On May 26, 2010 3:27 PM, "D
