Knowledge

Template talk:Zeppelin aircraft

Source 📝

686:
exist for manufacturers, for designers (where they are well known, particularly if they changed companies many times), for design bureaus (which weren't just a Soviet thing), for operators (be they airlines or air forces), for military designations, or to group pages related to a single type of aircraft, and for other reasons where there is an obvious grouping. Links do not have to be limited to just official designations, but can include nicknames, names used by other operators, and common names, so there is no need to exclude your ZMe designation - it has been referenced somewhere, so we need a link to redirect the person looking for it to the right place, regardless of how "correct" you think it is. Take for example the Messerschmitt 108. Most references list it as a Bf 108, but the factory's own drawings used both Bf 108 and Me 108 - regardless of how official the latter was. If something was commonly (but specifically) referred to in a certain way there is no reason not to include that. A note can be added if it horrifies you too much.
231:& Voss beacuse Messerschmitt were so busy. There it was heavily redesigned, and redesignated the BV 155. It is always listed as the BV 155; the Me 155 is regarded as a different type. In the case of the Me 323 the same transfer to another company and subsequent design modifications occurred. However the modified design was not taken forwards to the prototype stage. Nevertheless the modifications were of Zeppelin design and the RLM treated the designation accordingly. By the time Zeppelin had iterated their changes to the 523, manufacture had shifted one again - to France - and the RLM designated it as ZSO (presumably for Zeppelin-Sud-Ouest). The RLM were not always wholly consistent between such edge cases, but there is certainly no question but that all three of these 682:
same navbox is seen on every page that it provides a link to. These have proven to be extremely useful and effective. They overlap the category system, however they are more flexible, as they can include red links to show pages that need to be written, along with alternate names and designations, and it is easier to write a single file linking all related types than it is to add each page to a category, and whose removal is impossible to track. There is more flexibility in displaying links as well and the code allows for the page being viewed to be marked in black with self referential links disabled if each page is linked directly, and not through a redirect.
143: 22: 53: 77: 87: 587:
designer, and if the manufacturer has its own navbox, then it is sometimes included there as well (especially if it was assigned a distinct designation). Soviet and some Eastern Bloc aircraft are really the only major exceptions, as they were usually designed by a design bureau but produced in state-owned factories. In those cases, only the designer has a navbox. -
700:
Well, to each their own, I suppose. In my education it is rude to answer a question of which one is not the adressee. No further comments from me, neither regarding manners nor regarding templates or other navboxes. I must thank you, though, for patiently trying to explain - but, as stated above, the
677:
html code. Others can be thousands of lines long and call on hundreds of templates, such as the convert template. It makes the page using the template easier to read as the code is hidden, and it makes updating code across many pages (such as if a link is added or changed, or a bug needs to be fixed)
329:
I can see the use and advantage of generic templates like "Family car" or perhaps even "UK family car"; but not of "UK family car with radial tires" or "Family car built 1974-1975". Given the very limited number of Zeppelin designs, I would favour the complete removal of this template. What we don't
751:
That's a very kind reply, much appreciated. Yes, cultural differences seem to play, and I can only regret that some people seem to take their own very personal set of rules of good behaviour to be universally applicable. If ever again I gather the interest, I will surely enter upon your invitation!
526:
The consensus is in favor of having a navbox for all aviation manufacturers/designers with more than a few aircraft as a way to link aircraft articles of the same manufacturer to each other. This template is one of the largest aviation navboxes on Knowledge, so if you don't think it has value, you
736:
Thank you for your gracious replies. I am sure you are smart enough to understand these complexities if you were offered properly structured explanation. I expect we probably do not fully understand your concerns either, so we must keep answering the wrong points. The cultural differences you note
681:
A navbox is a specific type of template that provides links a reader might want to follow, and superseded the "sequence" that was in the "see also" section, which still shows up as orphan code on old pages. Unlike "see also", a template enforces consistency, and errors are caught sooner, since the
230:
The fact that the RLM used the designation ZMe is conclusive that Zeppelin-Messerschmitt was an official name. An instructive parallel to this case occurs with the Me 155. Basically a high-altitide development of the Bf 109, it went through a couple of iterations before being transferred to Blohm
685:
Your argument about aviation companies seems to be pointless pedantry for the sake of an argument, and your comment about it not being addressed to a previous commentator was rude. All discussions on talk pages are open to ANYONE to comment, and you don't get to police who does. Navbox templates
678:
vastly easier, since only one change is needed, instead of hundreds or even millions. Any block of text or code used a lot can be made into a template - whether it is the code for a navbox, a quote, a banner, a bibliographical entry, or an especially long name. I've seen all of those, and more.
586:
definition of few (more than two or three). In the case of most western aviation companies, the designer is usually the manufacturer, so it is not worth differentiating the two. For cases where the designer differs from the manufacturer, the aircraft is usually included in the navbox of the
389:
And also, you might notice the difference between "aircraft manufacturer" and "aircraft designer". In today's North-America, the two go together one-to-one, as I understand; but even today they do not everywhere, and in earlier times the landscape had even more shades.
674:
A template is any block of text or code placed its own page so the code can be reused in many places without rewriting it each time. It can be as simple as some html code, such as the abbr template ({{abbr|acronym|fullname}}), which just calls the <abbr:
195:
My argument for inclusion is that the aircraft were assigned distinct "Zeppelin-Messerschmitt" designations by the RLM, which, to my knowledge, was not standard practice for simple license production. Although the ZMe 323 may not have been a Zeppelin
619:
Also "most western aviation companies" (whereas many contributors use "aviation company" to indicate air transport companies, not aircraft designers or builders) and "usually" sound like very much generalist, far too much so for an encyclopedia.
642:. A navbox is an example of a navigation template. But seriously, you are wasting your time with this argument: this navbox is here to stay, and just because you do not understand it is not going to change that. — Cheers, 527:
would need a very compelling argument to do away with it. Your personal opinion about its value is not a valid reason, since there are many who do see value in these types of navboxes and have established a consensus. -
737:
also cannot be helping. If you'd like some further discussion on anything, feel free to drop me a line on my talk page and I will do my best. But I will not be too surprised if you have better things to do. — Cheers,
187:
from the template with the edit summary "Not Zeppelin designs, company not mentioned in article" (it is mentioned in the article). I reverted the change, but TheLongTone reverted my reversion and left a
429:
No that is not what I stated. I questioned the added value of this particular one, not of the whole race. But it seems obvious I am not really understanding you - neither will I try any further.
235:
developments (and I have seen others referred to) were products of the Zeppelin-Werke design office and the RLM treated them accordingly. So should we. I do believe that in this case
498:
The arguments for this template are the same as for all the others. The idea that consensus might randomly back down for one manufacturer is not tenable. Time to move on. — Cheers,
556:. Already stepwise giving in, though, now mentioning "manufacturers/designers" even if not yet seeing the real difference, apparently. Also: did Messerschmitt design more than 386:
Excuse me, I do not want to be rude, but I do not care tuppence about "standard practice". I asked about "added value". If there's none - as I feel - away with it!
204:
for the RLM to assign it a new designation. As for the ZMe 423, the fact that there is no known "Me 423" means that it wouldn't make sense to include it in
176: 560:
aircraft? It is not a very clear guideline, but I do not think the Messerschmitt works ever came to a hundred, likely much less. How's that for
320: 801: 796: 761: 746: 667: 651: 521: 472:
As if I cared. Have it all your own way. Still, you have to explain about the added value, and why you are so keen if there is none.
357: 339: 715:
And please do not accuse me of pedantry. If I were on that hunt, I might question the use of "existance", but I didn't, and I don't.
365:
This is an aviation manufacturer navbox. It's standard practice to have a manufacturer navbox at the end of aircraft articles. -
507: 272: 724: 710: 811: 806: 629: 603: 573: 543: 481: 467: 438: 424: 399: 381: 695: 308: 294: 248: 405: 224: 326:
Admitting that I am not sure I understand the full relevance: do we really need this template? What is its added value?
268: 117: 344:
And, by the way, though again I am unsure of the relevance: the Me423 IS mentioned, though briefly, in our article
104:. If you would like to participate, please visit the project page, where you can join the project and see lists of 635: 205: 152: 99: 63: 58: 33: 189: 345: 184: 180: 170: 404:
If you feel we should get rid of aviation manufacturer navboxes altogether, you should bring it up at
757: 720: 706: 663: 625: 569: 517: 477: 434: 395: 353: 335: 105: 616:. And I keep on looking forward to the (usually much valued) response from the intended adressee. 264: 658:
Thanks, I did my best to understand but the matter is obviously above my intellectual capacity.
742: 647: 583: 503: 304: 244: 39: 192:
on my talk page. I don't want an edit war over a few links, so I'll seek a consensus here.
753: 731: 716: 702: 659: 621: 565: 513: 473: 430: 391: 362: 349: 331: 256: 8: 738: 691: 643: 639: 499: 300: 260: 240: 236: 142: 701:
whole thing is beyond me. The blame for that is entirely upon myself, of course.
111: 92: 594: 534: 458: 448: 415: 372: 285: 215: 790: 582:
a navbox. Also, in the case of aviation navboxes, a "few" usually means the
444: 408:, not here. This is a discussion about the contents of a specific navbox. - 687: 588: 528: 452: 409: 366: 279: 209: 76: 52: 608:
Right so far: I do not understand the difference between a
552:, I was questioning (the existence of one particular) 82: 564:? Besides, the question was not addressed at you. 512:Sorry, this is not clear to me. Kindly elaborate? 788: 634:To understand the difference, see for example 299:I do my very best to choose interesting words! 578:I don't think you understand, this template 98:This template is within the scope of the 32:does not require a rating on Knowledge's 443:If that's the case, then you might try 789: 116:. To use this banner, please see the 21: 19: 447:. I'm almost positive it will be a 200:, it was still enough of a Zeppelin 15: 406:Knowledge talk:WikiProject Aviation 38:It is of interest to the following 13: 278:An interesting choice of words. - 141: 14: 823: 802:Template-Class aircraft articles 797:Template-Class aviation articles 85: 75: 51: 20: 636:Help:A quick guide to templates 206:Template:Messerschmitt aircraft 190:rather confrontational message 150:This template is supported by 126:Knowledge:WikiProject Aviation 1: 812:WikiProject Aviation articles 807:WikiProject Aircraft articles 762:15:28, 16 February 2023 (UTC) 747:15:02, 16 February 2023 (UTC) 725:14:25, 16 February 2023 (UTC) 711:12:38, 16 February 2023 (UTC) 696:09:26, 16 February 2023 (UTC) 668:12:38, 16 February 2023 (UTC) 652:20:21, 15 February 2023 (UTC) 630:18:26, 15 February 2023 (UTC) 604:18:19, 15 February 2023 (UTC) 574:18:04, 15 February 2023 (UTC) 544:17:53, 15 February 2023 (UTC) 522:17:18, 15 February 2023 (UTC) 508:16:53, 15 February 2023 (UTC) 482:16:49, 15 February 2023 (UTC) 468:16:35, 15 February 2023 (UTC) 439:16:28, 15 February 2023 (UTC) 425:16:17, 15 February 2023 (UTC) 400:16:06, 15 February 2023 (UTC) 382:16:01, 15 February 2023 (UTC) 358:15:53, 15 February 2023 (UTC) 340:15:50, 15 February 2023 (UTC) 309:14:31, 22 February 2023 (UTC) 295:18:23, 20 February 2023 (UTC) 273:13:59, 20 February 2023 (UTC) 253:I bow to superior knowledge! 249:16:53, 15 February 2023 (UTC) 225:17:30, 14 February 2023 (UTC) 129:Template:WikiProject Aviation 548:But I was not questioning a 7: 346:Messerschmitt_Me_323_Gigant 10: 828: 321:Existance of this template 208:but not this template. - 149: 70: 46: 239:has it wrong. — Cheers, 330:have cannot divide us. 146: 175:TheLongTone recently 145: 153:the aircraft project 101:Aviation WikiProject 147: 34:content assessment 275: 259:comment added by 168: 167: 164: 163: 160: 159: 132:aviation articles 118:full instructions 819: 735: 602: 597: 591: 542: 537: 531: 466: 461: 455: 451:keep, though. - 423: 418: 412: 380: 375: 369: 293: 288: 282: 254: 223: 218: 212: 134: 133: 130: 127: 124: 95: 90: 89: 88: 79: 72: 71: 66: 55: 48: 47: 25: 24: 23: 16: 827: 826: 822: 821: 820: 818: 817: 816: 787: 786: 754:Jan olieslagers 732:Jan olieslagers 729: 717:Jan olieslagers 703:Jan olieslagers 660:Jan olieslagers 622:Jan olieslagers 600: 599: 595: 589: 566:Jan olieslagers 540: 539: 535: 529: 514:Jan olieslagers 474:Jan olieslagers 464: 463: 459: 453: 431:Jan olieslagers 421: 420: 416: 410: 392:Jan olieslagers 378: 377: 373: 367: 363:Jan olieslagers 350:Jan olieslagers 332:Jan olieslagers 323: 291: 290: 286: 280: 221: 220: 216: 210: 173: 131: 128: 125: 122: 121: 93:Aviation portal 91: 86: 84: 61: 12: 11: 5: 825: 815: 814: 809: 804: 799: 785: 784: 783: 782: 781: 780: 779: 778: 777: 776: 775: 774: 773: 772: 771: 770: 769: 768: 767: 766: 765: 764: 713: 683: 679: 676:</abbr: --> 672: 671: 670: 617: 593: 584:WP:COMMONSENSE 533: 496: 495: 494: 493: 492: 491: 490: 489: 488: 487: 486: 485: 484: 457: 414: 387: 371: 342: 327: 322: 319: 318: 317: 316: 315: 314: 313: 312: 311: 284: 214: 172: 171:"ZMe" aircraft 169: 166: 165: 162: 161: 158: 157: 148: 138: 137: 135: 97: 96: 80: 68: 67: 56: 44: 43: 37: 26: 9: 6: 4: 3: 2: 824: 813: 810: 808: 805: 803: 800: 798: 795: 794: 792: 763: 759: 755: 750: 749: 748: 744: 740: 733: 728: 727: 726: 722: 718: 714: 712: 708: 704: 699: 698: 697: 693: 689: 684: 680: 673: 669: 665: 661: 657: 656: 655: 654: 653: 649: 645: 641: 637: 633: 632: 631: 627: 623: 618: 615: 611: 607: 606: 605: 598: 592: 585: 581: 577: 576: 575: 571: 567: 563: 559: 555: 551: 547: 546: 545: 538: 532: 525: 524: 523: 519: 515: 511: 510: 509: 505: 501: 497: 483: 479: 475: 471: 470: 469: 462: 456: 450: 446: 442: 441: 440: 436: 432: 428: 427: 426: 419: 413: 407: 403: 402: 401: 397: 393: 388: 385: 384: 383: 376: 370: 364: 361: 360: 359: 355: 351: 347: 343: 341: 337: 333: 328: 325: 324: 310: 306: 302: 298: 297: 296: 289: 283: 277: 276: 274: 270: 266: 262: 258: 252: 251: 250: 246: 242: 238: 234: 229: 228: 227: 226: 219: 213: 207: 203: 199: 193: 191: 186: 182: 178: 155: 154: 144: 140: 139: 136: 119: 115: 114: 109: 108: 103: 102: 94: 83: 81: 78: 74: 73: 69: 65: 60: 57: 54: 50: 49: 45: 41: 35: 31: 27: 18: 17: 613: 609: 579: 561: 557: 553: 549: 255:— Preceding 232: 201: 197: 194: 174: 151: 112: 106: 100: 40:WikiProjects 29: 739:Steelpillow 644:Steelpillow 500:Steelpillow 301:TheLongTone 261:TheLongTone 241:Steelpillow 237:TheLongTone 113:task forces 791:Categories 107:open tasks 640:WP:Navbox 688:- NiD.29 614:template 554:template 269:contribs 257:unsigned 202:aircraft 123:Aviation 64:Aircraft 59:Aviation 30:template 449:WP:SNOW 185:ZMe 423 181:ZMe 323 177:removed 752:Best, 612:and a 610:navbox 550:navbox 445:WP:TFD 233:Gigant 198:design 36:scale. 562:a few 558:a few 28:This 758:talk 743:Talk 721:talk 707:talk 692:talk 664:talk 648:Talk 638:and 626:talk 590:ZLEA 570:talk 530:ZLEA 518:talk 504:Talk 478:talk 454:ZLEA 435:talk 411:ZLEA 396:talk 368:ZLEA 354:talk 336:talk 305:talk 281:ZLEA 265:talk 245:Talk 211:ZLEA 183:and 179:the 110:and 675:--> 793:: 760:) 745:) 723:) 709:) 694:) 666:) 650:) 628:) 580:is 572:) 520:) 506:) 480:) 437:) 398:) 356:) 338:) 307:) 271:) 267:• 247:) 62:: 756:( 741:( 734:: 730:@ 719:( 705:( 690:( 662:( 646:( 624:( 601:\ 596:T 568:( 541:\ 536:T 516:( 502:( 476:( 465:\ 460:T 433:( 422:\ 417:T 394:( 379:\ 374:T 352:( 348:. 334:( 303:( 292:\ 287:T 263:( 243:( 222:\ 217:T 156:. 120:. 42::

Index

content assessment
WikiProjects
WikiProject icon
Aviation
Aircraft
WikiProject icon
Aviation portal
Aviation WikiProject
open tasks
task forces
full instructions
Taskforce icon
the aircraft project
removed
ZMe 323
ZMe 423
rather confrontational message
Template:Messerschmitt aircraft
ZLEA
T
17:30, 14 February 2023 (UTC)
TheLongTone
Steelpillow
Talk
16:53, 15 February 2023 (UTC)
unsigned
TheLongTone
talk
contribs
13:59, 20 February 2023 (UTC)

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