German Wikipedia logo look so much better than ours? Can we do whatever they did? Notice their smooth anti-aliasing and lack of any white edge around the globe, despite the transparency. Any thoughts?
I emailed all this to Brion about 3 weeks ago, but he didn't respond. I was going to wait another week, before emailing someone else, but since you've brought it up... :)
Well I doubt there is any one person in control of the logo, I'd imagine any admin can change it. I defiantly agree with its replacement, I say just use the exact image that our German counterpart is using, bar the German tag line of course... ☯Ferdia O'Brien(T)/(C)19:07, 11 May 2008 (UTC)
This has long been suggested but there's been no activity and has turned largely into a farce. Someone needs to take the initiative and get the mistakes in the logo fixed and the ugly transparency problems and get them included. -Halo (talk) 18:22, 12 May 2008 (UTC)
Oops, please note I corrected the DE link above. Apparently dewiki is configured to draw their logo from a location other than the default. Dragons flight (talk) 14:27, 15 May 2008 (UTC)
Thanks again. One more question: Anyone have any idea which fonts were used for the banner? I can fix the globe easily by copying the German one, but the English text has aliasing problems and I obviously can't copy the German text. Equazcion•✗/C •14:46, 15 May 2008 (UTC)
PS I just need to know which one was used for "The Free Encyclopedia". "WikipediA" itself can be copied from the German logo as well. Equazcion•✗/C •14:47, 15 May 2008 (UTC)
I also like the look of the Simple Wikipedia, it is very crisp and clean. Maybe just a tiny contrast adjustment and it would be better than the German Wikipedia. -- penubag (talk) 07:40, 19 May 2008 (UTC)
Let me know what you think. This is Image:WikiNewSample.png, a sample showing the new image, Image:WikiNew.png, against our background. See Image:WikiNew.png for the actual new logo with transparent background. According to the Bugzilla response, when we're ready, the image needs to be uploaded to Image:Wiki.png, then full protect the image description page again, then re-open the bugzilla ticket. Equazcion•✗/C •15:49, 15 May 2008 (UTC)
Definitely support I don't even know if this is controversial. I mean, it's not like we're changing the logo, it's just a higher quality version than we had before. J.delanoygabsadds16:58, 15 May 2008 (UTC)
I honestly can't see the difference. And does it make a difference? Who stares at the logo for hours deciding how transparent the barely visible back layer of colouring is? NIN (talk) 17:58, 15 May 2008 (UTC)
The difference is subtle, but on a site as prominent as ours, subtle imperfections come across as unprofessional. This would also vastly improve the appearance of user pages that have custom background image placed under the logo, such as User talk:LaraLove. I know that's not the most important thing to consider, but it is an added benefit. Equazcion•✗/C •18:06, 15 May 2008 (UTC)
i like the crisper look of the old logo. The new one looks too soft. Maybe something inbetween? --Dschwen18:15, 15 May 2008 (UTC)
Like Lawrence Cohen, I do not really even see a need for a discussion about this, I say apply WP:BOLD and just change it. Tiptoetytalk18:33, 15 May 2008 (UTC)
It needs to be done by an admin. Place Image:WikiNew.png at Image:Wiki.png, then full-protect the image description page again. Once that's done I can re-open the bugzilla ticket and the devs will make the switch. Thanks. Equazcion•✗/C •18:36, 15 May 2008 (UTC)
As far as I'm concerned, in direct comparison I like the new one better. I'd never notice the difference if they were on different pages. So yes, go ahead... --Stephan Schulz (talk) 20:24, 15 May 2008 (UTC)
Belated support. This one looks much cleaner to me. The lack of any halo artifact makes the illusion of depth look much more striking. Note, the new lettering below looks a bit thick/heavy to me but it's still professional and will likely show up more clearly on some displays. Gwen Gale (talk) 21:35, 15 May 2008 (UTC)
Yes if only it were that easy. I've done all I could, finished and submitted the request as instructed, roughly 6 hours ago, and so far nothing. Sigh. There's a reason Germany is ahead of us in the technology, wokmanship, and logo department. Equazcion•✗/C •01:44, 16 May 2008 (UTC)
Comment - Thanks for all the support. The new logo has been uploaded to Image:Wiki.png. We're now just waiting for a developer to get off his or her duff and make the switch. The request is at bugzilla:14137, in case anyone with a bugzilla account would like to comment there. Equazcion•✗/C •22:18, 16 May 2008 (UTC)
Seriously, there was an article in the New York Times about this on June 25, 2007. See my other comments at the top of this thread for the relevant links and details. Can nobody figure out how to fix these handful of problems at once?!? There are 2 major character issues (Devanagari and Japanese), and 2 minor misplaced accents (Ώ and Й), plus the aesthetic issues discussed above. I'm going to poke a few other talkpages/people, see if we can finally solve it. -- Quiddity (talk) 22:42, 18 May 2008 (UTC)
"Fix completely, or not at all"... I just love people who say that. How 'bout: "Bitch about it and fix it, but don't bitch about it while demanding that others fix it." It's along the same lines, you see. Complaining is just a partial fix -- the least-helpful part -- and yet, you demand that others either do a complete job or not try at all. Think about it. Equazcion•✗/C •23:09, 18 May 2008 (UTC)
I'm just saying, whilst we have the people together, and the programs open, and the issue raised, wouldn't it be nice to solve the multiple problems? It's shinier now, but it's still wrong. -- Quiddity (talk) 23:39, 18 May 2008 (UTC)
Yes, it's a capital idea. However to say that if all issues can't be fixed then none should be fixed is just wrong. I hope we agree there. Equazcion•✗/C •23:48, 18 May 2008 (UTC)
I just learnt, the character was not tamil, it's khmer. Quiddity, can you confirm what else is pending in Thue's version? Regards, Ganeshk (talk) 03:08, 19 May 2008 (UTC)
Yes, all the character errors seem to be fixed in Thue's version (2 characters, 2 accents).
I don't know the technical details of the transparency/anti-aliasing error, so that might be an issue still? -- Quiddity (talk) 06:19, 19 May 2008 (UTC)
If the developers change the logo settings to point to Image:Wiki.png, as we want, then the sitewide logo could be subsequently updated by any admin that uploads over that protected image. In other words there would be no bottleneck to uploading further corrections as they became available. Dragons flight (talk) 05:25, 19 May 2008 (UTC)
See Nohat's comments at the end of Talk:Main Page/Archive 86#Wrong devnagari symbol for "wi" in Wikipedia's logo: "The logo is a trademark of the Wikipedia Foundation. It is not subject to the same editing policies as Wikipedia content. Even if someone were to make an acceptable replacement image, any change to the logo will have to be subject to the approval of the board."
That's part of the reason I'm suggesting we need get everything fixed at once. Any board members following this thread? -- Quiddity (talk) 06:19, 19 May 2008 (UTC)
The part about the legal status was a comment from April 2005. It has been resolved since then since Nohat signed over the copyright to the Foundation. Angela.14:53, 19 May 2008 (UTC)
Heaven help us. I know the arguments about WMF copyright as well as anyone, but if we need the Board's approval to remove the white lip from the edges, then we truly have sunk imto a bureaucratic hell. The logo is an unregistered trademark, and it certainly will continue to be their trademark even after the much discussed errors are corrected. And lastly, as a point of order, I believe the WMF executive (rather than the Board) is principally responsible for brand management. Dragons flight (talk) 06:39, 19 May 2008 (UTC)
On the legal issue: That's actually another reason to get the minor change implemented first before worrying about the character errors. This was brought up at the bugzilla ticket, and my only saving grace was the fact that this is such a minor change, and most of all that this change has already been implemented on most other language wikis. If we need to wait for the approval it would take to do something totally different, then we'll be waiting a while. It's better to get this minor graphical error fixed first, get the logo uniform with the other languages, and then start worrying about this more major change. Equazcion•✗/C •15:32, 19 May 2008 (UTC)
I think the aliasing issues were only present as a result of the scaling-down. The original high-res image didn't have those issues, so it would just be a matter of scaling this one down correctly for the small version. Though I do believe as someone said above that such a change would require board approval. Equazcion•✗/C •19:39, 19 May 2008 (UTC)
several glyphs have extra diacritical marks that make them read 'vih' or 'wih', while others have only the base 'vah'/'wah'. All should, I think, be normalized to use the base character, sans diacritic (where possible). For instance, the Devanagri and Tibetan/Bhutanese (far left, respectively 2nd & 3rd from bottom) glyphs read 'vih' and 'wih' respectively -- instead of unadorned व (U+0935) and ཝ (U+0F5D).
the Thai symbol (far right, bottom) should be ว (U+0E27 with diacritic วิ U+0E27+0E34) and not ฉ (U+0E09).
I am not going to work on that. As Quiddity remarked, making all the characters sound like "W" was not the original priority, and changing it is currently a lot of effort. But you could start a list at meta:Errors in the Wikipedia logo, and then it might be changed if we decide to regenerate the logo from scratch. Thue | talk09:30, 20 May 2008 (UTC)
Editing and History page issues
There are a few things about the basic pages that come up when "edit this page" or "history" is pressed that I would like to improve.
Above all, it's so aggravating when I accidentally fire off an edit with an incomplete summary (or worse, wasn't even double-checked properly) because I catch the "Enter" by mistake when looking for a punctuation mark typing the edit summary. Enter is supposed to trigger a default action for a Web page, and that action should be show preview, notsave page!
The proximity of the "this is a minor edit" checkmark to the Save Page box is also annoying, especially since style guidelines practically prohibit minor edits, and some people might not see them on edit summaries. I think I only once actually managed to press minor edit and save page with the same click, but it's still discomfiting.
On the History page, the current GMT time (as of the time the History report is generated) should be printed at the top of the page just above the most recent edit. This way it is possible for people to instantly see how long ago an edit was made without having to check the system clock, do mental arithmetic, wonder if they are set differently etc. This would help with vandalism and inadvertent edit conflicts. It would also occasionally help people to notice if they are looking at an old history page in their browser. Wnt (talk) 16:20, 17 May 2008 (UTC)
Actually, I rather like the enter key defaulting to save. When I'm done entering my edit summary, my next action is generally to save the page, and I wouldn't want to have to switch to the mouse in order to click the save button (or tab over to it). "Style guidelines prohibit minor edits" -- You might not understand what minor edits are. They're usually for spelling/grammar corrections, versus major removals or additions. They're not prohibited at all. If you look at your preferences under the "gadgets" tab, there's a tool available that will constantly display the current GMT time at the top of your browser. Equazcion•✗/C •16:35, 17 May 2008 (UTC)
If you want preview to be the default action, then turn on 'Show preview on first edit' in your editing preferences. Algebraist18:16, 17 May 2008 (UTC)
Thanks, everyone. The GMT clock is a handy gadget that I'd missed, though it doesn't mark when the History page was actually served. It's also true on reviewing the current guidelines that I've been underusing minor edits; I'm not sure if the policy has evolved or if I just never paid enough attention. Showing the preview on the first edit might serve as a workaround, though it's not quite what I had in mind - but I suppose that if an editor speaks up so soon who likes the current system I'm unlikely to find a strong consensus for a change. Ah well. Wnt (talk) 19:58, 17 May 2008 (UTC)
Suggestions for image pages: Titles and Info Boxes
I'd like to suggest two additions to image pages; titles (as opposed to file names), and image information boxes.
My first suggestion is titles. While images that are displayed within a wikipedia entry are in boxes that also contain the image's name and artist/photographer, once you click through to the image's own page, there is no longer a simple artist & title summary, only the file name. There might be comments, or general info on the artist that is not specific to the particular image, but not a dedicated place or requirement for an image title. That leaves it to the uploader to have thought to name the file with the picture's title, or at least something that isn't "IMG-0024", but that is rarely the case with images on the internet.
The first example's picture title is "Image:Hokusai-fuji7.png", and the second's is "Image:Red_Fuji_southern_wind_clear_morning.jpg". Rather than having those file names as titles, I think it would be better if each page's title has both the image name and file name, but on separate lines, like so;
Red Fuji Southern Wind Clear Morning, by Katsushika Hokusai Filename: Image:Hokusai-fuji7.png
It's personal preference that I want the image title to be bigger than the file name. I'd actually like there to be less of a size difference between the two lines, however this is the best I could do with my limited knowledge of html.
My second suggestion is for a standard info box underneath each image, which can be filled in by users. I would suggest the following (example based on page 2 mentioned above);
Artist: Katsushika Hokusai Title: Red Fuji Southern Wind Clear Morning Series: 36 Views of Mount Fuji Date: Original wood print circa 1830 Edition: circa 1930 reprint Materials: Wood block print on paper
"Materials" could also be "composition", or whatever word is appropriate to represent the many types of art styles as well as photography, diagrams, etc. Or perhaps there could be different options for different image types, whatever you think would work best. There could also be Additional Comments, where further information, anecdotes, et. could be mentioned.
I have no idea what any of that means! I'm just a user, I don't know anything about developing the site. I emailed with a suggestion, and was told to post it in the village pump. Is there, or perhaps there could be, a suggestions page, where people like me can add things like this? Wwoorrddss (talk) 12:15, 19 May 2008 (UTC)
You're in the right place, friend. Thanks for your suggestion! I'll try to break this down for you.
The images you linked are on Wikimedia Commons, which is a free image repository that any Wikimedia project (including this one, the English Wikipedia) can use. The tight integration allows us here on Wikipedia to simply link an image on Commons as if it were on Wikipedia itself. Anyway, because those specific images are on Commons, we here at the English Wikipedia can't do anything with them.
That said, I believe Gadget850 missed your point. You were merely using those images as examples, not requesting any specific change to those specific images. We do have images here on Wikipedia -- lots of them -- including some that cannot be uploaded to the Commons because they aren't free. Your proposal would certainly apply to those images.
Most of your proposal is something that could be done easily by whoever uploads the image. As Gadget850 mentioned, we have a template called {{information}} that includes some of the information you suggest, but any of it could be added free-form without using a template. The catch is that it's up to the person who uploads the image to provide that information.
Titling an image is trickier. The software that runs Wikipedia is coded to display the filename at the top of any media page, and I think most of the folks here would prefer it that way because it makes linking the image easier. Plus, a properly constructed filename is almost as useful as a title. Take, for example, one of my own images: Image:Rochester Midtown Plaza - Interior.jpg. It would be redundant to have a title on another line that just said "Rochester Midtown Plaza - Interior".
Your proposal is not a bad one, and most of what you suggest can be done now -- but it would have to be done by the person who uploaded the image. The titling proposal is a technical issue that could be addressed if there was a strong consensus for it. Thanks again for bringing your concerns here and helping to make Wikipedia a better encyclopedia!
The stub template currently has two links, one to "wp:stub", the other to "edit this page". See the proposal at Wikipedia talk:Stub#Proposal to change the second link to a short tutorial on how to add to an article, like on the French wikipedia. 199.125.109.126 (talk) 16:09, 18 May 2008 (UTC)
New idea for redirect templates
[Note: I take no credit for this idea, I am just the messenger.] User:Lenoxus has had an idea for standardisation of redirect templates. The idea basically boils down to a meta-template replacing all those separate templates for categorising redirects. This would allow standardisation and easy adding of multiple reasons to redirects. Please comment over at WikiProject Redirects to keep all discussion coherent. Thanks. RichardΩ612Ɣɸ 20:01, May 18, 2008 (UTC)
To clarify — I don't actually intend to replace the other templates, as they are extremely useful for categorization and succinct standard explanations. I might, howver, like to see them change their wording over time. Lenoxus" * "20:14, 18 May 2008 (UTC)
But surely if the categories and explanations were incorporated into the meta-template, as they can be, then it makes the others redundant? RichardΩ612Ɣɸ 20:23, May 18, 2008 (UTC)
Aha, now we're having a conversation! What I believe makes a templates-based system best is that it allows for shortcuts in a way categories don't. A redirect category and its associated templates can have as long a name as they like, but only templates can be properly redirected, so that, for example, one could enter dab or r dab into the template instead of Redirects to disambiguation pages, the current category.
Additionally, in the preview of the entered text, using templates allows for uniform explanations of why a page of type X should redirect to Y. If editors had to enter the information by hand every time, there would certainly be typos and other errors. Of course, I'm secretly assuming that MediaWiki will eventually be able to properly display all the text on a redirect page… is there a possible technical limit to that?
Oh, and I just realized that you may have pictured this template containing some basic explanations itself (such as abbreviations, plural forms, etc). My problem with that is that I don't want to limit the creative power of template creation for new kinds of redirects. If the meta-template had to be locked, for example, I wouldn't want editors to have to propose a change in order to be able to have the redirect page say whatever they have in mind.Lenoxus" * "21:25, 18 May 2008 (UTC)
The problem I have with keeping the template-based system is that every single template would need to be modified to have the line removed, and the explanations standardised. Have a look at my example and play around with it. It does include an 'other' option so that people can include a custom reason.
Even if the template was locked, a quick proposal at WT:RE could get things approved and added by an admin, and it is probably not a good idea to have people creating new redirect categories willy-nilly anyway.
The template does have uniform explanations, using the 'abbrev' parameter generates the reason concerning abbreviations, which would be the same on any redirect the template is used on. [I'm the one who said 'comment at WT:RE', and here I am yakking on!. Oh, well, que sera sera!] RichardΩ612Ɣɸ 21:45, May 18, 2008 (UTC)
Moreover, if you were thinking that the template-based system would be easier, then don't worry. The options can be abbreviated, and full documentation can be written, with a guide at WP:RE for new users. RichardΩ612Ɣɸ 21:49, May 18, 2008 (UTC)
I want to merge my usernames.
I have 3 or 4 usernames.
REASON: forget password, email account is deleted, etc.
I want to merge their edit history, counts, watchlist, etc.
(Duped from here) So we've got stars at the top-right of individual FC items, but there's usually no way to tell if (say) an article's featured unless you go there. What if FC links appeared as a different color than blue, say, green? Since FC articles inevitably touch upon more than just their own subjects, greenlinks could help browsing by steering people to the best prospects for research. It'd also provide an additional reward for FC stuff in terms of added visibility. Thoughts? Cheers, Mdiamante (talk) 13:05, 15 May 2008 (UTC)
:) I think this is thinking more in terms of helping the regular editors than the casual reader, such as say the kind who arrives here via a google search etc. Different-colored links will be confusing and need to be explained. I think this proposal might be helpful but only as a user script or gadget (the kinds of extra tools we have in preferences under the "gadgets" tab). FYI there's already a gadget that colors article page titles according to their class -- green for good, blue for featured, etc. Equazcion•✗/C •00:37, 19 May 2008 (UTC)
Aye, I saw that gadget, but unless I'm wrong, it doesn't apply to links, which is what I'm getting at. I grant that there may be an element of confusion at first, but there could always be one of those hide-able "things you may not know/greenlinks" captions at the top of the article itself. And would one different link color (aside from the pretty self-explanatory red) really be so vague? Cheers, Mdiamante (talk) 15:38, 19 May 2008 (UTC)
I struggle to see how this could be technically feasible without putting massive strain on the servers. -Halo (talk) 16:14, 19 May 2008 (UTC)
The server already looks ahead at page links to see if pages exist for them, so it knows what to turn into red links. It probably wouldn't be any more of a strain to have it check a new assessment flag and color the links accordingly. I don't think it's unfeasible, but I also don't really see the necessity. Equazcion•✗/C •16:17, 19 May 2008 (UTC)
Its not feasible because the servers know nothing of "FA." Article classification occurs at the "presentation" level; it is not a database thing. -- Fullstop (talk) 17:13, 19 May 2008 (UTC)
This is possible with FlaggedRevs, i.e. create a "featured" level of assessment that is the highest and that list would be available through some special page. As for the different color links, that's an issue for Bugzilla. MER-C06:31, 21 May 2008 (UTC)
Changing assessment levels - please give us your choice
We've had considerable discussion, and we're considering putting A below GA, and adding a C-Class between Start and B. Please choose your favourite option here. Walkerma (talk) 05:37, 19 May 2008 (UTC)
Current birthdays
I have a suggestion. Why don't you include a tab listing birthdays of all notable people for the specific day? The tab could be right next to the "recent deaths" tab. In that way, you can read up on notable people. It should not be too difficult to manage. I find the "recent deaths" very informative, the same will apply here. —Preceding unsigned comment added by Cozinsky (talk • contribs) 07:40, 19 May 2008 (UTC)
This is already available from the main page, by clicking on the current date at the bottom of the 'On this day...' box. I agree this isn't as obvious as it might be. Algebraist09:55, 19 May 2008 (UTC)
favorite pages section
I think there should be a button I can click that lets me save my favorite pages for viewing later like on youtube. Did anyone already think of this yet, it seems pretty obvious. —Preceding unsigned comment added by Dcutler (talk • contribs) 08:45, 19 May 2008 (UTC)
Hello, When you type something into wikipedia and mispell it slighty the relavent page does not come up. But if you do the same on google it says " Did you mean.....". I was wondering how hard it would be to integrate a similar feature onto wikipedia. Could you plesae reply on my talk page or notify me on my talk page if you have replied. Thanks Bit Lordy (talk) 21:04, 4 May 2008 (UTC)
This has been proposed before (by me, among other people), and the response is usually that such a feature would be too much of a performance burden. I've disagreed with that response repeatedly, and wish we could try out something like this. Wikipedia is way behind in the site searching technology department. Nearly every other prominent site that features a site search function is light-years ahead of us. Equazcion•✗/C •21:39, 4 May 2008 (UTC)
Can't we introduce this on a small trial basis on Wikitionary or something? Can we put this to a vote? If theres enough Consensus then they will find it hard to turn down. What do you think? Bit Lordy (talk) 21:43, 4 May 2008 (UTC)
I don't think we can decide things regarding Wiktionary from here. And I don't think a vote would be beneficial here. This should be a discussion by people who know about the technology and can offer educated guesses as to how it would work and what the performance cost would be. I do think a new discussion on this would be a good idea though. Welcoming any comments. Equazcion•✗/C •21:58, 4 May 2008 (UTC)
It's not just a performance burden, it's also a difficult thing to do if you want it to give decent suggestions. --Carnildo (talk) 02:28, 5 May 2008 (UTC)
I think redirects and disambiguation pages work just fine for this purpose. If a redirect doesn't exist for a specific phrase, make one. If a redirect doesn't exist for a typo, learn how to type. --CrypticC62 · Talk00:21, 5 May 2008 (UTC)
Funny how for some reason all those other sites don't tell their users to "learn how to type". We must know something they all don't. Or maybe we're just better than them, or expect more from our users. Perhaps we're just very choosy about just who we want to accommodate here -- we wouldn't want just any idiot to be able to use the site. People who don't know how to spell something should really go and check the proper spelling using some other tool prior to searching here. Who needs user-friendliness? That's not our responsibility. Users should just get smarter. This is all sarcasm of course, cause "learn to type" was a ridiculous response. Again, other sites have this feature for a reason. It makes the site easier to use. That's reason enough to want it for ourselves. And if it isn't purely the performance issue that's keeping us from doing it, but rather that the feature is a challenge to construct, then let's roll up our sleeves and rise to it. Equazcion•✗/C •03:50, 5 May 2008 (UTC)
Users should get smarter. That is the purpose of Wikipedia (or of any encyclopedia), right? Let's take our bold goal of free education a step further: let's couple the vast amount of information available on Wikipedia with some classical conditioning. When you type poorly, you don't get what you want. When you type well, you do get what you want. This forces the user to get better at typing. Sounds like a nice educational program to me. That's not to say we would expect users to already know how to spell everything. That's what redirects are for. User-friendliness is only valuable up to a point. Pass that point, and you're training people to be stupid. I think user-friendliness is at a good level right now. --CrypticC62 · Talk20:24, 8 May 2008 (UTC)
Thanks, but this is a proposed change to the site for discussion. Even if I were a developer capable of creating this feature on my own, I wouldn't even start putting in the effort until the proposal gained consensus here. And, we have developers for that sort of thing, so if consensus here is that it would be a benefit to the site, they could take over from there and implement it, as is usually the case for such proposed features. Equazcion•✗/C •16:58, 5 May 2008 (UTC)
The vast majority of technical changes are implemented without any sort of community consensus or announcement. If you plan on waiting for the few paid developers we have to do this because people ask for it (most of the developers are volunteers, who work on whatever they feel like) you may be waiting for a while. Mr.Z-man17:23, 5 May 2008 (UTC)
I'm aware of SUL. I created persistent proposals because of it. That's neither here nor there. As with any proposal, we should first decide whether or not it should be done, then worry about actually doing it. That's what this page is for -- proposing and discussing changes. We don't tell people who post here "Well go and make it yourself, then get back to us", so I'm not sure where the sudden attitude problem is coming from. Let's have an actual discussion, thanks much. Equazcion•✗/C •17:42, 5 May 2008 (UTC)
I guess what I was trying to say was, I really don't see this as a controversial change in any way. If someone can code something that won't have a significant impact on performance, I don't see it as being the type of thing that the sysadmins would require a community consensus on every project to turn on, like the AJAX based search suggestions that were just added recently. Mr.Z-man17:48, 5 May 2008 (UTC)
When it's been brought up before it was controversial. Also, the point of this page is also to demonstrate interest in a proposed feature. If there is enough demonstrated interest, that would serve as motivation for people (designated developers and others alike) to try and create the feature. A discussion of the feature, its possible benefits, and a simple demonstrated interest by as many people as possible is instrumental in getting a change implemented. At least three people here have so far expressed the feeling that this would be a beneficial addition to the site. Great. Keep them coming. If I could write something myself and bring it to the table I would, but I just don't have the programming ability. Hopefully with enough demonstrated interest, someone who does will take notice.
In other words, you seem to be saying this is a non-controversial change. If it's just a matter of getting someone to create it, then let's do whatever we can towards that end. Equazcion•✗/C •17:57, 5 May 2008 (UTC)
I think this is a great idea. Can someone please implement this???? It would save so much time correcting little typos.Numpty454 (talk) 18:48, 5 May 2008 (UTC)
I'm all for anything that will improve Wikipedia's terrible search function. I too have mispelled things by one letter or something and it comes up with some other results at the bottom which are completely unrelated, but it doesn't come up with the thing I might have mispelled. In fact, sometimes you can have better luck looking up Wikipedia pages on Google than on Wikipedia itself! Please, please, PLEASE do something to drastically improve Wikipedia's search tool. .:Alex:.18:54, 5 May 2008 (UTC)
See WP:PEREN. This feature exists but is disabled on English Wikipedia for performance reasons - it's not that this would be fundamentally impractical, but that the current implementation does not scale to a wiki this large. Dcoetzee21:19, 5 May 2008 (UTC)
That's all very well but can't we find a solution to implement it to a large Wiki? I mean if Google the largest serach engine in the world can do it surely the largest Wiki can too :) Bit Lordy (talk) 21:33, 5 May 2008 (UTC)
Exactly. I'm not sure why this should be given up on just because the existing feature wasn't made for a site this large. If IMDb and especially Google can do it, I think we should be able to find a way, and what's more I think it should be a priority. Equazcion•✗/C •21:36, 5 May 2008 (UTC)
I agree - it's a matter of finding someone who knows Mediawiki and the approximate query research to do an implementation. I could do this myself, actually, but need to find a bit of time first. Dcoetzee06:36, 6 May 2008 (UTC)
I think one of the biggest flaws in wikipedia is it has articles on pretty much every subject but it doesn't take into account human error. For example if you spell a word incorrectly it doesnt recognise it as a mistake and come up with a "did you mean"? message like google does; the best you can hope for is a re-direct which in 9 out of 10 cases don't come up. I propose we implement a did you mean thing when displaying search results with obvious spelling errors --Hadseys12:46, 8 May 2008 (UTC)
Support this change - it is becoming more and more common on other sites, and is very useful to users. I have repeatedly noticed its absence (due to my own poor typing!) Dhollm (talk) 22:13, 12 May 2008 (UTC)