text:
Jovian Chronicles

Jovian Chronicles is a science fiction game setting published by Dream Pod 9 since 1997. It introduces a complete universe for role-playing and wargaming space combat featuring mecha, giant spacecraft, and epic space battles.

The Jovian Chronicles setting was originally published as a pair of licensed supplements for the Mekton role-playing game; Ianus Publications released two volumes—Jovian Chronicles and Europa Incident—in 1992. This first edition is known amongst fans as the "Green Edition" because of the color scheme of its cover design.

After Ianus decided to split into two ventures in 1995 — Protoculture, which would publish Protoculture Addicts magazine; and Dream Pod 9, which would design and market miniatures and gaming books, Jovian Chronicles was re-published as a full-fledged game line in 1997 by Dream Pod 9, this time using their own in-house rule system. This edition, because of its white cover, is known as the "White Edition", and subsequent supplements are also called this, even though several of the supplemental books feature a dark blue starfield cover.

Publication history
Ianus Publications had licensed the anime-related games of R. Talsorian Games, and Jovian Chronicles (1994) by Marc A. Vezina featured an original campaign setting for the Mekton role-playing game from R. Talsorian. Vezina had intended Jovian Chronicles to be published as a serial in the company's Mecha Press magazine. Jovian Chronicles was instead published as a standalone setting and supplemented soon after with Europa Incident (1994). Dream Pod 9 was soon split out from Ianus as a separate company, and their second game after Heavy Gear was Jovian Chronicles (1998), a game based on Dream Pod 9's Silhouette system, and a variant of the setting they previously published for Mekton. The new edition changed the theme to encompass an anime mecha game, a space-opera starfighter game, as well a near-future game using hard science. Many of the mecha were redesigned to accommodate a video game that would have been released by Activision but was never published.

The later Silhouette CORE Rulebook (2003) offered a new standalone version of Silhouette that turned it into a generic system, and was immediately followed by the Mecha Companion (2003), which offered d20 stats for all the mecha from Heavy Gear, Jovian Chronicles and Gear Krieg using Guardians of Order's d20 Mecha (2003) mech description rules. Jovian Chronicles second edition was also released in 2003.

In 2017, Dream Pod 9 launched a Kickstarter to create new resin spaceship miniatures. The goal was to raise 9,000 CAD; with the support of 143 backers, they raised a total of 25,090 CAD. Dream Pod 9 reported that by November 2017 they had "completed the shipping of Backer Reward Packages". In 2018, they launched a second Kickstarter to create additional new spaceships and exo-armor squad miniatures. The goal was smaller this time (4,000 CAD) and while it was successful, it was less successful than the first Kickstarter (57 backers raising 8,708 CAD). Dream Pod 9 reported that they had begun shipping out "Backer Reward Packages" in April 2019. During this time, Beta Playtest Rules for a new edition, called Jovian Wars, were released for free on DrivethruRPG as a PDF. These rules were last updated on February 14, 2018.

Setting
The game world shows one possible future, a time in which Mankind has expanded and settled the Solar System, going as far as terraforming Venus and Mars. The colonists living around Jupiter are at odds with the government of Earth, driving much of the series' intrigue. The game features a blend of action/adventure and hard-science space colonization facts. The books are based on plausible technical details to maintain a realistic hard science fiction setting.

 * Mercury: a small settlement, whose main exports are high quality electronics and metals. Mercury is the headquarters of the powerful Merchant Guild, an association of companies which provide most of the transportation throughout the system.
 * Venus: terraformed by a consortium of corporations, Venus is now a marginally habitable planet. The Venusian upper class and their workers live in polar arcologies, surrounded by terraforming processors.
 * Earth: damaged by centuries of overpopulation and civil wars, the motherworld is home to the Central Earth Government and Administration (CEGA), a bureaucratic planetary government that believes the Earth should lead the solar system.
 * Orbital Colonies: the salvation of many who fled Earth, these are huge O'Neill stations parked at the Lagrange points. Orbitals are peaceful people who follow CEGA's lead for protection.
 * United Solar Nations: evolved from the old United Nations to provide a neutral arbiter between the various settlements. It has a private peace-keeping army, the USN Guard, and an interplanetary law enforcement agency, the Solar Police (SolaPol).
 * The Moon: CEGA's industrial center, its inhabitants are living in huge complexes buried beneath the soil. Many of Earth's heavy industries were moved there long ago.
 * Mars: a divided planet, home to the Martian Free Republic and the Martian Federation. Border clashes between the two are frequent.
 * The Belt: the asteroids are populated by mobile nomad communities, each a micro-society of its own.
 * Jupiter: home to refugees from Earth. The enormous space stations of the Jovian Confederacy were the first to develop and field exo-armors. Thanks to the resources of the Jovian sub-system, the Confederacy is the richest nation in the solar system.
 * Titan: the largest moon of Saturn is the farthest human settlement. It is the main source for complex hydrocarbon compounds and plays an important role in the industries of the solar system.

Anime inspirations
Many recent Western cartoon shows and games have Japanese anime styling. Jovian Chronicles also features anime-inspired artwork and narrative elements, though the various technical elements (ships, stations, equipment, etc.) are original works illustrated with computer art.

Exo-armors are one of the main hooks of the series, these one-crew mecha consist of big armored space suits talling 15 metres or more with weapons capable of devastating even small warships. The main source of inspiration for the game was the various iterations of the Gundam Universal Century series up to the early 1990s, with strong influence from Gundam 0083 Stardust Memories and Gundam 0080 War in the Pocket. Hints of other influences such as Patlabor and to some extent, Macross and Mospeada, are present, although no transformable mecha appear to date. Jovian Chronicles can be placed in the Real Robot anime genre.

The series art and mechanical designs were created by John Moscato and Ghislain Barbe, the latter who was also responsible for the artistic style which characterized all of the Dream Pod 9's lines including Heavy Gear and Tribe 8.

Game rules
The concept has its origins on a campaign played by the authors Mark A. Vezina and Etienne Gagnon since 1987, using R. Talsorian's Mekton system. After 5 years of development, IANVS publications licensed the Mekton II rules and published the Jovian Chronicles Campaign Setting, a 112-page letter sized book which describes the JC universe, timeline, technologies and introduces players to the setting thru a 12 episode campaign. The JC campaign works as an extension of the Mekton rules set, with minimum changes required and then only for character status and wealth, however, compared to other Mecha depicted in Mekton, JC Exo-armors tend to be less resilient and their weapons are less powerful. It is also of note that at this stage, Exos tend to be more balanced with little differences among them, while on later editions, grunt exos are intentionally inferior to hero machines, for example, a CEGA Syreen and a JC Pathfinder are equally balanced in power, armor and weapons, and similar in capabilities to larger machines.

Mecha designs also vary on this edition, being more complex and elaborated in design than on latter iterations, during this release, there were also a number of metal miniatures for six of the exo-armors in the setting, these were produced by Canadian manufacturer RAFM and were based on the campaign book technical designs by John Moscato. Miniatures were in 1/325 scale due to the fictional size of the exo-armors and presented one of the finest and most dynamic mecha sculptings of the era.

The second release of Jovian Chronicles, was the first one published by DP9, adapts the Silhouette game system, a streamlined set of rules already tested and proved in Heavy Gear, Dream Pod 9's other successful science fiction game. It can be played as either a role-playing game, a tactical wargame, or an integration of both. There are major changes on this release, such as the aforementioned distinction among the different exo-armors and other equipment as well as the focus on the character creation.

Both the RPG and miniature games are built on the same basic rule mechanics. Silhouette which defines characters in terms of 10 base attributes (agility, knowledge, etc.), 5 derived attributes (health, etc.), and a variety of skills. Skill rolls make up the backbone of the system, which focuses on effect-based speed of play over grainy detail. The core mechanic involves rolling a number of 6-sided dice, taking the highest result, adding in modifiers for attributes and/or situation, and then comparing it to a set threshold number. If the result is higher than the threshold the test is a success; if it is lower the test is a failure. The margin by which the test succeeded (Margin of Success, MoS) or failed (Margin of Failure, MoF) helps to determine the outcome. Combat is handled by the same system, with characters taking penalty-inflicting wounds rather than depleting a set number of health points. As a result, the system can be lethal, especially on inexperienced characters.

New miniatures were also released for this edition, for both, exo-armor/fighters as well as spaceships. The new line of miniatures covered a much broader range of subjects, at the expense of size, being scaled at 1/500 for the exo armor/fighters which were near half the size of the original ones, this edition also marks the appearance of spaceship miniatures, which were scaled to 1/5000.

During this stage, the game system was splintered into the Silhouette Core RPG rules and the Lightning Strike system for tactical scenarios. The latter, is a more abstract version of the original tactical system which allow for combined arms maneuvers.

A third edition Jovian Wars was put on kickstarter during March–April 2017 and is in the process of delivering to its backers, the new edition is a fleet scale tactical game, whose rules are distributed for free at the DP9 website and changes (again) the scale of the miniatures to 1/1000 to exo-armors and fighters and 1/4000 for the spaceships.

This change in scale intends to represent more realistically the magnitude of the conflicts depicted, making combat units smaller and warships larger. It features a new turning template for ship maneuvers which is promoted as the major innovation in the system and due to the scale of the exo-armors, they now operate in squadrons of 3 miniatures each. With the new scale, each exo/fighter is around 15mm in height, compared to 30mm for Lightning strike minis and an average of 54mm for RAFM miniatures. The RPG aspect of the game is all but left aside.

The project was funded, however it is uncertain if besides backers, other potential or new players will accept the scale change which has turned the exo-armors, an emblematic symbol of the series and marketing hook (first edition depicted a full page illustration of a Jovian Exo-armor on cover which was also used on the RAFM blister's card) into a sort of battle counter (size matters... sometime), rather focusing on ship to ship maneuvers.

IANUS Games (Mekton Supplements)

 * IMP-01: Jovian Chronicles: Campagne (January 1993).
 * IMP-02: Europa Incident: Campagne (January 1995).

Dream Pod 9

 * DP9-PJC: Jovian Chronicles - Promotional Poster(2002).
 * DP9-300: Jovian Chronicles - Lightning Strike Demo Game (2002).
 * DP9-301: Rules & Background for Jovian Chronicles - Enter the Saga of Mankind (June 1997).
 * DP9-302: Companion to Jovian Chronicles - Advanced Rules & Background(October 1997).
 * DP9-303: Mechanical Catalog - Exo-Armors & Spacecraft (July 1997).
 * DP9-304: Chaos Principle - Original Cinematic Adventure (April 1998).
 * DP9-305: Game Aid for Jovian Chronicles - Gamemastering Made Easy (April 1998).
 * DP9-306: Ships of the Fleet - Volume 1: Jovian Confederation (November 1998).
 * DP9-307: Spacer's Guide - A Guide to Life in the Twenty-third Century (May 2001).
 * DP9-308: Solapol - Sourcebook (May 1999).
 * DP9-309: Ships of the Fleet - Volume 3: CEGA Navy (November 1999).
 * DP9-310: Earth - Planet Sourcebook (June 2000).
 * DP9-311: Mechanical Catalog Two - Civilian Equipment & Spacecraft (August 2000).
 * DP9-312: Jovian Fleet - Blueprint File(1998).
 * DP9-313: Ships of the Fleet - Volume 2: Jovian Confederation (February 1999).
 * DP9-314: Lightning Strike - Fleet Combat Rules(1999).
 * DP9-315: CEGA Fleet - Blueprint File (1999).
 * DP9-316: Lightning Strike - Behind the Veil: Venus (1999).
 * DP9-317: Jupiter - Planet Sourcebook (February 2000).
 * DP9-318: Lightning Strike - Call to Arms (1999).
 * DP9-319: Ships of the Fleet - Volume 4: Venus (May 2000).
 * DP9-320: Shadow of CEGA - Planet Sourcebook (March 2001).
 * DP9-321: Space Equipment Handbook - Advanced Tools & Weapons (December 2000).
 * DP9-322: Lightning Strike - Second Edition (2000).
 * DP9-323: Nomads - Planet Sourcebook (July 2001).
 * DP9-324: Lightning Strike - Companion
 * DP9-325: Mercury - Planet Sourcebook (January 2002).
 * DP9-326: Venus - Planet Sourcebook (May 2002).
 * DP9-327: Mars - Planet Sourcebook (August 2002).
 * DP9-328: Cislunar Space - Planet Sourcebook (Mars 2003).
 * DP9-920: Jovian Chronicles Second Edition - RPG Player's Handbook (July 2003).

Reception
In September 1994, White Wolf gave the game a 3.5 out of 5 rating and said the game "offers a lot of material in a beautiful package".

Jovian Chronicles was featured on the front cover of the March–April 1997 edition of Pyramid (Vol. 1, Issue 24), and a sneak preview of the game was offered inside the same issue.

In the February 1998 edition of Dragon (Issue 244), Rick Swan reviewed both the Jovian Chronicles setting and the Heavy Gear setting (also published by Dream Pod 9), and praised the high production values: "Both are beautiful games, into which a lot of effort has been invested." Swan admired the "Silhouette" game system, calling it "the smartest set of universal rules this side of the GURPS game." But he criticized the combat rules, which he called "more work than fun", and he found little to be excited about in the setting, saying, "There's nothing terribly interesting going on here, and the game's ambitions seem awfully modest compared to the wide screen spectacle of Trinity." Given the setting's emphasis on robot combat, Swan believed that "Jovian Chronicles aims at players more interested in hardware than human beings." He concluded with an ambivalent shrug: "Other than the lifeless settings, I couldn’t find anything seriously wrong with... Jovian Chronicles. But I couldn’t find much to be excited about either."

A review of the Ship of the Fleet, Vol. 4 — a supplement describing six Venusian ships of the Jovian Chronicles line — that appeared in the August 11, 2000 issue of Pyramid found the supplement had failed in the small details that other works by Dream Pod 9 had possessed, saying "Being truly excellent is a double-edged sword: On the one hand, of course, you're excellent -- and that comes with a lot of perks. On the other hand, though, you have set yourself a very high standard indeed -- and a failure in the details suddenly becomes a notable offense."

Reviews

 * Mecha Press #10 (Nov./Dec. 1993)
 * Alarums & Excursions #313 (Sept. 2001)
 * Pyramid Volume 1 Issue #24 (March/April 1997)
 * Backstab #6
 * Casus Belli #109

title: Jovian Chronicles


text:
Wikipedia talk:Articles for deletion/Grae Phillips

I dont know, I love her. drag queens can be such bitches.

license: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/4.0/


text: User talk:61.59.190.12

title: User talk:61.59.190.12


text:
Chavannes-le-Veyron

Chavannes-le-Veyron is a municipality in the district of Morges in the canton of Vaud in Switzerland.

History
Chavannes-le-Veyron is first mentioned in 1285.

Geography
Chavannes-le-Veyron has an area,, of 2.63 km2. Of this area, 1.81 km2 or 68.8% is used for agricultural purposes, while 0.68 km2 or 25.9% is forested. Of the rest of the land, 0.16 km2 or 6.1% is settled (buildings or roads), 0.01 km2 or 0.4% is either rivers or lakes.

Of the built up area, housing and buildings made up 2.7% and transportation infrastructure made up 3.4%. Out of the forested land, all of the forested land area is covered with heavy forests. Of the agricultural land, 52.5% is used for growing crops and 14.4% is pastures, while 1.9% is used for orchards or vine crops. All the water in the municipality is flowing water.

The municipality was part of the Cossonay District until it was dissolved on 31 August 2006, and Chavannes-le-Veyron became part of the new district of Morges.

The municipality is located in the heights above the Veyron river (a tributary of the Venoge river).

Coat of arms
The blazon of the municipal coat of arms is Azure, on a Bend wavy Argent three Minnows fesswise Or. The minnows (vairon) may be a canting reference to name of the river Veyron.

Demographics
Chavannes-le-Veyron has a population of. , 4.9% of the population are resident foreign nationals. Over the last 10 years (1999–2009 ) the population has changed at a rate of -12.1%. It has changed at a rate of -14.4% due to migration and at a rate of 2.3% due to births and deaths.

Most of the population speaks French (117 or 93.6%), with German being second most common (5 or 4.0%) and Portuguese being third (2 or 1.6%).

Of the population in the municipality 49 or about 39.2% were born in Chavannes-le-Veyron and lived there in 2000. There were 46 or 36.8% who were born in the same canton, while 13 or 10.4% were born somewhere else in Switzerland, and 17 or 13.6% were born outside of Switzerland.

In there was 1 live birth to Swiss citizens and 1 death of a Swiss citizen. Ignoring immigration and emigration, the population of Swiss citizens remained the same while the foreign population remained the same. The total Swiss population change in 2008 (from all sources, including moves across municipal borders) was an increase of 4 and the non-Swiss population increased by 1 people. This represents a population growth rate of 4.2%.

The age distribution,, in Chavannes-le-Veyron is; 13 children or 11.2% of the population are between 0 and 9 years old and 14 teenagers or 12.1% are between 10 and 19. Of the adult population, 12 people or 10.3% of the population are between 20 and 29 years old. 12 people or 10.3% are between 30 and 39, 21 people or 18.1% are between 40 and 49, and 19 people or 16.4% are between 50 and 59. The senior population distribution is 19 people or 16.4% of the population are between 60 and 69 years old, 3 people or 2.6% are between 70 and 79, there are 3 people or 2.6% who are between 80 and 89.

, there were 54 people who were single and never married in the municipality. There were 57 married individuals, 3 widows or widowers and 11 individuals who are divorced.

, there were 44 private households in the municipality, and an average of 2.8 persons per household. There were 7 households that consist of only one person and 8 households with five or more people. Out of a total of 44 households that answered this question, 15.9% were households made up of just one person. Of the rest of the households, there are 14 married couples without children, 20 married couples with children There were 2 single parents with a child or children. There was 1 household that was made up of unrelated people.

there were 15 single family homes (or 51.7% of the total) out of a total of 29 inhabited buildings. There were 4 multi-family buildings (13.8%), along with 9 multi-purpose buildings that were mostly used for housing (31.0%) and 1 other use buildings (commercial or industrial) that also had some housing (3.4%). Of the single family homes 7 were built before 1919, while 1 was built between 1990 and 2000. The most multi-family homes (3) were built before 1919 and the next most (1) were built between 1919 and 1945.

there were 43 apartments in the municipality. The most common apartment size was 4 rooms of which there were 13. There were 1 single room apartments and 20 apartments with five or more rooms. Of these apartments, a total of 42 apartments (97.7% of the total) were permanently occupied, while 1 apartment was seasonally occupied. , the construction rate of new housing units was 0 new units per 1000 residents. The vacancy rate for the municipality,, was 4.65%.

The historical population is given in the following chart:

Heritage sites of national significance
The sawmill Scierie is listed as a Swiss heritage site of national significance.

Politics
In the 2007 federal election the most popular party was the SVP which received 32.59% of the vote. The next three most popular parties were the SP (29%), the FDP (10.53%) and the Other (9.42%). In the federal election, a total of 48 votes were cast, and the voter turnout was 54.5%.

Economy
, Chavannes-le-Veyron had an unemployment rate of 0.2%. , there were 19 people employed in the primary economic sector and about 7 businesses involved in this sector. 1 person was employed in the secondary sector and there was 1 business in this sector. 8 people were employed in the tertiary sector, with 4 businesses in this sector. There were 72 residents of the municipality who were employed in some capacity, of which females made up 44.4% of the workforce.

the total number of full-time equivalent jobs was 21. The number of jobs in the primary sector was 14, all of which were in agriculture. The number of jobs in the secondary sector was 1, in construction. The number of jobs in the tertiary sector was 6. In the tertiary sector; 2 or 33.3% were in wholesale or retail sales or the repair of motor vehicles, 2 or 33.3% were technical professionals or scientists and 1 was in education.

, there were 3 workers who commuted into the municipality and 45 workers who commuted away. The municipality is a net exporter of workers, with about 15.0 workers leaving the municipality for every one entering. Of the working population, 4.2% used public transportation to get to work, and 58.3% used a private car.

Religion
From the, 24 or 19.2% were Roman Catholic, while 74 or 59.2% belonged to the Swiss Reformed Church. Of the rest of the population, there were 9 individuals (or about 7.20% of the population) who belonged to another Christian church. There were 2 individuals who belonged to another church. 13 (or about 10.40% of the population) belonged to no church, are agnostic or atheist, and 3 individuals (or about 2.40% of the population) did not answer the question.

Education
In Chavannes-le-Veyron about 52 or (41.6%) of the population have completed non-mandatory upper secondary education, and 19 or (15.2%) have completed additional higher education (either university or a Fachhochschule). Of the 19 who completed tertiary schooling, 47.4% were Swiss men, 36.8% were Swiss women.

In the 2009/2010 school year there were a total of 11 students in the Chavannes-le-Veyron school district. In the Vaud cantonal school system, two years of non-obligatory pre-school are provided by the political districts. During the school year, the political district provided pre-school care for a total of 631 children of which 203 children (32.2%) received subsidized pre-school care. The canton's primary school program requires students to attend for four years. There were 4 students in the municipal primary school program. The obligatory lower secondary school program lasts for six years and there were 7 students in those schools.

, there were 9 students in Chavannes-le-Veyron who came from another municipality, while 22 residents attended schools outside the municipality.

title: Chavannes-le-Veyron


text:
Pasha (disambiguation)

Pasha was an Ottoman higher rank, and an honorary title.

Pasha or Paşa may also refer to:

Places

 * Pasha, Queensland, a locality in the Isaac Region of Australia
 * Pasha (river), in Leningrad Oblast, Russia
 * "Pasha enclaves", another name for the India–Bangladesh enclaves

Science

 * Pasha, a name for the Herona marathus species of butterfly
 * Pasha butterflies, a name for some of the Charaxes genus of butterflies
 * Pasha (protein), an alias for the DGCR8 protein, used especially when it appears in non-human animals such as D. melanogaster and C. elegans

Other uses

 * Pasha, a diminutive of Pavel, itself a Russian and Czech form of Paul.
 * Pasha (film), a 1968 French film directed by Georges Lautner
 * Pasha (Hinduism), a supernatural weapon depicted in Hindu iconography
 * Pasha (surname), a list of individuals with the surname
 * Pasha Group, an American shipping company
 * Pasha Hawaii, a company in the Pasha Group that specializes in trade between Hawaii and the continental United States
 * PASHA Holding, an Azerbaijani financial corporation
 * Pasha Records, an American record label
 * Pakistan Software Houses Association for IT and ITeS (P@SHA), a Pakistani IT trade body that promotes and develops the software and services industry
 * Pasha, a GWR Iron Duke Class steam locomotive
 * Pasha, a virtual pinball table that first appeared in the video game Pinball FX 2
 * Pasha, a fictional villain in the 1988 Indian film Paap Ki Duniya, played by Danny Denzongpa
 * Purple Pasha, a fictional female character in Wee Sing in Sillyville

title: Pasha (disambiguation)


text: User talk:160.125.253.9

title: User talk:160.125.253.9


text:
Talk:Sweet Home Alabama

Off topic chat
In Agreement with the posts above First of all a listener would need to read and listen to the lyrics of the songs. Much like a poem it would be a wise measure to digest the directions one could interpret Sweet Home Alabama before posting something publicly.

Whomever wrote the interpretation on Wikipedia could be entirely incorrect? How would you feel as a Southerner reading Neil Young's lyrics in a time of turmoil (Vietnam, Nixon) and following civil rights movement?

If you study the economy and industrialization of Birmingham (steel, manufacturing) a small Pittsburgh, PA in some ways, Neil Young's comments seem too generalized.

Write a song about Eugene Bull Connor and his police force, or Wallace himself. Read parts of Young's songs below.

It's good to think about and healthy to discuss our history and culture in our songs. There are some other powerful songs on civil rights type themes: Dylan James Meredith, Emmet Till, Birmingham Bombing (Joan Baez, beautiful song)...

Here are some lyric samples. WIKIPEDIA, get some help!

Chorus to Neil Young's Southern Man

Southern man better keep your head Don't forget what your good book said Southern change gonna come at last Now your crosses are burning fast Southern man

I heard screamin' and bullwhips cracking How long? How long?

Lyric Samples from Neil Young Alabama

Alabama, you got the weight on your shoulders That's breaking your back. Your Cadillac has got a wheel in the ditch And a wheel on the track

Oh Alabama. Can I see you and shake your hand. Make friends down in Alabama. I'm from a new land I come to you and see all this ruin What are you doing Alabama? You got the rest of the union to help you along What's going wrong?

Strange fact: "George Wallace was the governor of Alabama when this was released. He loved this, especially the line, "In Birmingham they love the governor." He made the band honorary Lieutenant Colonels in the state militia."

There is some lively discussion at this website: http://www.songfacts.com/detail.lasso?id=1702

And, "Born in the USA" was used by the Reagan campaign in 1984, even though the lyrics were clearly critical of American society.... —Preceding unsigned comment added by 207.69.139.141 (talk) 19:15, 16 August 2008 (UTC)

If it's true, then that's very important and needs to be in the article. That site also has a post that claims wallace tried to make SHA the state song but he wanted "BOO BOO BOO" removed. The post said a Van Zant refused, so the song did not become the state song. If true, this would mean wallace liked the song but didn't want the song's clear dissaproval of him to be imortalized officially. (That is, it reflects wallace's own life in that he later regretted adopting segregationist views just because he thought it was a convenient way to get elected. Segregation meant nothing more to him than an "issue", an important messy lesson of history.)  The words "BOO BOO BOO" are crystal clear, there is no need for debate as to any other interpretation, the 'B' sound is quite present 3 times over. "woo hoo hoo" sort of ignores that no 'w' sound is heard on the first syllable, and no 'h' is heard on the last two. Ace Frahm 10:01, 16 April 2007 (UTC)

 * If the song clearly disapproved of Wallace, why leave it in the backing vocals? The fact is the two definitive statements about him are: (1)"In Birmingham they love the governor", and (2) "and the governor's true". I think that's pretty positive.--Jack Upland (talk) 08:40, 17 May 2012 (UTC)

Yeah but, One thing that IS completely verifiable is that the chorus is accompanied by a (black) gospel choir... unlikely the first choice of a pro-segregationist. — Preceding unsigned comment added by 82.35.245.31 (talk) 00:35, 16 January 2013 (UTC)

 * So the song's message is this: Alabama is a great place, but it's got plenty of racists, and we disapprove of that, and we love those black musicians, but how dare Neil Young criticise it, and by the way what was wrong with the Watergate burglary.--Jack Upland (talk) 10:28, 16 January 2013 (UTC)

 * No, the song's message is this: Alabama is more diverse than the very vocal racist segment would lead you to believe. Please don't generalize us for the actions and thoughts of some ugly people. Yes Birmingham loves the racist, horrible governor. We don't judge all northerners because of Watergate, please don't lump our band/all Alabamans with Birmingham. Jaweldon (talk) 05:20, 28 July 2014 (UTC)

 * OK, you basically made that up. No one has ever said that white people are ugly. Look at Kim Kardashian or Nicole Richie. No one has said the Birmingham is the only place that voted for Wallace. No one has said Nixon was a Northerner: he was from California. Gordon Liddy was from Pluto. No one has blamed Northerners for Watergate. No one has said the band was from Alabama. That's like saying a Nazi song is pro-Jewish because Jews invented music. No, it's not... because it makes even less sense.--Jack Upland (talk) 10:27, 1 February 2018 (UTC)

This article talk page is for discussing improvements to the article, not 10 years' worth of guesses as to what the song might be about. - Sum mer PhD v2.0 16:18, 1 February 2018 (UTC)

Is this song based on a Howlin Wolf Track?
I have listened to the Howlin Wolf album 'Message to the Young' which appeared in 1971 and the song 'If I were a bird' sounded like Sweet Home Alabama from Lynyrd Skynyrd. Since it was recorded three years earlier I wonder if it was not 'stolen' from Howlin Wolf. —Preceding unsigned comment added by 195.169.203.36 (talk) 22:13, 16 June 2010 (UTC)

Hallo. I would say that the vocal line is ripped off from some older blues. It is the same one in You're looking fine from The Kinks (1966). As Ray Davies never dared to sue Lynyrd Skynyrd for plagio, I guess that perhaps he was conscious of having used something from somewhere.89.217.159.241 (talk) 11:11, 15 September 2015 (UTC)

 * So Howlin Wolf attacked Neil Young first?--Jack Upland (talk) 11:24, 15 September 2015 (UTC)

No rock/pop song is born from void. They all have roots in some previous material. I guess this song is more about the clever lyrics than the banal melody46.14.140.220 (talk) 21:04, 11 December 2015 (UTC)

Swamper
I'm from the south. The word "swamper" is used in the oil field to refer to a crew member who is there for general labor, a helper. The article says they were called "swamper" due to their "swampy" sound. I doubt that is what was actually meant. — Preceding unsigned comment added by Jcacy00 (talk • contribs) 13:31, 15 August 2014 (UTC)

The Similarity Between "Sweet Home Alabama" and "You're Lookin' Fine" by the Kinks
The comment at the very end of the "Controversy" section of this segment concerning this should be removed. As a professional musician of 40+ years, I hear no distinct correlation between the two songs. The lines "You're Lookin' Fine" and "Sweet Home Alabama" don't even have the same syllabic rhythm. The words "note for note" would imply that the melody was stolen from this song, as "notes" are what constitute the structure of a melody, and not even the cascade of the verse lines are the same. This comment should be deemed bogus and removed. — Preceding unsigned comment added by 66.210.102.194 (talk) 17:48, 3 November 2015 (UTC)
 * ✅. It should not be added unless it is accompanied by a reliable source.  GoingBatty (talk) 05:01, 4 November 2015 (UTC)

Hallo GoingBatty. I came here intrigued after your comment in Youtube on "You're looking fine". I am also a musician and don't see it so clear as you now. That fifth little bridge verse the Kinks sing ("and I said") is very idiosincratic and Lynyrd Skynyrd eagerly replicated it with different syllable counts but same time whole count ("tell the truth" but also "And I think it's a sin", "Now how about you?"). No bogus there. I wouldn't cry to plagiarism or theft but I'd point to a very close unvoluntary quote as it always happens in pop songs. I dare to say that the author of the second song had obviously listened to the first one. Not so strange if you consider that the first band was not so obscure and the author of the second song had listened to mainstream pop in his teens. Anyway, both songs have a simple three-chord blues line and brilliant, different opening riffs. LS's song sticks as an opening guitar riff + clever lyrics. K's song is about a brilliant opening piano riff. By the way, I don't think that the Kinks created their song from scratch. I bet they had heard that bluesy cliché somewhere. I hope some reader leads us to the original source from which both bands are drinking.46.14.140.220 (talk) 20:37, 11 December 2015 (UTC)

NOT against Neil Young
Sweet Home Alabama was NOT a name check against Neil Young! I could argue the point, but just watched 20 Feet To Stardom, and the backup singer on the song elucidates, starting at 47:13 minutes. That song winks at you the whole time it plays. Pb8bije6a7b6a3w (talk) 21:29, 9 October 2016 (UTC)

 * I guess you meant 20 Feet from Stardom and Merry Clayton's contribution? I haven't seen the movie but in this interview she suggests she wasn't entirely happy about participating, although "the band were great [...] and the rest is history". JezGrove (talk) 23:32, 31 January 2018 (UTC)

 * Well, the song mentions Neil Young in a derisive way. As stated previously, if the song has no political message, all its political references are pointless. It makes no sense to say that the song made all these references, but didn't mean them at all. Why, why, why?--Jack Upland (talk) 10:05, 1 February 2018 (UTC)

 * Speculation here is off topic. The article cites reliable sources discussing the meaning of various sections of the song. - Sum mer PhD v2.0 16:28, 1 February 2018 (UTC)
 * Is Shmoop University reliable? Are the comments of the band and Neil Young reliable?--Jack Upland (talk) 08:43, 2 February 2018 (UTC)

 * The band and Neil Young are reliable sources for their own opinions about their own songs. - Sum mer PhD v2.0 15:31, 2 February 2018 (UTC)

 * I don't think that's true. We have reliable sources saying that they said those things at some point. We don't know how sincere or accurate those comments were. Many of the comments were made with hindsight, responding to criticism, and are very self-serving. The fact that the band members later said they didn't support Wallace doesn't make it true. It's like Germans saying they didn't vote for Hitler.--Jack Upland (talk) 21:22, 2 February 2018 (UTC)

 * From the entry: ""We thought Neil was shooting all the ducks in order to kill one or two," said Ronnie Van Zant at the time." The reference is to an article no longer available on the Rolling Stone website but Wikipedia fact checkers had plenty of time to go over it. Some research of your own will indicate the same, that statements were made at the time.
 * Not supporting Wallace is simple, the lyric "In Birmingham, they love the governor (boo boo boo)" Granted Wallace took this as support, not noticing the booing, but it is safe to say that Wallace believing something is very different from Wallace being correct.
 * You do know how accurate the comments were, that there are reliable sources. Still, even if neither Ronnie Van Zant nor Neil Young were sincere, said everything in response to criticism, or even as you claim self-serving it's a song. Eight stanzas, not 6 million Jews. Kovar 05:01, 17 July 2018 (UTC)

 * The Ronnie Van Zant quote indicates they were attacking Neil Young. About Wallace, the boos are in the ear of the beholder. And the song also says the "governor's true". And to say the song is anti-Wallace goes against the spirit of the song, "Sweet Home Alabama". The song also says, "Watergate does not bother me", again excusing a politician who was unpopular with liberals and leftists. Yes, it's a song. Did anyone say it was an elephant? Did anyone compare it with the Holocaust? But the function of an encyclopedia is to present the truth, not cowardly apologetics. It is a racist anthem. Let's be clear about that.--Jack Upland (talk) 08:47, 17 July 2018 (UTC)
 * Yes, let's be clear: If Van Zant said "water isn't wet", it is completely accurate to say that Van Zant said that water is not wet. It is original research to say that Van Zant was wrong about water, made a joke about water, doesn't understand wetness or lied about water. If you feel it is "self-serving" for Van Zant to have said "water isn't wet", it does not change the verifiable fact that Van Zant said water is not wet.
 * Your understanding of the "spirit of the song" is your opinion. You are entitled to it, but it is not relevant here. The boos are not "in the ear of the beholder", they are in the reliable sources.
 * Statements from a figure prominent in the subject are relevant, even if you feel they are "cowardly apologetics". If you would like to include that they are cowardly apologetics, you will need reliable sources that say that.
 * And yes, someone did compare it to the Holocaust. You compared us not knowing how true statements about a song are to someone saying they didn't vote for Hitler. One is someone discussing writing a song after there has been some reaction to the song and assuming they MUST be lying, the other is someone saying they didn't support a politician who is primarily notable for a world war and the murders of millions of people when it is clear that SOME people voted for him and some clearly have lied about it afterwards. - Sum mer PhD v2.0 18:20, 17 July 2018 (UTC)

To bring this back on track, the article currently says what it says. We have several disputes based on the charge that we might be too accepting of statements after-the-fact which might be self-serving.

While we cannot add analysis emphasizing that the statements are after some feedback or that gosh, people lie and I think this guy might be lying too, we can strive for objectivity.

We have three basic points:

1) Are the sources reliable. IMO, Van Zant is an unimpeachable source for what Van Zant said, so long as it is not him saying that he said it earlier. If Van Zant says "I hate asparagus", we cannot reasonably argue that he did not say it, so long as it is in a reasonably reliable source. (Frankly, the bar there should be low: Who would make that up and why?)

2) WP:WEIGHT. IMO, what a songwriter says about a song is worth including, so long as we aren't providing lengthy drivel about every single line and thought in the song. If we are including what others have said about the song, the songwriters' responses are certainly relevant. If we report that Rolling Stone and Spin said Jane Blow's new novel supports the mass murder of hipsters, Blow's response should certainly be included.

3) Objectivity. If, using that example, Jane Blow said "The novel presents characters' arguments for the mass murder of hipsters as a way of showing that horrible ideas can be supported by logical statements, but the ideas remain horrible" there are various ways of presenting that. We cannot say logic can support atrocities nor can we say Blow presents the mass murder of hipsters as a horrible idea. We can discuss on the talk page various ways of paraphrasing Blow's statement. If that doesn't work, direct quotes with in-line attribution solves it: In July 2018, Blow said, "The novel presents characters' arguments for the mass murder of hipsters as a way of showing that horrible ideas can be supported by logical statements, but the ideas remain horrible". Whether you agree with her or think she's engaging in apologetics is a moot point.

So, to move forward:

1a) Are there any sources currently in use that anyone feels are not reliable for what they are used to support?

2a) Is there any material that does not seem to be more than trivial?

3a) What particular wordings in the article is anyone uncomfortable with? Do you have alternative wordings to suggest or should we use direct quotes? - Sum mer PhD v2.0 18:20, 17 July 2018 (UTC)

 * Reliability of sources
 * Given that this is about the intention and feelings of people involved in the controversy those quotations are our primary source material. Seeing no contradiction in what they said, or reported to have said, and what was said or reported later I consider them reliable. Kovar 18:37, 22 July 2018 (UTC)
 * Ronny Van Zant, the primary composer, is a particularly good reference since he had little time to change comments: he died within three years of the songs' release. Kovar 00:05, 26 July 2018 (UTC)

''[:The problem is the article relies heavily on quotes from people involved in the controversy (band members and Neil Young). If your writing about the election in 1933, it's not a good idea to rely on the postwar claims of Germans, though these claims could be relevant if you're writing about postwar Germany. Similarly, after his recent summit with Putin in Helsinki, Trump said he'd misspoken. That's worth noting, but it shouldn't dominate coverage of the summit. I have never suggested the quotes from Van Zant etc aren't accurate or notable, but they shouldn't dominate the coverage of the controversy.--Jack Upland (talk) 18:56, 18 July 2018 (UTC)''

(Jack: I'm moving this out of the way because Germany's actions before, during and after WWII are irrelevant to this discussion and the article we're discussing. The US president, likewise. So are a number of other topics you might bring up. Please stop using them in correlation to people talking about a song. I'd like to hear your actual contributions but Germany et.al. can be moved elsewhere. I'll follow your talk page if you'd like. Or we can just make this a separate section on this page Kovar 18:37, 22 July 2018 (UTC)]

 * I object to your censorship of this page. This page does not have an extensive Talk page, and there are no major issues which would justify your actions. How would you feel if I "hatted" or moved your comments on arguably spurious protocol grounds??? This is ridiculous. If you think my comments are spurious, you have a right to say so, but you have no right to censor them in an arbitrary, one-sided fashion. You asked me a question and I answered it, and now you are "removing" my answer. This is a kangaroo court on steroids.--Jack Upland (talk) 11:33, 23 July 2018 (UTC)

 * I take it all back. I've been being a dick. It only just clicked.--Jack Upland (talk) 04:04, 27 July 2018 (UTC)

title: Talk:Sweet Home Alabama


text:
Wikipedia:WikiProject Ohio/Townships taskforce

Welcome to the Ohio townships taskforce of WikiProject Ohio, used to better organize information in articles related to Ohio townships. It is hoped that this taskforce will help to focus the efforts of other Wikipedians. If you would like to help, please sign up below!

Scope
This taskforce aims to create articles on all of Ohio's civil townships, which are listed here.

Inactive participants

 * 18:01, Apr 20, 2005 (UTC) (Founder) - No edits since November 2010
 * 11:33, 22 May 2005 (UTC) - No edits since February 2008
 * 22:38, May 22, 2005 (UTC) - No edits since December 2010
 * 02:06, 14 January 2006 (UTC) - No edits since March 2010
 * 18:30, 1 August 2007 (UTC) - No edits since January 2010

Goals
To improve the depth and content of Ohio township articles and to maintain their stability and accuracy.

Templates
To add this taskforce's banner to a talkpage use the following code: (When township=yes, the edit guidelines include a link to the model format)

Title
Articles shall have a title in the form "TOWNSHIP NAME Township, COUNTY NAME County, Ohio", e.g. Oxford Township, Butler County, Ohio. Names should be checked against the list at List of Ohio townships. If a township has a unique name and is not similar to any others, then a redirect at "TOWNSHIP NAME Township, Ohio" should be created. Where there are more than one of the same or similar names, a disambiguation page should be created that lists all the variants, e.g. Union Township, Ohio. The DAB page should be entered into the townships category (see below).

Articles on paper townships should be made as redirects unless there is historical value, e.g. Millcreek Township, Hamilton County, Ohio. Townships that incorporated as a city, e.g. Van Buren Township, Montgomery County, Ohio or which merged with a city should be redirects to the city article and the former township status noted in the lead.

Townships that no longer exist and were not incorporated into a city, e.g. Deerfield Township, Hamilton County, Ohio should have articles explaining their status. These should be placed under Category:Defunct townships in Ohio.

Basic Empty Syntax
As much information as possible should be included. If information is not available, remove that line. Some details have been filled in for you. See Template:Infobox Settlement for additional fields that are available and the table at there for all fields and descriptions of usage.

Lead paragraph
This is the lead from the article on Oxford Township:

 * Oxford Township, also known as the College Township, is one of thirteen civil townships in the county and is located in the northwestern corner of Butler County, where it meets Preble County, Ohio, and Union County, Indiana. The city of Oxford and Miami University are located here. The Census Bureau counted 24,133 inhabitants in 2000, up from 23,092 in 1990. Excluding the city of Oxford and the village of College Corner there are 2,088 residents of the unincorporated portion of Oxford Township. It comprises one full survey township (R1E T5) in the Congress Lands and is thirty-six square miles in area.

Lead paragraphs should contain:
 * 1) The name of the township
 * 2) How many townships are in the county
 * 3) Its position in the county
 * 4) If it is one of the corners of the county or borders others, this should be stated
 * 5) Incorporated places within the township should be noted
 * 6) The population in 2000 and 1990 should be given and if there is a dramatic change (e.g. Deerfield Township, Warren County, Ohio) an explanation should be given. The population outside the corporate limits of municipalities should also be noted
 * 7) If it is one of the largest or smallest in area or population, this should be noted
 * 8) The survey that it is in, e.g. Symmes Purchase, Virginia Military District, should be noted. If it corresponds to a survey township, the range and town numbers should be given.
 * 9) The area
 * 10) The derivation of the name
 * 11) Any special things about the township, e.g. Bath Township, Summit County, Ohio is the home of Jeffrey Dahmer or the Ohio Renaissance Festival is in Massie Township, Warren County, Ohio.

This information does not need to be presented in strict order given because that could result in awkward phrasing, but it is given a guide.

Maps

For every municipality and census designated place in Ohio, maps have been created. If the township contains one of these, just copy the map to the appropriate place. (See note in next paragraph.) If there are no maps available, insert a thumbnail of the county map or request one be made at the Graphic Lab. Examples of the maps on Oxford Township and Adams Township, Clinton County, Ohio are depicted.

If you do decide to create maps of the townships, a source to do so exists here:. This PDF file from the Ohio Department of Natural Resources contains a map showing all of Ohio's townships, along with the location of each of Ohio's 88 county seats. From this source, and using a good image editor, you may create a countywide map of that county's townships, as has been done for Logan County, Ohio. A county map in a somehwat different format, based on U.S. Census maps, has been done for Hancock County, Ohio. SVG would be the file format of choice for these created maps, which can then be uploaded to Wikipedia or Wikimedia Commons.

To provide links to more maps, it's helpful to include coordinates in the articles. Use the corresponding template, such as coord in the article (see WP:GEO for more details). See also Obtaining geographic coordinates.

Demographics
Detailed population data from the U.S. Census Bureau exists for all townships. See the information here. Where it says "United States" pull down to "County subdivision" and select Ohio. A list of counties will come up; choose one and the townships will be identified.

Another source is provided by the Ohio State University, here. Click on a county on the map and data can be obtained, including the population figures in each city and township. Clicking on the line "Subcounty data" under demographics, allows one to obtain an array of data on each township.

Historic population figures
If they can be obtained, previous Census data should be listed. If there is data for the township and municipalities within it, create a table to list the data, otherwise it should be displayed in a bulleted list. See Marion Township, Clinton County, Ohio for an example of a table and Liberty Township, Butler County, Ohio for an example of a list.

Creation
The date the township was created should be noted along with who established it. In nearly all cases it will be the county commissioners. If the township was one of the original ones of the county, this should be noted. The original and subsequent boundaries should be noted. St. Clair Township, Butler County, Ohio's article contains these paragraphs:

 * One of the original five townships of Butler County, it was erected by the Butler County Court of Quarter Sessions on May 10, 1803, with these boundaries:

 * Beginning on the west bank of the Miami at the southwest corner of the fractional township No. 1 of the fourth range west of the Miami; thence north to the northern boundary of the county; thence west to the northwest corner of the county; thence south to the southwest corner of the township No. 4 of the first range west of the Miami; thence east to the Miami; thence northeasterly and northwestwardly up the Miami to the place of beginning.

 * If the township was originally included within another or was divided to form more townships, these facts should also be noted. Again, St. Clair Township says:

 * The area of the township has been significantly reduced from the original boundaries. Four new townships were created from it: Milford Township and Wayne Township, both on December 2, 1805; Reily Township on December 7, 1807; and Hanover Township (from parts of St. Clair and Ross Townships) on December 2, 1811. What is now Oxford Township was originally within the bounds of St. Clair Township, Oxford having been erected from Milford Township in 1811.

 * From these reduced borders, which consisted of nineteen whole and nine fractional sections, a substantial area has been withdrawn from the township because of annexations by the city of Hamilton. Most of the area of Hamilton west of the Great Miami River, the township's southern boundary, was originally included in St. Clair Township. In 1857, a paper township, Hamilton, was erected from parts of St. Clair and Fairfield Townships.

Neighbors
The townships that border the subject should be noted, starting in the south and proceeding clockwise. Again, quoting St. Clair Township:

 * The southeastern border is the Great Miami River. East of it is Madison Township to the northeast and to the southeast Fairfield Township (but most of this territory has since been incorporated into the cities of Hamilton and Fairfield) and . Ross and Hanover Townships are to the west, Milford Township is to the northwest, and Wayne Township is to the north.

Government
Virtually all of Ohio's townships are governed on the basic plan described in this paragraph, which should be copied and added to all articles:
 * The township is governed by a three-member board of trustees, who are elected in November of odd-numbered years to a four-year term beginning on the following January 1. Two are elected in the year after the presidential election and one is elected in the year before it. There is also an elected township clerk, who serves a four-year term beginning on April 1 of the year after the election, which is held in November of the year before the presidential election. The trustees and clerk are all chosen in non-partisan elections. Vacancies in the clerkship or on the board of trustees are filled by the remaining trustees.

Townships have recently gained the option to expand to five trustees but few if any have done so. In 2002, Deerfield Township, Warren County, Ohio's voters rejected this idea. Some townships have adopted "home rule" status. If this is the case this should be noted and sourced. Special features of a township's government, e.g. having a full-time administrator to run its affairs, operating police and fire departments, and handling its own zoning (many let the county do this), should also be noted.

Listing the current officers of a township should be done with a sentence that begins "As of 2008, the officers were . . . " per policy.

History
Details on the township's history should be noted. Famous people who have resided there can also be noted.

Communications
Details on what post offices and telephone exchanges serve the township should be noted, e.g. Harlan Township, Warren County, Ohio. Try to be specific, such as saying most of the township is in a certain exchange but the southwest corner of the township is in another exchange. Major roads should be noted, e.g. interstates, U.S. and state highways. If an interstate highway passes through, any exits or the lack thereof should be listed. Airports and navigable waterways should be noted too. See the PUCO's page here for detailed maps of the service territories of electric, gas, water, and telephone companies.

Schools
The school districts that cover the township should be noted. Be specific, as with the post offices and telephone exchanges.

See the excellent maps of school districts on the PUCO's site, here which are PDF files and very detailed. (However, some are outdated, e.g. the Butler and Warren maps do not include the recently created Monroe Local School District.)

Another way to learn what districts cover each township is to consult the "rates of taxation" each County Treasurer is required by law to issue. For example, here are the Warren County rates for 2004. Under the first township, Clearcreek, we see that parts of it are in the Springboro Community City, Lebanon City, Franklin City, and Wayne Local School Districts.

A list of all districts in a county should be posted on the county article.

''Note: No official position has been rendered on titling articles on school districts. See Naming conventions (Ohio school districts) for a discussion.''

Footer templates
All townships should include   before the first category and after the last external link, with one line padding. See:Bath Township, Allen County, Ohio for an example

Categories
Every township should be listed in   and    (if available). Defunct townships should be categorized under Category:Defunct townships in Ohio and disambiguous pages should be under Category:Ohio township disambiguation pages.


text:
User:Goethean/sig

--goethean( talk )

title: User:Goethean/sig


text: Category:Liechtenstein people

title: Category:Liechtenstein people


text:
A Perfect Spy

A Perfect Spy (1986) is a novel by British-Irish author John le Carré about the mental and moral dissolution of a high-level intelligence-officer. Major aspects of the novel are lifted from the life of the author, including the relationship between the protagonist, Magnus Pym, and his father Rick Pym.

Plot overview
A Perfect Spy is the life story of Magnus Pym, a British intelligence officer and double agent. The book opens in Vienna where Magnus is ostensibly a diplomat and also a spy, living with his wife Mary who assists with diplomatic matters and their son Tom. After returning to England to attend his father's funeral, Pym mysteriously disappears. As his fellow intelligence officers frantically search for him it becomes clear that, throughout most of his career, Magnus worked as a spy for the Czechoslovak secret service. Although intrigue, wit, and suspense make up much of the novel, the story of Magnus Pym is partly an unadorned recollection of his childhood and memories of his father Rick Pym.

The non-linear narrative cuts back and forth between the present-day manhunt for Pym (being conducted by his mentor, boss, and longtime friend, Jack Brotherhood), and Pym's first-person reminiscences of his life as, in hiding, he writes a memoir explaining to his family and friends why he betrayed his country. It incorporates flashbacks to Pym's childhood with his father, the enterprising charismatic rogue and con-man, Rick; to his early years at school and university; to his amorous adventures, to his introduction to espionage and state secrets; and to his encounters with long-time friend and Czech spy Axel. The portraits reveal Pym as a man who for so long has manipulated his appearance to those closest to him that, in the end, he was unable to hold together the conflicting personae within him. Magnus Pym has been a perfect spy, but at the cost of his soul.

Autobiographical aspects
A large part of the novel is a thinly disguised account of le Carré's own early life. Before he became a novelist, David Cornwell (John le Carré) was an intelligence officer for MI6, the British intelligence service, although there are no allegations that he ever betrayed his country and spied for another country like the character Magnus Pym. Like Magnus, le Carré lost his mother at an early age, was sent to an abusive prep school, studied languages at the University of Berne in Switzerland, in the 1950s worked for the Intelligence Corps of the British Army in Austria interrogating Czech defectors, and at the University of Oxford spied on far-left student groups for MI5, the British security service.

Rick Pym, the charismatic con man father of Magnus in the novel, is based on le Carré's father, Ronnie Cornwell. Ronnie was "an epic con man of little education, immense charm, extravagant tastes, but no social value", and associate of the Kray twins, London organised crime figures. He made and lost several fortunes through elaborate confidence schemes, and was jailed for insurance fraud. Le Carré's relationship with his father was troubled, and he has said: "'Although I've never been to a shrink, writing A Perfect Spy is probably what a very wise shrink would have advised me to do anyway.'"

Literary significance
Matthew Bruccoli calls it "the book that is and may always be Le Carré's masterpiece". Philip Roth said it was "the best English novel since the war". David Denby, writing in 2014, agreed with Roth's view.

Adaptations
A 1987 TV adaptation of the same name was produced by the BBC starring Peter Egan.

In 1993, a BBC radio adaptation in eight parts by Rene Basilico was broadcast, with James Fox as Magnus Pym, James Grout as Jack Brotherhood, Brenda Bruce as Miss Dubber and Harriet Walter as Mary Pym.

In 2017, a radio adaptation of the same name was produced by BBC Scotland, directed by Bruce Young, starring Julian Rhind-Tutt, Bill Paterson, and Michael Maloney.

In an audiobook recording of John le Carré reading aloud an abridged version of this book, he introduces the work as "THE Perfect Spy".

title: A Perfect Spy


text:
Aleksander Stanisław Potocki

Count Aleksander Stanisław Potocki (, 1778–1845) was a Polish noble, landowner and politician. He was the senator-castellan of the Polish Kingdom in 1824 and chamberlain of Napoleon I. He was awarded Order of the White Eagle on 24 May 1829.

Youth and family
Born in Warsaw, he was the son of the third Prime Minister of Poland Count Stanisław Kostka Potocki and his wife Aleksandra Lubomirska. On 15 May 1805, in Vilnius, he married Anna Tyszkiewicz (with whom he had Augustus, Maurycy and Natalia Potocka). The unsuccessful marriage ended in divorce in 1821. In 1823 he entered into a marriage with Izabella Mostowska, with whom he had Stanisław Potocki. He divorced Izabella soon after the birth of the child. At the end of his life Potocki was involved in a romance with a widow, Aleksandra Stokowska, which he never married.

Politics and career
In 1802 was made a Knight of Malta. From 1805 he lived with his wife in the estate in the district of Wilanów, named in 1807 in honour of his daughter Natalia - Natolin (property several times rebuilt by Piotr Aigner, and after the divorce with his first wife in the years 1821-1845 under the supervision of Henryk Marconi).

Potocki was a chamberlain Emperor Napoleon Bonaparte, 1812 has been a member of the Committee set up by him of the Provisional Government of the Grand Duchy of Lithuania. In 1824 he was the Senator-Castellan of Congress Poland. On 24 May 1829 he was awarded the Order of the White Eagle. Potocki did not participate in the November Uprising, nor in any of the sessions of the Sejm, for which in 1831 was expelled from the Senate. On 12 April 1843 he inherited the title of count.

title: Aleksander Stanisław Potocki


text:
Chief of the Army Staff (India)

The Chief of the Army Staff (COAS) is a statutory office held by the professional head of the Indian Army (IA), the land forces branch of the Indian Armed Forces. Customarily held by a four-star general officer, the COAS is the senior-most operational officer of the IA, tasked with the roles of overseeing the overall functioning of the force during peace and wartime, committing to the preparation and maintenance of the force's operational effectiveness and defending the nation's territorial integrity and sovereignty.

Being a permanent member of the Chiefs of Staff Committee (COSC) and the National Security Council (NSC), the COAS also bears the responsibility of advising the nation's civilian leadership i.e., the Government of India on all matters privy to the IA.

Statutorily, the COAS ranks 12th-overall in the Indian order of precedence, and is the IA's status-equivalent of the Chief of Defence Staff, the Chief of the Naval Staff and the Chief of the Air Staff - all three positions of which are also occupied by four-star officers from the armed forces.

Roles and responsibilities
Seated at the Integrated Headquarters of Ministry of Defence (Army) (IHQ of MoD (Army)), stationed in New Delhi, the COAS is the senior-most operational officer of the IA, and is tasked with the following:

 * Advising the Central Government on all matters privy to the IA.
 * Commitment to enhancing the force's capabilities towards sustaining combat readiness and operational effectiveness during periods of peace and conflict.
 * Coordinating various components of the IA towards ensuring the protection-cum-realization of the nation's territorial integrity-cum-sovereignty during states of armed conflict or war.
 * Providing direction towards the overall functioning of the organization's facets, such as command, control, administration and strategy.
 * Convening court-martials at the behest of the Central Government to review cases of misconduct during peace and wartime.
 * Reviewing the judicial sentencing and pleas of officers convicted of professional misconduct whilst in service.

In addition to these responsibilities, the COAS is also a permanent member of:
 * Chiefs of Staff Committee (COSC)
 * National Security Council (NSC)
 * Defence Planning Committee (DPC)
 * Defence Acquisition Council (DAC)

The office's eminence in the aforementioned groups thus grants the appointee with the role to advise the Minister of Defence (Raksha Mantri or RM) on the affairs related to the IA's functioning and the promotion of an comprehensive integrated planning policy with respect to the affairs of tri-service integration, doctrinal strategy, capability development, defence acquisition and infrastructure.

Structure
As the professional head of the force, the COAS is assisted by one subordinate officer and three principal staff officers, namely:
 * Subordinate:
 * Vice Chief of Army Staff (VCOAS)
 * Principal Staff Officers:
 * Deputy Chief of the Army Staff (Capability Development and Sustenance) (DCOAS - CD&S)
 * Deputy Chief of the Army Staff (Information Systems and Coordination) (DCOAS - IS&C)
 * Deputy Chief of the Army Staff (Strategy) (DCOAS - Strategy)

Promotion
Beginning in the pre-independence era, the office of COAS has customarily been held by a four-star general. The move to appoint a new designate to the position usually begins three months before the change-of-command, wherein the Ministry of Defence (MoD) reviews the résumés of the IA's sole Vice Chief of Army Staff (VCOAS) and five General Officer Commanding-in-Chiefs (of the force's five combatant commands) - all of whom are lieutenant generals, before making a decision. Appointments to the position are made by the Appointments Committee of the Cabinet (ACC) - comprising the Prime Minister and the Minister of Defence, upon recommendation from the IHQ of MoD (Army); appointees to the office are automatically deemed promoted to the rank of general.

Notably, for the first two decades following India's independence, the C-in-C and the successor COAS were the only four-star officers in the Indian Armed Forces, while the chiefs of the Indian Navy (IN) and Indian Air Force (IAF) were headed by three-star vice admirals and air marshals, respectively; the first chiefs to be promoted to four-star ranks of admiral and air chief marshal occurred in 1968 and 1966, respectively.

Since 1950, the senior-most lieutenant generals in the IA's command cadre have customarily been appointed as COAS, nevertheless, this tradition has been broken twice, first in 1983 - when then-prime minister Indira Gandhi chose to appoint then-Lieutenant General A. K. Vaidya to supersede one senior officer, and in 2016 - when prime minister Narendra Modi chose to appoint then-Lieutenant General Bipin Rawat to supersede two senior officers.

Tenure
According to the IA's Army Rules, 1954 - a COAS-appointee reaches superannuation upon the completion of three years in the position or at the age of 62, whichever is earlier. However, an appointee may also be dismissed from office by the President of India before the conclusion of the tenure under Section 18-19 of the Army Act, 1950 and Article 310 of the Constitution.

Additionally, the appointee is eligible for an extension in tenure beyond the age of superannuation, as defined by Rule 16 A (4) Army Rules, 1954. However, extensions to serving appointees have been rare, and have only been granted twice since 1947; first in June 1972 to General S. H. F. J. Manekshaw, who received a six-month extension which allowed him to serve until January 1973; and in May 2024 to General Manoj Pande, who received a one-month extension which allowed to serve until June 2024.

Previously, in the event of an abrupt stoppage during the incumbent's tenure - by termination, resignation or sudden demise, the senior-most lieutenant-general in IA's command cadre has customarily been appointed as the successor; this situation has occurred twice in the past: first in 1962 - when then-Lieutenant General J. N. Chaudhuri was appointed after the resignation of then-incumbent General Pran Nath Thapar, and again in 1993 - when then-Lieutenant General Shankar Roychowdhury was appointed after the sudden demise of then-incumbent General B. C. Joshi.

Additionally, a COAS-appointee is also eligible to be selected for the position of Chief of Defence Staff (CDS), in accordance with the Army (Amendment) Regulations, 2022 - which prescribes that the designated nominee, in this case the COAS, must be under the age of 62 at the time of appointment as CDS; as of 2024, General Bipin Rawat has been the sole COAS-appointee to be appointed to the position of CDS.

Pre-independence era (1748-1947)
The position's initial roots finds its origins in the 18th century, when the East India Company (EIC) - a British-origin trade establishment and the then-de facto administrative organization of the Indian subcontinent, established the position of Commander-in-Chief, India (C-in-C) in 1748 to head its three Presidency Armies, namely the Bengal Army, the Bombay Army and the Madras Army. Following the 1857-58 Indian rebellion against EIC rule, the control of the Presidency Armies were transferred directly to the British Crown, which succeeded the EIC as the official ruling-cum-governing entity of India. In 1895, the three armies were merged to form a unified British Indian Army (BIA), under the direct control of the C-in-C. Following the Kitchener Reforms in 1903, up until the establishment of India's independence in 1947, the C-in-C functioned as the supreme commander of the armed forces in the subcontinent, liaising directly with the Governor-General of India over the administrative affairs of the stationed military.

Dominion-era (1947-1950)
Following independence and the subsequent partition of the subcontinent, the BIA was bifurcated into two new entities: the modern-day Indian Army (IA) - responsible for the Dominion of India, and the newly-formed Pakistan Army (PA) - responsible for the Dominion of Pakistan. However, the post of C-in-C was trifurcated into three positions: the C-in-C Indian Army, the C-in-C Pakistan Army and the Supreme Commander India and Pakistan.

Following independence, the IA retained GHQ India, New Delhi - headed by General Sir Rob Lockhart as the first post-independence C-in-C, while the PA established its headquarters at GHQ Pakistan, Rawalpindi - headed by General Frank Messervy (later succeeded by General Sir Douglas Gracey) as its inaugural C-in-C. Nevertheless, the two forces were directed under the auspices of the Supreme Commander's Headquarters (Supreme HQ), headed by Field Marshal Sir Claude Auchinleck, the Supreme Commander. In January 1948, the position of Supreme Commander was abolished and bifurcated into the positions of Commander British Forces in India and the Commander British Forces in Pakistan, located at Bombay and Karachi, respectively, and with the responsibility of overseeing the repatriation of British military units to the United Kingdom. In June 1948, the title of C-in-C was modified with the prefix Chief of the Army Staff, and re-designated as Chief of the Army Staff and Commander-in-Chief, Indian Army (COAS & C-in-C)

In January 1949, upon the impeding retirement of General Sir Roy Bucher - the IA's second C-in-C, the Government of India considered the decision to appoint a native Indian general officer to the position; up until then, Indian officers had only achieved the positions associated with the three-star rank of lieutenant general. Three lieutenant-generals were shortlisted as candidates for the position, namely:
 * Lieutenant General K. M. Cariappa - General Officer Commanding-in-Chief, Western Command.
 * Lieutenant General Nathu Singh Rathore - General Officer Commanding-in-Chief, Eastern Command.
 * Lieutenant General S. M. Shrinagesh - General Officer Commanding, XV Corps; also overall commander of Indian troops during the 1947-48 Indo-Pakistani War.

Ultimately, Cariappa was chosen to succeed Bucher, which he did on 15 January 1949, with the substantive rank of a four-star general - which thus made him the first Indian-origin general and first native chief of the Indian Army; the day of his appointment has been commemorated annually ever since as Army Day. Shrinagesh, nevertheless, later served as COAS from 1955 to 1957.

Republic-era (1950-present)
In 1955, the designation of the position was shortened to simply to Chief of the Army Staff (COAS) through the Commanders-In-Chief (Change in Designation) Act, 1955; as a result of the Act, the tenure of the then-serving C-in-C - General Rajendrasinhji Jadeja, continued under the new designation.

In January 1973, General S. H. F. J. Manekshaw, the Indian Army's seventh COAS, was promoted to the five-star rank of field marshal, in recognition of his leadership during the 1971 Indo-Pakistani War - which made him the only-serving COAS to have ever been promoted to the rank. K. M. Cariappa, the second C-in-C of the Indian Army too was promoted to field marshal thirteen years later, in January 1986; however, unlike Manekshaw, he had superannuated at the rank of general in 1953 and had been in retirement for thirty-three years before his elevation. To note, although a field marshal is nominally the highest-ranking officer in the IA, the rank is all but titular with no operational duties attached, which leaves the COAS as the highest operationally-active officer in the IA.

Appointees
The undermentioned table chronicles the appointees to the office of Commander-in-Chief, Indian Army (C-in-C) and the successor office of Chief of Army Staff (COAS), beginning from August 1947 to the present-day. Ranks and honours are as at the completion of their tenure:

Former command offices

 * Commander-in-Chief, India
 * Chief of the General Staff

Other offices of the Indian Armed Forces

 * Chief of Defence Staff
 * Chairman of the Chiefs of Staff Committee
 * Chief of Integrated Defence Staff
 * Chief of the Naval Staff
 * Chief of the Air Staff

History

 * Field Marshal of the Indian Army
 * List of serving generals of the Indian Army

title: Chief of the Army Staff (India)


text:
James Archibald Houston

James Archibald Houston (June 12, 1921 – April 17, 2005) was a Canadian artist, designer, children's author and filmmaker who played an important role in the recognition of Inuit art and introduced printmaking to the Inuit. The Inuit named him Saumik, which means "the left-handed one".

Biography
Born in St. Catharines, Ontario, James Houston studied art as a child with Arthur Lismer and was educated at the Ontario College of Art (1938–40), Académie de la Grande Chaumière in Paris (1947–48) and in Japan (1958–59) where he studied printmaking. He fought in World War II with the Toronto Scottish Regiment, receiving the Canadian Volunteer Service Medal. After the war, he went to the Eastern Arctic to paint and lived there for twelve years. He was a northern service officer and civil administrator of western Baffin Island. In 1962, he moved to New York and became associate director of design with Steuben Glass.

Moving effortlessly and with great success between different activities, perhaps his biggest accomplishment was his work in the Eastern Arctic of Canada, developing Inuit art. In 1948, Houston traveled to a small Inuit community in Arctic Quebec, Inukjuak (then Port Harrison), to draw and paint images of the Inuit and the Arctic landscape. He traded his own drawings, done on the spot, for a small carving, by an Inuit hunter named Nayoumealuk, of a seated deer. Houston recognized its aesthetic appeal and returned to the Canadian Handicrafts Guild, in Montreal, with roughly a dozen small carvings, done mostly in steatite. The guild, which had tried as early as the 1920s to foster an Inuit-handicrafts market, was impressed with the carving; they were equally impressed by Houston. The guild secured a federal government grant of $1,100 and sent Houston back north in the summer of 1949 to make bulk purchases in various communities in the Eastern Arctic.

When Houston returned to Montreal that fall, the guild mounted their first exhibition of Inuit carvings. According to collector Ian Lindsay, the first exhibition was a complete sell-out. The government put more resources into developing an art and handicrafts market in the Arctic, hiring Houston to live in Cape Dorset as the first "roving crafts officer", and tapping him to write promotional material for sales in the south. The guild's fall sales exhibitions became annual affairs, with lineups routinely stretching out the door and down the block on Peel Street. By the late 1950s, the Government had sponsored tours of Inuit art through Eastern and Western Europe, South America and the Middle East. After successfully launching Inuit sculpture, Houston introduced printmaking in 1957, which met with the same success.

Houston lived in Cape Dorset with his wife Alma Houston and his two sons, Samuel and John Houston until 1962, when the couple split and he moved to New York City. He was writer and producer of the 1974 film based on his novel, The White Dawn. In 1976, his 70-foot high acrylic and aluminum sculpture "Aurora Borealis" was installed in Calgary's new Glenbow Museum, where it is still on display. He died in New London, Connecticut, aged 83.

Honours

 * He was a Fellow of the Royal Society of Arts.
 * He was an honorary member of the College of Fellows of the Royal Canadian Geographical Society.
 * In 1972 he was made an Officer of the Order of Canada.
 * In 1972 he was awarded a Doctor of Literature, honoris causa, from Carleton University.
 * In 1975 he was awarded an honorary Doctor of Humane Letters from Rhode Island College.
 * In 1979 he was awarded an honorary Doctor of Fine Arts from the Rhode Island School of Design.
 * In 1977 he won the Vicky Metcalf Award.
 * In 1981 he was made an Honorary Fellow, Ontario College of Art.
 * In 1987 he was awarded an Honorary Doctor of Law from Dalhousie University.
 * In 1997 he was awarded the Massey Medal from the Royal Canadian Geographical Society.

Books for children

 * Akavak: An Eskimo Journey, 1968.
 * Black Diamonds: A Search for Arctic Treasure, 1982.
 * Drifting Snow: An Arctic Search, 1992, winner of the 1993 Governor General's Awards
 * Eagle Mask: A West Coast Indian Tale, 1966.
 * The Falcon Bow: An Arctic Legend, 1986.
 * Fire into Ice: Adventures in Glass Making, 1998.
 * Frozen Fire: A Tale of Courage, 1977.
 * Ghost Paddle: A Northwest Coast Indian Tale, 1972.
 * Ice Swords: An Undersea Adventure, 1985.
 * Kiviok's Magic Journey: An Eskimo Legend, 1973.
 * Long Claws: An Arctic Adventure, 1981.
 * River Runners: A Tale of Hardship and Bravery, 1979, winner of the 1980 Canadian Library Association Book of the Year for Children Award.
 * Tikta'liktak: An Eskimo Legend, 1965, winner of the 1966 Canadian Library Association Book of the Year for Children Award.
 * The White Archer: An Eskimo Legend, 1967, winner of the 1968 Canadian Library Association Book of the Year for Children Award.
 * Whiteout, 1991
 * Wolf Run: A Caribou Eskimo Tale, 1971.

Books for adults

 * Confessions of an Igloo Dweller, 1995.
 * Eagle Song: An Indian Saga Based on True Events, 1983.
 * Eskimo Graphic Art: 1964-1965, 1965.
 * Eskimo Handicrafts, 1951.
 * Eskimo Prints, 1967.
 * Ghost Fox, 1977.
 * Hideaway: Life on the Queen Charlotte Islands, 1999.
 * The Ice Master: A Novel of the Arctic, 1997.
 * Ojibwa Summer, 1972.
 * Running West, 1989.
 * Songs of the Dream People, 1972.
 * Spirit Wrestler, 1980. McClelland and Stewart, ISBN 0-7710-4250-7
 * The White Dawn: An Eskimo Saga, 1971.
 * Zigzag: A Life on the Move, 1998.

title: James Archibald Houston


text:
The Languages of Africa

The Languages of Africa is a 1963 book of essays by the linguist Joseph Greenberg, in which the author sets forth a genetic classification of African languages that, with some changes, continues to be the most commonly used one today. It is an expanded and extensively revised version of his 1955 work Studies in African Linguistic Classification, which was itself a compilation of eight articles which Greenberg had published in the Southwestern Journal of Anthropology between 1949 and 1954. It was first published in 1963 as Part II of the International Journal of American Linguistics, Vol. 29, No. 1; however, its second edition of 1966, in which it was published (by Indiana University, Bloomington: Mouton & Co., The Hague) as an independent work, is more commonly cited.

Its author describes it as based on three fundamentals of method:
 * "The sole relevance in comparison of resemblances involving both sound and meaning in specific forms."
 * "Mass comparison as against isolated comparisons between pairs of languages."
 * "Only linguistic evidence is relevant in drawing conclusions about classification."

Innovations
Greenberg's Niger–Congo family was substantially foreshadowed by Westermann's "Western Sudanic", but he changed the subclassification, including Fulani (as West Atlantic) and the newly postulated Adamawa–Eastern, excluding Songhai, and classifying Bantu as merely a subfamily of Benue–Congo (previously termed "Semi-Bantu").

Semitic, Berber, Egyptian and Cushitic had been generally accepted as members of a "Hamito-Semitic" family, while Chadic, Fulani, "Nilo-Hamitic" and Hottentot had all been controversially proposed as members. He accepted Chadic (while changing its membership), and rejected the other three, establishing to most linguists' satisfaction that they had been classified as "Hamitic" for purely typological reasons. This demonstration also led to the rejection (by him and by linguistics as a whole) of the term Hamitic as having no coherent meaning in historical linguistics; as a result, he renamed the newly reclassified family "Afroasiatic".

Following Schapera and rejecting Meinhof, he classified Hottentot as a member of the Central Khoisan languages. To Khoisan he also added the much more northerly Hadza (Hatsa) and Sandawe.

His most revolutionary step was the postulation of the Nilo-Saharan family. This is still controversial, because so far attempts to reconstruct this family have been unsuccessful, but it holds promise and it is widely used. Prior linguists had noticed an apparent relationship between the majority of the languages, but had never formally proposed a family. These languages – the Eastern Sudanic, Central Sudanic, Kunama and Berta branches – Greenberg placed into a core group he called Chari–Nile, to which he added all the remaining unclassified languages of Africa that did not have noun classes. The distinction between Chari–Nile and the peripheral branches has since been abandoned. On a lower level, he placed "Nilo-Hamitic" firmly within Nilotic, following a suggestion of Köhler, and placed Eastern Sudanic on a firmer foundation.

Finally, he assigned the unclassified languages of the Nuba Hills of South Kordofan to the Niger–Congo family, calling the result Congo–Kordofanian. The relationship has been accepted, with the exception of the "Tumtum" group, though the Kordofanian languages are no longer seen as being a primary branch, and the name 'Congo–Kordofanian' is no longer used.

Greenberg's four families became the dominant conception of African languages, though his subclassification did not fare as well. Niger−Congo and Afroasiatic are nearly universally accepted, with no significant support for Hamitic or the independence of Bantu. Nilo-Saharan is still considered provisional. Khoisan is now rejected by specialists, except as a term of convenience, though it may be retained in less specialized literature.

Classification
The book classifies Africa's languages into four stocks not presumed to be related to each other, as follows:

I. Congo–Kordofanian

 * I.A Niger–Congo
 * I.A.1 West Atlantic
 * I.A.1.a Northern: Wolof, Serer-Sin, Fulani, Serer-Non, Konyagi, Basari, Biafada, Badyara (Pajade), Dyola, Mandyak, Balante, Banyun, Nalu, Cobiana, Cassanga, Bidyogo
 * I.A.1.b Southern: Temne, Baga, Landoma, Kissi, Bulom, Limba, Gola
 * I.A.2 Mande
 * I.A.2.a Western
 * I.A.2.a.1 Malinke, Bambara, Dyula, Mandinka, Numu, Ligbi, Huela, Vai, Kono, Koranko, Khasonke Bobo
 * I.A.2.a.3 Mende, Loko, Gbandi, Loma, Kpelle (Guerze)
 * I.A.2.a.4 Susu, Dyalonke
 * I.A.2.a.5 Soninke, Bozo
 * I.A.2.a.6 Duun, Dzuun, Jo, Seenku (Sembla), Kpan, Banka
 * I.A.2.b Eastern
 * I.A.2.b.1 Mano, Dan (Gio), Guro (Kweni), Mwa, Nwa, Beng, Gban, Tura (Wen), Yaure
 * I.A.2.b.2 Samo, Bisa, Busa, Kyenga, Shanga
 * I.A.3 Voltaic
 * I.A.3.a Senoufo: Minianka, Tagba, Foro, Tagwana (Takponin), Dyimini, Nafana
 * I.A.3.b. Lobi-Dogon : Lobi, Dyan, Puguli, Gan, Gouin, Turuka, Doghosie, Doghosie-Fing, Kyan, Tara, Bwamu, Wara, Natioro, Dogon, Kulango
 * I.A.3.c Grusi: Awuna, Kasena, Nunuma, Lyele, Tamprusi, Kanjaga (Bulea) (moved to group d), Degha, Siti, Kurumba (Fulse), Sisala
 * I.A.3.d Mossi, Dagomba, Kusasi, Nankanse, Talensi, Mamprusi, Wala, Dagari, Birifo, Namnam, Kanjaga (Bulea) (moved from group c)
 * I.A.3.e Tem, Kabre, Delo, Chala
 * I.A.3.f Bargu (Bariba)
 * I.A.3.g Gurma, Tobote (Basari), Kasele (Chamba), Moba
 * I.A.3.x Dogon
 * I.A.4 Kwa
 * I.A.4.a Kru: Bete, Bakwe, Grebo, Bassa, De, Kru (Krawi)
 * I.A.4.b Avatime, Nyangbo, Tafi, Logba, Likpe, Ahlo, Akposo, Lefana, Bowili, Akpafu, Santrokofi, Adele, Kebu, Anyimere, Ewe, Aladian, Avikam, Gwa, Kyama, Akye, Ari, Abe, Adyukru, Akan (Twi, Anyi, Baule, Guang, Metyibo, Abure), Ga, Adangme
 * I.A.4.c Yoruba, Igala
 * I.A.4.d Nupe, Gbari, Igbira, Gade
 * I.A.4.e Bini, Ishan, Kukuruku, Sobo
 * I.A.4.f Idoma, Agatu, Iyala
 * I.A.4.g Ibo
 * I.A.4.h Ijo
 * I.A.5 Benue–Congo
 * I.A.5.A Plateau
 * I.A.5.A.1
 * I.A.5.A.1.a Kambari, Dukawa, Dakakari, Basa, Kamuku, Reshe
 * I.A.5.A.1.b Piti, Janji, Kurama, Chawai, Anaguta, Buji, Amap, Gure, Kahugu, Ribina, Butawa, Kudawa
 * I.A.5.A.2 Afusare, Irigwe, Katab, Kagoro, Kaje, Kachicheri, Morwa, Jaba, Kamantan, Kadara, Koro, Afo
 * I.A.5.A.3 Birom, Ganawuri (Aten)
 * I.A.5.A.4 Rukuba, Ninzam, Ayu, Mada, Kaninkwom
 * I.A.5.A.5 Eggon, Nungu, Yeskwa
 * I.A.5.A.6 Kaleri, Pyem, Pai
 * I.A.5.A.7 Yergam, Basherawa
 * I.A.5.B Jukunoid: Jukun, Kentu, Nyidu, Tigong, Eregba, Mbembe, Zumper (Kutev, Mbarike), Boritsu
 * I.A.5.C Cross-River
 * I.A.5.C.1 Boki, Gayi (Uge), Yakoro
 * I.A.5.C.2 Ibibio, Efik, Ogoni (Kana), Andoni, Akoiyang, Ododop, Korop
 * I.A.5.C.3 Akunakuna, Abine, Yako, Asiga, Ekuri, Ukelle, Okpoto-Mteze, Olulomo
 * I.A.5.D Bantoid: Tiv, Bitare, Batu, Ndoro, Mambila, Bute, Bantu
 * I.A.6 Adamawa–Eastern
 * I.A.6.A Adamawa
 * I.A.6.A.1 Tula, Dadiya, Waja, Cham, Kamu
 * I.A.6.A.2 Chamba, Donga, Lekon, Wom, Mumbake
 * I.A.6.A.3 Daka, Taram
 * I.A.6.A.4 Vere, Namshi, Kolbila, Pape, Sari, Sewe, Woko, Kotopo, Kutin, Durru
 * I.A.6.A.5 Mumuye, Kumba, Gengle, Teme, Waka, Yendang, Zinna
 * I.A.6.A.6 Dama, Mono, Mbere, Mundang, Yasing, Mangbei, Mbum, Kpere, Lakka, Dek
 * I.A.6.A.7 Yungur, Mboi, Libo, Roba
 * I.A.6.A.8 Kam
 * I.A.6.A.9 Jen, Munga
 * I.A.6.A.10 Longuda
 * I.A.6.A.11 Fali
 * I.A.6.A.12 Nimbari
 * I.A.6.A.13 Bua, Nielim, Koke
 * I.A.6.A.14 Masa
 * I.A.6.B Eastern
 * I.A.6.B.1 Gbaya, Manja, Mbaka
 * I.A.6.B.2 Banda
 * I.A.6.B.3 Ngbandi, Sango, Yakoma
 * I.A.6.B.4 Zande, Nzakara, Barambo, Pambia
 * I.A.6.B.5 Bwaka, Monjombo, Gbanziri, Mundu, Mayogo, Bangba
 * I.A.6.B.6 Ndogo, Bai, Bviri, Golo, Sere, Tagbo, Feroge, Indri, Mangaya, Togoyo
 * I.A.6.B.7 Amadi (Madyo, Ma)
 * I.A.6.B.8 Mondunga, Mba (Bamanga)
 * I.B Kordofanian
 * I.B.1 Koalib: Koalib, Kanderma, Heiban, Laro, Otoro, Kawama, Shwai, Tira, Moro, Fungor
 * I.B.2 Tegali: Tegali, Rashad, Tagoi, Tumale
 * I.B.3 Talodi: Talodi, Lafofa, Eliri, Masakin, Tacho, Lumun, El Amira
 * I.B.4 Tumtum: Tumtum, Tuleshi, Keiga, Karondi, Krongo, Miri, Kadugli, Katcha
 * I.B.5 Katla: Katla, Tima

II. Nilo-Saharan

 * II.A Songhai
 * II.B Saharan
 * II.B.a Kanuri, Kanembu
 * II.B.b Teda, Daza
 * II.B.c Zaghawa, Berti
 * II.C Maban: Maba, Runga, Mimi of Nachtigal, Mimi of Gaudefroy-Demombynes
 * II.D. Fur
 * II.E. Chari–Nile
 * II.E.1 Eastern Sudanic
 * II.E.1.1 Nubian
 * II.E.1.1.a Nile Nubian (Mahas-Fadidja and Kenuzi-Dongola)
 * II.E.1.1.b Kordofanian Nubian: Dair, Dilling, Gulfan, Garko, Kadero, Kundugr
 * II.E.1.1.c Midob
 * II.E.1.1.d Birked
 * II.E.1.2 Murle (Beir), Longarim, Didinga, Suri, Mekan, Murzu, Surma (including Tirma and Zulmanu), Masongo
 * II.E.1.3 Barea
 * II.E.1.4 Ingassana (Tabi)
 * II.E.1.5 Nyima, Afitti
 * II.E.1.6 Temein, Teis-um-Danab
 * II.E.1.7 Merarit, Tama, Sungor
 * II.E.1.8 Dagu of Darfur, Baygo, Sila, Dagu of Dar Dagu (Wadai), Dagu of Western Kordofan, Njalgulgule, Shatt, Liguri
 * II.E.1.9 Nilotic
 * II.E.1.9.a Western
 * II.E.1.9.a.1 Burun
 * II.E.1.9.a.2 Shilluk, Anuak, Acholi, Lango, Alur, Luo, Jur, Bor
 * II.E.1.9.a.3 Dinka, Nuer
 * II.E.1.9.b Eastern
 * II.E.1.9.b.1 Bari, Fajulu, Kakwa, Mondari
 * II.E.1.9.b.2a Jie, Dodoth, Karamojong, Teso, Topotha, Turkana
 * II.E.1.9.b.2b Masai
 * II.E.1.9.b.3 Southern: Nandi, Suk, Tatoga
 * II.E.1.10 Nyangiya, Teuso
 * II.E.2 Central Sudanic
 * II.E.2.1 Bongo, Baka, Morokodo, Beli, Gberi, Sara dialects (Madjinngay, Gulai, Mbai, Gamba, Kaba, Dendje, Laka), Vale, Nduka, Tana, Horo, Bagirmi, Kuka, Kenga, Disa, Bubalia
 * II.E.2.2 Kreish
 * II.E.2.3 Binga, Yulu, Kara [= Tar Gula]
 * II.E.2.4 Moru, Avukaya, Logo, Keliko, Lugbara, Madi
 * II.E.2.5 Mangbetu, Lombi, Popoi, Makere, Meje, Asua
 * II.E.2.6 Mangbutu, Mamvu, Lese, Mvuba, Efe
 * II.E.2.7 Lendu
 * II.E.3 Berta
 * II.E.4 Kunama
 * II.F Koman/Coman: Komo, Ganza, Uduk, Gule, Gumuz, Mao

III. Afroasiatic

 * III.A Semitic
 * III.B Egyptian
 * III.C Berber
 * III.D Cushitic
 * III.D.1 Northern Cushitic: Beja (Bedauye)
 * III.D.2 Central Cushitic: Bogo (Bilin), Kamir, Khamta, Awiya, Damot, Kemant, Kayla, Quara
 * III.D.3 Eastern Cushitic: Saho-Afar, Somali, Galla, Konso, Geleba, Marille, (Reshiat, Arbore), Gardula, Gidole, Gowaze, Burji, Sidamo, Darasa, Kambata, Alaba, Hadya, Tambaro, Mogogodo (added 1966)
 * III.D.4 Western Cushitic: Janjero, Wolamo, Zala, Gofa, Basketo, Baditu, Haruro, Zaysse, Chara, Gimira, Benesho, Nao, Kaba, Shako, She, Maji, Kafa, Garo, Mocha, Anfillo (Mao), Shinasha, Bako, Amar, Bana, Dime, Gayi, Kerre, Tsamai, Doko, Dollo
 * III.D.5 Southern Cushitic: Burungi (Mbulungu), Goroa (Fiome), Alawa (Uwassi), Iraqw, Mbugu, Sanye [= Dahalo], Ngomvia (added 1966)
 * III.E Chad
 * III.E.1
 * III.E.1.a Hausa, Gwandara
 * III.E.1.b Ngizim, Mober [= Kanuri, not Chadic], Auyokawa, Shirawa, Bede
 * III.E.1.c
 * III.E.1.c.i Warjawa, Afawa, Diryawa, Miyawa, Sirawa
 * III.E.1.c.ii Gezawa, Sayawa, Barawa of Dass
 * III.E.1.d
 * III.E.1.d.i Bolewa, Karekare, Ngamo, Gerawa, Gerumawa, Kirifawa, Dera (Kanakuru), Tangale, Pia, Pero, Chongee, Maha (added 1966)
 * III.E.1.d.ii Angas, Ankwe, Bwol, Chip, Dimuk, Goram, Jorto, Kwolla, Miriam, Montol, Sura, Tal, Gerka
 * III.E.1.d.iii Ron
 * III.E.2 Kotoko group: Logone, Ngala [= Mpade?], Buduma, Kuri, Gulfei, Affade, Shoe, Kuseri
 * III.E.3 Bata–Margi group
 * III.E.3.a Bachama, Demsa, Gudo, Malabu, Njei (Kobochi, Nzangi, Zany), Zumu (Jimo), Holma, Kapsiki, Baza, Hiji, Gude (Cheke), Fali of Mubi, Fali of Kiria, Fali of Jilbu, Margi, Chibak, Kilba, Sukur, Vizik, Vemgo, Woga, Tur, Bura, Pabir, Podokwo
 * III.E.3.b Gabin, Hona, Tera, Jera, Hinna (Hina)
 * III.E.4
 * III.E.4.a Hina, Daba, Musgoi, Gauar
 * III.E.4.b Gisiga, Balda, Muturua, Mofu, Matakam
 * III.E.5 Gidder
 * III.E.6 Mandara, Gamergu
 * III.E.7 Musgu
 * III.E.8 Bana, Banana (Masa), Lame, Kulung
 * III.E.9
 * III.E.9.a Somrai, Tumak, Ndam, Miltu, Sarwa, Gulei [= Tumak?]
 * III.E.9.b Gabere, Chiri, Dormo, Nangire
 * III.E.9.c Sokoro (Bedanga), Barein
 * III.E.9.d Modgel
 * III.E.9.e Tuburi
 * III.E.9.f Mubi, Karbo, (added 1966: Jegu, Jonkor, Wadai-Birgid)

IV Khoisan

 * IV.A South African Khoisan
 * IV.A.1 Northern South African Khoisan
 * IV.A.2 Central South African Khoisan
 * IV.A.3 Southern South African Khoisan
 * IV.B Sandawe
 * IV.C Hatsa

title: The Languages of Africa