On Wed, 29 Jun 2011, Alexander Wagner wrote:
> The above is sufficient, indeed. I missed the important
> point with the naming convention for triggering the
> content/type.
Note that these naming conventions are surviving in our code base mostly
due to our `laziness'. It should not be necessary to use them. We used
to use these conventions in the distant past, but then we switched to a
configurable content/type setup some years ago. However, many parts of
the code base still rely on the old technique:
if output_format.startswith('x'):
do_xml_stuff()
while only some parts of the code base switched to the new technique:
if get_output_format_content_type(output_format) == 'text/xml':
do_xml_stuff()
It has been one of several dormant `infrastructure' tasks on our TODO
list to release these output format naming conventions fully. I'll
ticketise this as well as some other tasks so that we have them listed
explicitly.
Best regards
--
Tibor Simko
