Feature Proposal: Add encode, newline, nofinalnewline, allowanytype to INCLUDE Variable

Motivation

For some TWiki applications, more features are needed in %INCLUDE{...}%

Description and Documentation

nofinalnewline="on",

Borrowing from %SEARCH{...}%

encode="..."

Borrowing from %FORMFIELD{...}%

newline="..."

Borrowing from %FORMFIELD{...}%

allowanytype="on"

When you retrieve content from another web server, it may return a content type that %INCLUDE{...}% usually doesn't accept - %{...}% accepts only text/html and text/plain. If this parameter is on, INCLUDE accepts the content regardless of the content type.

There are cases where the content type field of an HTTP response has an unusual type such as application/octet-stream even though the content is actually text/plain. This parameter is useful in that situation.

Examples

Impact

Implementation

-- Contributors: HideyoImazu - 2012-11-02

Discussion

These are sensible enhancements.

I renamed the topic to be specific and trackable.

I am not clear on allowanytype. Is this the URI protocols? Protocols are already settable in configure.

-- PeterThoeny - 2012-11-04

I'm talking about the Content-Type: field of an HTTP response. I added some sentences clarifying that above.

-- HideyoImazu - 2012-11-05

Accepted by 7 day review period at JerusalemReleaseMeeting2012x11x09.

-- PeterThoeny - 2012-11-09

Topic name had a typo, which is now fixed.

-- HideyoImazu - 2012-12-25