[00:02:13] where is the universal page header file? [00:02:22] i want to add my site header to it and make it look integrated [00:02:23] hmm? [00:02:35] using monobook [00:03:03] sorry, but I'm drawing a complete blank right now... what type of header? [00:03:13] can probably use the user, my talk, preferences, thing? i want to put it above that [00:03:18] graphical header [00:03:28] ah [00:03:57] you probably have to edit the /includes/MonoBook.php file to get anything up there [00:04:27] hi OverlordQ [00:23:33] how do i change links in the toolbox? [00:23:47] i went to MediaWiki:Toolbox and it's not showing up like with the sidebar [00:27:31] LG|Devil: the toolbox is defined solely in the PHP file for the skin, so you'd have to edit that [00:27:53] although you can use javascript to add elements to it on a per-page basis [00:33:13] LG|Devil: the toolbox is automatic. it's contents depend on the page you are on, in some cases. and other stuff [00:55:05] Duesentrieb: I'm not sure what to put on the toolserver new accounts request page, it seams heavily oriented at users who want access to help with Wikimedia wikis - as apposed to MediaWiki. [00:56:30] MinuteElectron: what do you want an account for? [00:57:54] A MediaWiki extensions repository that will be accessed via a integrated extension manager for one-click installation, upgrade and deinstallation of extensions. I don't have the resources to host one on my own. [00:59:06] that seems fine, just write that on the page [00:59:18] ok, thanks [00:59:30] MinuteElectron: see, you already got approval from two of three toolserver roots :) [00:59:45] (the third being the one who grants accounts...) [00:59:47] :p [01:00:31] MinuteElectron: DaB only does account creation every coupls of weeks though. don't be too impatient (but prod him if need be) [01:00:42] *flyingparchment is doing most of the account creation recently though [01:00:47] (dab does the approvals) [01:02:02] oh you do? didn't know that [01:08:23] mediawiki seems to convert some spaces to non breaking spaces for no good reason [01:08:49] the french space thing [01:08:51] it's terrible [01:09:32] ah it could be. it's in the context of colons that i've spotted it. thought it was a firefox perversion [01:10:00] that should be in a locale or language specific layer [01:10:12] spaces before colons are converted to non-breaking space, even if they're in the middle of an HTML attribute [01:11:03] but you're worried about conversion in ordinary text, right? [01:11:10] is it really better to have these unexpected artefacts than to not have the conversion for french? [01:11:14] Duesentrieb: There we go. Thanks for the advice, hopefully I'll be able to take this somewhere. :) [01:11:34] yes i'm doing lexical analysis on text nodes and expected what i put in to be what came out [01:13:01] it sounds like something that would be better converted to entities at input time for users or wikis with a french language setting [01:13:57] well, it's not like it's the only kind of text conversion [01:14:28] why is it such a big problem? [01:15:17] it was a problem finding why my nice lexer didn't work. wasted all last night on it. breaks the principle of least surprise or whatever it's called [01:15:59] Goodnight. [01:16:02] well, the least surprising course of action probably depends whether you're french or not [01:16:24] what about ISBN/RFC, or dynamic dates? won't they screw you up too? [01:16:46] french doesn't actually use regular non breaking spaces near puncutation anyway, it uses non breaking half spaces [01:17:04] what about any point where your parser is not identical to our parser? [01:17:27] i'm only lexing and parsing wiktionary which has structured text rather than prose [01:18:56] i'm trying to parse that structure into javascript objects which can be used by other parts of the system. a kind of data mining or annotation i suppose [01:20:58] in a wiktionary translation table you will have things like [01:21:00] *Spanish: [[comer]] [01:21:01] the colon is more structural than prose punctuation [01:21:47] that example wouldn't be affected [01:21:59] there's no space before the colon [01:22:32] yes it's when i try to parse variants where some editors do put a space before the colon that i struck this problem [01:23:04] a good parser should be tolerant of its input and strict with its output [01:28:44] yes it should [01:29:26] but maybe you'll forgive me for thinking that the tolerance of your own parser is your own problem [01:29:49] you seem to just be talking about how annoyed you are that some shortcut you're taking didn't work out for you [01:29:54] and you want to take it out on mediawiki [01:30:25] no i'm happy i got my answer and got it fixed. it was a huge surprise why it was happening [01:30:33] if you want to have a discussion about wikitext, then fine [01:31:12] but I don't want to hear about failed attempts to write your own parser for it [01:31:56] i'm very much in favour of language specific support for characters missing from keyboards etc. the same could be done for hyphens vs dashes, curved apostrohes, hebrew maqaf, hawaiian okina, etc [01:32:24] but you're not in favour of this particular feature because it's pissing you off [01:33:08] i'm not pissed off now. but i was wondering if it was overarching enough to be considered a bug [01:35:34] there are some obvious advantages to having language-independent features, such as the existence of multilingual wikis [01:36:35] so if it reasonably can be supported in a general way, I'd prefer that it is [01:38:44] it's a particularly bad implementation at the moment, because it's not sensitive to context at all [01:40:30] do you think there should be a low priority bug report? i'm sure i'm not the first one to be surprise and i'm having trouble finding info about it on google. a context-sensitive implementation could tackle similar issues that this one can't [01:41:02] I'm not sure the particular example you're talking about should change [01:41:23] the question as far as I'm concerned is: does the user expect the software to insert a line break before the colon? [01:42:06] not: does a developer expect the software to take extraordinary measures to avoid a line break? [01:43:28] i'm wondering more if there are other use cases besides mine where people could be surprised [01:47:16] 03(mod) Support collation by a certain locale ( sorting order of characters) - 10https://bugzilla.wikimedia.org/show_bug.cgi?id=164 (10octahedron80) [01:47:34] hi brion :) [01:48:20] evening [01:48:52] here's an interesting side effect: if you have two or more spaces before a colon the browser will display it as 2 spaces, two or more spaces after a colon will only be displayed as a single space [01:49:05] brion: we're just talking about french spaces [01:49:16] might be interesting to those working on the wikitext grammar/spec [01:49:31] ah, zee frennnnnch espacessss [01:49:33] brion: I sent you an email regarding this, but would you please set me up for SVN commit access? [01:49:52] Skizzerz: i'll take a peek [01:49:58] awesome :) [01:49:59] thanks [01:51:01] lowercase 'skizzerz' ok? [01:51:39] sure :) [01:51:43] since we implemented them, why didn't we go all the way and implement them as half spaces? [01:52:29] personally, i think wrapping the french quotes and colon correctly is the responsibility of the user-agent, not mediawiki [01:52:33] 03(mod) Support collation by a certain locale ( sorting order of characters) - 10https://bugzilla.wikimedia.org/show_bug.cgi?id=164 (10octahedron80) [01:52:45] I thought there was some problem with the spaces in the 200x range in IE, but I'm not seeing it now [01:52:45] but i guess few user agents actually do it properly, or the feature wouldn't exist [01:52:47] maybe it's fixed [01:52:56] flyingparchment: user agents are quite stupid [01:53:30] like formatting in chinese text by skewing the already very dense characters to the point of unreadability [01:54:01] surprisingly when i cut and past such text from firefox into another application all the spaces are regular x20 again [01:54:13] yeah, that's firefox's fault [01:54:18] yeah, i've seen some chinese text where i'm surprised anyone could read it... i guess chinese users set a large font size ;) [01:54:31] we had trouble with that once upon a time, when people were allowed to use non-breaking space in usernames [01:54:39] you couldn't copy and paste them to block them [01:54:57] hi Charitwo :) [01:56:09] problem is could contain a mix of characters, should one cjk char change the rendering of the whole span? or should different parts of a single span render differently depending on their character range? [01:56:29] Skizzerz: can you send your key in the one-line format that openssh likes? [01:56:36] ssh-keygen isn't being friendly to me with converting today [01:56:37] the latter [01:56:40] 1 ping is enough :P [01:56:47] CJK fonts should never be skewed [01:56:49] sure [01:57:09] italics is just how they write things in italy [01:58:09] it's a poor cultural assumption to assume that's how they do it in beijing as well [01:58:10] i wanted to make some javascript for wiktionary that put spans with CSS classes around any cjk text so we could style them without the editors having to use templates, but javascript has no concept of character ranges - not even ec4 [01:58:42] brion: er, how would I go about doing that? just remove all the linebreaks? [01:58:57] Skizzerz: ssh-keygen -i -f (if you have openssh) [01:59:17] japanese can put a dot alongside each character for emphasis but i've never heard of that being implemented in html [01:59:27] otherwise your ssh client might have an option to export in openssh format [02:00:06] ah, there we go [02:00:14] I haven't seen that [02:00:17] without the -f it bitched and moaned, despite apparently asking me for the input filename [02:00:25] Skizzerz: ok i got it :D [02:00:36] ok, thanks [02:00:46] in japan of course they have lots of stylised fonts that are actually readable, that can be used for emphasis [02:00:48] *Skizzerz uses PuTTY, didn't see an export option there... [02:01:00] and they can just shift the whole thing from hiragana to katakana [02:01:08] owait, there it is >_> [02:01:11] *Skizzerz just can't read [02:01:17] strangely enough there's no way to do that transformation in CSS :) [02:01:20] the only chinese novel i have handy doesn't translate the italics from the english. can't find any bold... [02:01:50] Skizzerz: ok, added [02:01:51] enjoy :D [02:01:57] ok, thanks :) [02:02:21] kana conversion requires a dictionary and morphological analysis )-: [02:03:50] well, conversion between kanji and a phonetic alphabet of some kind does [02:04:11] but katakana and hiragana are both phonetic, and have a simple one-to-one mapping [02:04:11] *PONGTimStarling [02:04:50] many of the katakana are just angular forms of the corresponding hiragana [02:05:53] here are the spaces 2000-2000d: http://noc.wikimedia.org/~tstarling/spaces.html [02:05:57] 200d [02:06:36] brion: uh, I'm being prompted for a password... [02:06:50] the 200c and 200d look like a vertical line to me [02:07:03] Skizzerz: make sure you're using the right username (it's case-sensitive!) [02:07:13] it's all lowercase, right? [02:07:18] but the rest are OK [02:10:27] mmm, wikipedia has a long article called [[French spacing]] [02:10:59] brion: still not working... [02:12:58] I've updated the public key file with the openssh one, if that's what the problem was [02:15:03] 03dale * r30816 10/trunk/extensions/MetavidWiki/ (9 files in 4 dirs): interface and scraper enhancements [02:17:04] brion: nvm, it was a problem on my end I guess [02:17:08] *Skizzerz fixed it :) [02:18:27] What's it called when there's a hard link instead of a link with a question mark in it? [02:18:27] cheers, Skizzerz. [02:18:54] i.e. just domain.com/ instead of domain.com/index.php?title=Main_Page [02:19:21] 03(mod) Support collation by a certain locale ( sorting order of characters) - 10https://bugzilla.wikimedia.org/show_bug.cgi?id=164 (10octahedron80) [02:19:27] wow that spacing article contains much more convoluted stuff than i ever would've expected [02:19:31] geez.. [02:20:09] the table under "French spacing rules and English spacing rules" is enlightening [02:23:33] *Skizzerz "tests" this out by adding his thingy to userinfo... [02:24:34] 03skizzerz * r30817 10/USERINFO/skizzerz: adding myself to USERINFO [02:24:40] w00t :) [02:25:11] a much better article all round than i had expected [02:26:29] does it make you want to add em spaces after the ends of sentences? [02:26:49] is there a way to test if a named argument was even passed into a template at all? [02:27:02] 03(mod) Support collation by a certain locale ( sorting order of characters) - 10https://bugzilla.wikimedia.org/show_bug.cgi?id=164 (10octahedron80) [02:29:53] it makes me think that everybody is wrong and everybody is right in arguments about spacing (-: [02:32:20] maybe we can have a little javascript slider bar at the top of the page that lets you adjust the space between words, and around punctuation [02:34:49] Sounds like a good plan [02:35:42] (-: [02:36:26] css will probably support such concepts someday in the future i suppose [02:38:52] 03aaron * r30818 10/trunk/extensions/FlaggedRevs/ (FlaggedRevs.php FlaggedRevsPage.i18n.php flaggedrevs.css): Various fixes [02:55:11] there's a character called narrow no-break space, NNBSP [02:55:34] that's the only possible replacement for the NBSP in question, the other spaces are breaking [02:55:41] and avoiding breaking is the whole point [02:58:02] Mongolian... [02:58:13] ehhhh, but it's a box in IE [02:58:15] bugger [02:58:56] *Splarka had it in his list of annoying invisible (in Mozilla) unicode: http://en.wikipedia.org/wiki/User:Splarka/alpha [02:59:09] 03siebrand * r30819 10/trunk/extensions/MetavidWiki/languages/MV_Messages.php: fix typo [03:05:37] 03aaron * r30820 10/trunk/phase3/includes/Linker.php: If a link is made to an old version of an image that doesn't exists, but a current version exists, blue link it. [03:27:20] 03aaron * r30821 10/trunk/phase3/includes/Linker.php: Tweak r30820. Pass $time variable further in. This avoids extra wfFindFile() calls if we were fetching the current revision. [03:34:20] 03aaron * r30822 10/trunk/extensions/FlaggedRevs/FlaggedArticle.php: Fix silly typo [03:36:03] 03aaron * r30823 10/trunk/extensions/FlaggedRevs/FlaggedArticle.php: And again... [03:37:39] (CommitOfAll) [03:42:19] Anyone here using single sign-on between MediaWiki 1.11.1 and vBulletin? [05:45:53] hello [05:46:37] maybe i'm blind, but where is the $wgOut variable initialised ? [05:47:12] i see a "new OutputPage" only in SpecialPages.php [05:48:18] Setup.php [05:48:48] $wgOut = new StubObject( 'wgOut', 'OutputPage' ); [05:51:24] ah yes, thanks [06:02:30] imho it's quite confusing with the wiki setup script (which create the db tables and LocalSettings.php), maybe Initialisations.php should be less confusing name ? [06:04:22] maybe Init.php, to avoid the US-UK spelling conflict [06:04:28] but it's still a synonym [06:04:40] setup, initialisation, configuration -- all synonyms [06:05:20] the fact that it's in the includes directory goes some way towards disambiguation [06:05:32] it sets up the things that are in that directory [06:47:55] Whenever I try to use short URLs by changing .htaccess, the layout of pages is messed up - it looks like I lose the default skin. Any ideas? [07:02:28] 03aaron * r30824 10/trunk/extensions/FlaggedRevs/FlaggedRevs.php: Don't include JS/CSS several times. Not sure how this gets called twice though... [07:09:40] 03nikerabbit * r30825 10/trunk/extensions/FlaggedRevs/FlaggedRevsPage.i18n.php: * -bom [08:18:46] So I upgraded from 1.9.3, to http://download.wikimedia.org/mediawiki/1.11/mediawiki-1.11.1.tar.gz, 1.9.3 has a .htaccess, 1.11 doesn't. So the site is 404, and apache's log says "File does not exist: /home/ross/www/vinyasakrama.com/Main_Page" [08:18:54] any clues to what i did wrong? [08:22:52] the 1.11.0 tarball is missing the .htaccess file as well. [08:23:06] i must be missing something completely obvious [08:23:14] the .htaccess files don't include rewrite rules [08:23:22] it did in 1.9.3 [08:23:39] copy the rewrite rules to the new .htaccess file [08:23:51] so how does Main_Page map to index.php in 1.11.x? [08:24:08] ok, but that's not mentioned anywhere in the docs (or is it?) [08:24:21] /index.php/Main_Page i think... [08:24:53] great, i'll just ask everyone on the Internet to update their links :) [08:25:23] i don't think 1.9.3 came with rewrite rules [08:25:31] but i'm too tired to think [08:27:22] could be I hacked that file myself, too tired to remember, thx 4 assistance!!! [08:29:52] protect/unprotect have stopped working: [08:30:01] Internal error: This action cannot be performed on this page. [08:30:12] no errors in apache's log [08:31:29] went back to 1.9.3, and protect/unprotect work fine [08:33:14] rasa: No version ever came with rewrite rules. [08:33:36] If you were lucky your server used an API that support /index.php/Main_Page style links. [08:34:10] To get back to your linking system you need to read the manual and create a new .htaccess file (or add the new rewrite rules to your own). [08:34:14] !shorturls | rasa [08:34:14] --mwbot-- rasa: To create simple URLs (such as the /wiki/PAGENAME style URLs on Wikimedia sites), follow the instructions at . There are instructions for most different webserver setups. If you have problems getting the rewrite rules to work, see !rewriteproblem [08:47:42] 03siebrand * r30826 10/trunk/phase3/languages/messages/MessagesEn.php: Remove a leading space in 'uctop' [08:57:32] 03huji * r30827 10/trunk/phase3/maintenance/findhooks.php: (log message trimmed) [08:57:32] Allows findhooks to find these hooks: [08:57:32] * FileUpload [08:57:32] * LanguageGetMagic [08:57:32] * LanguageGetSpecialPageAliases [08:57:33] * MonoBookTemplateToolboxEnd [08:57:35] Regardless, these hooks are still not found (although they are in use by extensions): [09:01:08] TimStarling: have a second? [09:03:56] Hojjat: for r30827 i had a bug at https://bugzilla.wikimedia.org/show_bug.cgi?id=12301 to find all missing bugs :) [09:04:20] ialex: hi! I'll take a look in a sec [09:05:34] the idea is the same, you just expanded it more! [09:06:09] ialex: why didn't it get applied? [09:06:27] Hojjat: dunno, nobody saw that bug :D [09:06:34] including me! [09:06:46] :) [09:06:48] Why don't you apply it right now? [09:06:52] I think it is fine. [09:07:00] i don't have commit access :) [09:07:07] oh, really? [09:07:17] :( [09:07:27] Then why don't you recreate the patch based on the latest version and let me commit it for you? [09:07:40] while I'm doing some other htings [09:08:33] 'kay [09:09:23] 03huji * r30828 10/trunk/phase3/images/: Adding 'deleted' folder to the subversion ignore list [09:14:10] 03(mod) Allow maintenance/findhooks. php to search hooks in multiple directories - 10https://bugzilla.wikimedia.org/show_bug.cgi?id=12301 +comment (10alex.emsenhuber) [09:16:09] I'm on it [09:16:23] thanks :) [09:19:29] hello [09:19:41] hi Nikerabbit [09:20:23] Hi Nikerabbit [09:25:31] hey people - how can i get the Sitenotice to not appear to google as the first actual content on each page? it's ruining my google listings: http://www.google.co.uk/search?source=ig&hl=en&rlz=&q=site%3Ahobbsknowledgebase.co.uk&btnG=Google+Search&meta= [09:27:02] maybe dismissable sitenotice? not sure though [09:27:25] heh [09:27:39] AaronSchulz has ruined test.wikipedia in the same way: http://www.google.com/search?q=site%3Atest.wikipedia.org&btnG=Google+Search [09:27:50] wow! [09:28:07] Nikerabbit: what's a dismissable sitenotice? [09:28:24] Nikerabbit: isn't that pure js/Css trickery? [09:28:37] http://www.mediawiki.org/wiki/Extension:DismissableSiteNotice [09:28:52] ! DismissableSiteNotice [09:29:00] !DismissableSiteNotice [09:29:00] --mwbot-- I don't know anything about "dismissablesitenotice". [09:29:04] pity! [09:29:07] lol [09:29:18] Hojjat: add it [09:29:21] *Splarka notes it is often *more* work to try to use the mwbot [09:29:25] why isn't this built in by default? lol, surely a sitenotice appearing as the first googleable content is ridiculous! lol [09:29:28] Duesentrieb: I'm doing this [09:29:53] the dismissable sitenotice is... hmm... not a good thing IMHO [09:29:59] it never shows for non-js users, for example [09:30:12] Splarka: huh? it never does? really? [09:30:16] !DismissableSiteNotice is DismissableSiteNotice is an extension which lets users hide SiteNoticess. For more information see [09:30:16] --mwbot-- Successfully added keyword: dismissablesitenotice [09:30:18] that would be odd. [09:30:30] Splarka: why does google see it, then? [09:30:33] well that's the thing - i want it to be visible to all, including Google's cache of pages, but i don't want it as the first content in the listings! lol [09:30:35] !dismissablesitenotice | Duesentrieb [09:30:35] --mwbot-- Duesentrieb: DismissableSiteNotice is an extension which lets users hide SiteNoticess. For more information see [09:30:39] :D [09:30:42] Duesentrieb: does it? [09:30:53] I don't think it does.... [09:31:07] it sees AaronSchulz's FlaggedRevs page headers... and not the sitenotice, on test.wp [09:32:25] Splarka: hm... maybe you are right. i would have though non-js users can't dismiss it. [09:32:41] for non-js users it simply doesn't show [09:32:46] anyway - why is it done by js at all? it should be possible without [09:32:47] since it is generated by js [09:32:51] *Splarka shrugs [09:32:53] ask brion [09:32:56] :P [09:32:59] I'd have done it differently [09:33:08] for me, that is not an option, unfortunately - i want all users to see the Sitenotice, but i don't want it as the first googleable content, if you know what i mean... [09:33:23] more importantly, it drops a crapload of JS directly into the page source, whyyyyyy... [09:33:25] fishsponge: hack the skin. [09:33:26] is there a CSS trick that can take it away from being whatever it is and turn it into something Google doesn't care about? [09:33:40] I'd have created a div that was visible, and then had some javascript make it invisible [09:33:45] fishsponge: look where it inserts the citenotice, and at that point, check against a list of user agents to hide it for. [09:33:47] Duesentrieb: i would hack the skin, but i don't know what to hack! i don't know enough about CSS to know what to change anything to [09:33:52] and then have more javascript make it visible if the cookie wasn't set, and generate a [hide] tab [09:34:08] fishsponge: though... hm... that would play bad with caching. but if you don't use squids of filecache, you should be ok. [09:34:10] (and only the hide tab operating on document load, so it would be transparent) [09:34:11] Duesentrieb: is there no CSS class that google ignores? [09:34:23] fishsponge: you wouldn't hack css. you'd hack the php paert of the skin [09:34:51] fishsponge: a special not-for-google class? would be usefull. no idea if it exists. how about asking google? [09:34:56] Duesentrieb: i know what you are suggesting, but on a different topic (almost) can CSS not be used to simply make google ignore it somehow? [09:35:12] fishsponge: hehe, #google exists [09:35:23] i.e.

headings can be made small so Google treats them as H1, but really they're just text etc... can the opposite be done? can text be ignored? [09:35:43] fishsponge: i have no idea in how foar google interprets css. they do to some extend, i'm sure, to ignore hidden keyword spam [09:36:05] fishsponge: ask google experts, not mediawiki experts... [09:36:50] at the very least, brion could have stuck in a