Knowledge

talk:Twinkle - Knowledge

Source đź“ť

716:
possible for other scripts to cancel the page unload in their own beforeunload listeners. I figured not firing the event was not an issue (the error will just still show up, which is not a change), and that the chance of both having another script installed listening for beforeunload, and having the user both navigate away and also cancel that navigation in the VERY short time between the request being sent and completed is so low as to be negligible, especially for something as relatively trivial as displaying an error message.
182: 753:
complete normally. It would be very surprising, though, for someone to be able to load the Knowledge page they are viewing but not their Twinkle preferences page, thinking about it further. Maybe changing only the "Could not load" error to a console.log (or .error, probably) and leaving the "Could not parse" error as mw.notify would make sense? Personally I would want to be harassed by an error message if I had screwed up my config file, but I might be an exception.
1243:. Any edits created on Knowledge is irrevocably released and typically searchable by any other editors. In the current implementation, if a CSD tag is declined, that would be permanently visible in edit history of that page as well as a user's edit. If someone is so concerned about privacy, that their declined CSD tags become visible they should not engage in CSD tagging to begin with. All that said, they still would be able to turn off the logs setting and request 159: 123: 651: 712:
resorting to default preferences". It seems like the browser (Firefox at least – haven't tested across browsers) makes all pending network requests fail as soon as navigation to a new page starts, but before JS execution stops, so the error handler still has a chance to run and display the message even though there was never actually an error.
1405:
can answer this question (and a comment). I see an admin somehow mass-tag pages with CSD notices. Except for Batch Delete/Undelete, I thought Twinkle only worked on one article/User notification at a time. What is this feature that would allow me to tag multiple pages and, at the same time, send out
711:
I've been noticing this issue for a while now but figured there was no way to fix it, until very recently when I managed to fix it in a script of mine. If you click a link to another page immediately after the page loads, there will often be an error message "Could not load your Twinkle preferences,
1409:
My comment is one I have raised here several times over the years. While, when I delete a page, Twinkle will delete the Article, the Article talk page, any Redirects but NOT Redirect talk pages. I have to run a special Quarry query to find orphaned talk pages that weren't deleted by Twinkle. This
752:
I had figured it was a useful message if it was actually supposed to show up – not sure, though. Reading the code, I don't think someone's preferences being corrupted would cause this particular error to fire (the "Could not load" one), since it should only happen if the network request doesn't
715:
The way I (mostly) fixed this was to add a beforeunload listener which sets a flag, and test that flag before displaying the error message. There are a few scenarios where this won't work, because a couple browsers (iOS Safari appearing to be the biggest example) don't fire the event, and it is
731:
I've noticed this nuisance message too. Perhaps the best way to handle it would be to convert it to a console.log() instead. Even if this message is legit, for example a person's Twinkle preferences page became corrupted, it is hard to imagine that the user would want a mw.notify() about this
1410:
seems like an easy feature to add and, if it was a concern, exempt User talk pages from this operation. But I assume that I'm not the only admin who has brought this up here so you must have some explanation for why Twinkle doesn't do this. Thanks for any answers you can supply.
1359:
I saw "Refactoring other's talk page comments" and didn't know if striking the Keep was refactoring. Maybe I will use it next time, but maybe there won't be a next time, because I think that this is the first time I have seen that behavior, and it should be the last
148:, which is our todo list for volunteer developers. For most tickets, expect them to take a long time (months). They will need to attract the interest of a volunteer developer, then go through code review, then get merged to master, then get deployed. 1277:!vote, and the nominator struck out the bolded Keep with an explanation. My question is what Twinkle warning can or should I issue. I gave a Level 3 warning for Disruptive Editing, but I would have preferred to give something more specific. 1431:
articles. You can certainly mass-delete using d-batch, but tagging pages needs to be done on a per-page basis. Since Twinkle is semi-automated, it would be fairly easy to pull up a large list of pages and then tag them sequentially
976:
I followed the history of the line containing "has to be notified" in GitHub, and it goes back 14 years to the "initial import from Knowledge". So it has been this way for at least 14 years. So the "why" is probably lost to
580: 980:
Isn't BLPPROD intended to motivate the author to add sources within 1 week to avoid deletion? If I had to guess, that is probably the reason. Kind of hard to motivate the author of an article to act if they are not
609:)? I've been using "CSD G6 Housekeeping" as a deletion criteria for expired maintenance categories because I didn't see C4 on your list of options and I think this criteria would be more appropriate. Thank you. 872:
which displays the same template and has a description of "notability guideline for companies and organizations". However it wouldn't hurt to add it if it helps people find the correct entry. Ticket created.
1077:. Can you please provide an example diff of a correct Db-commons or Now Commons containing the date parameter, so I know how to format it? What date should it take, the date tagged or something else? – 524: 964:
notify a page creator is deactivated when applying a BLPPROD? I'm guessing it is because these are usually very new articles but I just ran across one where the creator is long-term inactive.
1143:
It took me some fiddling around, looking at other people's CSD logs to figure out that they're not manually added, but typically via Twinkle. That said, CSD logging is disabled by default in
1470:
for this once for batchdelete, but batchdelete is a lot of work to test, so I gave up on it. Maybe one day when I have more time I'll take another stab at it. No time this month though. –
696: 838: 666: 1310:
for more. Not sure if any more precise warning exists, but I think "Disruptive Editing" is very accurate if they remove an opposing !vote without a clear and valid reason.
1201:
This is easy to code, but could get some pushback once deployed. Hopefully some more talk page watchers can chime in with their thoughts before we commit to doing this. –
1335:
Warn, then clicking on the dropdown box with all the user warnings. There's a spot to search. I typed "talk", and if that didn't work, I was going to try searching for "
850: 826: 1222: 606: 1291:
More generally, if I would like to propose that a new Twinkle warning be added, is this the place to make the suggestion, or should I make it somewhere else?
1154:
manually or if it would be created automatically once setting is enabled. If automatic, are there any defaults, e.g archiving set up? Is there a good reason
551: 725: 984:
This is also related to the discussion of how much to notify blocked users, which has been discussed on this talk page a couple times this year. –
1307: 970: 641: 1300: 691: 99: 1286: 415: 411: 407: 403: 399: 64: 539:
When adding a "globalize" tag, I had the "use multiple issues box" checked. To my surprise, some section tags were moved to the top
1264: 999: 952: 1460:
While, when I delete a page, Twinkle will delete the Article, the Article talk page, any Redirects but NOT Redirect talk pages.
1375: 1354: 1102: 862: 792: 440: 436: 432: 428: 424: 105: 1319: 1167: 1158:
to make this a default setting with automatic creation the first time an editor nominates article for speedy deletion? ~ 🦝
453: 449: 194: 597: 1138: 687: 1216: 1058:
on a file's description page using Twinkle's file maintenance tagging module, which does pass the date as a parameter.)
767:
Sure, that's fine. I've updated the ticket to just change the load message to console.log() and not the parse message. –
1130: 1092: 942: 918: 888: 658: 1196: 782: 762: 747: 1240: 1067: 385: 381: 377: 373: 369: 365: 361: 357: 353: 349: 345: 341: 337: 333: 329: 325: 321: 317: 313: 309: 305: 301: 297: 293: 289: 285: 281: 277: 273: 269: 265: 261: 257: 253: 249: 245: 241: 237: 233: 17: 1144: 1182: 620: 540: 229: 225: 221: 217: 213: 209: 205: 201: 197: 1485: 1256: 1234: 1118: 45: 1406:
multiple notifications? I've been using Twinkle almost as long as I have been editing but this is news to me.
519: 1448: 1005: 635: 94: 1106: 968: 483: 420: 85: 445: 138: 849:
are the same notability guideline, but it means a bunch of non-company organizations have ended up in
1371: 1296: 1282: 662: 1480: 1349: 1211: 1098: 1087: 994: 965: 937: 883: 777: 742: 683: 592: 1151: 1436: 1435:
As a minor note, you don't need to do a Quarry search to find what links to a page, just use
1315: 1192: 1463: 1421: 1391: 1367: 1292: 1278: 1048: 1038: 1013: 800: 704: 564: 532: 501: 32: 508:
Please can you add {{Fringe theories}} to the standard installation for maintenance tags
8: 1467: 1324:
I'd use one of the Uw-tvp* templates. "Refactoring other's talk page comments". Example:
1252: 1163: 1028: 904: 896: 832: 820: 811: 75: 1471: 1444: 1402: 1340: 1202: 1178: 1126: 1078: 1063: 985: 928: 914: 874: 858: 768: 733: 674: 631: 588: 493: 90: 24: 954: 758: 721: 514: 71: 49: 605:
Could you add "C4. Unused maintenance categories" to your list of CSD criteria (see
583:, which I deleted under the old G8 not remembering that it had been changed to C4). 1328: 1311: 1230: 1188: 571:
Just noting that our language needs to be changed in the CSD reasons, the text for
165: 1363:
They didn't remove an opposing !vote. They struck it. The principle is the same.
1366:
The editor deleted my warning, so they saw it and have been warned. Thank you.
924: 842: 654: 643: 1248: 1159: 846: 547: 145: 462: 1440: 1336: 1270: 1174: 1173:
I would support opt-out rather than the current opt-in for CSD/PROD logging.
1122: 1074: 1059: 910: 854: 627: 584: 466: 181: 1439:. I do agree though that catching the talk page redirects would be useful. 1244: 1021: 754: 717: 576: 1226: 607:
Knowledge:Criteria for speedy deletion#C4. Unused maintenance categories
468: 909:
aren't just synonyms – they place the article in different categories.
893:
It's not just to help people find the correct entry. The issue is that
927:
combines the two. But anyway, sounds good. I've updated the ticket. –
923:
I guess the template that is visible to the user is the same because
556: 543: 1101:. Any reasonable date format should work, though, since it uses the 1412: 1383: 1306:
Twinkle only exposes some of the standard warnings available - see
611: 464: 697:
Error when navigating away from page very quickly after page load
1044:, which ideally should be given a date as parameter. (Note that 839:
Category:Organization articles with topics of unclear notability
1223:/Archive 47#csd/prod/xfd: turn on userspace logging by default 469: 960:
Just curious if anyone can direct to me to why the option to
573:
G8: Categories populated by a deleted or retargeted template
525:"One source|Section" tag moved to multiple issues box at top 1239:
I read the older discussion, but I am not persuaded by the
851:
Category:Company articles with topics of unclear notability
827:
Category:Company articles with topics of unclear notability
1187:
I concur, default on with opt-out makes more sense to me.
1113:
as two examples. As for which date to use: yes, it's the
1034:
is placed on the description page. This is a redirect to
128:
Tips for writing good bug reports and feature requests:
1456:
Post a diff and I can take a look at how they did this.
1454:
I see an admin somehow mass-tag pages with CSD notices.
175: 40: 144:We will use this information to create a ticket on 665:. You are invited to comment on the discussion at 671:on the Templates for discussion page. Thank you. 581:Category:Singapore political party logo templates 1115:date when the file was tagged with this template 1024:using Twinkle's dated speedy deletion module, 817:, Twinkle lets you select a subcategory, like 164:Twinkle has detailed documentation located at 477:This page has archives. Sections older than 131:Include the affected article name and a diff. 1308:Knowledge:Template index/User talk namespace 1150:It wasn't clear to me if I needed to create 626:Merged into previous section, same request. 16:"WT:TW" redirects here. For other uses, see 841:. I didn't notice this for a while, since 732:displayed every time they visit a page. – 1462:Yeap, this has had a ticket since 2021. 829:. However, the dropdown menu is missing 1119:Template:Now Commons/doc § TemplateData 542:. This seems to be unwanted behaviour. 487:when more than 10 sections are present. 1427:As far as I am aware, you cannot mass- 1145:Knowledge:Twinkle/Preferences § Speedy 141:the bug. Bugs need to be reproducible. 1265:Question About What Warning to Issue 153: 117: 1107:Template:Now Commons/doc § Detailed 48:for discussing improvements to the 13: 1334:. I found it by going to TW -: --> 793:Notability category: organizations 14: 1497: 1241:reasonable expectation of privacy 481:may be automatically archived by 1401:I'm hoping Twinkle experts like 1139:Default behaviour of CSD logging 649: 180: 157: 121: 65:Click here to start a new topic. 575:needs to be updated to the new 1486:18:05, 20 September 2024 (UTC) 1449:10:35, 20 September 2024 (UTC) 1422:02:37, 20 September 2024 (UTC) 1376:17:50, 20 September 2024 (UTC) 1355:21:17, 19 September 2024 (UTC) 1320:18:54, 19 September 2024 (UTC) 1301:18:50, 19 September 2024 (UTC) 1287:18:50, 19 September 2024 (UTC) 1257:10:23, 20 September 2024 (UTC) 1235:21:26, 19 September 2024 (UTC) 1217:21:15, 19 September 2024 (UTC) 1197:12:16, 19 September 2024 (UTC) 1183:18:35, 18 September 2024 (UTC) 1168:13:31, 18 September 2024 (UTC) 1: 1221:We've discussed this before: 1131:22:40, 6 September 2024 (UTC) 1111:2010-07-01 and 20100601023255 1093:22:25, 6 September 2024 (UTC) 1068:01:04, 6 September 2024 (UTC) 1000:23:21, 4 September 2024 (UTC) 971:22:44, 4 September 2024 (UTC) 943:00:16, 5 September 2024 (UTC) 919:23:15, 4 September 2024 (UTC) 889:22:57, 4 September 2024 (UTC) 863:22:37, 4 September 2024 (UTC) 783:00:15, 5 September 2024 (UTC) 763:23:04, 4 September 2024 (UTC) 748:22:45, 4 September 2024 (UTC) 726:21:22, 4 September 2024 (UTC) 692:09:05, 4 September 2024 (UTC) 636:00:16, 4 September 2024 (UTC) 621:20:31, 2 September 2024 (UTC) 598:Addition to CSD criteria list 62:Put new text under old text. 825:, which puts the article in 137:For bugs, include the exact 18:WikiProject Taiwan talk page 7: 1020:When deleting a file under 807:If you tag an article with 593:10:16, 30 August 2024 (UTC) 552:12:24, 29 August 2024 (UTC) 520:01:18, 27 August 2024 (UTC) 70:New to Knowledge? Welcome! 10: 1502: 1387: 1009: 1006:db-commons should be dated 953:Creator notification with 796: 700: 560: 528: 497: 22: 15: 869: 868:The dropdown already has 663:Template:Promotional tone 642:Nomination for merger of 100:Be welcoming to newcomers 1273:discussion, I entered a 870:{{notability|Companies}} 398:Friendly talk archives: 837:, which would populate 1152:User:Shushugah/CSD log 602:Hello, Twinkle folks, 484:Lowercase sigmabot III 95:avoid personal attacks 1437:Special:WhatLinksHere 1388:Tracked in github.com 1103:#time parser function 1099:here's one I just did 1010:Tracked in github.com 797:Tracked in github.com 701:Tracked in github.com 659:nominated for merging 561:Tracked in github.com 529:Tracked in github.com 498:Tracked in github.com 134:Include a screenshot. 668:the template's entry 1054:can also be placed 579:language (see e.g. 1398:Hello, Twinklers, 966:Just Step Sideways 139:steps to reproduce 106:dispute resolution 67: 1484: 1353: 1215: 1091: 998: 941: 887: 781: 746: 491: 490: 172: 171: 152: 151: 116: 115: 86:Assume good faith 63: 1493: 1478: 1476: 1420: 1394: 1347: 1345: 1333: 1327: 1209: 1207: 1085: 1083: 1053: 1047: 1043: 1037: 1033: 1027: 1016: 992: 990: 935: 933: 908: 907:|organizations}} 900: 881: 879: 871: 836: 835:|organizations}} 824: 816: 810: 803: 775: 773: 740: 738: 707: 690: 681: 677: 653: 652: 619: 567: 535: 517: 504: 486: 470: 184: 176: 161: 160: 154: 125: 124: 118: 41: 35: 1501: 1500: 1496: 1495: 1494: 1492: 1491: 1490: 1472: 1411: 1396: 1390: 1386: 1368:Robert McClenon 1341: 1331: 1325: 1293:Robert McClenon 1279:Robert McClenon 1267: 1247:deletion. ~ 🦝 1203: 1141: 1079: 1051: 1045: 1041: 1035: 1031: 1025: 1018: 1012: 1008: 986: 958: 929: 902: 894: 875: 830: 818: 814: 808: 805: 799: 795: 769: 734: 709: 703: 699: 679: 673: 672: 655:Template:Advert 650: 647: 644:Template:Advert 610: 600: 569: 563: 559: 537: 531: 527: 515: 506: 500: 496: 494:Fringe theories 482: 471: 465: 456: 443: 418: 396: 189: 158: 122: 112: 111: 81: 39: 38: 31: 27: 21: 12: 11: 5: 1499: 1489: 1488: 1457: 1451: 1433: 1395: 1389: 1385: 1382: 1381: 1380: 1379: 1378: 1364: 1361: 1322: 1266: 1263: 1262: 1261: 1260: 1259: 1219: 1199: 1185: 1140: 1137: 1136: 1135: 1134: 1133: 1017: 1011: 1007: 1004: 1003: 1002: 982: 978: 957: 951: 950: 949: 948: 947: 946: 945: 804: 798: 794: 791: 790: 789: 788: 787: 786: 785: 708: 702: 698: 695: 646: 640: 639: 638: 599: 596: 568: 562: 558: 555: 536: 530: 526: 523: 505: 499: 495: 492: 489: 488: 476: 473: 472: 467: 463: 461: 458: 457: 444: 419: 397: 394:Other archives 392: 389: 388: 356: 316: 276: 236: 191: 190: 185: 179: 170: 169: 162: 150: 149: 143: 142: 135: 132: 126: 114: 113: 110: 109: 102: 97: 88: 82: 80: 79: 68: 59: 58: 55: 54: 53: 37: 36: 28: 23: 9: 6: 4: 3: 2: 1498: 1487: 1482: 1477: 1475: 1474:Novem Linguae 1469: 1468:wrote a patch 1465: 1461: 1458: 1455: 1452: 1450: 1446: 1442: 1438: 1434: 1430: 1426: 1425: 1424: 1423: 1419: 1417: 1416: 1407: 1404: 1403:Novem Linguae 1399: 1393: 1377: 1373: 1369: 1365: 1362: 1358: 1357: 1356: 1351: 1346: 1344: 1343:Novem Linguae 1338: 1330: 1323: 1321: 1317: 1313: 1309: 1305: 1304: 1303: 1302: 1298: 1294: 1289: 1288: 1284: 1280: 1276: 1272: 1258: 1254: 1250: 1246: 1242: 1238: 1237: 1236: 1232: 1228: 1224: 1220: 1218: 1213: 1208: 1206: 1205:Novem Linguae 1200: 1198: 1194: 1190: 1186: 1184: 1180: 1176: 1172: 1171: 1170: 1169: 1165: 1161: 1157: 1153: 1148: 1146: 1132: 1128: 1124: 1120: 1116: 1112: 1108: 1104: 1100: 1096: 1095: 1094: 1089: 1084: 1082: 1081:Novem Linguae 1076: 1072: 1071: 1070: 1069: 1065: 1061: 1057: 1050: 1040: 1030: 1023: 1015: 1001: 996: 991: 989: 988:Novem Linguae 983: 979: 975: 974: 973: 972: 969: 967: 963: 956: 944: 939: 934: 932: 931:Novem Linguae 926: 922: 921: 920: 916: 912: 906: 898: 892: 891: 890: 885: 880: 878: 877:Novem Linguae 867: 866: 865: 864: 860: 856: 852: 848: 844: 840: 834: 828: 822: 813: 802: 784: 779: 774: 772: 771:Novem Linguae 766: 765: 764: 760: 756: 751: 750: 749: 744: 739: 737: 736:Novem Linguae 730: 729: 728: 727: 723: 719: 713: 706: 694: 693: 689: 685: 680:Pigsonthewing 676: 670: 669: 664: 660: 656: 645: 637: 633: 629: 625: 624: 623: 622: 618: 616: 615: 608: 603: 595: 594: 590: 586: 582: 578: 574: 566: 554: 553: 549: 545: 541: 534: 522: 521: 518: 512: 509: 503: 485: 480: 475: 474: 460: 459: 455: 451: 447: 442: 438: 434: 430: 426: 422: 421:Old Bugs page 417: 413: 409: 405: 401: 395: 391: 390: 387: 383: 379: 375: 371: 367: 363: 359: 355: 351: 347: 343: 339: 335: 331: 327: 323: 319: 315: 311: 307: 303: 299: 295: 291: 287: 283: 279: 275: 271: 267: 263: 259: 255: 251: 247: 243: 239: 235: 231: 227: 223: 219: 215: 211: 207: 203: 199: 196: 193: 192: 188: 183: 178: 177: 174: 167: 163: 156: 155: 147: 140: 136: 133: 130: 129: 127: 120: 119: 107: 103: 101: 98: 96: 92: 89: 87: 84: 83: 77: 73: 72:Learn to edit 69: 66: 61: 60: 57: 56: 51: 47: 43: 42: 34: 30: 29: 26: 19: 1473: 1459: 1453: 1428: 1414: 1413: 1408: 1400: 1397: 1342: 1290: 1274: 1268: 1204: 1155: 1149: 1142: 1114: 1110: 1080: 1055: 1019: 987: 961: 959: 930: 899:|companies}} 876: 823:|companies}} 806: 770: 735: 714: 710: 688:Andy's edits 684:Talk to Andy 675:Andy Mabbett 667: 648: 613: 612: 604: 601: 572: 570: 538: 516:Daisytheduck 513: 510: 507: 478: 446:Old RFA page 393: 186: 173: 44:This is the 1392:Issue #1382 1312:KylieTastic 1189:KylieTastic 1049:Now Commons 1039:Now Commons 1014:Issue #2011 801:Issue #1999 705:Issue #1998 565:Issue #1994 533:Issue #1997 502:Issue #1996 1251:(he/him • 1162:(he/him • 1029:db-commons 955:WP:BLPPROD 905:notability 897:notability 833:notability 821:notability 812:notability 448:; archive 423:; archive 1432:per-page. 1249:Shushugah 1160:Shushugah 981:notified. 657:has been 166:WP:TW/DOC 108:if needed 91:Be polite 46:talk page 1441:Primefac 1175:Primefac 1123:jlwoodwa 1075:Jlwoodwa 1060:jlwoodwa 1056:directly 977:history. 925:WP:NCORP 911:jlwoodwa 855:jlwoodwa 843:WP:NCORP 628:Primefac 585:Primefac 511:thanks, 187:Archives 76:get help 25:Shortcut 1466:I even 1464:Ticket. 1329:Uw-tpv3 847:WP:NORG 755:Tollens 718:Tollens 479:30 days 50:Twinkle 1269:In an 1227:Nardog 1109:gives 1097:Sure, 557:CSD C4 146:GitHub 1384:Query 1360:time. 1245:WP:U1 1022:WP:F8 661:with 577:WP:C4 195:Index 104:Seek 52:page. 33:WT:TW 1481:talk 1445:talk 1372:talk 1350:talk 1339:". – 1316:talk 1297:talk 1283:talk 1275:Keep 1253:talk 1231:talk 1212:talk 1193:talk 1179:talk 1164:talk 1127:talk 1088:talk 1064:talk 995:talk 938:talk 915:talk 901:and 884:talk 859:talk 845:and 778:talk 759:talk 743:talk 722:talk 632:talk 589:talk 548:talk 544:Fram 93:and 1429:tag 1337:tpo 1271:XFD 1156:not 1147:. 1121:). 962:not 682:); 1447:) 1418:iz 1374:) 1332:}} 1326:{{ 1318:) 1299:) 1285:) 1255:) 1233:) 1225:. 1195:) 1181:) 1166:) 1129:) 1105:. 1066:) 1052:}} 1046:{{ 1042:}} 1036:{{ 1032:}} 1026:{{ 917:) 903:{{ 895:{{ 861:) 853:. 831:{{ 819:{{ 815:}} 809:{{ 761:) 724:) 686:; 634:) 617:iz 591:) 550:) 452:, 439:, 435:, 431:, 427:, 414:, 410:, 406:, 402:, 386:48 384:, 382:47 380:, 378:46 376:, 374:45 372:, 370:44 368:, 366:43 364:, 362:42 360:, 358:41 354:40 352:, 350:39 348:, 346:38 344:, 342:37 340:, 338:36 336:, 334:35 332:, 330:34 328:, 326:33 324:, 322:32 320:, 318:31 314:30 312:, 310:29 308:, 306:28 304:, 302:27 300:, 298:26 296:, 294:25 292:, 290:24 288:, 286:23 284:, 282:22 280:, 278:21 274:20 272:, 270:19 268:, 266:18 264:, 262:17 260:, 258:16 256:, 254:15 252:, 250:14 248:, 246:13 244:, 242:12 240:, 238:11 234:10 232:, 228:, 224:, 220:, 216:, 212:, 208:, 204:, 200:, 74:; 1483:) 1479:( 1443:( 1415:L 1370:( 1352:) 1348:( 1314:( 1295:( 1281:( 1229:( 1214:) 1210:( 1191:( 1177:( 1125:( 1117:( 1090:) 1086:( 1073:@ 1062:( 997:) 993:( 940:) 936:( 913:( 886:) 882:( 873:– 857:( 780:) 776:( 757:( 745:) 741:( 720:( 678:( 630:( 614:L 587:( 546:( 454:2 450:1 441:5 437:4 433:3 429:2 425:1 416:5 412:4 408:3 404:2 400:1 230:9 226:8 222:7 218:6 214:5 210:4 206:3 202:2 198:1 168:. 78:. 20:.

Index

WikiProject Taiwan talk page
Shortcut
WT:TW
talk page
Twinkle
Click here to start a new topic.
Learn to edit
get help
Assume good faith
Be polite
avoid personal attacks
Be welcoming to newcomers
dispute resolution
steps to reproduce
GitHub
WP:TW/DOC

Index
1
2
3
4
5
6
7
8
9
10
11
12

Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.

↑