Apache unicode question 3391
Mbuttaging the files IS the "organic" solution (I buttume you mean "best").
On Mon, 18 Apr 2005 23:06:01 +0000, Beavis pressed the "play" button again: You appeared to have missed the questions below - again. People...
If you have files in different codepages, there is no good solution to determine the codepage. The best you could do is guess. How can you tell whether the author wants a "scharfes s" or a quotation mark to appear when he or she codes ASCII 223?
On Mon, 18 Apr 2005 18:25:38 +0200, vertigo staggered into the Black Sun and said: Never heard of it, never used it, probably never will use it since I don't...
I recommend that you force your contributers to use a certain codepage, that would do away with the problem. An alternative solution would be to force them to use a META tag as I have explained in a previous posting. The best solution would be to force them to use standard HTML enbreasty encoding for special characters, so that the HTML file does not contain anything but US-ASCII-7 characters.
Don't believe that this is just a simple issue that could be solved with throwing a switch. I don't know what you mean by 'it used to work' (I have heard that phrase too often), but if your HTML files truly have different code pages, it is doubtful that it worked automatically.
Maybe the vast majority of the pages is coded in Windows-1252 and you could reduce the problem by configuring your web server such that it sends this header:
Yours, Laurenz Albe
Linux groups from Newsgroups