Knowledge (XXG):Redirects for discussion/Log/2017 April 5

3980:, it is the unit measure, in a standard, upright, ten point typeface, or "font" as the modern word is, because Steve Jobs thought "font" meant "typeface", it does not, and never has, a font is a particular siye and style of a typeface, and do not believe what you read to the contrary, anyone who has done any inky in real life knows the difference between a font and a typeface. That is why in your font cabinet you have the type set out in trays for each face and each tray is a font, that is to say a fountain, that each tray has all the letters and penalty (tricky bits) for a particular size and type. That is a font. Different sizes or styles, eyeties and sub caps and so on, and other penalty like greek, are different fonts of the same typeface. But because Steve Jobs didn't understand that, we now are lumbered with the word "font" to mean "typeface". Nevertheless all that is explained on the various articles, all we have to do is point them to them, and if the consensus is that people will type two hyphens, well, it does no harm, so no big deal. Thanks in retrospect because we have a load more useless clutter that 6591: 3326: 2698: 1416: 795: 101: 82: 63: 3221:

name of the place to the metadata when the images are being processed. However, I've never purchased a stock photograph and so don't know what metadata the image will come with (although I'd be very surprised if didn't come with at the very least a copyright field and it would seem odd to remove things like the date and time). It doesn't really matter though why it's being used only that it is.

2952:, so that to add an ambiguity by having two ways of saying the disambiguation instead of one, does not help, but harms, the ability of people to search. If I may put words in Thryduulf's mouth, it is to say "does no harm, gets people to where they want to go". It is on the cusp of the balance, but I see no harm in deleting it, whereas the harm in keeping it is evident: we must discuss it. 6137:. ` is a character that's almost impossible to search for on Google, but I'm not seeing any instances of it getting uses in this manner. Sources all seem to use "ʻAkohekohe", "'Akohekohe" or simply "Akohekohe". The redirect got 5 hits last year, which is at the top end of the noise level but not exceeding it. Combined, I'm not convinced this redirect is correct. 5151:. Roughly translated this just means "Songs you heard in the Finals" (of a singing competition). I asked my Hungarian missus and it made her laugh a lot, but she can't work it out either. She also had one from a Czech colleague who had some dentistry to explain she couldn't speak too well because "my kiss hurts". Such are the marvels of MT. 2059: 3179:. I'm seeing lots of uses of this spelling unrelated to Knowledge (XXG). Most commonly on stock photo websites for some reason, but it seems likely that people using such stock photos will keep the labels given when using them (or search for more information when writing their own caption) and thus this is a plausible redirect. 5517:. I hope as with in previous purges of eubotiness it is realised I keep about 90% if them without question, it is only the ones I have any doubt about I bring here... plus the obvious deletes because we have consensus there is no need for a speedy delete criterion. So with that given, if someone says keep, it means keep. 2180:(eubot). The em dash goes to double hyphen again. What is interesting here, or not, is that this is obviously English names but has the French linguistic trend of the way it does the names of station lines. I think for this one it is fairly simple delete, but I shall summon up by the powers of Knowledge (XXG) 6081:

confusing, not at target. I'm aware that US keyboards have the left apos at top left on the kb ( have it here too, right ` here on my UK keyboard but rarely use it); WP goes for straight quotes, and this is slightly but only slightly worse than harmless because the ` indicates an inflection, but then

3975:

came out were they substituted by two hyphen characters. There is a reason that typefaces are measured in "ems" (or more accurately pica ems, although that size has been metricated), because that is the width of an "m", usually the widest letter in the font. Similar measures are for x cross and x bar

3243:

of your camera pretty much automatically, add the brand of camera, that kind of thing. The stuff you see when you look at the bottom of a page on Wikimedia Commons, all that stuff. Now, it would not surprise me in the least if a software engineer was told to add a field to brand their camera and just

5571:

approach when targeted at those that are doubtful still supports the view that we don't need a CSD on this, but does mean that we have to throttle RfD a bit. As I say, a good 90% are kept without discussion here, and that's a conservative figure, of the batch between 3,000 and 5,000, I've kept about

3205:

or whatever, then, i.e. the camera records various things outside the image data proper, such as time of day, lens settings, "Sprakebuell" and so on. I shouldn't be surprised if it was, and then copying from site to site would tend to preserve that. I am sure Thryduulf is well aware of all that, it

321:

does get lots of hits in reliable sources. Unsurprisingly perhaps it's the obvious thing for sports writers to call him when he isn't doing well - particularly it seems when he got sacked from Chelsea. It's not being used to insult or denigrate him but neither is it flattering - more a sort of bring

3220:

From my limited understanding of how metadata works, if this is a metadata issue, then what will happen is that the camera will note the coordinates (taken from GPS) of the location the photograph was taken and store them. It is far from implausible that a lookup of those coordinates could add the

4722:

He doesn't have a standard citation form of the kind that I'm familiar with (which is for botanists who describe species, not horticulturalists who breed new cultivars). It does appear from a quick Google search for "Pernet pere" that specialty source related to roses do cite him this way. French

6467:, is "it's the same name without diacritics", but it's not the same name, it's a name differently spelled, in my opinion, and so you should take the advice and look at the DAB. To send someone off on a wild goose chase I think is worse in terms of the average number of clicks to find the right 3248:

demand, so that is where my curiosity lay. Contrary to popular opinion, most software engineers do not lay easter eggs, if there is any kind of peer review, although I set aside most of december for one person to make the most fantastic demo to send to our clients, with a total abuse of the 3d

5553:

Corollary. I do still argue about some of them, but that is what discussion is about. All I'm saying is I'm more than happy if a second set of eyes says keep, to withdraw it speedily. I don't want to flood RfD and most I speedily keep, but the few I have doubts about I do bring here, because

4680:, but does he have a standard form name thingy is generally quoted by in horticultural references? Not in the reference at the current article. If he does, do we need the "père" is that standard form when there is no junior to be confused with? At the moment, this R redirects to a redirect, 4464:

as withdrawn. I know Thryduulf expects me to do me homework, but I couldn't find any meself. That's probably a consequence of searches targeting your geolocation, but I did my best and couldn't find anything. It's still a rather weird transliteration,, but if it is in the wild, so be it,

461: 6279:. While this does generate a lot of google hits, even excluding Knowledge (XXG) and the target spelling from the list, I can't find any that actually use this spelling or anything like it - I guess Google is trying to be helpful, but on this occasion failing. 2364:. It is easier when you don't immediately clock it as wrong, and do it kinda pattern matching linguistically rather than what was that past fog george had (I guess, when the translation button doesn't get pressed) this really threw me for a few seconds. 4684:

moved it today, so it's only really this RfD that stops it being a double redirect that would be "fixed" by a bot (by virtue of it not being a redirect right now). We probably don't need either redirect with or without the accent, it's essentially

4641:, the title of the actual article. (I can understand why an English-language user without a French-language keyboard (or without the knowledge of keyboard shortcuts for accents) might search for pere instead of <the version with an accent: --> 3612:. I'm seeing lots of google hits for this term, but the meaningful ones are almost exclusively in Dutch and appear unrelated to Hungary. It's not a word that Google translate recognises, nor is there an entry in the English or Dutch Wiktionaries. 3017:, etc). Not everybody is able to type all diacritics in all environments, nor should we expect them to be able to - I don't know the compose key sequence for breve accents for example and I have a lot more knowledge of this than average. 2987:. I'm afraid I don't see how any harm in keeping this can exist. Multiple ways to disambiguate something is not an example of confusion, but rather a standard way to assist people in finding the page they want to read or link to (cf 1693: 6082:

if we're doing that then this is a bit nonsense, cos ` and ! and ^ and so on indicate different inflections. This needs RS to stay, and Eubot was not so good on RS. I suppose someone will say it is harmless. It is not. It is the

1193:

I would oppose a disambiguation. It's a shortcut redirect, it's fine for them to be ambiguous (even though I'm not seeing ambiguity here). If it's converted to a disambiguation page, it can no longer be used as a shortcut.

252:

Now that I think of it, I'm not sure if "The Happy One" is meant as pejorative or not. And of course, there's nothing in the article to help me determine that. So let's call it confusing at best, pejorative at worst.

5566:

approach to listing those of which I have doubt, but also those that are in no doubt, will clog up RfD for those that in seven days "or so" will be deleted. Looking back over my last batch in December, I think the

244:

Redirects need not be neutral, but that doesn't mean pejorative redirects to BLPs are at all advisable. Neither of these are especially well used, nor are they mentioned in the article. (For reference, these parody

297:. It wouldn't harm to mention it in the article though - the amount of coverage it got (and seemingly occasionally still does) would seem to justify it, although football really isn't my field (no pun intended). 5447: 604: 5474:

and "expose" mean different things? Since they are kinda used in different ways (and I speak French as she is spoke proper) I am not sure this is helpful, and borders on harmful. But probably

6102:

applies here, but when this closes, the consensus will stand as precedent to sort out a lot of others, too. (Not many hawaiian but many with the back apos here used unfortunately by eubot).

5927:

is that Eubot ignored the first letter of the title; all German nouns start with capitals like... er... Knowledge (XXG) titles. If the justification wasn!t that, it was something like that.

5327: 5306: 3925: 2211: 2382:. This spelling does get a very small number of google hits, but not in anything I'm confident calling a reliable source and with only 3 hits last year it's safe to say this is unused. 2184:

who may or may not know the standards of how we name railway lines in English-speaking Ontario. The hyphens seem inconsistent both sides of the "kent" anyway, but that's cos it's from

6598: 3333: 2705: 1423: 108: 89: 70: 39: 34: 3235:

Sort of. JPEG allows you, even before 2000 that was just the simplest link I thought, to store extra information against the photo. This is not part of the image itself, it's not

449: 5496:, this is useful for searches when someone doesn't have access to diacritics. Technical reasons aside, I've seen "exposé" written as "expose" pretty frequently. I highly doubt 802: 5084: 1369: 1347: 1274: 3206:

is just a supposition, do you think that could be where you get the hits from? If so, it would suggest it is a kinda cookie encoded in the metadata, hidden in plain sight.

4800:

involved although not an admin. So it must stay open for now. It was silly to move it boldly when it was just opened for discussion. That's a bit trigger-happy, I think.

2940:(eubot) I've brought this up a couple of times with no real consensus, but no consensus that there is no consensus, i.e. I think it was passed over. My argument is that 3620:(it was also created by a bot, so I don't think we can take that as reliable evidence of anything). Whatever it does mean it would probably not be a good redirect per 5741:, I must have cocked up on this one. There was a similar where the addition of the accent had Eubot put another "e" in it, but patently this wasn't it, I cocked up. 2360:(eubot) Not Germanic but French. This one really threw me, it's obvious really it just put "u umlaut" to "ue", but when you actually understand the language it is 455: 5256: 2640:

Consensus was back in december with German via Swedish to English we don't do oeoe, it would be oo or oe, not the qualigature or whatever you want to call oeoe.

5896: 4897: 4416:(eubot) Not Germanic but Hungarian; yet "cz" is not in the Hungarian alphabet so it's a bit of an import, nevertheless, "cz" is Slav and not Germanic either. 444: 317:

on it's own gets all sorts of hits about things that happen to be the average (rent in New York city, price of fruit, length of planks of wood, you name it).

5441: 2917: 641:

be helpful since it's a page in the "Knowledge (XXG):" namespace about a subject named "Knowledge (XXG):The Musical". (Seeking input on this: consider me "

4446:. Regardless of what Si might expect, this is a very well used spelling of her name in the real world with lots of uses unconnected with Knowledge (XXG). 4688: 4081: 3011: 877: 5919:(Eubot) Not Germanic but Finnish. From what I understand from previous discussions, it's unlikely that "Ää" would be transliterated as "Aae". In short, 5435: 2617: 2157: 1687: 21: 6097: 5752: 3883: 3001: 4985:(according to Google), and we should certainly have something at that title. To avoid getting too off-topic I'll reply further on your talk page. 4576: 4420:

nonsense. Unusual Hungarian surname but old surnames are allowed their old forms, modern Hungarian surnames would be magyarized and be, probably,

4249: 1323: 999: 4792:

after I raised this discussion but before anyone else had a chance to comment on it. So neither Tavix nor Thryduulf can now close it, because of

2948:

contributed to previous discussions on this but I don't think there was ever much a conclusion. My argument, as I put and still stands, was that

1311: 1676: 3408: 6485:

I was giving the benefit to the user who doesn't know how to get an umlaut, over the one who can't spell ;-) In the meantime, I've tidied up

5539:

When I was typing the above remarks Thryduulf had not closed it. Forgive me for modifying it but it was not technically an EC on either part.

5129:, not used in the real world. Amusingly one automated scraper appears to have gone awry with this and translated it as "A dog and pony show". 3971:'s argument that people did think em dashes were two hyphens is putting the cart before the horse. The em dashes were the size of an em, and 2479: 181: 17: 4393: 2991: 1066: 987: 6459:

To a target that says "for different spellings see...." right at the top. If this is not a different spelling, what is it? The answer by

5558:, or at least I took it that way, that when I said in December that most are kept and I don't think we need a speedy deletion criterion, 3743: 221: 2337: 598: 5072: 6054: 3138: 5147:

I'm not sure that is totally scraped, to be honest, but has gone round the houses by an MT that has a corpus of idioms. We do have

322:

him down to earth sort of term. If it were mentioned in the article I'd say to keep it, but as it isn't I'm on the fence about it.

270: 5854: 2778: 1806: 587: 249:", a more common nickname which is used in his article.) There's little to no value in keeping these, and some harm in doing so. 1681: 6234: 2886: 1599: 1563: 1292: 1053: 698:

I bet this event was a lot of fun! Makes me wish I was both in the area and also actively editing Knowledge (XXG) at the time.

367: 4968:? I would have to check Wikt on whether propa- or propo- I think the former, but never thought about it. Odd we haven't that. 4885: 2062:

but that is an OCR error for "Gýmir". If it were a common error I'd support keeping the redirect but it doesn't appear to be.

1215:(and add hatnote at target) unless someone decides to take up the task of fixing all the two thousand or so incoming links. – 1502: 569: 5217: 3466:

as keep. Not sure how I misread that, obviously if Austrian then keep. Was only the fact that I wondered what to do with an

559: 2005: 1716:

Seems to have been created in error, but per the redirect's edit history, it seems as though it may have been intentional.

6379: 5679: 1144: 5078: 3784:. Unsurprisingly for something that transliterates Ö → O and ö → oe this gets no hits not sourced from Knowledge (XXG). 6329: 6187: 6007: 5950: 5807: 5630: 5398: 5244: 5201: 5037: 4850: 4523: 4344: 4202: 4034: 3834: 3696: 3520: 3359: 3089: 2858: 2731: 2570: 2432: 2290: 2112: 1958: 1771: 1646: 1449: 1260: 950: 828: 543: 414: 134: 3567: 3161:(eubot) Well I can sprake bull at the best of times, but we need some consensus on these Danish ones. Not many of em. 2049: 1980: 1818: 1381: 1127: 2662:. All but one of the Google hits for this is obviously sourced from Knowledge (XXG), and the exception may also be. 484:

Double "Knowledge (XXG):" namespace in title. However, per its edit history, this redirect wasn't created in error.

5250: 5067: 2911: 6564: 6539: 6518: 6498: 6480: 6450: 6433: 6415: 6352: 6288: 6270: 6209: 6146: 6129: 6111: 6029: 5966: 5936: 5890: 5829: 5766: 5733: 5715: 5652: 5589: 5548: 5530: 5509: 5487: 5420: 5357: 5339: 5318: 5296: 5229: 5160: 5138: 5120: 5059: 4994: 4977: 4951: 4933: 4891: 4872: 4809: 4775: 4736: 4710: 4659: 4628: 4549: 4482: 4455: 4437: 4366: 4303: 4285: 4224: 4161: 4131: 4113: 4056: 3993: 3958: 3937: 3915: 3856: 3793: 3775: 3718: 3657: 3633: 3603: 3542: 3479: 3458: 3440: 3381: 3299: 3270: 3230: 3215: 3188: 3170: 3111: 3048: 3044:. I don't see what difference it makes if the diacritics are in the disambiguator rather than the title proper. – 3026: 2979: 2961: 2890: 2818: 2753: 2671: 2653: 2592: 2529: 2511: 2454: 2391: 2373: 2312: 2249: 2223: 2201: 2130: 2071: 1917: 1900: 1879: 1858: 1842: 1793: 1731: 1668: 1605: 1579: 1539: 1475: 1389: 1359: 1296: 1219: 1203: 1184: 1162: 1135: 1100: 1078: 1057: 1035: 972: 910: 852: 766: 735: 713: 685: 660: 579: 503: 436: 373: 346: 331: 306: 282: 262: 156: 5954: 5884: 5500:

using the redirect will be harmed by it, unless of course there's a separate award for "expose" (there's not). --

726:

per Pharos (although I wasn't there). I'm actually not sure I'd vote against moving the page back to this title.

1317: 993: 5284: 4075: 3257:

it to make these seasonal scenes all in glorious cinemascope 3D. Customers loved it, we loved doing it, and it

3038: 2151: 1845:

of lede says it is also known as ODTÜ, " in Turkish, Orta Doğu Teknik Üniversitesi". Not Germanic but Turkish.

871: 4122:. It seems that all uses of this outside of something to do with MD5 hashes are sourced from Knowledge (XXG). 2905: 2611: 748: 592: 5946: 5879: 4880: 4424:

the equivalent sound for the cz i.e. like English "ch" as in "cheese" or "czech". Well not like the "ch" in "

6494: 6446: 6125: 5280: 4655: 4243: 3949:. I shan't list more on the same pattern, thanks for reminding me of that discussion, I did try to find it. 3877: 2975: 2605: 1896: 6527: 4759: 2145: 5724:, this is helpful for people who don't have access to diacritics. There's nothing nonsensical about it. -- 4570: 4069: 4064: 2473: 860: 850: 343: 175: 4237: 3871: 3250: 2600: 6325: 6183: 6003: 5803: 5626: 5394: 5197: 5033: 4846: 4612: 4519: 4340: 4198: 4030: 3830: 3737: 3692: 3516: 3402: 3355: 3085: 2854: 2727: 2566: 2428: 2286: 2108: 1954: 1767: 1642: 1445: 1256: 946: 824: 539: 410: 215: 130: 5555: 4982: 4965: 4961: 4793: 4698: 4232: 2331: 1023: 5945:. I'm not seeing any actual uses not originating from Knowledge (XXG). For the same reason I've added 6048: 5848: 4796:. I will close it as nom, but there's some tidywork still to do, which I can't reasonably do because 4763: 4751: 4564: 2772: 2462: 631: 164: 6228: 4694: 293:"The Happy One". It seems this is not at all pejorative, and is what he asked the media to call him 6560: 6535: 6476: 6411: 6284: 6266: 6142: 6107: 6087: 5962: 5932: 5762: 5711: 5648: 5585: 5544: 5526: 5483: 5416: 5353: 5335: 5292: 5222: 5156: 5134: 5116: 4990: 4973: 4947: 4929: 4805: 4771: 4732: 4706: 4624: 4478: 4451: 4433: 4387: 4299: 4281: 4127: 4109: 3989: 3954: 3911: 3852: 3789: 3771: 3726: 3653: 3629: 3599: 3475: 3436: 3377: 3266: 3226: 3211: 3184: 3166: 3022: 2957: 2882: 2814: 2667: 2649: 2525: 2507: 2387: 2369: 2245: 2197: 2126: 2067: 2045: 1913: 1875: 1854: 1727: 1593: 1569: 1288: 1049: 762: 731: 709: 656: 499: 361: 327: 302: 204: 53:

This is a list of redirects that have been proposed for deletion or other action on April 5, 2017.

3641: 3621: 2320: 6552: 6510: 6490: 6460: 6442: 6121: 5924: 4651: 3906:(Eubot) same pattern of replacing em dash with double hyphen. This one is in Quebec, not France. 3245: 2971: 1999: 1892: 1355: 1031: 672: 574: 6037: 5837: 4724: 3731: 3561: 3396: 3240: 2761: 1812: 6217: 4150: 4104:(eubot) Consensus was to keep Swedish ones with Germanic umlauts but this is Danish. Not sure. 6349: 5148: 4157: 3295: 3045: 2467: 1216: 1180: 843: 340: 6344: 6324:

Subsequent comments should be made on an appropriate discussion page (such as the redirect's

6182:

Subsequent comments should be made on an appropriate discussion page (such as the redirect's

6002:

Subsequent comments should be made on an appropriate discussion page (such as the redirect's

5802:

Subsequent comments should be made on an appropriate discussion page (such as the redirect's

5625:

Subsequent comments should be made on an appropriate discussion page (such as the redirect's

5393:

Subsequent comments should be made on an appropriate discussion page (such as the redirect's

5279:(Eubot) I forgot what consensus we had, if any, on Eubot turning em dashes into two hyphens. 5196:

Subsequent comments should be made on an appropriate discussion page (such as the redirect's

5032:

Subsequent comments should be made on an appropriate discussion page (such as the redirect's

4942:. All uses of the mixed transliteration (Ö → O, ö → oe) appear to stem from Knowledge (XXG). 4845:

Subsequent comments should be made on an appropriate discussion page (such as the redirect's

4518:

Subsequent comments should be made on an appropriate discussion page (such as the redirect's

4421: 4339:

Subsequent comments should be made on an appropriate discussion page (such as the redirect's

4197:

Subsequent comments should be made on an appropriate discussion page (such as the redirect's

4029:

Subsequent comments should be made on an appropriate discussion page (such as the redirect's

3829:

Subsequent comments should be made on an appropriate discussion page (such as the redirect's

3691:

Subsequent comments should be made on an appropriate discussion page (such as the redirect's

3515:

Subsequent comments should be made on an appropriate discussion page (such as the redirect's

3354:

Subsequent comments should be made on an appropriate discussion page (such as the redirect's

3249:

molecular modelling software to build snowmen and icy scenes etc out of atoms with a certain

3084:

Subsequent comments should be made on an appropriate discussion page (such as the redirect's

2873: 2853:

Subsequent comments should be made on an appropriate discussion page (such as the redirect's

2726:

Subsequent comments should be made on an appropriate discussion page (such as the redirect's

2565:

Subsequent comments should be made on an appropriate discussion page (such as the redirect's

2427:

Subsequent comments should be made on an appropriate discussion page (such as the redirect's

2285:

Subsequent comments should be made on an appropriate discussion page (such as the redirect's

2107:

Subsequent comments should be made on an appropriate discussion page (such as the redirect's

1953:

Subsequent comments should be made on an appropriate discussion page (such as the redirect's

1766:

Subsequent comments should be made on an appropriate discussion page (such as the redirect's

1641:

Subsequent comments should be made on an appropriate discussion page (such as the redirect's

1444:

Subsequent comments should be made on an appropriate discussion page (such as the redirect's

1279: 1255:

Subsequent comments should be made on an appropriate discussion page (such as the redirect's

945:

Subsequent comments should be made on an appropriate discussion page (such as the redirect's

900:

This seems like a BLP violation, and certainly questionable as a useful redirect regardless.

823:

Subsequent comments should be made on an appropriate discussion page (such as the redirect's

538:

Subsequent comments should be made on an appropriate discussion page (such as the redirect's

409:

Subsequent comments should be made on an appropriate discussion page (such as the redirect's

129:

Subsequent comments should be made on an appropriate discussion page (such as the redirect's

5575: 4469:, Thryduulf provides no evidence of that but I imagine it is correct, because if we haven't 4381: 4294:. All uses of "Omnoegovi" (a mixed transliteration) seem to originate from Knowledge (XXG). 3132: 2033: 1988: 1552:. Is this discussion necessary? The bot broke the redirect, that could've just been undone. 681: 209: 169: 6258: 6091: 6078: 5703: 5108: 4921: 4758:, the spelling without the diacritic should redirect to the same target in accordance with 4608: 4470: 4417: 4273: 3591: 3550: 2806: 2641: 2189: 2037: 1867: 1846: 1801: 5475: 246: 5920: 5842: 3645: 747:

Yeah, I'd say it would probably be best to move it back since the subject is not called "

6556: 6531: 6472: 6407: 6280: 6262: 6222: 6138: 6103: 5958: 5928: 5758: 5707: 5644: 5581: 5540: 5522: 5479: 5412: 5349: 5331: 5288: 5152: 5130: 5112: 4986: 4969: 4943: 4925: 4801: 4767: 4728: 4717: 4702: 4669: 4620: 4474: 4447: 4429: 4295: 4277: 4123: 4105: 3985: 3950: 3907: 3848: 3785: 3767: 3649: 3625: 3595: 3471: 3432: 3373: 3262: 3222: 3207: 3198: 3180: 3162: 3018: 2953: 2945: 2878: 2810: 2766: 2663: 2645: 2521: 2503: 2383: 2365: 2325: 2241: 2193: 2122: 2063: 2041: 1909: 1871: 1850: 1717: 1587: 1555: 1534: 1284: 1045: 908: 752: 742: 727: 699: 646: 489: 355: 323: 298: 803:

Knowledge (XXG):Redirects for discussion/Log/2017 May 1#Needle inside a ball of cotton

6042: 3126: 1496: 1351: 1158: 1027: 968: 564: 278: 258: 5757:(which Eubot always marks them anyway so should be there), my cock-up on this one. 6373: 5673: 4153: 3968: 3291: 3236: 2188:

to Essex; that's normal in French typography but not here at EN:WP, which makes it

2185: 2181: 1908:

even if this were Germanic, initialisms don't get translated/transcribed this way.

1175: 71:

Knowledge (XXG):Redirects for discussion/Log/2017 April 12#Van Buren Democrat Party

6391: 6246: 6066: 5908: 5866: 5691: 5459: 5328:

Knowledge (XXG):Redirects for discussion/Log/2016 December 26#Saint-Leonard--Anjou

5307:

Knowledge (XXG):Redirects for discussion/Log/2016 December 26#Saint-Leonard--Anjou

5268: 5096: 4960:

Yes, within an order of magnitude they all stem from Eubot. We don't seem to have

4909: 4588: 4405: 4261: 4093: 3926:

Knowledge (XXG):Redirects for discussion/Log/2016 December 26#Saint-Leonard--Anjou

3895: 3755: 3579: 3420: 3150: 2929: 2790: 2629: 2491: 2349: 2212:

Knowledge (XXG):Redirects for discussion/Log/2016 December 26#Saint-Leonard--Anjou

2169: 2017: 1830: 1705: 1514: 1335: 1011: 889: 616: 473: 233: 193: 6468: 6464: 5563: 4755: 4677: 4638: 4537: 2802: 1549: 1526: 1463: 865: 693: 677: 294: 3334:

Knowledge (XXG):Redirects for discussion/Log/2017 April 15#Toegroeg, Govi-Altai

354:

used mainly in 2013 as a quote, not kept as a nickname or branded beyond that.

6514: 6486: 6425: 6403: 6201: 6021: 5821: 5725: 5667: 5568: 5559: 5501: 5310: 5051: 4864: 4785: 4681: 4541: 4358: 4216: 4048: 3981: 3929: 3710: 3534: 3450: 3103: 2745: 2584: 2446: 2304: 2233: 2215: 1972: 1785: 1660: 1467: 1375: 1195: 1121: 1092: 1070: 428: 148: 6424:. The redirect has one 'f', so this one is pointing to the correct target. -- 5283:

already exists if your keyboard, like mine, doesn't have an em dash key. (My

2970:. Seems to me a useful redirect for users without easy access to diacritics. 3202: 1529: 1026:

when I went looking for policy on how much context is needed in an article.

901: 6367: 4148: 90:

Knowledge (XXG):Redirects for discussion/Log/2017 April 15#Less ripe (wine)

6318:

The following is an archived discussion concerning one or more redirects.

6176:

The following is an archived discussion concerning one or more redirects.

5996:

The following is an archived discussion concerning one or more redirects.

5796:

The following is an archived discussion concerning one or more redirects.

5619:

The following is an archived discussion concerning one or more redirects.

5387:

The following is an archived discussion concerning one or more redirects.

5190:

The following is an archived discussion concerning one or more redirects.

5026:

The following is an archived discussion concerning one or more redirects.

4839:

The following is an archived discussion concerning one or more redirects.

4512:

The following is an archived discussion concerning one or more redirects.

4333:

The following is an archived discussion concerning one or more redirects.

4191:

The following is an archived discussion concerning one or more redirects.

4023:

The following is an archived discussion concerning one or more redirects.

3823:

The following is an archived discussion concerning one or more redirects.

3685:

The following is an archived discussion concerning one or more redirects.

3509:

The following is an archived discussion concerning one or more redirects.

3348:

The following is an archived discussion concerning one or more redirects.

3078:

The following is an archived discussion concerning one or more redirects.

2847:

The following is an archived discussion concerning one or more redirects.

2720:

The following is an archived discussion concerning one or more redirects.

2559:

The following is an archived discussion concerning one or more redirects.

2421:

The following is an archived discussion concerning one or more redirects.

2279:

The following is an archived discussion concerning one or more redirects.

2101:

The following is an archived discussion concerning one or more redirects.

1947:

The following is an archived discussion concerning one or more redirects.

1760:

The following is an archived discussion concerning one or more redirects.

1635:

The following is an archived discussion concerning one or more redirects.

1438:

The following is an archived discussion concerning one or more redirects.

1249:

The following is an archived discussion concerning one or more redirects.

939:

The following is an archived discussion concerning one or more redirects.

817:

The following is an archived discussion concerning one or more redirects.

532:

The following is an archived discussion concerning one or more redirects.

403:

The following is an archived discussion concerning one or more redirects.

123:

The following is an archived discussion concerning one or more redirects.

4140: 3253:

and mesoscale backgrounds and essentially entirely abusing the software,

1154: 964: 274: 254: 1346:

There are quite a few places this could go to. I thought it would go to

445:

Knowledge (XXG):Knowledge (XXG):WikiProject Novels/Roald Dahl task force

394:

Knowledge (XXG):Knowledge (XXG):WikiProject Novels/Roald Dahl task force

3555: 2706:

Knowledge (XXG):Redirects for discussion/Log/2017 April 15#Migros Tuerk

1993: 6578:

Subsequent comments should be made on the appropriate discussion page.

6302:

Subsequent comments should be made on the appropriate discussion page.

6160:

Subsequent comments should be made on the appropriate discussion page.

5980:

Subsequent comments should be made on the appropriate discussion page.

5780:

Subsequent comments should be made on the appropriate discussion page.

5603:

Subsequent comments should be made on the appropriate discussion page.

5470:(Eubot) what is it exposing? Am I too pedantic to think that "exposé" 5371:

Subsequent comments should be made on the appropriate discussion page.

5174:

Subsequent comments should be made on the appropriate discussion page.

5010:

Subsequent comments should be made on the appropriate discussion page.

4823:

Subsequent comments should be made on the appropriate discussion page.

4496:

Subsequent comments should be made on the appropriate discussion page.

4317:

Subsequent comments should be made on the appropriate discussion page.

4175:

Subsequent comments should be made on the appropriate discussion page.

4147:. (Google finds some information about it on railway hobbyist websites 4007:

Subsequent comments should be made on the appropriate discussion page.

3807:

Subsequent comments should be made on the appropriate discussion page.

3669:

Subsequent comments should be made on the appropriate discussion page.

3617: 3493:

Subsequent comments should be made on the appropriate discussion page.

3313:

Subsequent comments should be made on the appropriate discussion page.

3062:

Subsequent comments should be made on the appropriate discussion page.

2831:

Subsequent comments should be made on the appropriate discussion page.

2685:

Subsequent comments should be made on the appropriate discussion page.

2543:

Subsequent comments should be made on the appropriate discussion page.

2405:

Subsequent comments should be made on the appropriate discussion page.

2263:

Subsequent comments should be made on the appropriate discussion page.

2085:

Subsequent comments should be made on the appropriate discussion page.

1931:

Subsequent comments should be made on the appropriate discussion page.

1744:

Subsequent comments should be made on the appropriate discussion page.

1619:

Subsequent comments should be made on the appropriate discussion page.

1424:

Knowledge (XXG):Redirects for discussion/Log/2017 April 17#Brexit 1975

1403:

Subsequent comments should be made on the appropriate discussion page.

1233:

Subsequent comments should be made on the appropriate discussion page.

1067:

Knowledge (XXG):Writing better articles#Provide context for the reader

923:

Subsequent comments should be made on the appropriate discussion page.

782:

Subsequent comments should be made on the appropriate discussion page.

516:

Subsequent comments should be made on the appropriate discussion page.

387:

Subsequent comments should be made on the appropriate discussion page.

2942:

the dias here are only in the disambiguation parenthesis of the title

109:

Knowledge (XXG):Redirects for discussion/Log/2017 April 15#Less sleep

6572: