is around it tho [12:28:56]

headline [edit]

would work too, right ? [12:29:38] s-3 uses

headline

[edit]

[12:29:43] Well I guess we also wanted the [edit] outside the

[12:29:55] ok, seems semantically correct [12:29:59] So you can copypaste the header text without the annoying [edit] [12:30:01] Not sure though [12:30:05] I didn't actually write this code [12:30:16] H.. I think copypasting makes no difference tho [12:30:19] I pulled an ancient patch by AryehGregor from Bugzilla, brought it up to date with trunk [12:30:26] And Trevor wrote the Vector CSS for it I think [12:30:34] Krinkle: Triple-clicking the header does [12:30:37] But anyhow, you say that dewiki has right-aligned [edit] links that are not subjecto to the stacking bug ? [12:30:42] Oh wait it doesn't :( [12:30:47] No [12:30:56] RoanKattouw: tripple click select the block element afaik [12:31:00] What they do is pretty much the same as we do [12:31:04] Yeah, saw that, sorry [12:31:16] RoanKattouw: "we do" [12:31:22] you mean, as we do in s-3 ? [12:31:23] They use JS to reverse the order, then un-float and the [Bearbeiten] link [12:31:25] Yes [12:31:27] oh, ok. [12:31:41] So no fix has been found for right-aligned [edit] links? [12:31:55] Not that I know of [12:31:58] But I'm not a CSS ninja [12:32:05] ok [12:32:23] And the only one I know is changing flights right now [12:32:56] Well, I have been called a CSS guru :) [12:33:29] Well you don't seem to know how to fix those right-floating edit links or you wouldn't be asking me :) [12:33:32] But I've challanged this issue twice (2008 and 2009) - but left it to 'float' away since it was too much of a pain and the time wasted didn't justify the ends at the time [12:33:41] Right [12:33:42] RoanKattouw: that's... true [12:34:21] So while you may very well be a ninja otherwise, this particular issue seems to be beyond your reach :) [12:34:40] But maybe it's just impossible to solve, I'll ask Trevor when he's done traveling [12:35:14] Well, vector changes somethings in my opinion. There's new motivation to fix this + I asked here since there is a lot on your planning table and this could have been one of the solved things in a sandbox already. [12:35:25] I rather not troubleshoot if someone solved it already behind the screens [12:35:30] Right [12:35:59] But I here, as far as you know, it remains unchanged. [12:36:10] hear* [12:36:15] For now, yes [12:36:21] We somehow never got anywhere with that patch [12:37:01] Alrighty - one other thing. On nl.wiki we had a javascript to replace "page" with "main page" on the main page in the tabs on top. - that has been ported to vector/jquery in the mean time, and works. [12:37:14] I was looking to do the same on Commons, but I noticed something interseting. [12:37:32] interesting* - On Commons in mononobook the tabs says "main page" even with javascript disabled. [12:40:03] So I guess this is done in the skin itself - I propose this should be in vector aswell (right now it's not an the main page is "Article" wikis (or "Gallery" on Commons) [12:40:44] Yeah it's some MediaWiki: page somewhere [12:40:56] I think it's nstab-main (Monobook) and ca-main (Vector), not sure [12:41:30] Ah noo, I dont mean the tab-name of the entire main namespace :P [12:41:42] just the "Main Page" in the main namespace [12:41:49] Oh the /title/ [12:41:57] it reads "Article" or "Gallery" on the tab in vector [12:42:05] Oh wait yes, sorry [12:42:08] in monobook at Commons it says "main page" - [12:42:09] ca-main is something else [12:42:11] Got it now [12:42:50] in vector I was going to fix this using jafvascript (if wgTitle = "Main page" ca-main span => "Main Page" or something like that) [12:43:07] but since it's fixed in the skin in monobook, cant this be done that way in vector aswell ? [12:43:19] (ie. w/o js) [12:43:22] Yeah I'm looking for the msg key [12:43:27] OK. Thanks [12:51:20] hello people [12:58:14] were we ralking about the bunching problem ? [12:59:55] that is how floats work. Rather annoying. basically, you shouldn't stack floats and expect it to work. css was designed to have a div around stacks. But that doesn't really work in Wikipedia of course. [15:35:13] Leaving this page may cause you to lose any changes you have made. [15:35:14] If you are logged in, you can disable this warning in the "Editing" section of your preferences. [15:35:23] Isn't that only true for some versions of IE? [15:35:37] Most browsers preserve form contents across navigation. [15:35:47] "may" [15:36:07] Yes, I spotted that, but if you can detect when it's "will not", there's no point in bothering the user with a pop-up. [15:36:09] I think it's annoying, but apparently some 80% of newbies don't. [15:36:10] Even if they can opt out. [15:36:13] AryehGregor: You're right, in Firefox.Chrome.Safari you can click "Back" and see it again. [15:36:22] AryehGregor: But not when tou close the window [15:36:23] Do those newbies know that it's false in their browser? [15:36:24] you* [15:36:34] Krinkle, I can restore the tab and get the same contents back. [15:36:43] AryehGregor: You can, a newbie can't [15:36:50] :) [15:36:54] Most newbies don't know how to get the contents back. [15:37:18] A popup seems unduly intrusive, though. [15:37:32] apparently those newbies don't think so. [15:37:40] AryehGregor, you and I can disable it however. [15:37:48] granted, I have to disable it 770 times [15:37:51] on every project. [15:37:54] but w/e [15:37:58] :P [15:38:01] yeah, I noticed that too [15:38:42] I accept the principle that we should focus on newbies, but even for a newbie, I don't see why it should display when just navigating back in browsers where you can navigate forward again to get the content back. [15:38:58] I'm wondering what section "editing" corresponds to in French. [15:39:17] Ah, "Fenêtre de modification" [15:39:58] Yay, I disabled it. [15:41:57] cary: I hope Preferences will be part of SUL at some point in the future. In other words, let it override the defaults for that local wiki with my own defaults. Still accepting local different settings. [15:43:03] AryehGregor wonders how that would be stored in the database, with the new user_properties system [15:43:50] I think werdna had some ideas about that [15:44:00] Like, there's some settings you want to have different sharing semantics for, like language [15:45:35] I can image myself using that system. Setting for example my SUL preferences to skin:vector, language:English, Edit-closewarning:Off - and then on my homewiki Language to Dutch /whatever/ [15:45:43] imagine [18:00:26] nimish_g: come in anytime [18:02:10] hey parutron_ [18:02:34] hey hannes [18:02:35] how can I join the meeting? [18:02:41] we might have a limit on callers [18:03:16] you can call in on the extension that you normally use [18:03:21] ack [18:03:23] i mean use 2004 [18:03:33] lets see if that works [18:03:57] hopefully without videogame noises this time [18:05:23] 2004 does not work [18:05:26] shall I try 2002? [18:06:32] hannes i just sent you the outline we are talking over [18:17:35] we will do something better ;) [18:46:02] parutron_: need to leave for some minutes - I will try to come back later [18:46:21] no worries [19:03:29] poke nimish_g [19:03:39] or anyone [19:03:41] http://commons.wikimedia.org/wiki/Wikipedia/2.0 [19:03:58] this page will be able to be transcluded into another page. [19:52:46] <{c|lunch}> !ux [19:52:46] --elephant-- I don't know anything about "ux". [19:53:03] *{c|lunch} wonders why this bot is coded to ! [19:54:58] It's a copy of MWBot basically [19:55:00] !help [19:55:00] --elephant-- Hi! I'm mwbot, a bot that was quickly whipped up by Daniel Cannon (AmiDaniel) to help out around #mediawiki. There's not much documentation on me, but you can find all my source code at http://amidaniel.com/viewvc/trunk/MWBot/?root=svn [19:57:31] <{c|lunch}> RoanKattouw, I want someone to give me some wikilove about the Commons page I made. [19:58:12] OK [19:58:22] I probably won't have time for that today, but then it's already 10pm here [19:58:36] Just drop the URL here and someone will hopefully poke at it [19:58:40] I might in the morning [19:58:44] <{c|lunch}> I did [19:58:50] <{c|lunch}> It's a blank page. [19:58:53] <{c|lunch}> well, not a blank page [19:58:58] <{c|lunch}> a page ready to be filled in. [19:59:03] <{c|lunch}> http://commons.wikimedia.org/wiki/Wikipedia/2.0 [20:04:44] Oh this is about the logos [23:25:58] is NTOC supposed to be working? [23:26:16] it's still marked as enabled in my preferences, but I don't see it in the edit window [23:47:23] thedj, you around? [23:47:45] wait, mebbe mdale is around [23:47:52] hello [23:47:58] hi :) [23:48:26] mdale, how are you doing? [23:48:32] doing oky [23:48:50] mdale, I've got reports that uploading a .mov to Commons with the mwEmbed gadget enabled transcodes it ok to ogv, but the video size is much smaller than the original [23:48:56] is this a bug or a feature ? [23:49:06] well the default settings are as follows: [23:49:28] 'maxSize' : '400', [23:49:29] 'videoBitrate' : '544', [23:49:29] 'audioBitrate' : '96', [23:49:29] 'noUpscaling' : true [23:49:44] is there a reason for the maxSize? [23:49:51] yes [23:50:09] I would love to bump that up to preserve high quality uploads but 2 issues [23:50:19] 1) 100meg upload limit ( chunks has not been re-enabled ) [23:50:32] 2) my transcoding extension has not been reviewed [23:51:01] so right now the best way to upload a .mov is to actually convert it to .ogv first with another tool, then upload the .ogv to Commons? [23:51:06] and not use the mwEmbed gadget? [23:51:16] so if you upload a 720P video file and embed it in 200px wide you still get the 720P video [23:51:23] no we have a logical default given the state of mw [23:51:48] the day the transcode extension is reviewed and deployed then I will up the quality in firefogg [23:51:57] ok [23:52:10] thanks [23:52:24] guillom: and no, NTOC is not part of the current deployment, because it requires the iframe editor i believe. [23:52:52] thedj, heh, well, I was going to ask you the questions I asked mdale , because I thought he was offline :) [23:53:07] here is a sample page with the transcode extension enabled: http://prototype.wikimedia.org/sandbox.2/Transcode_Test [23:53:09] for the NTOC I could harass my co-workers here :) [23:53:34] but thanks [23:54:56] guillom: really its one of the biggest broken things about video on wikipedia right now. [23:55:22] since often people embed the HD version at a low resolution [23:55:34] and HD videos even crash some versions of firefox [23:56:09] arbitrary encode uploads do not have consistent encode settings that set proper keyframe distances and bitrates for we streaming etc. [23:56:27] yeah, that really needed some work. [23:56:39] its been in the review queue for months... I may have to write a bot that transcodes and uploads and edits... if it does not make it into review [23:56:41] mdale: how many transcode profiles are you thinking of ? [23:57:12] I have 4 [23:57:27] seems reasonable. [23:57:27] plus original HD ( only for download ) [23:57:35] you can see them on that page [23:57:40] nn

[edit] XX

headline [edit]

headline