[FIX] structures: Charset sepcified for structures tree exports was not correctly handled by Internet Explorer (it expects 'utf-8' instead of 'utf8'. Firefox handle both without problems). Moreover, there is no need for the HTML tags since they have no real effect (neither on the charset, nor on the formatting since everything is only in PRE tags). If we really need this file encoding to be correctly detected outside the browser (were the HTTP headers won't exist), we will have to choose between a BOM (Byte Order Mark) at the file's beginning or HTML tags with a charset specified using http-equiv in a META tag.
[FIX] structures: Charset sepcified for structures tree exports was not correctly handled by Internet Explorer (it expects 'utf-8' instead of 'utf8'. Firefox handle both without problems). Moreover, there is no need for the HTML tags since they have no real effect (neither on the charset, nor on the formatting since everything is only in PRE tags). If we really need this file encoding to be correctly detected outside the browser (were the HTTP headers won't exist), we will have to choose between a BOM (Byte Order Mark) at the file's beginning or HTML tags with a charset specified using http-equiv in a META tag.


git-svn-id: 3d5924c06390d9880c3f6dc8614bfed48a70bf89@7912 b456876b-0849-0410-b77d-98878d47e9d5

oregional/tiki,tikiorg/tiki,changi67/tiki,tikiorg/tiki,oregional/tiki,oregional/tiki,changi67/tiki,oregional/tiki,tikiorg/tiki,changi67/tiki,changi67/tiki,changi67/tiki,tikiorg/tiki