etc

Note that the only occurrence of `utf8_encode()` in core is `safe_encode()` function, that acts already as a wrapper.

It looks like a check for `is_callable('utf8_encode')` is already done in `safe_encode()`, wouldn't this suffice? As for `safe_decode()`, it is just a shortcut for `safe_encode($str, 'ISO-8859-1', 'UTF-8')`, probably not worth...

Dunno, maybe. Decoding to `ISO-8859-1` only seems to be used in mail functions. Once these few calls are swapped, we should be all done?

@Bloke yes, you can trash the whole `PHP in Templates` section, but only after 4.8 is released.

Thank you for the report, but I'm not sure textile interferes here. Could you provide more details re the article body content?

Thank you. Have you also set `escape="tags"` attribute before `trim`? Unless php `strip_tags()` function is somehow disabled on your server (see diagnostics), it should have removed all html tags prior...

Thanks @philwareham, that's fine for `css`, I would just put it more like this for `output_form`: ``` format="image, link, script, url" ``` eventually prepended by `flat.` to fetch the form...

@philwareham `` outputs various chunks of information that currently have no their own tag. For example, `` outputs pagination urls inside ``. I don't think it's ready for documentation.

Dunno, @Bloke and @NicolasGraph are your men for everything theme-related. But how can you upload a theme to @petecooper demo site, I thought it was write-protected?

> I don't think the default Page and Style is necessary any more. I was already for relaxing it in 4.7, but which Page/Style would we use on sectionless "home"...