User talk:Be..anyone/Archive 1

Archive 1

Archive 2

License tagging for File:Rexx3 orig size transparent.gif

Thanks for uploading File:Rexx3 orig size transparent.gif. You don't seem to have indicated the license status of the image. Wikipedia uses a set of image copyright tags to indicate this information.

To add a tag to the image, select the appropriate tag from this list, click on this link, then click "Edit this page" and add the tag to the image's description. If there doesn't seem to be a suitable tag, the image is probably not appropriate for use on Wikipedia. For help in choosing the correct tag, or for any other questions, leave a message on Wikipedia:Media copyright questions. Thank you for your cooperation. --ImageTaggingBot (talk) 12:06, 24 January 2014 (UTC)

Fixed, already tagged for move to commons by another editor (thanks for review). –Be..anyone (talk) 12:04, 3 February 2014 (UTC)

Disambiguation link notification for February 3

Hi. Thank you for your recent edits. Wikipedia appreciates your help. We noticed though that you've added some links pointing to disambiguation pages. Such links are almost always unintended, since a disambiguation page is merely a list of "Did you mean..." article titles. Read the FAQ • Join us at the DPL WikiProject.

International Components for Unicode (check to confirm | fix with Dab solver)

added a link pointing to OSI

NetRexx (check to confirm | fix with Dab solver)

added a link pointing to OSI

It's OK to remove this message. Also, to stop receiving these messages, follow these opt-out instructions. Thanks, DPL bot (talk) 08:54, 3 February 2014 (UTC)

Fixed without touching the tools, they didn't exist in 2007 and are not on toollabs: in 2014, for two links manual fixes will do. –Be..anyone (talk) 12:10, 3 February 2014 (UTC)

Article .ilbm

Hello. I've undid your blanking of the article. If you believe that the redirect is unnecessary, please nominate the page for deletion at WP:RFD. It will be better if you can expand on the article if it's notable enough. If you have a question, please leave a question or comment on my talk page. Thanks KJ ^{click here} 23:20, 13 March 2014 (UTC)

The article and the two other redirects .iff and .lbm are fine, but .ilbm appears to be unsourced at the moment. –Be..anyone (talk) 23:24, 13 March 2014 (UTC)

What do you mean unsourced? I thought it looked like an alternative spelling redirect. KJ ^{click here} 01:18, 14 March 2014 (UTC)

Oops, no, I added lots of missing {{R from file extension}}, .ilbm was the one exception where I went for "not really". –Be..anyone (talk) 01:23, 14 March 2014 (UTC)

Oh, I see. You can go to WP:RFD with this, I think. Maybe nominate it for deletion? KJ ^{click here} 04:21, 14 March 2014 (UTC)

It's not harmful needing an RFD, only unnecessary. I tried an obscure redirect category instead of blanking. –Be..anyone (talk) 09:16, 15 March 2014 (UTC)

The same hack now also on .dib, BMP file format has the reference why that is bogus/dubious. –Be..anyone (talk) 17:30, 18 March 2014 (UTC)

Disambiguation link notification for March 15

Hi. Thank you for your recent edits. Wikipedia appreciates your help. We noticed though that when you edited Progressive Graphics File, you added a link pointing to the disambiguation page PGF (check to confirm | fix with Dab solver). Such links are almost always unintended, since a disambiguation page is merely a list of "Did you mean..." article titles. Read the FAQ • Join us at the DPL WikiProject.

It's OK to remove this message. Also, to stop receiving these messages, follow these opt-out instructions. Thanks, DPL bot (talk) 08:50, 15 March 2014 (UTC)

Yes, that was intentional, with a help request on the talk page. ;-) –Be..anyone (talk) 09:11, 15 March 2014 (UTC)

Re: JXR

Hi.

I try to be very careful about using the word "funny" to refer to people's confusion and distress. But, that's not surprising at all; at least not as surprising as you writing that WPG supports DjVu. WPG can be made to takeover those filename extensions and their associated MIME types, but whether it really supports decoding it, is a different question. Then again, WPG's native decoders can be augmented with plug-ins, which might not be available on other people's system.

Best regards,
Codename Lisa (talk) 19:55, 16 March 2014 (UTC)

I appreciate your attempt to improve the article; however, we cannot accept synthesis of published material that advances a position. You provided source that WPG supports HD Photo (.wdp), and a source that says Windows 7 later received an updated WIC codec supporting JPEG XR. But you use these sources to conclude that WPG supports .jxr. It could easily be false.

Best regards,

Codename Lisa (talk) 00:22, 17 March 2014 (UTC)

Just tested it on a virtual machine with Windows only. Answer is negative. Something else in your machine is supplying it. Best regards, Codename Lisa (talk) 00:56, 17 March 2014 (UTC)

That ended up on the relevant talk page, all opinions from 3rd parties welcome (there, here would be odd.) –Be..anyone (talk) 17:20, 18 March 2014 (UTC)

WTFPL

Hi, I'm curious about the purpose of the {{-}} you have put in the "Terms" section of the WTFPL article.

Best, Malparti (talk) 21:48, 28 October 2014 (UTC)

@Malparti:, now I'm also curious (after an unscheduled+unintended login after about seven months... well.) Okay, I added it in section Terms, and the purpose of {{-}} is to break some floating right or left content (image, infobox, whatever) before it pushes normal content to the bottom. IOW, you might see no problem at all with a wide display or a small font, but I saw a problem and fixed it based on a "works for me" (now) observation. That's bogus if it's only me, otherwise it's fine.

The version 1 sub-section contains the preformatted license <pre> stuff </pre>, that needs the full width, and some floating content would push it down with an ugly empty gap between the sub-section header and the license. –Be..anyone (talk) 15:21, 11 November 2014 (UTC)

@Be..anyone: Well that's weird because it seems that adding {{-}} caused the very problem you were trying to solve on my laptop : with a 1366*768 and fonts within the 12-16 range, it creates a big gap between the H1 (Terms) and H2 (Version 1) headers. For instance, with my default settings the empty space is 2.6 cm (instead of 0.5 cm), which looks weird. Before that, everything was OK. I've used Browserstack to see what it looks like with other settings -- same problem (though admittedly it seems that my settings make it pretty extreme). So I'll remove it (also because it is more coherent with the idea of using a markup language, in my opinion). If you come up with another solution for your problem, feel free to ask me to test it.

Best, Malparti (talk) 16:12, 11 November 2014 (UTC)

ACK, it also creates that gap for me, but at least the sub-section header is where it should be. Just (try to) shuffle the {{-}} around, obviously we want the same thing. ;-) –Be..anyone (talk) 08:37, 12 November 2014 (UTC)

Archive 1

Archive 2