text:
Rough Collie

The Rough Collie (also known as the Long-Haired Collie) is a long-coated dog breed of medium to large size that, in its original form, was a type of collie used and bred for herding sheep in Scotland. More recent breeding has focused on the Collie as a show dog, and also companion. The breed specifications call for a distinctive long narrow tapered snout and tipped (semiprick) ears, so some dogs have their ears taped when young. Rough Collies generally come in shades of sable and white (sometimes mahogany), blue merle, tri-coloured, and colour-headed white.

Originating in the 19th century, the breed is now well known through the stories of author Albert Payson Terhune about his dog Lad, and later with Eric Knight's character of Lassie and her novels, movies, and television shows.

There is a smooth-coated variety known as a Smooth Collie; some breed organisations, including both the American and Canadian Kennel Clubs, consider smooth-coat and rough-coat collies to be variations of the same breed. Rough Collies closely resemble the smaller Shetland Sheepdogs or "Shelties", but the two breeds do not have an exclusive linear relationship.

History
Both Rough and Smooth collies are descended from a localised variety of herding dog originating in Scotland and Wales. The Scottish variety was a large, strong, aggressive dog, bred to herd highland sheep. The Welsh variety was small and nimble, domesticated and friendly, and also herded goats. When the English saw these dogs at the Birmingham market, they interbred them with their own variety of sheepdogs, producing a mixture of short- and long-haired varieties. After the industrial revolution, dog ownership became fashionable, and these early collies were believed to have been crossed with the Borzoi (Russian Wolfhound) to get a more "noble" head (longer muzzle), which is today one of the true characteristics of the Rough Collie. It is not known conclusively if the Borzoi cross made it into the mainstream of the breed.

When Queen Victoria acquired a Rough Collie, after seeing one at Balmoral Castle, they were transformed into something of a fashion item. Continued breeding for show purposes drastically changed the appearance of the dogs; in the 1960s, it was a much taller dog than it is today (in the UK; in the US, the size standard has not been revised downward and dogs have remained between 24 and 26"). Earlier dogs were also more sturdy in build and reportedly capable of covering up to 100 miles in one day. In the UK the Rough Collie is no longer used for serious herding, having been replaced by the Border Collie, though in the United States and a number of European countries, there has been a resurgence in the use of the Collie as a working and performance dog.

The Collie Club of America is one of the oldest breed-specific clubs in existence in the United States (founded in 1886). The Collie Club in England dates from 1881.

Quoted from Collie Club of America: Unfortunately, the Collie's exact origins are shrouded in obscurity. It has been the subject of much research and speculation. The word "Collie" is as obscure as the breed itself. The name has been spelled many different ways: Coll, Colley, Coally and Coaly. Generally, the most accepted origin of the word is "Coll" - the Anglo-Saxon word for "black".

In the 18th century, the Rough Collie's natural home was in the highlands of Scotland, where he had been used for centuries as a sheepdog. The dogs were bred with great care in order to assist their masters in the herding and guarding of their flock.

Without a doubt, it is to the English fancy of the late 1800s that the breed owes its development as a popular show dog. Rough Collies were first exhibited in 1860 at the Birmingham, England dog show, in the generic class "Scotch Sheep-Dogs". "In 1879 the first English Rough Collie was imported to this country. It is from England that we find the famous pillars of the breed, from which the American fanciers sought not only their next big winner, but also their foundation stock."

By the turn of the century, the American Rough Collie was in a state of continued development. The breed continued to thrive in England. American show prizes were dominated by the British imports. As a result of the imports, the breed made rapid progress between 1900 to 1920. These dogs built the foundations upon which the present day Rough Collie is based and paved the way for the emergence of the great American kennels of the 1920s and 1930s

Appearance
Recognized colours include:

 * Sable and white, where the "sable" ranges from pale tan to a mahogany
 * Tricolour, which is primarily black edged in tan
 * Merle, Blue or Sable merle, which is mottled.
 * Colour-headed white, which is a mainly all-white coat, except for the head, which could be tri-, sable or blue.

All have white coat areas, in the collar, parts of the leg, and usually the tail tip. Some may have white blazes on their faces. Note that the American Kennel Club accepts colour-headed white, where the dog is predominantly white with coloured markings of sable, tricolour, or blue merle on the head and sometimes body patches. The downy undercoat is covered by a long, dense, coarse outer coat with a notable ruff around the neck, feathers about the legs, a petticoat on the abdomen, and a frill on the hindquarters. One of the characteristic features of the Rough Collie is its head. This is light in relation to the rest of the body, and resembles a blunted wedge tapering smoothly from ears to black nose, with a distinct stop and parallel head planes. The muzzle is well rounded, and never square. There is considerable variation in the colour of the head, however. The eyes are medium-sized and almond shaped. The ears are supposed to be semi-prick, or tipped, with the upper third folded over. Ears which do not "tip" properly, however, are common, and many collies have their ears taped as puppies (using medical adhesive or paper tape) to encourage them to lie properly – no cutting or surgery is involved.

Rough Collies have a more blunt, gradually tapering, face than the smaller, but otherwise very similar Shetland Sheepdog, which is partly descended from the Rough Collie. The planes of the muzzle and the top of the skull should be parallel in collies, with a slight but distinct stop. (In shelties, the planes are not parallel.) The ears of a Rough Collie are similar to a Shetland Sheepdog's, but larger. Furthermore, once seen, the contrast between the Rough Collie head and that of a Border Collie is immediately apparent, the latter having a considerably shorter muzzle and a more distinct stop between muzzle and forehead. The ruff is also distinctive in distinguishing the two breeds.

The size and weight varies among breed standards; male collies can stand 55.8 to 66 cm (22 to 26 in) at the shoulder; the female averages 5 cm (2 in) shorter. The males are usually in the weight range (50–70 lbs), and the females are usually 5 to 10 lbs less. Collies in the US are sometimes reported to be over one hundred pounds, but a large collie typically weighs no more than 70 pounds. US and UK standards may differ. The UK standard calls for dogs to be significantly smaller than those under the American Kennel Club.

Temperament
Rough collies should show no nervousness or aggression, and are generally great with children and other animals. However, they must be well socialised to prevent shyness. They are medium to large sized dogs, and they generally need a house instead of being in a small apartment. Like many herding dogs, collies can be fairly vocal, and some are easily trained not to bark. The amount of herding instinct varies, with some dogs being quite drivey and others calmer.

Rough Collies are very loyal and may be one-family dogs (although most make exceptions for children), but are very rarely aggressive or protective beyond barking and providing a visual deterrent. They are typically excellent with kids. They are eager to learn and respond best to a gentle hand.

The rough collie's long coat has made the breed successful on northern Midwest farms as an able herder and guardian of the farm during the winter. The dog needs to be gradually acclimated to the cold and a suitable insulated outdoor shelter must be provided for the dog along with ample quality food and a source of unfrozen water. The rough collie also relishes playing in the snow with children during the winter months. They guard the farm while the owner is away and are naturally protective of small children.

Health
While Rough Collies are generally resilient and healthy, there are some health problems that can affect the breed.

Collie eye anomaly (CEA), a genetic disease which causes improper development of the eye and possible blindness, is a common ailment in the breed. More rarely, Rough Collies can be affected by progressive retinal atrophy (PRA), another genetic disease in which bilateral degeneration of the retina results in progressive vision loss culminating in blindness. Through genetic testing and careful screening program it would be theoretically possible to eradicate both of these problems in purebred lines, however, certainly in the UK, the Kennel Club does not require these tests to be done either for registration or showing. CEA is so prevalent that elimination of affected dogs except through very slow and careful breeding decisions to avoid shrinking the gene pool more than absolutely necessary. Rough Collie puppies should be screened at an early age (6–8 weeks) by a certified veterinary ophthalmologist to check for CEA. PRA has a later onset and can be detected by DNA test, but is much less widespread (in the US) than CEA. (In the UK, PRA is more common.) Note, the UK Kennel Club "Accredited Breeder Scheme" requires eye tests and recommends the genetic test for this class of members.

Canine cyclic neutropenia is a cyclic blood disorder that is usually fatal to affected puppies. The disease is also referred to as "gray collie syndrome", due to affected puppies having a pale gray, pinkish/gray or beige colouring, none of which are normal Rough Collie colours. Puppies that survive through adulthood are plagued with immune disorders throughout their lives and rarely live more than three years. DNA testing can help detect carriers of the recessive gene that causes the disease.

Hip dysplasia: As with most of the larger breeds, hip dysplasia is a potential concern for Rough Collies. Although this disease appears to be "multigene", careful selection by many breeders is reducing this problem. The UK Kennel Club "Accredited Breeder Scheme" requires hip-scores this class of members, however, a very small proportion of UK registered puppies are bred under this scheme. Hip dysplasia is rare in collies compared to their closest relatives and other breeds of the same size.Rough Collies may carry a mutant Mdr1 gene that results in a sensitivity to Ivermectin and related drugs. A screening test is used to determine if alternative medications are required. Overdoses from the proscribed medications can result in neurological impairment or even death, but preventative doses are usually safe. This faulty gene is present in several breeds, but is well known among collies.

In addition to these problems, all of which can be tested for, there are a number of problems which are thought to be genetic but for which no screening test exists. These include epilepsy, bloat, a tendency towards allergies, and thyroid disorders (primarily hypothyroidism.). Because no DNA tests exist for these disorders (and all can have causes other than genetic origins), breeders can only do their best to avoid producing them by removing affected dogs from the gene pool.

Ulcerative dermatosis of Shetland sheepdog and rough collie (UDSSC) is a disease that is believed to be a vesicular variant of discoid lupus erythematosus. It is an ulcerative dermatosis that affects the thigh, groin, axillae, and ventral abdomen.

Herding
In the 18th century, the Collie's natural home was in the highlands of Scotland, where it had been used for centuries as a sheepdog. The dogs were bred with great care in order to assist their masters in the herding and guarding of their flock.

Collies are capable of being keen herders while remaining sensible, flexible family companions, whether as working dogs on a ranch or farm or helping out a suburban owner who keeps a few sheep, goats, or ducks as a hobby. Participation in herding helps preserve the special heritage of the Collie and opens up new opportunities for owner and dog. The qualities that make a good herding dog – trainability, adaptability, loyalty, soundness of body and character, agility, grace – are important in many areas, and contribute so much toward making the dog an outstanding companion as well.

Throughout the country there are local herding clubs that provide clinics, work days, trials and tests. Several organizations provide herding title programs in which Collies regularly participate. A Herding Instinct Test introduces Collies and their handlers to herding at the basic level. It is designed to show whether or not a Collie, who may have never had any exposure to livestock, still has the natural instinct to perform the function for which the breed was initially created. It is a non-competitive introduction to carefully selected and easily handled livestock under favorably controlled conditions.

Activities
Rough Collies can compete in dog agility trials, obedience, conformation, flyball, tracking, and herding events. Herding instincts and trainability can be measured at noncompetitive herding tests. Rough Collies exhibiting basic herding instincts can be trained to compete in herding trials. The breed has also been known to work as search and rescue dogs, therapy dogs and guide dogs for the blind.

Notable Rough Collies

 * Lassie, a line of Rough Collies originally owned by Rudd Weatherwax that have starred in numerous films, multiple television series, a radio program, and has been the subject of various novels and non-fiction works. One of the few animal actors to have a star on the Hollywood Walk of Fame.
 * Reveille is the name of the current mascot of Texas A&M University. Since Reveille III became the mascot in 1966, each dog to bear that name has been a Rough Collie; the current mascot is Reveille X. She assumed her duties in 2021, and she was donated by Rough Collie breeders Julie Hinrichsen and Russell Dyke of Juell Collies.
 * Dylan, Argentine president Alberto Fernández's pet dog.
 * Lad, the main hero of Albert Payson Terhune's early 20th-century novels about his Sunnybank Rough Collies.
 * Wolf, the main hero of Albert Payson Terhune's early 20th-century novels about his Sunnybank Rough Collies.
 * Gray Dawn, another of Albert Payson Terhune's early 20th-century novels about his Sunnybank Rough Collies.
 * Pal, the first Rough Collie to portray Lassie.
 * Ch. Laund Loyalty of Bellhaven, a nine-month-old Rough Collie who is the youngest dog to ever win the Westminster Kennel Club Dog Show.

title: Rough Collie


text:
La Rioja Province, Argentina

La Rioja, officially Province of La Rioja is a province of Argentina located in the west of the country. The landscape of the province consist of a series of arid to semi-arid mountain ranges and agricultural valleys in between. It is in one of these valleys that the capital of the province, the city of la La Rioja, lies. Neighboring provinces are, from the north clockwise, Catamarca, Córdoba, San Luis and San Juan. The dinosaur Riojasaurus is named after the province.

History

Petroglyphs created by early indigenous peoples at the Talampaya National Park are dated around 10,000 years BC. Succeeding cultures of indigenous peoples developed here. The Diaguita, Capayan and the Olongasta peoples inhabited the territory of present-day La Rioja Province at the time of encounter with the Spanish colonists in the 16th century.

Juan Ramírez de Velazco founded Todos Los Santos de la Nueva Rioja in 1591 under the government of Tucumán of the Viceroyalty of Peru. In 1630 the Calchaquí people revolted against the Spanish, but the governor Albornoz suppressed them.

In 1783, after the creation of the Viceroyalty of the Río de la Plata, the control of the province of 10,000 inhabitants passed to the Córdoba independency. The province acquired independence from Córdoba in 1820. Following attempts by Bernardino Rivadavia, the first elected President of Argentina, to impose a centralist constitution, the caudillo Juan Facundo Quiroga emerged as a popular leader. He represented their preference for more autonomy, for which they continued to press following Quiroga's 1835 assassination. After a period of internal instability in Argentina, the province finally joined the Argentine Confederation in 1853.

La Rioja attracted fewer immigrants from Europe than did other Argentine provinces from 1890 to the 1930s.

Some Syrian and Lebanese immigrants did settle in the province, among whom the most well-known is probably the Menem family. Coming from what had been the Ottoman Empire, Saul Menem and his wife were of Armenian and Alawi ancestry. He prospered as a traveling salesman and sent his eldest son, Carlos Menem, to Spain for college. The younger Menem was elected governor of La Rioja Province in March 1973, was imprisoned during the subsequent dictatorship and was elected president of Argentina in 1989, serving until 1999. During those years, he steered billions in federal public works spending into La Rioja. Although the province remains less developed than the average in the nation, its economy today compares favorably with those of its neighbors.

Geography

Located in the Argentine Northwest area, its landscape is arid to semi-arid, and the dry climate receives annually 200 mm of precipitation, has short winters, and very hot summers.

From the Andes at the west, with peaks of up to 6,795 meters (Monte Pissis), the relief's height descends towards the sierras of the neighbouring dry Pampas zone. Most ranges in La Rioja are oriented north-south. The province's two largest cities, La Rioja and Chilecito are separated by Sierra de Velasco and west of Chilecito and Famatina rises the Sierra de Famatina with heights of up to 6,250 m.a.sl. (≈20500 feet).

The Talampaya National Park is a dry red-soil canyon of the dry Talampaya river, which contains many cliff walls and rock formations that make it an interesting tourist destination.

Economy
La Rioja's economy, estimated at US$1.822 billion in 2006, is the second-smallest among Argentina's provinces. Its per capita output of US$6,283, though about 30% below the national average, makes it the most well-developed in northern Argentina.

Its economy is, likewise, very well-diversified. Agriculture (long limited by La Rioja's dry, mountainous terrain) adds less than 5% to its output. La Rioja's agriculture (as well as cities) lies on the banks of the few permanent rivers and oases that allow irrigation, with only 190 square kilometres of cultivated land. Vineyards, nuts and olive plantations are the most common, followed by cotton.

The province's main crop is the grape, and its associated wine production, especially around the Chilecito area, with a production of 8 million litres per year.

Cattle (250,000 head) and goats (150,000 head) are secondary activities, particularly for skin and leather. Clay represents the main mining activity, and uranium is also extracted near El Colorado.

Manufacturing in La Rioja has expanded considerably since Gov. Menem began attracting investment into the province, after 1983. Limited mostly to light industry like bottling and food processing, it, nevertheless, adds about 20% to La Rioja's output. Tourism is, likewise, an expanding activity. Besides the Talampaya National Park, tourists visiting La Rioja usually go also to the Chilecito town, Cerro de La Cruz, Termas de Santa Teresita hot springs and the village of Villa Sanagasta.

Since 2024 it has its own currency.

Government
The provincial government is divided into the usual three branches: the executive, headed by a popularly elected governor, who appoint the cabinet; the legislative; and the judiciary, headed by the Supreme Court.

The Constitution of La Rioja Province, Argentina forms the formal law of the province.

In Argentina, the most important law enforcement organization is the Argentine Federal Police but the additional work is carried out by the La Rioja Provincial Police.

Political divisions
The province is divided in 18 departments (Spanish departamentos). They are formally considered to be a single municipality, and usually contain one or more population centers (i.e. towns and cities).

 * 1) Arauco (Aimogasta)
 * 2) Capital (La Rioja)
 * 3) Castro Barros (Aminga)
 * 4) Chamical (Chamical)
 * 5) Chilecito (Chilecito)
 * 6) Coronel Felipe Varela (Villa Unión)
 * 7) Famatina (Famatina)
 * 8) General Ángel Vicente Peñaloza (Tama)
 * 9) General Belgrano (Olta)
 * 10) General Juan Facundo Quiroga (Malazán)
 * 11) General Lamadrid (Villa Castelli)
 * 12) General Ocampo (Milagro)
 * 13) General San Martín (Ulapes)
 * 14) Independencia (Patquía)
 * 15) Rosario Vera Peñaloza (Chepes)
 * 16) San Blas de los Sauces (San Blas de los Sauces)
 * 17) Sanagasta (Sanagasta)
 * 18) Vinchina (Vinchina)

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

title: La Rioja Province, Argentina


text:
X PixMap

X PixMap (XPM) is an image file format used by the X Window System, created in 1989 by Daniel Dardailler and Colas Nahaboo working at Bull Research Center at Sophia Antipolis, France, and later enhanced by Arnaud Le Hors.

It is intended primarily for creating icon pixmaps, and supports transparent pixels. Derived from the earlier XBM syntax, it is a plain text file in the XPM2 format or of a C programming language syntax, which can be included in a C program file.

XPM1
The first (1989) XPM format is relatively similar to the XBM format. Compared to XBM, it uses additional macro definitions and variables for indexed colors, and replaces bits with characters for describing the image. The following is a black-and-white image in the 1989 XPM format.

XPM2
XPM2 (1990) simplifies the format by removing all C code. The structure is simplified to ! XPM2

 * The value section describes the overall dimension of the image similar to the  statements.
 * The color section defines the values, and a new concept of the "type" of the color. The types may be c for "color", m for "monochrome" output, g for "grayscale", and s for "symbolic", explaining what a defined color is supposed to do.
 * The pixels and optional extensions remain as in the original format.

The above file, with width 48, height 4, 2 colors, and 1 character per pixel, becomes:

! XPM2 48 4 2 1 a c #FFFFFF b c #000000 abaabaababaaabaabababaabaabaababaabaaababaabaaab abaabaababaaabaabababaabaabaababaabaaababaabaaab abaabaababaaabaabababaabaabaababaabaaababaabaaab abaabaababaaabaabababaabaabaababaabaaababaabaaab

Colors
In addition to hexcodes, the colors can be any of the X11 color names. In addition,  indicates transparency.

The "symbolic" feature permits adjusting colors depending on the context where they are used. Code such as  could be adjusted on a blue background.

Many-color encoding
One tool is known to use only a to p for 16 colors, switching to aa up to dp for 64 colors, but still reading single character encodings for 64 colors; compare Base64.

With more colors the codes use more characters, e.g. aa up to pp for 16 × 16 = 256 colors. This is less useful for text editors, because a string ab could be actually the middle of two adjacent pixels dabc. Spaces are allowed as color code, but might be a bad idea depending on the used text editor. Without control codes, backslash, and quote (needed in XPM1 and XPM3) 128 − 33 − 2 = 93 ASCII characters are available for single character color codes.

Simplified example: 90 US-ASCII characters could be arranged into nine non-overlapping sets of 10 characters. Thus unambiguous strings of nine characters could set the color of each pixel by its XPM palette index with up to 109 = $1,000,000,000$ colors (compare to GIF, which supports only 256).

For XPM2 it is clear how many lines belong to the image – two header lines, the second header line announcing the number of color codes (2 lines in the example above) and rows (height 4 in the example above), e.g. 2 + 2 + 4 = 8 lines.

XPM3
The current and last format is XPM3 (1991). It re-introduces the C wrapper, but instead of explicitly showing a file's structure, the strings stored are essentially identical to XPM2.

If the "values" line contains six instead of four numbers, the additional values indicate the coordinates of a "hotspot", where 0 0 is the upper left corner of a box containing the icon and the default. A "hotspot" is used for mouse pointers and similar applications.

Comparison with other formats

The following code displays the same blarg file in the XBM, XPM and PBM formats.

XBM version:

XPM2 version:

! XPM2 16 7 2 1 . c #ffffff ...............* .............**.
 * c #000000

XPM3 version:

PBM file: P1 16 7 1 1 0 0 1 0 0 0 0 0 0 0 0 0 0 0 1 0 1 0 1 0 0 0 0 0 0 0 0 0 0 0 1 1 0 0 1 0 0 1 1 0 1 1 0 0 1 1 1 0 1 0 1 0 1 0 1 0 1 0 0 1 0 1 1 1 0 0 1 0 0 1 1 0 1 0 0 0 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 0

Application support
ACDSee, Amaya, CorelDRAW, GIMP, ImageMagick, IrfanView (formats plugin), PaintShop Pro, PMView, Photoshop (plugins), and XnView among others support XPM. Gravatar and picons also support XPM.

An X11 libXpm vulnerability was fixed in 2005, and three more in 2023.

FFmpeg version 3.3 or later can decode XPM.

title: X PixMap


text:
Wikipedia:Requests for comment/User conduct disputes archive/Jiang-Pigsonthewing

Jiang: British English (Secretlondon)

 * User:Jiang keeps moving Halls of residence to Residence hall, from the UK English to the US English term. I believe this is against policy and is offending British contributors. Secretlondon 12:29, Dec 14, 2003 (UTC)
 * No, I did not "move" the page there multiple times in the wikipedia technical sense. I am just preventing Pigsonthewing from hijacking the page history by doing a cut and paste move. Copying and pasting can never be accepted, as I have stated at User talk:Pigsonthewing more than once. Unfortunately, Pigsonthewing fails to either 1) get a sysop to move the page properly and 2) convince me why that page deserves to be under the less common name. --Jiang | Talk 12:37, 14 Dec 2003 (UTC)
 * I am hijaacking nothing, as has already been explained. Jiang has deleted my comments on this matter, from at least one page. Andy Mabbett 19:35, 14 Dec 2003 (UTC)
 * The act of copying and pasting and disregarding entire page histories constitutes hijacking. I did not delete your comments. Want to tell me where? --Jiang | Talk 02:25, 15 Dec 2003 (UTC)
 * See above. Andy Mabbett 10:56, 15 Dec 2003 (UTC)

Pigsonthewing: common names (Jiang)

 * User:Pigsonthewing (contributions) keeps copying and pasting the content at Residence hall to Hall of residence without using the "move this page" function. When asked to sit and discuss at Talk:Residence hall, this user blatantly refuses to offering the only defense of "so what" against the naming conventions. More on this conflict can be found at Current disputes over articles. --Jiang | Talk
 * I have already explained why I cut & pasted. I have said more than "so what", and that was not my response to the invitation to talk. I am in no way in conflict with "common names". I am tired of Jiang's lies on this matter.Andy Mabbett 19:33, 14 Dec 2003 (UTC)
 * I've already explained to you that copying and pasting can be accepted under no circumstances, yet you continued to ignore me and copy and paste. You have no excuse - ask another sysop to do it. --Jiang | Talk 02:24, 15 Dec 2003 (UTC)
 * I am concerned that User:Pigsonthewing is making quite a habit of this. Note that I am not talking here about his opinions, but an unwillingness to discuss and an unwillingness to stop re-changing things to reflect his opinion while a discussion takes place.  It is not acceptable to try and win any disagreement by consistently re-doing changes in the hope that the other people will tire of it and let you have your way, and IMO this is what's being done.  This has NOTHING to do with who's right in this particular disagreement, (I'm inclined to think that Jiang's wrong and Pigsonthewing is right on this particular naming dispute), but rather to do with willingness to follow standard practise and allow consensus to be reached.  Pig-headed stubbornness is not that method. --Morven 08:18, 15 Dec 2003 (UTC)
 * I'll second that (re a silly insistence on the spelling of 'humorous' on dead tree, cf. Talk:dead tree. --Charles Matthews 11:59, 15 Dec 2003 (UTC)
 * I repeat: there is no unwillingness to discuss. To say that there is ais a lie. My comments on this issue have been deleted from at least on page byJiang. The "unwillingness to stop re-changing things to reflect his opinion while a discussion takes place" is Jiang's. Andy Mabbett 09:17, 15 Dec 2003 (UTC)
 * You have been told repeatedly that moving by copying and pasting is not considered acceptable practice. That is definitely the case.  If you are not able to move the page via the normal 'Move this page' interface, the acceptable way to proceed is to ask an admin to make the change; it is not acceptable to copy and paste the content instead. You have also been told that repeating a controversial edit again and again rather than discussing it with others is not acceptable.  Jiang made a change you disagreed with, yes, but he's allowed (Be Bold).  You can revert that change if you disagree, once or twice, but after that, discussion is the way forward.  And the fact is, on this issue you are LIKELY TO PREVAIL in that discussion. --Morven 20:17, 15 Dec 2003 (UTC)
 * You appear to be confusing me with someone else. What "controversial" edit? Your represntation of the "Hall of residnce" exchange is distorted, since Jinag wasn't "being bold" - he was restoring a bad change which I had already reverted. Surely by your logic, he should have discussed it first? I wonder why he didn't mention the correct method of moving such a page?Andy Mabbett 20:51, 15 Dec 2003 (UTC)
 * As seems to be normal practice for you, you avoid the main question to pick at a little detail. Yes, Jiang's decision to rename the page was controversial.  Reverting it is ALSO controversial, since it is clearly against the wishes of a number of users.  It does not matter who is right here, nor whose version is more controversial, nor anything else; the issue is that we do not decide issues here on Wikipedia by a contest of stubbornness.  Jiang has, I believe, stated that if you renamed the page back USING THE APPROVED PROCEDURE he would not revert the change but would rather wait for a consensus in talk. (correct, Jiang?).  I would advise YOU in turn to try and achieve agreement on the talk page rather than by warring on the article.  And your insistence that you would only discuss on the talk page of your copied article and nowhere else is rather petty. --Morven 21:05, 15 Dec 2003 (UTC)
 * You again appear to be confusing me with someone else; and this issue for some other conflict. Leastways, the views you ascribe to me are not mine.Andy Mabbett 21:15, 15 Dec 2003 (UTC)
 * I don't see how any of that is not true. You even admitted that you would discuss it nowhere else but on the copied talk page. Perhaps you should quote the parts of his argument that you find false, rather than dismissing the entire post? --Jiang | Talk
 * I ask you again to cite where (provide a link to the page history) I deleted or altered your comments. That did not happen. Of course there is an unwillingness to discuss - you admitted to refsuing to discuss at Talk:Residence hall and instead would only post on the hijacked version at Talk:Hall of residence. --Jiang | Talk 09:23, 15 Dec 2003 (UTC)
 * In you reply to one of my comments, though you have excised that comment. You did so more than once. Your comment here is again a lie. There was, and is, no "unwillingness to discuss" Nothing was "hijacked", other than by you. Andy Mabbett 10:56, 15 Dec 2003 (UTC)
 * No, that doesn't show that I deleted your comment. It shows that I restored the content of a page over a redirect you created when you tried to "move" the page using copy/paste methods. Please try again. --Jiang | Talk 11:05, 15 Dec 2003 (UTC)

 * Refer to the talk, history and yet more history of Concorde for another example. Tannin 12:15, 15 Dec 2003 (UTC)

Jiang: Introduction headers (pigsonthewing)
User Jiang insists that "introducton" is not allowed as a header, but can cite no policy to support this. I have scrupulously attempted to conduct a discussion on my talk page (and in the history of edits), but he denies that I have refuted his baseless claims, and inssts on reverting pages, and making damaging edits (putting content under inappropriate and misleading headings, for instance) in an attempt to eradicate any heading using the word "introduction"; all while the duiiscussion is ongoing. I have specifically asked his to desist from reversions while we discuss, yet he refuses. I have also invited him to make different, better changes to replace "introduction". See, for example, Netscape Navigator; BBC Radio 4 (and many others). Andy Mabbett 01:10, 16 Dec 2003 (UTC)
 * He also says, rightly, that "you are not trying to communicate with me by purposely giving me ambigous answers"! Andy Mabbett 01:11, 16 Dec 2003 (UTC)
 * and has just reverted my move of Music_of_Scotland to Scottish folk music, even though discussion on that is ongoing on the talk page, I'm begining to think this is personal. Andy Mabbett 01:13, 16 Dec 2003 (UTC)
 * I moved Music of Scotland back because consensus was not achieved to move it in the first place and "Music of..." is the standard title. --Jiang | Talk
 * So now every edit requires consenus FIRST? Andy Mabbett 01:26, 16 Dec 2003 (UTC)
 * No, an edit is not a move, but you shouldn't get irritated if you see whatever you do undone if it comes out as inappropriate. --Jiang
 * Not inappropriate. *** So now every move requires consenus FIRST? Andy Mabbett 13:09, 19 Dec 2003 (UTC)
 * No, but don't get upset if you are reverted for making an illogical move. Illogical moves are prevented if you discuss. --Jiang 13:18, 19 Dec 2003 (UTC)
 * Not illogical. Andy Mabbett 13:29, 19 Dec 2003 (UTC)
 * You skills at argumentation are very admirable. I guess I'm expected to believe that it's not logical just because you say so. LOL --Jiang 13:40, 19 Dec 2003 (UTC)
 * NO different to you expecting me to belive your unsubstantiated assertions, Still no piolicy cited to support them. Andy Mabbett 14:06, 19 Dec 2003 (UTC)
 * See User_talk:Pigsonthewing for the discussion and a sampling of pigsonthewing's discussion style. Let it speak for itself. --Jiang | Talk 01:18, 16 Dec 2003 (UTC)
 * These damaging reversions and changes are ocntinuing, see, for example, Orca. Still no policy cited in support. Andy Mabbett 11:19, 17 Dec 2003 (UTC)
 * Still ongoing. Andy Mabbett 08:19, 18 Dec 2003 (UTC)
 * I personally don't see much value in "Introduction" as a header title. A good rule of writing (IMO) is "be specific".  A header I think ought to describe what a section is about: History, Statistics, Geography, Synopsis, etc.  My experience is that if a section feels like it should be labelled "Introduction" then either I haven't thought hard enough about the best name for the section, or the section is too vague and needs fleshing out or to be broken up into several sections.  That's my thought. -mhr 06:45, 19 Dec 2003 (UTC)
 * Consider an intorduction with, say, four sentences, each making a different point,. How would you sub-divide that? Andy Mabbett 12:31, 19 Dec 2003 (UTC)
 * Four sentences can fit into a single introduction. Why subdivide it? If if needs subdivision, then parts of the intro needs to be snipped and placed in relevant sections. --Jiang
 * Why ask me? It was Michael Rawdon' susgegstion. Andy Mabbett 13:09, 19 Dec 2003 (UTC)
 * I am agreeing with Michael on this. --Jiang
 * Then perhaps you can say how you would split such a section, as he suggests? Andy Mabbett 13:29, 19 Dec 2003 (UTC)
 * Depending on situation...usually moving to existing sections, or if the info can be made into another section with a specific title - just what I have been trying to do. --Jiang 13:40, 19 Dec 2003 (UTC)
 * Subdivision was just a suggestion, not a mandate, and I can see that not all such sections could reasonably be subdivided. If the introduction is short, then I'd advocate simply not putting a header on it.  Heck, there's no reason an introduction need even be a single paragraph.  For example, see Cyclops (comics), which has a two-para introduction - but no header marking them as such.  Actually I think your two examples, Netscape Navigator and BBC Radio 4 work perfectly well as presently written; the former's Introduction section is now Development, which is more descriptive (and thus more useful as a header to a reader), and the latter's Introduction has been conflated with the unlabelled introductory paragraph, which I also think is appropriate. -mhr 16:25, 19 Dec 2003 (UTC)
 * Still spreading; see Conservation (where the new heading is grossly inappropriate for the content beneath it) et al. Andy Mabbett 12:26, 19 Dec 2003 (UTC)
 * Trying to discuss it at Talk:Conservation. --Jiang
 * This is a meta issue; no point discussing it on each page in turn. I have already asked you to stop making chanegs to "introduction" headinsgs while this is discussed, but you persist in doing so. Still no policy cited in suport. Andy Mabbett 13:09, 19 Dec 2003 (UTC)
 * Say I acknowledge your position that introduction headers are fine. Even then, you have no reason to revert my insertions of more specific headers without explaining how my headers are "grossly inappropriate". I asked for an answer at Talk:Conservation for that specific case (yes, we have to talk specifics for this is not just about whether the intro header is allowable, but whether the alternative for that specific article is appropriate), but so far, you have refused to answer me. Perhaps you don't have an answer? Anthere, a principal contributor of that article said mine was fine. Now what is wrong with the headings I have inserted (aside from how ridiculous your header is)? --Jiang 13:18, 19 Dec 2003 (UTC)
 * Not ridiculous; I have made no such refusal; "grossly inappropriate" IS a reason; Anthere is just one other user. STILL no policy cited to support your stance.Andy Mabbett 13:29, 19 Dec 2003 (UTC)
 * You have failed to explain how it is not ridiculous and how it is grossly inappropriate. The words "grossly inappropriate" cannot possibly reasons for themselves. That's just begging the question. You are refusing to elaborate on your claims, and then shutting your eyes to this fact. I already told you, even if policy does not support my view that no section be titled "introduction," the fact that I replace "introduction" with more specific and useful headings is not grounds for reversion unless you explain why those headings do not work - but you refuse to. --Jiang 13:40, 19 Dec 2003 (UTC)
 * I have not changed one of you headings, where thay have been useful (as opposed to misleading or grossly inappropriate). Andy Mabbett 14:06, 19 Dec 2003 (UTC)

Andy, I wanted to thank you for initially proposing a heading to the conservation page. That was certainly an improvement over no headings. This said, Jiang new headings were an improvment over your initial proposition, so there are worth keeping.

An introduction is something short at the beginning of a text or a book. Generally speaking, the length of the introduction is highly related to the length of the total text. It is quite frequent that a book introduction will be at least one page long, or perhaps even a dozen. In an article of say a dozen pages, an introduction will be rather perhaps a couple of paragraphs to one page. On an article of perhaps 2 pages (10 kb), it looks like good balance to have an introduction of something between one sentence, to one or two paragraphs. This is not a rule. This is just how an piece of text is "balanced". It make no sense that an introduction represent half of a text. If it is so, then either the introduction is too long, or the article is just missing content, or more likely, the introduction *IS* the text. This does not have to be a rule. That is just how a good and informative article is written, with balanced parts, and informative headings.

For example, if we kept your "introduction" header, the conservation article would be made of three parts
 * 1) a short introduction
 * 2) a second part representing 45% of the content and called introduction and
 * 3) a third part representing 45% of the content and called history

That would make little sense.

PomPom
 * An introduction is something short at the beginning of a text or a book.: No, that's just one definition. Andy Mabbett 11:38, 20 Dec 2003 (UTC)
 * Really ? What are the other definitions then ? Please, elaborate. PomPom
 * Andy Mabbett 12:32, 20 Dec 2003 (UTC)

 * 1) noun:   the act of beginning something new
 * 2) noun:   the first section of a communication
 * 3) noun:   a basic or elementary instructional text
 * 4) noun:   a new proposal (Example: "They resisted the introduction of impractical alternatives")
 * 5) noun:   the act of putting one thing into another
 * 6) noun:   formally making a person known to another or to the public
 * 7) noun:   the act of starting something for the first time introducing something new (Example: "He regards the fork as a modern introduction")

All this is perfectly in line with all what I wrote above. And none of these definitions justify to put half of the content of an article under a heading call "introduction" to leave only another section called history. PomPom

Jiang
Jiang is trying to lump me in with Lir in the item below without the slightest explanation. Instead of answering a simple question, he's having an edit war on this page. --Wik 03:29, Jan 11, 2004 (UTC)

 * Well, Wik, maybe this because you frequently behave like Lir. Adam 09:58, 12 Jan 2004 (UTC)

 * OOOOOOO, sup now foo! Lirath Q. Pynnor

 * I have no idea what that means, and I'm not even sure to whom it's directed... -- Cyan 19:46, 17 Jan 2004 (UTC)
 * I think it means something like "Ooh, I'm being challenged, you fool." But that's just a guess...I'm not all too fluent in what appears to be ebonics.. PMC 03:16, 18 Jan 2004 (UTC)


text:
User:Getkashyap

Hi... A bug was introduced in 1.2.0rc3 which broke saved password cookies. If you don't want to wait for the next release, you can grab the updated files and drop them into the includes directory:

 * User.php
 * Setup.php

That should fix it. --Brion 22:02, 2004 Mar 12 (UTC)

12 July 2005,16:22

Referenced a Page Word Processor. Found that it was reading: "ROONEY IS A GYPO" Used the How_to_revert_a_page_to_an_earlier_version to revert it to the previous version.

Hope I didn't muck up anything!

--getkashyap 10:57, 12 July 2005 (UTC)

title: User:Getkashyap


text:
Talk:New Communist Party of Britain

Misc comments
I have tried to correct the inaccurracies as to the political stance of the NCPB in this edit, but there is clearly much more that needs to be here. I'll get back to it when I get a chance.

General comments about the origins of the NCP deleted as they are oversimplified and obviously written by someone with no first hand knowledge of the events. The term "tankie" was used by the Euro wing of the CPGB largely for the group around Nicholson, which was far more prominent in London that the supporters of the Surrey District. More importantly it did not come into common parlance until the arguments over the British Road to Socialism became heated in the run-up to the 1977 Congress. It has nothing whatsoever to do with the Hungarian events of 1956 and only very obliquely with the Soviet intervention in Czechoslovakia in 1968. While it's true that French, Nicholson and some others did take a common stance vis-a-vis the CPGB's leadership support for Dubcek post-1968 the defining issue as far as Sid French was concerned was the BRS ( though it's true this was not understood fully by some of his supporters).

Stalin Society'
While I've left the edit as I can't give a reliable source, I would be intrigued to see an official NCP repudiation of Stalin from the last 5-10 or so years. I know for a fact of a couple of members who are in the Stalin Society but won't name them here without their consent.

My opinion, which for obvious reasons I won't edit into the article, is that the anti-1977 British Road to Socialism origins of the NCP was rather a front for what was, even then, a predominantly anti-revisionist group. While some of their members were 'tankies' in the out and out pro-Moscow sense I'd argue many more had far more in common with Hoxhaists of the Bill Bland anti-Mao variety.

Lastly, the NCP's continuing joint work with the RCPB(M-L), who I can only assume no-one will deny are active within the Stalin Society, gives another indication. Again, supporting without a source I can give, but that was a forum where much of the idea of collaboration began.

Samchallis 14:46, 18 July 2005 (UTC)

You may have missed my point. While what you say is broadly correct the question is simply the participation of the NCP with the Stalin Society. When the Society was set up the NCP did advertise its meetings but broke with them when a veteran member was insulted by the then Chair of the Stalin Society, Prof Majid. Majid was subsequently banned from all NCP meetings. Though the NCP, including many of its leaders, maintained good personal relations with Bill Bland and to a very limited extent to Harpal Brar, the NCP has not had anything to do with the Stalin Society since Prof Majid's day. Once again I would not quibble with the general analysis you've made and perhaps this can be introduced into the text under the heading of "background" or "origins".

Fair enough. And indeed an incident I was previously unaware of. Thanks. Sam

Recent Amendments on splits etc: The NCP has dealt with more factions than those mentioned. All were very small with the exception of a right-wing split in 1980 and the North-West anti-party faction mentioned that had opposed the NCP's support for Ken Livingstone's candidature for the London Mayoral post. The Elizabeth Farrell entry was deleted because she first of all was not International Secretary but was London organiser and briefly a member of the Central Committee. Likewise Jim Hillier was only "editor" for one issue of the paper (the issue that led to his departure) though he was on the Central Committee. This para needs more work and maybe I'll try to find a form of words that takes this in as well as the deleted references. Pedant

There are rumours that Farrell really worked either the south Korean secret service,Mi6 or the CIA and worked to disrupt the NCP from within.Apparently she vanished,some believe that she is in Seoul!

Main Communist parties
It is factually accurate that the NCPB is one of the two main Communist parties. Warofdreams states of his reversion: "(revert POV "two main communist parties" - CPB(M-L), CPGB(PCC), and various Trotskyist groups would disagree)". This I disagree with. Firstly, Trotskyist groups do not refer to themselves as Communist parties (at least not in public). Secondly, both the CPB(M-L) and CPGB(PCC) are far smaller, and do not have relations with other parties generally recognised as Communist, or participate in the International Communist Movement as do both the NCPB and the CPB. It is true that the CPB(M-L) is an older organisation, but that does not make it one of the main ones. The CPGB(PCC) has only about 20 members.

I do not want to get into reverting and unreverting, but the point should be made that both the original text, and edit are factually accurate, and not just POV.

 * If you can find some reliable reference, I'd be happy to describe the NCPB as the second largest Communist party in Britain; you're probably right that the Trotskyist groups could be disregarded here.   But use of the term "main" is bound to be controversial - no doubt other groups would claim that they are a main communist party, because of their history, their influence, their principled positions or whatever.  Your original text also implies that there is a commonality between the CPB and the NCPB which is not shared by other communist parties in Britain.  If this is this case, it needs to be stated explicity, not just alluded to. Warofdreams talk 02:26, 23 May 2006 (UTC)

I think you are correct that the word "main" could be argued in terms of size, history, influence, position. Size is a difficult one as the NCPB do not publish membership figures, and the CPB exagerate theirs. Both are very small, but the CPB is marginally larger. The NCPB follows an anti-revisionist position, whilst the CPB would be generally regarded as being revisionist, or "crLeative" (depending on your POV). Both organisations, however, have relations with the ruling Communist Parties of Cuba, Vietnam, DPRK, etc. as well as the major Communist Parties of Greece, Cyprus, India, etc. I think that is a strong aguement for them being called the main Communist organisations in Britain, because both represent different parts of the mainstream international Communist movement.

By no means is the CPB marginally larger. It claims around 1,000 members while the NCP is most certainly under the 100 mark. That's quite a margin in my book. Troublemaker1973 (talk) 11:28, 10 October 2008 (UTC)

L-R-C Affiliation
There is no evidence of current LRC affilation

Grmdy 19:56, 10 October 2007 (UTC)

LRC Affiliation The NCP was an "associate affiliate" until November 2007 and became an "affiliate" following the rule changes made at the November 2007 annual meeting in London. The NCP is listed as an affiliate in the LRC's web page. —Preceding unsigned comment added by 86.152.122.86 (talk) 21:49, 19 November 2007 (UTC)

Recent changes
I have made some additions to the page regarding NCP membership, problems related to expulsions in the party, content of the "New Worker" and its discontinued publications. Someone obviously is a bit touchy about too many current facts about the NCP being on this page. Anyone who complains about this material not being sourced is talking out of the back of their head. When do communist parties publish membership figures in the public domain - the NCP certainly never has (we used to be told it was less than 10,000), so don't use that as an excuse to chop this newly added material again. If it is, I will just keep putting it back. —Preceding unsigned comment added by 221.222.195.135 (talk) 00:13, 22 September 2008 (UTC)

The CPB is the only communist party in Britain that publishes its membership. The NCP like the others does not and any estimate of membership can only be speculation which is not the role of wikipedia, nor is it the place for original research. —Preceding unsigned comment added by 81.129.140.147 (talk) 15:55, 22 September 2008 (UTC)

Constantly repetition doesn't make things true. Without sourcing it is merely hearsay. —Preceding unsigned comment added by 86.151.110.81 (talk) 12:59, 23 September 2008 (UTC)

Edit warring and sources
I'm coming in to point out that Wikipedia guidelines and policies require articles to be well sourced, and this one is badly sourced, one of the reasons so far as I can see for the current edit wars. I also notice that a lot of edit summaries are blank, and this really should stop. Also, a couple of editors are lucky they haven't been blocked for WP:3RR violations and can expect to be blocked if this continues. Doug Weller (talk) 11:38, 25 September 2008 (UTC)
 * Can I also point out that a large chunk of this article reads like an individuals biography rather than an article about a political party. Can I suggest that some of the editors here take a look at other wikipedia articles about Political parties and add more about election results?  Ϣere Spiel  Chequers  12:46, 25 September 2008 (UTC)

 * I've fully protected the article for 72 hours as a result of the edit war. Can the involved users come here to talk about it now?  lifebaka++ 14:53, 25 September 2008 (UTC)

This entry is indeed badly sourced and the few references that are given need to be relaid for easy reference. The major dispute with Troublemaker73 is over the unsourced statistics for membership which he claims is "common knowledge" amongst British communists and which amounts to nothing more than gossip. The only British communist party to publish its membership figures is the CPB, apart from the RCPB-ML which for electoral register purposes claims a membership of one. The CPB claims it is the biggest communist party in Britain and this is not challenged by any of the others which claim to be communist, including the NCPB. The NCPB refers to itself as "small" in its own documents and makes no other claims. This is the only neutral conclusion that can be drawn.

The question of the "purged" activists is clearly a point of view unless it can be sourced.

On the question of past publications and the content of the New Worker I have argued that if this is relevant then the content about the New Worker should go in the New Worker wiki entry. I cannot see the point of listing past publications thoug it is clear that Troublemaker73 knows very little about the NCPB because any one who cares to plough through the NCPB websites will see that there were at least two other bulletins or magazines that the NCPB published in the past (Irish Bulletin and an Economic Bulletin) and there may be more.

Borewatch (talk) 20:29, 25 September 2008 (UTC)

I am currently adding references as and when I have time. Hopefully this is helpful to improve the article. Sorry ... not an expert. Maybe WarofDreams or another Wiki person could help tidy up what I am doing. —Preceding unsigned comment added by 86.144.202.133 (talk) 15:17, 2 October 2008 (UTC)

I have refrained from doing anything other than adding references, and maintaining the article as it stands. Troublemaker1973 must discuss his repeated adding of unverifiable material here or I shall continue to delete it if no consensus can be found. Grauniad100 (talk) 15:16, 6 October 2008 (UTC)

I would like to remove the Original Research box at the top of the article if there is consensus on that. I think the items falling into that category have been removed - if not please discuss them here. Grauniad100 (talk) 11:32, 15 October 2008 (UTC)

Past publications
Dear "Borewatch", please tell us where these references to the NCP's past publications, such as the Irish Bulletin and Economic Bulletin, can be found. Troublemaker1973 (talk) 11:47, 27 September 2008 (UTC)

Cut and paste job
In fact, most of the material on the New Communist Party page is gleaned from old NCP publications and material on their websites -- a bit of an "inside job" if you ask me. The page should most certainly be nuked and replaced with something not so shoddy.Troublemaker1973 (talk) 11:53, 29 September 2008 (UTC)

Pamplets and books
I think it would be legitimate to put back the section of pamphlets that explain the ideology of the NCPB. I note that the Wiki CPB entry, quite rightly, lists its pamphlets, and so should the Wiki NCPB entry. —Preceding unsigned comment added by 86.152.40.129 (talk) 18:26, 1 October 2008 (UTC)

Semi-protected
Semi-protected for a week. I suspect the IP editor that I just reverted is a blocked editor (which is why the reversion). If other Admins feel it should be unprotected, and of course if they provide a rationale, that's fine by me. Doug Weller (talk) 16:59, 7 October 2008 (UTC)

Thank you Doug. I, and others, have requested Troublemeker1973 to discuss and provide sources for his persistant edits. He continues to ignore the requests. I am aware that more work needs to be done on this page, and hope this may be possible by consensus in the future. Grauniad100 (talk) 17:25, 7 October 2008 (UTC)

New Communist Review
Why did the New Communist Review cease publication when its editor died? Was there no one else in the NCP capable of editing a theoretical journal? Troublemaker1973 (talk) 11:26, 10 October 2008 (UTC)

Communist Parties in Europe
(editsemiprotected) I would like the Communist Parties in Europe box to be added at the bottom of the page - as appears on the bottom of the CPB page. Grauniad100 (talk) 19:48, 12 October 2008 (UTC)

Leadership or faction?
It's wrong to say a coup d'etat by "the leadership" if nine members of that the party's actual "leadership" (the central committee) were expelled for opposing the expulsions and closure of the North West District. The "leadership" was split down the middle on the issue (viz the one-vote majority), so it's more accurate to say that, in the view of those expelled, it was a move taken by a faction around general secretary Andy Brooks. Troublemaker1973 (talk) 02:46, 17 October 2008 (UTC)

Don't be so silly as to take out one thing you think is "POV" when it's slap bang next to something that could be regarded the same way. Grauniad100, you don't happen to be Andy Brooks do you? I can't imagine many other people would bother so much about you being named like this. Your "leadership" of the NCP has been an unmitigated disaster. Did you plan to make such a pig's breakfast of it when you took over or is all this just a result of blind incompetence? The NCP used to be a party worth being a member of, now it's just a joke. Troublemaker1973 (talk) 06:55, 17 October 2008 (UTC)

Wrong age, sex, size etc. In answer to your question ... No I am not Andy Brooks. I have been trying to maintain the status quo on this article until consensus can be acheived through rational discussion, and edit warring stops. I have added references, and stopped additional POV edits. I quite agree that your last edit removed a sentence that did not belong in a Wiki article. Maybe you could declare your interest in this article as it is obviously more personal than a general interest in the NCP? I am a regular reader of the New Worker (not a writer or employee), and have been for many years, and I am keen that the article should be accurate, sourced, and as unbiased as it is possible to be. I am quite happy to be guided by suggestions from neutral people about how the article should be improved within Wiki rules and standards. Your agressivness does make it difficult to have a reasoned discussion about changes needed to improve the article. Grauniad100 (talk) 09:52, 17 October 2008 (UTC)

It seems that Pembroke08 is Troublemaker1973 using a different account to pursue his personal vendetta and has no interest in improving the site - on the one hand he demands proof for things threatening deletion, and on the other adds assertions with no source of the assertion. —Preceding unsigned comment added by 86.144.206.181 (talk) 08:02, 21 October 2008 (UTC)

What "Pembroke08" and "Troublemaker1973" both have in common is that they know so little about the NCPB and they rarely trouble to even check references before making their spurious comments. I've referenced the last query concerning the NCPB's internal debate of revisionism by citing a document that can be easily accessed on the Web through Google. I've deleted the reference to Andy Brooks because his union activity in CPSA, TSSA, or in the CPGB before the NCPB was formed is irrelevant to this article. There may be a case for a seperate entry for Brooks but there's a greater one for Sid French whose role in the British communist movement spans a much greater period that the last two years of his life as leader of the NCPB. This would also help streamline and focus the main NCPB entry. If some of the regular contributors to British communist wiki entries like Warofdreams and Soman think this would be useful I could have a first stab at it. But I would like to read their comments first. Borewatch (talk) 10:01, 21 October 2008 (UTC)

I am not Pembroke08 Troublemaker1973 (talk) 09:44, 21 October 2008 (UTC)

I think the article would be improved if there was a separate piece on Sid French, I think he merits his own Wikipedia entry. Troublemaker1973 (talk) 11:55, 21 October 2008 (UTC)

Although I think it quite correct that there should be a separate entry for Sid French, his history is very relevent to the formation of the NCP and it's positions today. The most relevent elements should be kept within this article.

I would also agree with the idea for separate entries for people like Andy Brooks, and also Eric Trevett, and their backgrounds should only be part of this article insofar as it is relevent to the history and development of the NCP. For example ET's personal friendship with Kim Il Sung would be relevent to the history of the NCP (if it can be referenced), whilst AB's involvement with the satirical magazine, PFLCPSA, is not and should be in the new article instead. Grauniad100 (talk) 14:10, 21 October 2008 (UTC)

Correct headings
The reference to the New Worker and publications should not be under the Ideology heading as that is more appropriate for policies. Grauniad100 (talk) 06:21, 23 October 2008 (UTC)

In fact most of that section belongs above and a new Ideology section should be written. I am happy to colaborate if anyone volunteers. Grauniad100 (talk) 07:02, 23 October 2008 (UTC)

Resignations from CC over Livingstone vote
Did the resignations from the CC include Maisie Carter from Merton? When did Chas Fraser (one-time New Worker industrial editor) and Sue Fraser (former NCP chairperson) leave the party and what was the reason? —Preceding unsigned comment added by 123.123.5.206 (talk) 16:15, 25 May 2009 (UTC)

External links modified
Hello fellow Wikipedians,

I have just added archive links to 1 one external link on New Communist Party of Britain. Please take a moment to review my edit. If necessary, add after the link to keep me from modifying it. Alternatively, you can add to keep me off the page altogether. I made the following changes:
 * Added archive http://web.archive.org/web/20080907205451/http://www.lcdtu.co.uk/ to http://www.lcdtu.co.uk/

When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at ).

Cheers.—cyberbot II  Talk to my owner :Online 01:40, 19 March 2016 (UTC)

External links modified
Hello fellow Wikipedians,

I have just modified one external link on New Communist Party of Britain. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
 * Added archive https://web.archive.org/web/20080929055025/http://www.solidnet.org/redlink.html to http://www.solidnet.org/redlink.html

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

Cheers.— InternetArchiveBot  (Report bug) 08:11, 4 September 2017 (UTC)

External links modified
Hello fellow Wikipedians,

I have just modified one external link on New Communist Party of Britain. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
 * Added tag to http://www.osa.ceu.hu/files/holdings/300/8/3/text/135-4-162.shtml
 * Added archive https://web.archive.org/web/20090803122617/http://files.osa.ceu.hu/holdings/300/8/3/text/137-4-63.shtml to http://files.osa.ceu.hu/holdings/300/8/3/text/137-4-63.shtml
 * Added tag to http://www.osa.ceu.hu/files/holdings/300/8/3/text/142-1-568.shtml

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

Cheers.— InternetArchiveBot  (Report bug) 02:31, 11 December 2017 (UTC)

title: Talk:New Communist Party of Britain


text: Template:Tori Amos

title: Template:Tori Amos


text:
Furanose

A furanose is a collective term for carbohydrates that have a chemical structure that includes a five-membered ring system consisting of four carbon atoms and one oxygen atom. The name derives from its similarity to the oxygen heterocycle furan, but the furanose ring does not have double bonds.

Structural properties

The furanose ring is a cyclic hemiacetal of an aldopentose or a cyclic hemiketal of a ketohexose.

A furanose ring structure consists of four carbon and one oxygen atom with the anomeric carbon to the right of the oxygen. The highest numbered chiral carbon (typically to the left of the oxygen in a Haworth projection) determines whether or not the structure has a -configuration or L -configuration. In an -configuration furanose, the substituent on the highest numbered chiral carbon is pointed downwards out of the plane, and in a D -configuration furanose, the highest numbered chiral carbon is facing upwards.

The furanose ring will have either alpha or beta configuration, depending on which direction the anomeric hydroxy group is pointing. In a -configuration furanose, alpha configuration has the hydroxy pointing down, and beta has the hydroxy pointing up. It is the opposite in an -configuration furanose. Typically, the anomeric carbon undergoes mutarotation in solution, and the result is an equilibrium mixture of α and β configurations.

title: Furanose


text:
Bridger Mountains

The Bridger Mountains may refer to either of two mountain ranges in the United States:

 * Bridger Range (Montana)
 * Bridger Mountains (Wyoming)

title: Bridger Mountains


text:
Mutarotation

In stereochemistry, mutarotation is the change in optical rotation of a chiral material in a solution due to a change in proportion of the two constituent anomers (i.e. the interconversion of their respective stereocenters) until equilibrium is reached. Cyclic sugars show mutarotation as α and β anomeric forms interconvert. The optical rotation of the solution depends on the optical rotation of each anomer and their ratio in the solution.

Mutarotation was discovered by French chemist Augustin-Pierre Dubrunfaut in 1844, when he noticed that the specific rotation of aqueous sugar solution changes with time.

Measurement
The α and β anomers are diastereomers of each other and usually have different specific rotations. A solution or liquid sample of a pure α anomer will rotate plane polarised light by a different amount and/or in the opposite direction than the pure β anomer of that compound. The optical rotation of the solution depends on the optical rotation of each anomer and their ratio in the solution.

For example, if a solution of β- D -glucopyranose is dissolved in water, its specific optical rotation will be +18.7°. Over time, some of the β- D -glucopyranose will undergo mutarotation to become α- D -glucopyranose, which has an optical rotation of +112.2°. The rotation of the solution will increase from +18.7° to an equilibrium value of +52.7° as some of the β form is converted to the α form. The equilibrium mixture is about 64% of β- D -glucopyranose and about 36% of α- D -glucopyranose, though there are also traces of the other forms including furanoses and open chained form.

 * [[Image:Α- and β-D-glucopyranose.svg|500px|left]]

The observed rotation of the sample is the weighted sum of the optical rotation of each anomer weighted by the amount of that anomer present. Therefore, one can use a polarimeter to measure the rotation of a sample and then calculate the ratio of the two anomers present from the enantiomeric excess, as long as one knows the rotation of each pure anomer. One can monitor the mutarotation process over time or determine the equilibrium mixture by observing the optical rotation and how it changes.

Reaction mechanism

 * [[Image:generalmutamech.png|thumb|left|upright=2.5|Reaction mechanism for the interconversion of α and β anomers]]

title: Mutarotation


text:
Requirements analysis

In systems engineering and software engineering, requirements analysis focuses on the tasks that determine the needs or conditions to meet the new or altered product or project, taking account of the possibly conflicting requirements of the various stakeholders, analyzing, documenting, validating, and managing software or system requirements.

Requirements analysis is critical to the success or failure of a systems or software project. The requirements should be documented, actionable, measurable, testable, traceable, related to identified business needs or opportunities, and defined to a level of detail sufficient for system design.

Overview
Conceptually, requirements analysis includes three types of activities:
 * Eliciting requirements: (e.g. the project charter or definition), business process documentation, and stakeholder interviews. This is sometimes also called requirements gathering or requirements discovery.
 * Recording requirements: Requirements may be documented in various forms, usually including a summary list, and may include natural-language documents, use cases, user stories, process specifications, and a variety of models including data models.
 * Analyzing requirements: determining whether the stated requirements are clear, complete, unduplicated, concise, valid, consistent and unambiguous, and resolving any apparent conflicts. Analyzing can also include sizing requirements.

Requirements analysis can be a long and tiring process during which many delicate psychological skills are involved. New systems change the environment and relationships between people, so it is important to identify all the stakeholders, take into account all their needs, and ensure they understand the implications of the new systems. Analysts can employ several techniques to elicit the requirements from the customer. These may include the development of scenarios (represented as user stories in agile methods), the identification of use cases, the use of workplace observation or ethnography, holding interviews, or focus groups (more aptly named in this context as requirements workshops, or requirements review sessions) and creating requirements lists. Prototyping may be used to develop an example system that can be demonstrated to stakeholders. Where necessary, the analyst will employ a combination of these methods to establish the exact requirements of the stakeholders, so that a system that meets the business needs is produced. Requirements quality can be improved through these and other methods:
 * Visualization. Using tools that promote better understanding of the desired end-product such as visualization and simulation.
 * Consistent use of templates. Producing a consistent set of models and templates to document the requirements.
 * Documenting dependencies. Documenting dependencies and interrelationships among requirements, as well as any assumptions and congregations.

Stakeholder identification
See Stakeholder analysis for a discussion of people or organizations (legal entities such as companies, and standards bodies) that have a valid interest in the system. They may be affected by it either directly or indirectly.

A major new emphasis in the 1990s was a focus on the identification of stakeholders. It is increasingly recognized that stakeholders are not limited to the organization employing the analyst. Other stakeholders will include:
 * anyone who operates the system (normal and maintenance operators)
 * anyone who benefits from the system (functional, political, financial, and social beneficiaries)
 * anyone involved in purchasing or procuring the system. In a mass-market product organization, product management, marketing, and sometimes sales act as surrogate consumers (mass-market customers) to guide the development of the product.
 * organizations that regulate aspects of the system (financial, safety, and other regulators)
 * people or organizations opposed to the system (negative stakeholders; see also Misuse case)
 * organizations responsible for systems that interface with the system under design.
 * those organizations that integrate horizontally with the organization for whom the analyst is designing the system.

Joint Requirements Development (JRD) Sessions
Requirements often have cross-functional implications that are unknown to individual stakeholders and often missed or incompletely defined during stakeholder interviews. These cross-functional implications can be elicited by conducting JRD sessions in a controlled environment, facilitated by a trained facilitator (Business Analyst), wherein stakeholders participate in discussions to elicit requirements, analyze their details, and uncover cross-functional implications. A dedicated scribe should be present to document the discussion, freeing up the Business Analyst to lead the discussion in a direction that generates appropriate requirements that meet the session objective.

JRD Sessions are analogous to Joint Application Design Sessions. In the former, the sessions elicit requirements that guide design, whereas the latter elicit the specific design features to be implemented in satisfaction of elicited requirements.

Contract-style requirement lists
One traditional way of documenting requirements has been contract-style requirement lists. In a complex system such requirements lists can run hundreds of pages long.

An appropriate metaphor would be an extremely long shopping list. Such lists are very much out of favor in modern analysis; as they have proved spectacularly unsuccessful at achieving their aims; but they are still seen to this day.

Strengths

 * Provides a checklist of requirements.
 * Provide a contract between the project sponsor(s) and developers.
 * For a large system can provide a high level description from which lower-level requirements can be derived.

Weaknesses

 * Such lists can run to hundreds of pages. They are not intended to serve as a reader-friendly description of the desired application.
 * Such requirements lists abstract all the requirements and so there is little context. The Business Analyst may include context for requirements in accompanying design documentation.
 * This abstraction is not intended to describe how the requirements fit or work together.
 * The list may not reflect relationships and dependencies between requirements. While a list does make it easy to prioritize each item, removing one item out of context can render an entire use case or business requirement useless.
 * The list does not supplant the need to review requirements carefully with stakeholders to gain a better-shared understanding of the implications for the design of the desired system/application.
 * Simply creating a list does not guarantee its completeness. The Business Analyst must make a good faith effort to discover and collect a substantially comprehensive list and rely on stakeholders to point out missing requirements.
 * These lists can create a false sense of mutual understanding between the stakeholders and developers; Business Analysts are critical to the translation process.
 * It is almost impossible to uncover all the functional requirements before the process of development and testing begins. If these lists are treated as an immutable contract, then requirements that emerge in the Development process may generate a controversial change request.

Alternative to requirement lists
As an alternative to requirement lists, Agile Software Development uses User stories to suggest requirements in everyday language.

Measurable goals
Best practices take the composed list of requirements merely as clues and repeatedly ask "why?" until the actual business purposes are discovered. Stakeholders and developers can then devise tests to measure what level of each goal has been achieved thus far. Such goals change more slowly than the long list of specific but unmeasured requirements. Once a small set of critical, measured goals has been established, rapid prototyping and short iterative development phases may proceed to deliver actual stakeholder value long before the project is half over.

Prototypes
A prototype is a computer program that exhibits a part of the properties of another computer program, allowing users to visualize an application that has not yet been constructed. A popular form of prototype is a mockup, which helps future users and other stakeholders get an idea of what the system will look like. Prototypes make it easier to make design decisions because aspects of the application can be seen and shared before the application is built. Major improvements in communication between users and developers were often seen with the introduction of prototypes. Early views of applications led to fewer changes later and hence reduced overall costs considerably.

Prototypes can be flat diagrams (often referred to as wireframes) or working applications using synthesized functionality. Wireframes are made in a variety of graphic design documents, and often remove all color from the design (i.e. use a greyscale color palette) in instances where the final software is expected to have a graphic design applied to it. This helps to prevent confusion as to whether the prototype represents the final visual look and feel of the application.

Use cases
A use case is a structure for documenting the functional requirements for a system, usually involving software, whether that is new or being changed. Each use case provides a set of scenarios that convey how the system should interact with a human user or another system, to achieve a specific business goal. Use cases typically avoid technical jargon, preferring instead the language of the end-user or domain expert. Use cases are often co-authored by requirements engineers and stakeholders.

Use cases are deceptively simple tools for describing the behavior of software or systems. A use case contains a textual description of how users are intended to work with the software or system. Use cases should not describe the internal workings of the system, nor should they explain how that system will be implemented. Instead, they show the steps needed to perform a task without sequential assumptions.

Requirements specification
Requirements specification is the synthesis of discovery findings regarding current state business needs and the assessment of these needs to determine, and specify, what is required to meet the needs within the solution scope in focus. Discovery, analysis, and specification move the understanding from a current as-is state to a future to-be state. Requirements specification can cover the full breadth and depth of the future state to be realized, or it could target specific gaps to fill, such as priority software system bugs to fix and enhancements to make. Given that any large business process almost always employs software and data systems and technology, requirements specification is often associated with software system builds, purchases, cloud computing strategies, embedded software in products or devices, or other technologies. The broader definition of requirements specification includes or focuses on any solution strategy or component, such as training, documentation guides, personnel, marketing strategies, equipment, supplies, etc.

Types of requirements
Requirements are categorized in several ways. The following are common categorizations of requirements that relate to technical management:

Business requirements
Statements of business level goals, without reference to detailed functionality. These are usually high-level (software and/or hardware) capabilities that are needed to achieve a business outcome.

Customer requirements
Statements of fact and assumptions that define the expectations of the system in terms of mission objectives, environment, constraints, and measures of effectiveness and suitability (MOE/MOS). The customers are those that perform the eight primary functions of systems engineering, with special emphasis on the operator as the key customer. Operational requirements will define the basic need and, at a minimum, answer the questions posed in the following listing:
 * Operational distribution or deployment: Where will the system be used?
 * Mission profile or scenario: How will the system accomplish its mission objective?
 * Performance and related parameters: What are the critical system parameters to accomplish the mission?
 * Utilization environments: How are the various system components to be used?
 * Effectiveness requirements: How effective or efficient must the system be in performing its mission?
 * Operational life cycle: How long will the system be in use by the user?
 * Environment: What environments will the system be expected to operate in an effective manner?

Architectural requirements
Architectural requirements explain what has to be done by identifying the necessary systems architecture of a system.

Structural requirements
Structural requirements explain what has to be done by identifying the necessary structure of a system.

Behavioral requirements
Behavioral requirements explain what has to be done by identifying the necessary behavior of a system.

Functional requirements
Functional requirements explain what has to be done by identifying the necessary task, action or activity that must be accomplished. Functional requirements analysis will be used as the toplevel functions for functional analysis.

Non-functional requirements
Non-functional requirements are requirements that specify criteria that can be used to judge the operation of a system, rather than specific behaviors.

Performance requirements
The extent to which a mission or function must be executed; is generally measured in terms of quantity, quality, coverage, timeliness, or readiness. During requirements analysis, performance (how well does it have to be done) requirements will be interactively developed across all identified functions based on system life cycle factors; and characterized in terms of the degree of certainty in their estimate, the degree of criticality to the system success, and their relationship to other requirements.

Design requirements
The "build to", "code to", and "buy to" requirements for products and "how to execute" requirements for processes are expressed in technical data packages and technical manuals.

Derived requirements
Requirements that are implied or transformed from higher-level requirements. For example, a requirement for long-range or high speed may result in a design requirement for low weight.

Allocated requirements
A requirement is established by dividing or otherwise allocating a high-level requirement into multiple lower-level requirements. Example: A 100-pound item that consists of two subsystems might result in weight requirements of 70 pounds and 30 pounds for the two lower-level items.

Well-known requirements categorization models include FURPS and FURPS+, developed at Hewlett-Packard.

Stakeholder issues
Steve McConnell, in his book Rapid Development, details a number of ways users can inhibit requirements gathering: This may lead to the situation where user requirements keep changing even when system or product development has been started.
 * Users do not understand what they want or users do not have a clear idea of their requirements
 * Users will not commit to a set of written requirements
 * Users insist on new requirements after the cost and schedule have been fixed
 * Communication with users is slow
 * Users often do not participate in reviews or are incapable of doing so
 * Users are technically unsophisticated
 * Users do not understand the development process
 * Users do not know about present technology

Engineer/developer issues
Possible problems caused by engineers and developers during requirements analysis are:
 * A natural inclination towards writing code can lead to implementation beginning before the requirements analysis is complete, potentially resulting in code changes to meet actual requirements once they are known.
 * Technical personnel and end-users may have different vocabularies. Consequently, they may wrongly believe they are in perfect agreement until the finished product is supplied.
 * Engineers and developers may try to make the requirements fit an existing system or model, rather than develop a system specific to the needs of the client.

Attempted solutions
One attempted solution to communications problems has been to employ specialists in business or system analysis.

Techniques introduced in the 1990s like prototyping, Unified Modeling Language (UML), use cases, and agile software development are also intended as solutions to problems encountered with previous methods.

Also, a new class of application simulation or application definition tools has entered the market. These tools are designed to bridge the communication gap between business users and the IT organization — and also to allow applications to be 'test marketed' before any code is produced. The best of these tools offer:
 * electronic whiteboards to sketch application flows and test alternatives
 * ability to capture business logic and data needs
 * ability to generate high-fidelity prototypes that closely imitate the final application
 * interactivity
 * capability to add contextual requirements and other comments
 * ability for remote and distributed users to run and interact with the simulation

title: Requirements analysis


text:
USS Lunga Point

USS Lunga Point (CVE-94), originally named Alazon Bay, was a Casablanca-class escort carrier of the United States Navy. It was named for Lunga Point on the northern coast of Guadalcanal, the site of a naval battle during World War II. The ship notably participated in support of the landings on Iwo Jima and Okinawa. Post war, the ship was decommissioned in 1946, before becoming part of the Pacific Reserve Fleet. In 1960, the ship was struck from the Navy list and broken up.

Design and description

Lunga Point was a Casablanca-class escort carrier, the most numerous type of aircraft carriers ever built, and designed specifically to be mass-produced using prefabricated sections, in order to replace heavy early war losses. Standardized with her sister ships, she was 512 ft long overall, had a beam of 65 ft, and a draft of 20 ft. She displaced 8188 LT standard, 10902 LT with a full load. She had a 257 ft long hangar deck, a 477 ft long flight deck. She was powered with two Uniflow reciprocating steam engines, which provided a force of 9000 hp, driving two shafts, enabling her to make. The ship had a cruising range of 10240 nmi, assuming that she traveled at a constant speed of 15 kn. Her compact size necessitated the installment of an aircraft catapult at her bow end, and there were two aircraft elevators to facilitate movement of aircraft between the flight and hangar deck: one on the fore, another on the aft.

One 5 in /38-caliber dual-purpose gun was mounted on the stern, and she was equipped with 16 Bofors 40 mm anti-aircraft guns in twin mounts, as well as 12 Oerlikon 20 mm cannons, which were used in an anti-aircraft capability. By the end of the war, Casablanca-class carriers had been modified to carry 30 20 mm cannons, as a response to increasing casualties due to kamikaze attacks. Anti-aircraft guns were mounted around the perimeter of the deck. Casablanca-class escort carriers were designed to carry 27 aircraft, but she sometimes went over or under this number. For example, during the Philippines campaign, she carried 14 FM-2 fighters and 12 TBM-3 torpedo bombers, for a total of 26 aircraft. However, during the Iwo Jima campaign and the Okinawa campaign, she carried 18 FM-2 fighters, 11 TBM-3 torpedo bombers, and a TBM-3P reconnaissance plane, for a total of 30 aircraft.

Construction
Her construction was awarded to Kaiser Shipbuilding Company, Vancouver, Washington, under a Maritime Commission contract, on 18 June 1942, under the name Alazon Bay (a misspelling of Alazan Bay, located in Kleberg County, Texas, as part of a tradition which named escort carriers after bays or sounds). She was laid down on 19 January 1944 under a Maritime Commission contract, MC hull 1131, by Kaiser Shipbuilding Company of Vancouver, Washington. She was launched on 11 April 1944; sponsored by Mrs. Mary Elizabeth McKay. She was renamed Lunga Point, and was transferred to the United States Navy and commissioned on 14 May 1944, Captain G. A. T. Washburn in command.

World War II
Following a period of brief training in the months following her commissioning, Lunga Point sailed for the Pacific to ferry United States Army bombers to New Guinea and to bring damaged P-47 Thunderbolts back to the United States. Upon return, she became a unit of Carrier Division 29 (CarDiv 29), a component of Admiral Thomas C. Kinkaid's 7th Fleet, alongside her fellow sister ships USS Makin Island (CVE-93), USS Bismarck Sea (CVE-95), USS Salamaua (CVE-96), and USS Hoggatt Bay (CVE-75). She departed San Diego, California, on 16 October to participate in the Leyte Gulf operations, touching Pearl Harbor, Eniwetok, and Kossol Roads en route. From 13 to 22 November, she provided air cover for transports and surface units engaged in the campaign. Relieved on the 23rd, she sailed to Manus Island, Admiralty Islands, to prepare for the Luzon campaign.

Philippine Sea
Lunga Point sailed on 27 December from Manus to supply air support for 6th Army landing operations at Lingayen Gulf. En route, on 4 January 1945, at 17:00, approximately 15 Japanese planes were picked up on radar, 45 mi west of the task group, and approaching quickly. These planes split into two groups, one group heading towards the rear of the task group, whilst the other continued on its course towards the center. Albeit fighters from the carrier group was scrambled, false radar signals hampered their efforts to intercept, and the only successful interception was when P-47 fighters intercepted two enemy planes, shooting down one. The other plane escaped, and is believed to be the kamikaze which would attack USS Ommaney Bay (CVE-79). A lack of radar contacts led the task group to believe that the enemy planes had called off their attack.

At 17:12, a Yokosuka P1Y dove onto Ommaney Bay, rupturing the fire mains and sparking a fire which quickly became untenable. She quickly sank, with the loss of 95 crewmen. Minutes after Ommaney Bay was hit, a second kamikaze dove towards Lunga Point. Gunners on the battleship USS California (BB-44) and cruiser USS Portland (CA-33), joined with anti-aircraft fire on Lunga Point, tore the kamikaze apart. The flaming wreckage passed over her, about a hundred feet above her stern, showering her deck with metal fragments, which slightly wounded two men.

For the next few days, her task group fought their way through 14 enemy attacks, the majority of them kamikazes, most of which were repelled through excellent fighter cover and anti-aircraft fire. During this running engagement, USS Louisville (CA-28), USS Stafford (DE-411), and USS Manila Bay (CVE-61) were all damaged by kamikazes. She arrived off Lingayen Gulf on 6 January, commencing 11 days of intensive air support during which time her aircraft flew an average of 41 sorties a day. On 17 January, the support carriers were withdrawn and returned to Ulithi.

Iwo Jima
From 23 January 1945 to 10 February, Lunga Point prepared for the invasion of Iwo Jima, and stood off the beaches with the amphibious forces, acting as target coordinators and striking enemy positions during the landings on 19 February.

On 16 February 1945, Vice-Admiral Kimpei Teroaka authorized the formation of a kamikaze special attack unit to counter the imminent landings on Iwo Jima. The kamikaze force consisted of twelve fighters, twelve carrier bombers, and eight torpedo bombers, divided into five groups, thirty-two aircraft in total. On the early morning of 21 February, they departed from Katori Naval Air Base, in Asahi, Chiba. They refueled at Hachijō-jima, and then proceeded towards the U.S. naval contingent surrounding Iwo Jima, arriving near sunset.

On the evening of 21 February, Lunga Point was performing routine close air support with the rest of Task Group 77.4. At the time, the escort carrier task group consisted of Lunga Point, her sister ships Bismarck Sea, Makin Island, USS Saginaw Bay (CVE-82), USS Rudyerd Bay (CVE-81), and USS Anzio (CVE-57), along with a destroyer contingent. The task group was steaming approximately 21 mi east of Iwo Jima. At 18:45, the task group spotted the Japanese planes headed for them, when a Mitsubishi G4M made a dive towards Lunga Point. Gunners from Bismarck Sea shot it down. At 18:46, five Nakajima B6Ns dove towards Lunga Point. The first plane, approaching from the starboard missed with its torpedo, passing harmlessly in front of Lunga Point. It subsequently crashed into the ocean at a high velocity. The second plane also missed with its torpedo, but managed to disengage and fly away. The third plane also missed with its torpedo, which proceeded behind the stern, and, set aflame and damaged heavily, attempted to crash into the carrier, approaching from the starboard side. The kamikaze exploded before it could hit the ship, and the wreckage of the plane skidded across the deck, and off the side of the carrier, sparking a brief gasoline fire. The fourth plane detonated in mid-air, due to a direct hit from a 5 in anti-aircraft shell. The fifth plane switched targets to Bismarck Sea, sinking it with the loss of 318 lives. Damage to Lunga Point was minimal, and eleven of her crew was wounded. There were no fatalities. She was able to continue operating in support of troops on Iwo Jima.

The special attack unit, in addition to sinking Bismarck Sea, also heavily damaged USS Saratoga (CV-3), USS Keokuk (CMc-6), and slightly damaged Lunga Point, USS LST-477, and USS LST-809. Bismarck Sea was the only ship to sink as a result of the attacks. The kamikaze attacks killed 43 Japanese in total.

She supported operations on Iwo Jima until 8 March, when land-based planes were present in sufficient strength to allow the ship to return to Ulithi to get ready for the Okinawa campaign. When Lunga Point returned to Ulithi, she only had six bombs left in her magazine, having dropped 596 in support of operations on Iwo Jima.

Okinawa
The ship re-provisioned, and on 21 March sortied from Ulithi with Rear Admiral Clifton Sprague's Task Unit. Three days later, on 24 March, she, along with her task group, arrived south of Kerama Retto, providing air cover and bombing targets throughout Okinawa. On 2 April, several kamikazes attempted to strike Lunga Point, all of them being shot down before they came close. However, several transports were damaged and the destroyer USS Dickerson (DD-157) was heavily damaged in the attack, subsequently being scuttled on 4 April. On 3 April, whilst making a turn, Lunga Point rolled 23 degrees, flinging an FM-2 Wildcat and a lookout off the deck. The lookout was quickly recovered. Lunga Point remained in support of the operation providing air cover, pounding enemy ground targets in the Ryukyu Islands and fighting off constant kamikaze attacks. She completed this duty without mishap, and returned to Leyte on 27 June.

This was followed by a minesweeping operation west of Okinawa in early July, and on 1 August, she departed on an anti-shipping sweep along the Chinese coast from Shanghai northward. On 5 August, Wildcats from Lunga Point downed a Yokosuka P1Y, the last recorded kill by a Wildcat, which had, in the service of escort carriers, shot down a recorded total of 422 Japanese aircraft. On 6 August, an air contingent was sent to attack Japanese installations near Tinghai Harbor, southeast of Shanghai, including an airfield. On 7 August, further strikes were deemed unproductive, and she sailed to Buckner Bay, Okinawa, where she received news of the Japanese peace offerings on 15 August.

Postwar
In late August the ship, attached to the 5th Fleet, aided in repatriating Allied prisoners of war (POWs) from the ports of Wakayama and Nagasaki. On 15 September, she arrived, steered through Japanese minefields, in the port of Wakayama. On 19 September she transported 760 men of various nationalities to Okinawa. The captain was obliged to assign two men to a bunk to accommodate the ex-POWs. She then unloaded her cargo in Manila harbor. She was ordered to Tokyo Bay in early October, and en route took part in the unsuccessful search for Rear Admiral W. D. Sample missing in a PBM Mariner on a patrol flight. Lunga Point stood out of Tokyo Bay 28 October, and arrived at Pearl Harbor on 7 November. She sailed to San Diego arriving on 15 November, and made voyages to the Pacific before returning to the west coast early in 1946.

On 24 October 1946, the ship was decommissioned and became part of the Pacific Reserve Fleet, Tacoma, Pacific Reserve Fleet. She was reclassified CVU-94 on 12 June 1955 and AKV-32 on 7 May 1959. She was struck from the Navy list on 1 April 1960, and sold at San Diego to Hyman Michaels Co. on 25 July 1960. Later in the year, she was broken up in Japan.

title: USS Lunga Point


text:
Talk:Son Byong-hi

Style improvements
If anyone's reading this in future, the article is currently a wall of text that's hard to parse.

Recommend splitting it up into smaller paragraphs that are focused on tighter subjects and adding images to improve understanding and break up the wall. toobigtokale (talk) 03:57, 19 June 2023 (UTC)

title: Talk:Son Byong-hi