Hi all,
So, is xhtml_slim.pt gone in 1.4beta6? I wanted to add the sourceforge and donation logos to the quickbar and was pointed to that file, which I can't actually find in the source. I've added the logos directly to MonoBook.php on line 180 before the last </div>, and that seems to work, but is that the correct way? (looks like there's a note on the Look and Feel wiki page about it). Should I do that with the rest of the skin files and call it safe, or is there a more appropriate way?
Cheers, -John
Jonathan Pennington wrote in gmane.org.wikimedia.mediawiki:
Hi all,
So, is xhtml_slim.pt gone in 1.4beta6?
no, but it was renamed to MonoBook.pt. additionally, it's not required unless you really want to modify the TAL template; the shipped MonoBook.php is the rendered version of the TAL file (and you can modify it without problems).
I wanted to add the sourceforge and donation logos to the quickbar and was pointed to that file, which I can't actually find in the source. I've added the logos directly to MonoBook.php on line 180 before the last </div>, and that seems to work, but is that the correct way?
you can do it like this. alternatively, you can use the new (1.4) $wgNavigationLinks configuration setting; see http://meta.wikimedia.org/wiki/Quickbar#Changing_the_makeup_of_the_Quickbar_... doing it this way is more likely to not break when you upgrade (because you don't need to modify any source files); however, it's slightly less flexible.
Cheers, -John
kate.
Kate Turner wrote:
you can do it like this. alternatively, you can use the new (1.4) $wgNavigationLinks configuration setting; see http://meta.wikimedia.org/wiki/Quickbar#Changing_the_makeup_of_the_Quickbar_... doing it this way is more likely to not break when you upgrade (because you don't need to modify any source files); however, it's slightly less flexible.
Kate, Thanks, I'm glad to hear that about MonoBook.pt. Unfortunately, changing the $wgNavigationLinks configuration (which I have also done) doesn't seem to give me a way to add the linked button images of SourceForge (and the donation button from SF) at the bottom of all of the quickbar stuff. That's why it seemed I had to manually edit the source to get what I have at http://pyarie.sourceforge.net/
Cheers, -JW
Is there a way to just turn off case sensitivity on searches? The suggested solution seems to be to make redirect pages for all the possible lower-case queries, but that seems way too much work to get around something that I don't even want there in the first place.
Thanks.
Tor Kinlok wrote:
Is there a way to just turn off case sensitivity on searches? The suggested solution seems to be to make redirect pages for all the possible lower-case queries, but that seems way too much work to get around something that I don't even want there in the first place.
There is no way to turn *on* case sensitivity for searches. The full text search index is case insensitive.
-- brion vibber (brion @ pobox.com)
On Feb 15, 2005, at 1:37 PM, Brion Vibber wrote:
Tor Kinlok wrote:
Is there a way to just turn off case sensitivity on searches? The suggested solution seems to be to make redirect pages for all the possible lower-case queries, but that seems way too much work to get around something that I don't even want there in the first place.
There is no way to turn *on* case sensitivity for searches. The full text search index is case insensitive.
Then there's something very basic I'm not understanding. On my site, and even on Wikipedia, if you search for something using the search box that can be found on the left of all the pages, the results are case sensitive. Yes, it will ignore the case of the first letter in the query, but with the remaining letters, the case is important. Is this something different from the "full text search index"?
For instance, on wikipedia, a search for "Albert Einstein" takes you directly to his page, but "albert einstein" only works because of a redirect. Or at least, that's what used to happen this morning. On just checking this, they seem to have (temporarly?) replaced their own search function with google's. On my site, try
http://supermanica.info/wiki/index.php/Special:Search?search=wonder-man versus http://supermanica.info/wiki/index.php/Special:Search?search=Wonder-Man
The former doesn't return any results, the latter does.
Tor Kinlok wrote:
On Feb 15, 2005, at 1:37 PM, Brion Vibber wrote:
There is no way to turn *on* case sensitivity for searches. The full text search index is case insensitive.
Then there's something very basic I'm not understanding. On my site, and even on Wikipedia, if you search for something using the search box that can be found on the left of all the pages, the results are case sensitive. Yes, it will ignore the case of the first letter in the query, but with the remaining letters, the case is important. Is this something different from the "full text search index"?
For instance, on wikipedia, a search for "Albert Einstein" takes you directly to his page, but "albert einstein" only works because of a redirect
You may be thinking of the "go" function, which takes you directly to an exact-matching title if present, and then goes on to perform a search if there is not an exact match.
-- brion vibber (brion @ pobox.com)
Tor Kinlok tor@superman.ws wrote:
For instance, on wikipedia, a search for "Albert Einstein" takes you directly to his page, but "albert einstein" only works because of a redirect. Or at least, that's what used to happen this morning. On just checking this, they seem to have (temporarly?) replaced their own search function with google's. On my site, try
If there is a redirect sitting at [[albert einstein]] for whatever reason-- which on Wikipedia, there is--the "go" search will find it first. It'll even find [[albert einstein]] if you search for "aLbErT eInStEiN". That is, the go search is case-insensitive, but if there are multiple matches, the one it returns may not be the one you were looking for. (It seems that if you happen to hit upon the exact casing of an article title, it'll take you straight to it.) For example, Wikipedia has full articles about "latex" (at [[Latex]]) and "LaTeX" (at [[LaTeX]]).
* go-searching for "latex" will take you to [[Latex]] * go-searching for "LATEX" will take you to [[Latex]] * go-searching for "lAtEx" will take you to [[Latex]], etc., but: * go-searching for "LaTeX" will take you to [[LaTeX]]
When there's no ambiguity, case-insensitive search works just like you might expect it to: go-searching for "LaTiN" will take you to [[Latin]].
*Muke!
So perhaps my original question was mis-worded. The problem is that I don't want to have to write redirect pages for all of my entries, especially if various users are the ones who are going to be adding them.
Is there any way to have "Go" searching (not "Search" searchig) be case-insensitive?
On Feb 15, 2005, at 10:16 PM, Muke Tever wrote:
Tor Kinlok tor@superman.ws wrote:
For instance, on wikipedia, a search for "Albert Einstein" takes you directly to his page, but "albert einstein" only works because of a redirect. Or at least, that's what used to happen this morning. On just checking this, they seem to have (temporarly?) replaced their own search function with google's. On my site, try
If there is a redirect sitting at [[albert einstein]] for whatever reason-- which on Wikipedia, there is--the "go" search will find it first. It'll even find [[albert einstein]] if you search for "aLbErT eInStEiN". That is, the go search is case-insensitive, but if there are multiple matches, the one it returns may not be the one you were looking for. (It seems that if you happen to hit upon the exact casing of an article title, it'll take you straight to it.) For example, Wikipedia has full articles about "latex" (at [[Latex]]) and "LaTeX" (at [[LaTeX]]).
- go-searching for "latex" will take you to [[Latex]]
- go-searching for "LATEX" will take you to [[Latex]]
- go-searching for "lAtEx" will take you to [[Latex]], etc., but:
- go-searching for "LaTeX" will take you to [[LaTeX]]
When there's no ambiguity, case-insensitive search works just like you might expect it to: go-searching for "LaTiN" will take you to [[Latin]].
*Muke!
website: http://frath.net/ LiveJournal: http://kohath.livejournal.com/ deviantArt: http://kohath.deviantart.com/
FrathWiki, a conlang and conculture wiki: http://wiki.frath.net/ _______________________________________________ MediaWiki-l mailing list MediaWiki-l@Wikimedia.org http://mail.wikipedia.org/mailman/listinfo/mediawiki-l
On Wed, 16 Feb 2005 08:57:56 -0500, Tor Kinlok tor@superman.ws wrote:
So perhaps my original question was mis-worded. The problem is that I don't want to have to write redirect pages for all of my entries, especially if various users are the ones who are going to be adding them.
You shouldn't have to make a redirect page--if there's _no_ redirect page, "go" should send you to the article directly.
_If_ you make a redirect page, "go" will probably find it first.
Is your wiki not behaving this way?
*Muke!
Muke Tever wrote:
On Wed, 16 Feb 2005 08:57:56 -0500, Tor Kinlok tor@superman.ws wrote:
So perhaps my original question was mis-worded. The problem is that I don't want to have to write redirect pages for all of my entries, especially if various users are the ones who are going to be adding them.
You shouldn't have to make a redirect page--if there's _no_ redirect page, "go" should send you to the article directly.
Since the fields are not case-insensitive, 'go' can't do a case-insensitive exact match check. Instead, it checks for several variants (exact, exact all lowercase, exact all uppercase, etc). On a multi-word title such as a name where the second word is capitalized, typing in all lowercase won't get a 'go' match and the search will be engaged instead.
-- brion vibber (brion @ pobox.com)
On Feb 16, 2005, at 11:04 AM, Muke Tever wrote:
On Wed, 16 Feb 2005 08:57:56 -0500, Tor Kinlok tor@superman.ws wrote:
So perhaps my original question was mis-worded. The problem is that I don't want to have to write redirect pages for all of my entries, especially if various users are the ones who are going to be adding them.
You shouldn't have to make a redirect page--if there's _no_ redirect page, "go" should send you to the article directly.
_If_ you make a redirect page, "go" will probably find it first.
Is your wiki not behaving this way?
No, it is not. As an example, I have an article named "Wonder-Man" and a "Go" lookup on "wonder-man" won't find it, nor will it return any search results at all. It seems like the hyphen may be an issue here too.
mediawiki-l@lists.wikimedia.org