CRLF line endings 2001-12-19
In David Lynch, as an example, if you inspect the resulting page, apparently, each stored line is ended with a CR-LF sequence. However, if I edit it within Lynx, the endings disappear, as they don't exist on Unix. That's all good, but all edits will then differ in all the lines (since no lines match their previous version, everything has a different ending..) See, for example: [] I just fixed a typo in the first lines, and it looks as if everything has changed. Arguably, Lynx, and/or my text editor can be at fault too, but I don't think CR-LF should be stored as part of the text either.. --Chexum
On going to a random page I got http://www.wikipedia.com/wiki.cgi?NNTP, what came up was nntp, I redirected it to NNTP but this did'nt work. "Describe the new page here." would'nt go away. Also if I go to http://www.wikipedia.com/NNTP by searching and edit it when I hit save I am directed to nntp rather than my changed version. If I click on the NNTP link in this paragraph I get a 404 error.
I'm not sure if this is a bug: when you search for something, the old logo shows up on the search page, as in http://wikipedia.com/search.fcgi?request=happy
All's Well That Ends Well When I try to get to the page http://www.wikipedia.com/wiki/Alls_Well_That_Ends_Well--Text (Alls Well That Ends Well--Text), I get a 500: Server Error. This is the only page that's been doing this to me in recent months, and it's done it every time I've gone there. -- BD
Diff function http://wikipedia.com/wiki.cgi?action=browse&diff=1&id=Tissue gevies me the diff of 1394. Finally, a bug I won't have to fix myself ;) -- Magnus Manske, November 26, 2001
http://www.wikipedia.com/wiki.cgi?action=browse&diff=2&id=Vegetarianism gives the diff of JT. -- KQ, December 2 2001.
Superscripts in ASCII Tables distort vertical lines
This isn't really a bug, but I thought I should pass it along. There are some footnotes in the geologic Timescale 11/26/01 that are superscripted using HTML. They don't look all that bad in IE, but they do somewhat alter the spacing of the vertical bars following them on the same line in this ASCII table. They look worse in a text mode browser like LYNX than in IE or Netscape. Same will be true of other HTML that alters text sizes. That is the way things are I guess. Also, I suspect that ASCII tables and ASCII art (if any) need to be checked with LYNX. I trimmed the geologic Timescale to get a one to one of intended lines to displayed lines when using Lynx. Others might want to do the same if they have similar situations.
<XHTML bug moved to NEW>
AOL Bug Users of America Online versions 4.0 and 5.0 FOR APPLE MACINTOSH running on various PowerMacs? with down-lever OS 8.5 and 8.6 (sorry I should have said) can no longer access Wikipedia -- they see a blank web screen and unaccountably a download dialog box opens and invites them to save "untitled" to their hard drives. AOL tech support confirms this and simply does not care. Since the world is teeming with prospective readers and contributors who may be using AOL, is there anything to be done, besides the obvious work around of running external browser? -- WOL
Case sensitivity Links that do not work:
Example: Nitroglycerine. Compare the source with the appearance. Is something wrong. (At the time i make this complaint, there is no such article. This may matter.)
I assumed the site was junk and didn't bother looking at it again for months. You really should fix this ASAP. Who knows how many potential participants have been lost. I'd recommend more care with initial user entry into the site; that's make or break time.
Note: caching problems are more common in the Czech version.
Pages claim to be XHTML 17 November 2001
Wikipedia pages include a DOCTYPE that claims the content is XHTML Basic. Given just how far from the truth this is, and how difficult it will be to ensure correctness when anyone can enter a range of HTML tags, no DOCTYPE should be included at all.
Examples of HTML used that isn't XHTML Basic below. See  for an even more picky analysis.
This does have actual effects on the pages: in Mozilla, the top hr element overlaps the logo, and nested indents (like on Carey Evans/Talk) don't work.
The pages also claim to be UTF-8 encoded XML (<?xml ...?> PI at the top of the page) while the HTTP headers say ISO-8859-1.
I can confirm this. The problem with nested indents is particularly bad, as it makes some pages more difficult to read. -- Taral