Low blood sugar? Too much Gawker?
Okay, maybe there was a reason...
The relationship between class and high level character concept isn't as clear cut as you're making it out to be, regardless of edition.
For example, a "holy warrior" could be cleric, or a fighter/cleric, too, A ranger could be anything from a hunter (as you say), to an archer or two-weapon fighter, to AD&D's heavily-armored tank with pets (and a fireball or two, if they're high enough level).
A cleric could be if he worshipped a god connected to warriors in some way but he could just as easily be a scholar if he worships Ioun, or a trickster if he worships Coyote. That said...
In all honesty I would, for the purposes of this discussion, refine the paladin archetype to be that of holy knight... since paladins (even in 4e) are suppose to be martial combatants imbued with divine power who hold themselves to higher ideals. So you are correct their archetype isn't holy warrior, while in a more general sense that probably is the archetype of the cleric where warrior is not taken literally but in a more spiritual sense.
Now, let's compare two examples of class descriptions from 4e...
The Ranger
...As a ranger, you possess almost supernaturally keen
senses and a deep appreciation for untamed wilderness.
With your knowledge of the natural world, you
are able to track enemies through nearly any landscape,
using the smallest clue to set your course, even
sometimes the calls and songs of beasts and birds.
Your severe demeanor promises a deadly conclusion to
any enemy you hunt.
The Fighter
Regardless of your level of skill and the specific
weapons you eventually master, your motivations
determine who you defend and who you slay. You
could be a noble champion who pledges your blade
to gallant causes, a calculating mercenary who cares
more for the clink of gold than praise, a homeless
prince on the run from assassins, or a blood-loving
thug looking for the next good fight.
Now, honestly... you don't see a difference in these two descriptions? Honestly? IMO, the fighter would seem to be a much broader archetype than the Ranger as presented here... and if I wasn't into the whole woodland and nature thing I wouldn't want to be a ranger just to be a competent or even good archer.
My answer is: most classes don't really have specific fiction attached to them (though a few come close, like the paladin and monk).
I think my example of the wizard and warlock as well as the ranger above show that at least in the more recent editions, this isn't true. There is an archetype very much implied in the narrative surrounding classes...
For example, in older editions like AD&D and 2e, the fighter class could represent anything from a knight to a highwayman to a dashing court swashbuckler. These are all very different roles in terms of the fiction, but modeled using the same class mechanics.
A highwayman is not an archetype, neither is a swashbuckler... they are more specific concepts of particular archetypes... Even the knight is not really an actual archetype because he's a specific concept (culturally based) within the warrior archetype.
I'm not really familiar with AD&D but I would assume this was because we had more general mechanics, but it's only a natural evolution that as the game mechanics (skills, kits, feats, abilities, etc.) used to represent specific concepts became more precise and less general... the classes that represent the archetypes would become less encompassing and more precise (sometimes bordering on concepts in and of themselves).
One AD&D example I am aware of is kits... you could only take certain kits if you were of a certain class... this definitely argues for classes representing more than just generic packages of abilities. These kits were a way of customizing a general archetype into a more specific concept under it and were rarely generic in their benefits.
In 3e, with it's more liberal multiclassing rules, it was common to have a single character archetype represented using a mixture of classes and PrC's. Frankly, it was the 3e framework that put the nail in the coffin of classes-as-archtypes, in favor of classes as packages of abilities which players combined to create their (potentially archetypal) characters.
I think you're talking about more specific concepts here as opposed to higher level archetypes. I would also argue that PrC's were in no way archetypical or intended to be but instead were suppose to be used by the DM to customize concepts that existed in his particular campaign.
I mean, the sheer (eventual) number of 3e classes/PrC's is a good indication they were no longer meant to represent a small number of universal archetypes.
I agree, they were created to represent more and more specific concepts of archetypes by giving you more specific mechanics as I said above... and this is even more apparent in things like PrC's, builds, backgrounds, etc. The classes however are still the overarching, high-level archetypes that your character is under.
In most cases, the designer's didn't. And sometimes they used multiple classes to model a single character -- consider the write-ups for some of the classic fantasy fiction heroes in the old Deities and Demigods; Conan, The Grey Mouser, et al.
A character is not an archetype... there is no Conan archetype, or Mouser archetype... what they are is a variation on a particular archetype... maybe even two or more archetypes combined... because the totality of a character does not equal archetype and I have never claimed it did.
I'd describe it as a militant religious order, and mention some of the abilities its noteworthy members are known to use.
Fair enough... though you originally claimed they were an order of paladins. If you did just that and I was in your camapign I would assume they were all paladins...
Just as a side note... you do realize in sourcebooks of nearly every edition they did exactly the opposite of this... there were actual orders of paladins, or rangers and characters had to be of that class to join.
Nope.
I think "avenger" sounds kinda dumb, while "paladin" is a lovely word. Ergo, I have no problem using "paladin" to refer a wide variety a holy wide variety of holy warriors, not just ones who have the exact abilities of the PHB class. And while I like the Avenger mechanics, I'm feel no obligation to use the term in the setting fiction and this hasn't caused any confusion in my group.
Uhmm, I was talking about on a meta game level. Earlier in your post you stated that they were an order of paladins you were renamming... well apparently if there are avengers this isn't true.
Back on the 2e era, you had the option to use specialty priests, which could have wildly divergent granted powers, spell lists, permissible arms and armors. Yet they were still all "priests".
I'm not sure what your point is here... you were free to create holy warriors of varying faiths, and like in the real world and literature, they had differing armaments, beliefs, knowledge, etc. You took an archetype (the holy warrior) and through customization made it a more specific concept.
In the 4e era, our campaign had a character who, mechanically, was a Dwarven Avenger. In the game fiction, he was a Communist revolutionary empowered by something called "dialectical materialism", and claimed his 'powers' where just reason cutting through the bogus, bourgeoisie delusions that permeated his world.
(I mention him to illustrate how a certain... flexibility with regard to tying the character fiction to actual mechanics can be useful. We'd still be waiting for WotC --or for that matter, anyone who wasn't us-- to publish an official philosophically-powered Communist revolutionary class).
I'm not sure what this has to do with our larger discussion. His concept apparently still used the holy assasin archetype... the trappings and specific concept still fit under that unbrella and then he refined his concept through selection of abilities and fictional trappings... what does this have to do with attaching combat role to the archetypes in the game?
Eventually. And it wasn't very good. And it certainly didn't stop 3e players from mixing other classes together in order to create an archetypal swashbuckler. For instance, dipping into Ranger for the two-weapon feats, or Rogue for Sneak Attack.
BTW... Monte did a much better job at a playable, single-classed swashbuckler with AE's Unfettered.
All of this is irrelevant, since the question was about how to represent a swashbuckler in 3.5... there was a swashbuckler class plain and simple. this is of course ignoring the fact that the swashbuckler isn't an archetype in and of itself either.
I'd say this analysis is simply wrong. In pre-3e D&D, you had single classes representing multiple character concepts --unless you'd like to claim that "knight", "pirate", and "swashbuckler" are the same fictional archetype-- and in 3e/Pathfinder, you frequently have multiple classes combined in service of a single concept/archetype. The most you can say is certain classes had more... expected fictions associated with them.
A character concept =/= archetype.
The tight correlation between metagame class and in-game fiction is something you're reading into the rules, not out of. Heck, the 2e class write-ups explicitly list several different kinds archetypal character each individual class can be used for. Both Conan and Hercules are fighters... do they strike you as the same guy, fiction-wise?
I've provided enough examples from the current edition that you're either willfully ignoring them or have made up your mind and are not open to the possibility... either way I'm not going to keep posting examples.
Again Conan and Hercules aren't the same guy but they fall under the warrior archetype (though some would argue Conan is mixture of the warrior and rogue archetype). You keep missing the fact that archetypes are not the sum of a character... they never have been they are the overarching umbrella(s) that characters fall under.
I'm not trying to critique preferences here, but your description of how D&D has functioned with regard to the relationship between class and concept throughout the editions is inaccurate.
No it's just not how you chose to look at it... and for some reason you assume that because you didn't look at it that way... it's not that way that anyone else ore even the majority of D&D players have or did. I honestly think you are wrong.