Dave Anderson writes: > >So, in summary, the options are: > > > >Use HTML escapes everywhere. IMO, highly impractical. > > > >Use any encoding you wish, and set a meta tag when appropriate. This is > >basically what we have now. (The front pages of /, /de/, /fr/ all use > >ISO-8859-1; /cs/ uses UTF-8; /lt/ uses ISO-8859-13.) > > > >Use UTF-8 everywhere, and enforce this either with an HTTP header or > >meta tags. > > You missed one: use any encoding you wish, and configure the server to > send the proper charset value in the real headers (by encoding the > appropriate charset info in the file-name extension).
I was limiting the options to those that can be easily mirrored. All of those are basically server-agnostic; yours is not. And I can't imagine a situation when you'd ever want to do that anyway--sticking to one encoding is much simpler and saner. -- Anthony J. Bentley
