text:
Superior oblique muscle

The superior oblique muscle or obliquus oculi superior is a fusiform muscle originating in the upper, medial side of the orbit (i.e. from beside the nose) which abducts, depresses and internally rotates the eye. It is the only extraocular muscle innervated by the trochlear nerve (the fourth cranial nerve).

Structure
The superior oblique muscle loops through a pulley-like structure (the trochlea of superior oblique) and inserts into the sclera on the posterotemporal surface of the eyeball. It is the pulley system that gives superior oblique its actions, causing depression of the eyeball despite being inserted on the superior surface. The superior oblique arises immediately above the margin of the optic foramen, superior and medial to the origin of the superior rectus, and, passing forward, ends in a rounded tendon, which plays in a fibrocartilaginous ring or pulley attached to the trochlear fossa of the frontal bone.

The contiguous surfaces of the tendon and ring are lined by a delicate mucous sheath, and enclosed in a thin fibrous investment.

The tendon is reflected caudally, laterally, and inferiorly beneath the superior rectus to the lateral part of the bulb of the eye, and is inserted onto the scleral surface, behind the equator of the eyeball, the insertion of the muscle lying between the superior rectus and lateral rectus.

Function
The primary (main) action of the superior oblique muscle is intorsion (internal rotation), the secondary action is depression (primarily in the adducted position) and the tertiary action is abduction (lateral rotation).

The extraocular muscles rotate the eyeball around vertical, horizontal and antero-posterior axes. Extraocular muscles other than the medial rectus and lateral rectus have more than one action due to the angle they make with the optical axis of the eye while inserting into the eyeball. The superior and inferior oblique muscles make an angle of 51 degrees with the optical axis.

The depressing action of superior oblique (making the eye look down towards the mouth) is most effective when the eye is in an adducted position. This is because as the eye is abducted (looks laterally), the contribution made by superior oblique to depression of the eye decreases, as the inferior rectus muscle causes this movement more directly and powerfully. The main muscle for abduction is the lateral rectus, so although superior oblique contributes to a downwards and lateral eye movement, testing this motion would not be specific enough as inferior and lateral recti muscles would also be tested. Therefore, during neurological examinations, the superior oblique is tested by having the patient look inwards and downwards, testing only the depressing action of the muscle. This is a source of confusion on the subject as although clinical testing asks the patient to adduct and depress the eye, anatomically the muscle depresses and abducts it.

The great importance of intorsion and extorsion produced by the two oblique muscles can only be understood when it is considered with regards to the other muscle actions present. The two obliques prevent the eye from rotating about its long axis (retina to pupil) when the superior and inferior rectus muscles contract. This is because the orbit does not face directly forwards- the centre-line of the orbit is a little over 20 degrees out from the mid-line. But because the eyes do face forwards, when acting alone, as well as making the eye look up, superior rectus causes it to rotate slightly about the long axis, so the top of the eye moves medially (intorsion). Similarly, in addition to making the eye look down, inferior rectus would cause the eye to rotate about the long axis so the top of the eye moves slightly laterally (extorsion), if acting alone. Clearly this is undesirable as our vision would rotate when we looked up and down. For this reason, these two rectus muscles work in conjunction with the two obliques. When acting alone, superior oblique causes intorsion, inferior oblique, extorsion. Hence, when inferior rectus contracts so we look down, superior oblique also contracts to prevent extorsion of the eye, and when superior rectus contracts so we look up, inferior oblique contracts to prevent intorsion, thus the undesired rotatory actions of the inferior and superior recti about the long axis of the eye are cancelled out. This keeps our vision horizontally level, irrespective of eye position in the orbit.

Clinical significance
Superior oblique palsy is a common complication of closed head trauma. Restriction of superior oblique relaxation movement due to an inelastic tendon is found in Brown syndrome, leading to difficulty elevating the eye in the adducted position.

Superior oblique myokymia is an uncommon neurological condition caused by vascular compression of the trochlear nerve resulting in repeated, brief, involuntary episodes of movement of the eye.

Surgical operations of the superior oblique include tenotomy, recession, silicone expander lengthening, split tendon lengthening, tucking, and the Harada-Ito procedure.

title: Superior oblique muscle


text:
Lamé (fencing)

In modern fencing, a lamé is an electrically conductive jacket worn by foil and sabre fencers in order to define the scoring area and register contact with it. Lamés are wired by use of a body cord to a scoring machine, which allows the other person's weapon to register touches when their tips (or blades, in sabre) contact the lamé.

Lamés generally consist of a polyester jacket overlain with a thin, interwoven metal, usually steel or copper. This gives the lamés a metallic, gray appearance, but colored foil lamés have become increasingly popular. Lamés used in higher-level competitions usually have the last name and country of their owner printed in blue across the back.

Because the scoring area is different for each weapon, the lamé may cover more or less of the body depending on which weapon the fencer uses. In foil, the lamé extends on the torso from the shoulders to the groin area, including the back. In sabre, the lamé covers both arms, the torso from the shoulders to the waist, and the back. In addition, sabre fencers wear masks that allow them to register head touches, and manchettes, which are conductive glove covers, on their weapon hand. A lamé is not required in épée, since the target in épée is the whole body.

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

title: Lamé (fencing)


text:
Regional assembly (England)

The regional chambers of England were a group of indirectly elected regional bodies that were created by the provisions of the Regional Development Agencies Act 1998. There were eight regional chambers, one for each of the regions of England except Greater London, which had opted for an elected mayor and assembly in 1998. All eight regional chambers had adopted the title "regional assembly" or "assembly" as part of their name, though this was not an official status in law. The chambers were abolished over a two-year period between 31 March 2008 and 31 March 2010 and some of their functions were assumed by newly established local authority leaders' boards.

Greater London has a directly elected London Assembly, which was established by separate legislation and is part of the Greater London Authority.

Role
Their original defined role was to channel regional opinions to the business-led regional development agencies. Their role later included scrutinising their regional development agency; integrating policy development and enhancing partnership working at the regional level across the social, economic and environmental policy agenda; as well as carrying out a wide range of advocacy and consultancy roles with UK government bodies and the European Union; but their public profile was low. Each acted as a regional planning body with a duty to formulate a regional spatial strategy including regional transport strategy, replacing the planning function of county councils.

Membership
The eight regional chambers as defined by the Regional Development Agencies Act 1998 were not directly elected. About two-thirds of assembly members were appointees from the county and district councils and unitary authorities in each region, the remaining one-third were appointees from other regional interest groups.

The London Assembly is part of a wider Greater London Authority and has 25 directly elected members. Its role is defined in the Greater London Authority Act 1999.

The regional chambers
There was some inconsistency in the naming of the individual assemblies. Each chamber adopted either "regional assembly" or "assembly":
 * East of England Regional Assembly (abolished March 2010)
 * East Midlands Regional Assembly (abolished March 2010)
 * North East Assembly (abolished March 2009)
 * North West Regional Assembly (abolished June 2008)
 * South East England Regional Assembly (abolished March 2009)
 * South West Regional Assembly (abolished May 2009)
 * West Midlands Regional Assembly (abolished March 2010)
 * Yorkshire and Humber Assembly (abolished March 2009)

The London Assembly was established as a directly elected body by separate legislation and is part of the Greater London Authority. It continues to exist after the abolition of the eight regional chambers.

Each assembly corresponded to a region of England.

Plans for elected regional assemblies
In May 2002, the then Labour UK government published a white paper, Your Region, Your Choice, outlining its plans for the possible establishment of Elected Regional Assemblies. These assemblies were to be responsible for regional strategies dealing with sustainable development, economic development, spatial planning, transport, waste, housing, culture (including tourism) and biodiversity. They would be funded primarily by central government grant, with powers to raise additional funds from a precept (demand for payment) on the council tax.

The Assemblies were expected to be elected by an Additional Member System similar to those used for the London Assembly, the Scottish Parliament and the National Assembly for Wales. The Regional Assemblies (Preparations) Act 2003 made provisions for referendums to be held to create such assemblies, and to simplify the structure of local government where this is done. Three such referendums were planned, for the regions of North East and North West England and Yorkshire and the Humber.

On 12 February 2004, Local Government Minister Nick Raynsford announced that elected Assemblies would be able to direct local authorities to refuse strategic planning applications that are not in the region's best interest. They would be able to look across local boundary constraints and ensure planning decisions are made with region-wide interests taken into account. On 8 July 2004, it was announced that the referendums would be held on 4 November, but on 22 July Raynsford announced that only the North East England vote would go ahead on that date. This region was chosen because the government thought it was the most likely to approve the proposal.

However, the voters rejected the assembly by 696,519 votes to 197,310, or about 78 percent to 22 percent. This overwhelmingly negative vote was seen as an insurmountable obstacle to elected regional assemblies elsewhere in England outside London. On 8 November, Deputy Prime Minister John Prescott told the House of Commons he would not move orders for the other two regions within the effective time limit of June 2005 permitted by the Act.

The 'no' vote by the North East also affected the Labour Government's attempt to address the West Lothian question, because the government had canvassed regional assemblies as a partial solution to this anomaly.

The English Regions Network (ERN) was the umbrella organisation for England's eight partnership Regional Assemblies. While the London Assembly worked with ERN on some issues it was not a full member of the Network.

Structure and powers of the proposed assemblies
The Deputy Prime Minister John Prescott presented a Draft Regional Assemblies Bill to Parliament in July 2004. The bill outlined the structure of the proposed assemblies and defined their powers.

The draft bill proposed the following structure:
 * The assembly would be a body corporate with a distinct legal identity.
 * Each assembly would be composed of between 25 and 35 assembly members elected by the Additional Member System.
 * The assembly would select one member as the Chairman and another as Deputy Chairman to preside over its debates.
 * The assembly would have an Executive (cabinet) composed of a Leader and between two and six Executive Members.

The draft bill would have given the assemblies the following powers:
 * Promotion of economic development
 * Promotion of social development
 * Promote health, safety and security of the community
 * Reduce health inequalities
 * Enhance individual participation in society
 * Improve the availability of good housing
 * Improve skills and the availability of training
 * Improve the availability of cultural and recreational activities
 * Improvement and protection of the environment
 * Additional functions and duties that the Secretary of State thinks appropriate

Abolition and replacement
On 17 July 2007 the UK government published the Review of Sub-National Economic Development and Regeneration. The review brought forward the Government's plans to alter the structure of regional governance in England known as the Single Regional Strategy. The impact of the review was that the regional assemblies in their current form and function would not continue and that the regional development agencies were given executive responsibility for developing the single regional strategy.

The regional chambers were abolished between 2008 and 2010 with their executive functions transferring to the regional development agencies. Local authorities were given an increased role in scrutiny at the regional level including scrutiny of regional strategies and the RDAs through participation in new local authority leaders' boards which were established in each region. The two bodies would jointly produce new single regional strategies, with Ministers exercising an oversight function.

Local authority leaders' boards
Following the abolition of the regional chambers, smaller local authority leaders' boards took over responsibilities for scrutiny of RDAs and single regional plans.

The first local authority leaders' board, 4NW, was established in July 2008 and others were formed once the regional chamber for that region was abolished. By April 2010, eight leaders' boards had been established.

In June 2010, the new Conservative-Liberal Democrat coalition government announced plans to remove funding from the new boards and to remove their statutory functions. The boards may continue as voluntary associations of council leaders. Regional development agencies were abolished on 31 March 2012, with their functions being taken over by smaller local enterprise partnerships which are not based on regional boundaries.

Cornish Assembly
In Cornwall, there was opposition to the South West Regional Assembly and the South West Regional Development Agency. A campaign for a Cornish Assembly had been running since July 2000, and attracted the support of a petition signed by 50,000 Cornish residents and visitors, which was presented to 10 Downing Street on 12 December 2001. The campaign had the support of all five Cornish Liberal Democrats MPs, Mebyon Kernow and others; they stated that the SW regional assembly was undemocratic and unaccountable, and believed Cornwall should be able to take decisions about local services in its own directly elected and accountable assembly.

Merseyside Assembly
In July 2004, five Merseyside MPs, led by George Howarth MP, launched a Manifesto for Merseyside which proposed a Merseyside Assembly, which would take a form similar to the existing London Assembly. As well as the five Merseyside boroughs, the proposals also included the Cheshire authorities of Halton and Ellesmere Port / Neston. The main argument was that the North West was too large and did not represent a cultural or economic area; something Merseyside did better.

City regions
Since the General Election in May 2005, the concept of city regions has gained currency in academic, policy and government circles, with several think tanks pushing the idea as a viable alternative to elected regional assemblies. However, opinion is divided on the question of whether to impose new city regional structures from above or to allow existing elected bodies to come together on a more informal voluntary basis.

Devolved English parliament
The Campaign for an English Parliament, the minor English Democrats party, and several Conservative Party MPs, see a devolved English parliament as another alternative to regional assemblies. They believe that rather than breaking up the historic nation of England, it should be preserved - with its own parliament similar to that of the Scottish Parliament - and that this is the only way the West Lothian question can be resolved while maintaining the United Kingdom.

title: Regional assembly (England)


text:
User talk:Ferg~enwiki

Hey Ferg, I just noticed your images on Lenticular cloud. Some of them have copyright on them. Have you received permission to use them? If you have, you can note them on the image pages. ,, and. Please respond on my talk page, or here. Burgundavia 06:49, 25 May 2004 (UTC)
 * Hey Ferg, I noticed you just removed the first image. If it is a copyvio, please list in on Copyright problems and it will get deleted. Cheers. Burgundavia 07:39, 25 May 2004 (UTC)

Hey Ferg,

Sorry about the time in getting back to you. As for fair use, IANAL, does not apply outside the USA. I am a Canadian, so this affects me. Try leaving a note for User:Angela who could get you in touch with somebody for more specific copy right info. Burgundavia 00:28, 1 Jun 2004 (UTC)

Your account will be renamed
Hello,

The developer team at Wikimedia is making some changes to how accounts work, as part of our on-going efforts to provide new and better tools for our users like cross-wiki notifications. These changes will mean you have the same account name everywhere. This will let us give you new features that will help you edit and discuss better, and allow more flexible user permissions for tools. One of the side-effects of this is that user accounts will now have to be unique across all 900 Wikimedia wikis. See the announcement for more information.

Unfortunately, your account clashes with another account also called Ferg. To make sure that both of you can use all Wikimedia projects in future, we have reserved the name Ferg~enwiki that only you will have. If you like it, you don't have to do anything. If you do not like it, you can pick out a different name. If you think you might own all of the accounts with this name and this message is in error, please visit Special:MergeAccount to check and attach all of your accounts to prevent them from being renamed.

Your account will still work as before, and you will be credited for all your edits made so far, but you will have to use the new account name when you log in.

Sorry for the inconvenience.

Yours, Keegan Peterzell Community Liaison, Wikimedia Foundation 23:54, 19 March 2015 (UTC)

Renamed
 This account has been renamed as part of single-user login finalisation. If you own this account you can |log in using your previous username and password for more information. If you do not like this account's new name, you can choose your own using this form after logging in: . -- Keegan (WMF) (talk) 12:51, 22 April 2015 (UTC)

title: User talk:Ferg~enwiki


text:
British Columbia Highway 93

Highway 93 is a north–south route through the southeastern part of British Columbia, in the Regional District of East Kootenay and takes its number from U.S. Highway 93 that it connects with at the Canada–United States border. It follows the Crowsnest Highway (Highway 3) and Highway 95 through Radium Hot Springs and to where it crosses the Continental Divide into Alberta at Vermilion Pass, where it continues as Alberta Highway 93. The section between the Canada-U.S. border and the Crowsnest Highway is known as the Elko–Roosville Highway, the section between the Crowsnest Highway and Radium Hot Springs is known as the Kootenay–Columbia Highway, while the section east of Radium Hot Springs is known as the Banff–Windermere Parkway.

Route description
From the international border crossing at Roosville, the 321 km long Highway 93 parallels the eastern shore of Lake Koocanusa for 36 km to where it meets the Crowsnest Highway (Highway 3) at Elko. Highway 3 carries Highway 93 west for 53 km to where it is handed off to Highway 95 just south of Fort Steele. Highway 95 carries Highway 93 north for another 134 km along the Kootenay River and the Columbia River passing through Wasa, Canal Flats, Fairmont Hot Springs and Invermere to Radium Hot Springs, where Highway 95 diverges north towards Golden.

Highway 93 leaves the concurrence and proceeds east from Radium Hot Springs for about 1.3 km to the western gate of Kootenay National Park. Through the park, the highway travels northeast along the Kootenay and Vermilion rivers for 93 km to Vermilion Pass and the Alberta border, where it is continues as Alberta Highway 93. After crossing the border, the highway continues for another 11 km to meet the Trans-Canada Highway (Alberta Highway 1) near Castle Junction.

History
The Highway first opened in 1953 from the international border to Elko, on Highway 3, but it did not follow its current route from the border until 1958. Before 1959, the Banff–Windermere Parkway, the segment of Highway 93 east of Radium Hot Springs, had a designation of Highway 1B, reflecting its connection to the Trans-Canada Highway within Alberta at Castle Junction. In 1959, Highway 93 was extended from Elko along Highway 3 and Highway 95 to Radium Hot Springs, while Highway 1B and the Icefields Parkway (known as Highway 1A) were renumbered to their present designation.

Major intersections
From south to north:

title: British Columbia Highway 93


text:
Liberec Region

Liberec Region (Liberecký kraj) is an administrative unit (Czech: kraj) of the Czech Republic, located in the northernmost part of its historical region of Bohemia. It is named after its capital Liberec. The region shares international borders with Germany and Poland. Domestically the region borders the Ústí nad Labem Region to the west, the Central Bohemian Region to the south and the Hradec Králové Region to the east.

Administrative divisions
The Liberec Region is divided into 4 districts:

At a lower level, the region has 215 municipalities, comprising 65 in the Semily District, 59 in the Jablonec nad Nisou District, 57 in the Česká Lípa District and 34 in the Liberec District.

Cities and towns
The table below gives an overview of towns and cities in the region that have at least 7,000 inhabitants (as of 1 January 2024).

Physical geography
The region's landscape includes the Jizera Mountains, part of the Krkonoše Mountains and part of the Lusatian Mountains.

The region was affected by flash floods in August 2010, with swelling of the river Smědá being one of the factors to prompt evacuation efforts in the region.

Demographics
As of 1 January 2019, the population of the Liberec Region was 442,356 with 217,791 men and 224,565 women, accounting for 49.2% and 50.8% of the population respectively.

Economy
The Liberec Region hosts manufacturing, glassmaking, mechanical engineering and jewellery production industries among others. The region is part of the so-called Black Triangle, an area of heavy industrialization and environmental damage on the three-way border of Poland, Germany, and the Czech Republic.

Culture
The Liberec Region is home to 11 national cultural monuments including Bezděz Castle, Dlaskův statek in Dolánky u Turnova and the Ještěd Tower which transmits television signals as well as being a hotel. 2013 saw the proposal of an additional two sites to the list, those being a glass grinding plant in Harrachov dating from 1895 and the Janatův Mlýn watermill in Buřany, Jablonec nad Jizerou part of which remains from 1767.

A Neolithic site dating to around 4,500 BC was uncovered in 2007 near the village of Příšovice.

Lake Mácha near the town of Doksy is an important regional centre for leisure, attracting around 30,000 visitors annually. The vicinity of the lake has a caravan park and hosts an annual music festival called Mácháč, which was attended by approximately 8,000 people in 2013.

Since the region was for a long time part of the Holy Roman Empire, and later (in 1938–1945) the major part of the region was a part of Germany as part of Sudetenland, the local buildings and the culture in general have been influenced by the Germans, also considering the fact that parts of the region were populated by a majority of Sudeten Germans, prior to their expulsion after World War II.

Transport
The region is linked to Prague by the D10 motorway, which terminates in the town of Turnov. The length of operated railway lines in the region is 551 km. Three airports are in the region; Hradčany Airport, a disused military airport near the town of Ralsko, is the most significant. Other minor airports exist in Česká Lípa and Hodkovice nad Mohelkou.

Education
The region is home to the public Technical University of Liberec, which was founded in 1953. The university, which originally specialized in Mechanical and Textile Engineering, added a further four faculties in the 1990s, namely those specialising in Education, Economy, Architecture and Mechatronics.

title: Liberec Region


text:
List of rivers of Maryland

List of rivers of Maryland (U.S. state).

The list is arranged by drainage basin from east to west, with respective tributaries indented under each larger stream's name and ordered from downstream to upstream.

Delaware River

 * Christina River

Atlantic Ocean

 * Ayres Creek
 * Greys Creek
 * St. Martin River
 * Turville Creek
 * Trappe Creek

Chesapeake Bay Eastern Shore

 * Pocomoke River
 * Marumsco Creek
 * Dividing Creek
 * Nassawango Creek
 * Little Annemessex River
 * Big Annemessex River
 * Manokin River
 * Monie Creek
 * Wicomico River
 * Beaverdam Creek
 * Nanticoke River
 * Barren Creek
 * Mockingbird Creek
 * Marshyhope Creek
 * Big Creek
 * Stony Bar Creek
 * Krafts Creek
 * Spears Creek
 * Becky Taylor Branch
 * Mill Branch
 * Mill Creek
 * Puckum Branch
 * Wrights Branch
 * Skinners Run
 * Davis Millpond Branch
 * North Davis Millpond Branch
 * South Davis Millpond Branch
 * Miles Branch
 * Tanyard Branch
 * Faulkner Branch
 * Tull Branch
 * Sullivan Branch
 * Raccoon Branch
 * Wolfpit Branch
 * Tommy Wright Branch
 * Smithville Ditch
 * Transquaking River
 * Chicamacomico River
 * Blackwater River
 * Little Blackwater River
 * Meekins Creek
 * Honga River
 * Little Choptank River
 * Slaughter Creek
 * Parsons Creek
 * Fishing Creek
 * Choptank River
 * Harris Creek
 * Broad Creek
 * Tred Avon River
 * Town Creek
 * Warwick River
 * Tuckahoe Creek
 * Miles River
 * Front River
 * Wye River
 * Wye East River
 * Chester River
 * Corsica River
 * Cypress Branch
 * Andover Branch
 * Sewell Branch
 * Sassafras River
 * Elk River
 * Bohemia River
 * Big Elk Creek
 * Little Elk Creek
 * North East River
 * North East Creek
 * Little North East Creek
 * Stony Run
 * Principio Creek
 * Mill Creek

Susquehanna River

 * Susquehanna River
 * Deer Creek
 * Octoraro Creek
 * Basin Run
 * Conowingo Creek
 * Broad Creek

Chesapeake Bay Western Shore

 * Swan Creek
 * Gasheys Creek
 * Romney Creek
 * Bush River
 * Otter Point Creek
 * Winters Run
 * Bush Creek
 * Bynum Run
 * James Run
 * Grays Run
 * Cranberry Run
 * Gunpowder River
 * Saltpeter Creek
 * Dundee Creek
 * Bird River
 * Whitemarsh Run
 * Gunpowder Falls
 * Beaverdam Run
 * Western Run
 * McGill Run
 * Piney Run
 * Little Falls
 * Georges Run
 * Little Gunpowder Falls
 * Middle River
 * Seneca Creek
 * Frog Mortar Creek
 * Back River
 * Bread and Cheese Creek
 * Herring Run
 * Moores Run
 * Patapsco River
 * Bodkin Creek
 * Main Creek
 * Stony Creek
 * Bear Creek
 * Curtis Creek
 * Furnace Creek
 * Marley Creek
 * Northwest Branch Patapsco River
 * Jones Falls
 * Western Run
 * Towson Run
 * Middle Branch Patapsco River
 * Gwynns Falls
 * Deep Run
 * Herbert Run
 * Tiber Branch
 * North Branch Patapsco River
 * Morgan Run
 * Middle Run
 * Beaver Run
 * South Branch Patapsco River
 * Piney Run
 * Magothy River
 * Little Magothy River
 * Severn River
 * South River
 * North River

 * West River
 * Rhode River
 * Bear Creek
 * Sellman Creek
 * Patuxent River
 * Town Creek
 * Cuckold Creek
 * St. Leonard Creek
 * Indian Creek
 * Swanson Creek
 * Lyons Creek
 * Green Branch
 * Mill Branch
 * Western Branch Patuxent River
 * Collington Branch
 * Little Patuxent River
 * Middle Patuxent River
 * Hawlings River

Potomac River

 * Potomac River
 * St. Marys River
 * St. George Creek
 * Difficult Run
 * Wicomico River
 * Budds Creek
 * Popes Creek
 * Port Tobacco River
 * Nanjemoy Creek
 * Chicamuxen Creek
 * Mattawoman Creek
 * Pomonkey Creek
 * Piscataway Creek
 * Broad Creek (see Broad Creek, Prince George's County, Maryland)
 * Henson Creek (see Broad Creek, Prince George's County, Maryland)
 * Oxon Creek
 * Oxon Run
 * Anacostia RiverAnacostiamap.png
 * Watts Branch (Anacostia River tributary)
 * Dueling Creek
 * Northeast Branch Anacostia River
 * Beaverdam Creek
 * Paint Branch
 * Little Paint Branch
 * Indian Creek (Anacostia River tributary)
 * Northwest Branch Anacostia River
 * Sligo Creek
 * Rock Creek
 * Coquelin Run
 * Little Falls Branch
 * Minnehaha Branch
 * Cabin John Creek
 * Rock Run
 * Carroll Branch
 * Limekiln Branch
 * Watts Branch (Potomac River tributary)
 * Muddy Branch
 * Seneca Creek
 * Dry Seneca Creek
 * Little Seneca Creek
 * Tenmile Creek
 * Great Seneca Creek
 * Horsepen Branch
 * Broad Run
 * Little Monocacy River
 * Monocacy RiverMonocacy.png
 * Bennett Creek
 * Ballenger Creek
 * Bush Creek
 * Linganore Creek
 * Carroll Creek
 * Israel Creek
 * Tuscarora Creek
 * Little Tuscarora Creek
 * Fishing Creek
 * Big Hunting Creek
 * Little Hunting Creek (Maryland)
 * Owens Creek (Maryland)
 * Beaver Branch
 * Double Pipe Creek
 * Big Pipe Creek
 * Little Pipe Creek
 * Sams Creek
 * Toms Creek
 * Friends Creek
 * Middle Creek
 * Flat Run
 * Piney Creek
 * Alloway Creek
 * Marsh Creek
 * Rock Creek
 * Tuscarora Creek
 * Catoctin Creek
 * Broad Run (Catoctin Creek tributary)
 * Little Catoctin Creek (east)
 * Little Catoctin Creek (west)
 * Middle Creek
 * Little Catoctin Creek
 * Israel Creek
 * Antietam Creek
 * Little Antietam Creek (south)
 * Beaver Creek
 * Marsh Run
 * Little Antietam Creek (north)
 * Conococheague Creek
 * Little Conococheague Creek
 * Licking Creek
 * Little Cove Creek
 * Tonoloway Creek
 * Sideling Hill Creek
 * Bear Creek
 * Fifteenmile Creek
 * Town Creek
 * Flintstone Creek
 * North Branch Potomac RiverMonon YoughioghenyRiver.png
 * Evitts Creek
 * Wills Creek
 * Jennings Run
 * Georges Creek
 * Laurel Run
 * Savage River

Mississippi River

 * Mississippi River
 * Ohio River
 * Monongahela River (PA)
 * Youghiogheny River
 * Casselman River
 * Reason Run
 * Bear Creek
 * Little Youghiogheny River

Alphabetically

 * Alloway Creek
 * Anacostia River
 * Antietam Creek
 * Back River
 * Ballenger Creek
 * Basin Run
 * Bear Creek (Rhode River tributary)
 * Bear Creek (Sideling Hill Creek tributary)
 * Bear Creek (Youghiogheny River tributary)
 * Beaver Branch
 * Beaver Creek
 * Beaver Run
 * Beaverdam Creek (Anacostia River tributary)
 * Beaverdam Creek
 * Beaverdam Run
 * Bennett Creek
 * Big Annemessex River
 * Big Elk Creek
 * Big Hunting Creek
 * Big Pipe Creek
 * Bird River
 * Blackwater River
 * Bodkin Creek
 * Bread and Cheese Creek
 * Broad Creek (Choptank River tributary)
 * Broad Creek (Potomac River tributary)
 * Broad Creek (Susquehanna River tributary)
 * Broad Run
 * Broad Run (Catoctin Creek tributary)
 * Budds Creek
 * Bush Creek
 * Bush Creek
 * Bush River
 * Bynum Run
 * Casselman River
 * Cabin John Creek
 * Carroll Branch
 * Catoctin Creek
 * Chester River
 * Chicamuxen Creek
 * Choptank River
 * Christina River
 * Conococheague Creek
 * Cranberry Run
 * Cuckold Creek
 * Curtis Creek
 * Deer Creek
 * Deep Run
 * Difficult Run
 * Dividing Creek
 * Double Pipe Creek
 * Dry Seneca Creek
 * Dueling Creek
 * Dundee Creek
 * Elk River
 * Evitts Creek
 * Fifteenmile Creek
 * Fishing Creek
 * Flat Run
 * Flintstone Creek
 * Friends Creek
 * Frog Mortar Creek
 * Furnace Creek
 * Gasheys Creek
 * Georges Creek
 * Georges Run
 * Great Seneca Creek
 * Grays Run
 * Gunpowder Falls
 * Gunpowder River
 * Gwynns Falls
 * Hawlings River
 * Harris Creek
 * Henson Creek
 * Herring Run
 * Horsepen Branch
 * Indian Creek (Anacostia River tributary)
 * Indian Creek (Patuxent River tributary)
 * Israel Creek
 * Israel Creek (Potomac River tributary)
 * James Run
 * Jennings Run
 * Jones Falls
 * Laurel Run
 * Licking Creek
 * Limekiln Branch
 * Linganore Creek
 * Little Antietam Creek (north)
 * Little Antietam Creek (south)
 * Little Catoctin Creek (east)
 * Little Catoctin Creek (west)
 * Little Catoctin Creek (Potomac River tributary)
 * Little Choptank River
 * Little Conococheague Creek
 * Little Cove Creek
 * Little Elk Creek
 * Little Falls Branch
 * Little Gunpowder Falls
 * Little Hunting Creek
 * Little Monocacy River
 * Little North East Creek
 * Little Paint Branch
 * Little Patuxent River
 * Little Pipe Creek
 * Little Seneca Creek
 * Little Tuscarora Creek
 * Little Youghiogheny River
 * Lyons Creek
 * Magothy River
 * Marley Creek
 * Marsh Creek (Catoctin Creek tributary)
 * Marsh Creek (Monocacy River tributary)
 * Marsh Run
 * Marshyhope Creek
 * Marumsco Creek
 * Mattawoman Creek
 * McGill Run
 * Middle Creek (Catoctin Creek tributary)
 * Middle Creek (Toms Creek tributary)
 * Middle Run
 * Middle Patuxent River
 * Middle River
 * Mill Branch
 * Mill Creek
 * Minnehaha Branch
 * Monocacy River
 * Moores Run
 * Morgan Run
 * Muddy Branch
 * Nanjemoy Creek
 * Nanticoke River
 * North Branch Patapsco River
 * North Branch Potomac River
 * North East Creek
 * North East River
 * Northeast Branch Anacostia River
 * Northwest Branch Anacostia River
 * Northwest Branch Patapsco River
 * Octoraro Creek
 * Otter Point Creek
 * Oxon Creek
 * Owens Creek (Maryland)
 * Paint Branch
 * Patapsco River
 * Patuxent River
 * Piney Creek
 * Piney Run
 * Piney Run (Western Run tributary)
 * Piscataway Creek
 * Pocomoke River
 * Pomonkey Creek
 * Popes Creek
 * Port Tobacco River
 * Potomac River
 * Principio Creek
 * Reason Run
 * Rhode River
 * Rock Creek (Monocacy River tributary)
 * Rock Creek (Potomac River tributary)
 * Rock Run
 * St. Marys River
 * Saltpeter Creek
 * Sams Creek
 * Sassafras River
 * Savage River
 * Seneca Creek
 * Severn River
 * Sideling Hill Creek
 * Sligo Creek
 * South Branch Patapsco River
 * South River
 * Stony Creek
 * Stony Run (North East River tributary)
 * Susquehanna River
 * Swan Creek
 * Swanson Creek
 * Tenmile Creek
 * Toms Creek
 * Tonoloway Creek
 * Town Creek (Patuxent River tributary)
 * Town Creek (Potomac River tributary)
 * Town Creek (Tred Avon River tributary)
 * Towson Run
 * Tuckahoe Creek
 * Tuscarora Creek (Monocacy River tributary)
 * Tuscarora Creek (Potomac River tributary)
 * Watts Branch (Anacostia River tributary)
 * Watts Branch (Potomac River tributary)
 * West River
 * Western Run
 * Western Run (Gunpowder Falls tributary)
 * Western Branch Patuxent River
 * Whitemarsh Run
 * Wicomico River (Maryland eastern shore)
 * Wicomico River (Potomac River tributary)
 * Wills Creek
 * Winters Run
 * Wye River
 * Youghiogheny River

title: List of rivers of Maryland


text:
Telegraph code

A telegraph code is one of the character encodings used to transmit information by telegraphy. Morse code is the best-known such code. Telegraphy usually refers to the electrical telegraph, but telegraph systems using the optical telegraph were in use before that. A code consists of a number of code points, each corresponding to a letter of the alphabet, a numeral, or some other character. In codes intended for machines rather than humans, code points for control characters, such as carriage return, are required to control the operation of the mechanism. Each code point is made up of a number of elements arranged in a unique way for that character. There are usually two types of element (a binary code), but more element types were employed in some codes not intended for machines. For instance, American Morse code had about five elements, rather than the two (dot and dash) of International Morse Code.

Codes meant for human interpretation were designed so that the characters that occurred most often had the fewest elements in the corresponding code point. For instance, Morse code for E, the most common letter in English, is a single dot, whereas Q is. These arrangements meant the message could be sent more quickly and it would take longer for the operator to become fatigued. Telegraphs were always operated by humans until late in the 19th century. When automated telegraph messages came in, codes with variable-length code points were inconvenient for machine design of the period. Instead, codes with a fixed length were used. The first of these was the Baudot code, a five-bit code. Baudot has only enough code points to print in upper case. Later codes had more bits (ASCII has seven) so that both upper and lower case could be printed. Beyond the telegraph age, modern computers require a very large number of code points (Unicode has 21 bits) so that multiple languages and alphabets (character sets) can be handled without having to change the character encoding. Modern computers can easily handle variable-length codes such as UTF-8 and UTF-16 which have now become ubiquitous.

Optical telegraph codes
Prior to the electrical telegraph, a widely used method of building national telegraph networks was the optical telegraph consisting of a chain of towers from which signals could be sent by semaphore or shutters from tower to tower. This was particularly highly developed in France and had its beginnings during the French Revolution. The code used in France was the Chappe code, named after Claude Chappe the inventor. The British Admiralty also used the semaphore telegraph, but with their own code. The British code was necessarily different from that used in France because the British optical telegraph worked in a different way. The Chappe system had moveable arms, as if it were waving flags as in flag semaphore. The British system used an array of shutters that could be opened or closed.

Chappe code
The Chappe system consisted of a large pivoted beam (the regulator) with an arm at each end (the indicators) which pivoted around the regulator on one extremity. The angles these components were allowed to take was limited to multiples of 45° to aid readability. This gave a code space of 8×4×8 code points, but the indicator position inline with the regulator was never used because it was hard to distinguish from the indicator being folded back on top of the regulator, leaving a code space of 7×4×7 = 196. Symbols were always formed with the regulator on either the left- or right-leaning diagonal (oblique) and only accepted as valid when the regulator moved to either the vertical or horizontal position. The left oblique was always used for messages, with the right oblique being used for control of the system. This further reduced the code space to 98, of which either four or six code points (depending on version) were control characters, leaving a code space for text of 94 or 92 respectively.

The Chappe system mostly transmitted messages using a code book with a large number of set words and phrases. It was first used on an experimental chain of towers in 1793 and put into service from Paris to Lille in 1794. The code book used this early is not known for certain, but an unidentified code book in the Paris Postal Museum may have been for the Chappe system. The arrangement of this code in columns of 88 entries led Holzmann & Pehrson to suggest that 88 code points might have been used. However, the proposal in 1793 was for ten code points representing the numerals 0–9, and Bouchet says this system was still in use as late as 1800 (Holzmann & Pehrson put the change at 1795). The code book was revised and simplified in 1795 to speed up transmission. The code was in two divisions, the first division was 94 alphabetic and numeric characters plus some commonly used letter combinations. The second division was a code book of 94 pages with 94 entries on each page. A code point was assigned for each number up to 94. Thus, only two symbols needed to be sent to transmit an entire sentence – the page and line numbers of the code book, compared to four symbols using the ten-symbol code.

In 1799, three additional divisions were added. These had additional words and phrases, geographical places, and names of people. These three divisions required extra symbols to be added in front of the code symbol to identify the correct book. The code was revised again in 1809 and remained stable thereafter. In 1837 a horizontal only coding system was introduced by Gabriel Flocon which did not require the heavy regulator to be moved. Instead, an additional indicator was provided in the centre of the regulator to transmit that element of the code.

Edelcrantz code
The Edelcrantz system was used in Sweden and was the second largest network built after that of France. The telegraph consisted of a set of ten shutters. Nine of these were arranged in a 3×3 matrix. Each column of shutters represented a binary-coded octal digit with a closed shutter representing "1" and the most significant digit at the bottom. Each symbol of telegraph transmission was thus a three-digit octal number. The tenth shutter was an extra-large one at the top. Its meaning was that the codepoint should be preceded by "A".

One use of the "A" shutter was that a numeral codepoint preceded by "A" meant add a zero (multiply by ten) to the digit. Larger numbers could be indicated by following the numeral with the code for hundreds (236), thousands (631) or a combination of these. This required fewer symbols to be transmitted than sending all the zero digits individually. However, the main purpose of the "A" codepoints was for a codebook of predetermined messages, much like the Chappe codebook.

The symbols without "A" were a large set of numerals, letters, common syllables and words to aid code compaction. Around 1809, Edelcrantz introduced a new codebook with 5,120 codepoints, each requiring a two-symbol transmission to identify.

There were many codepoints for error correction (272, error), flow control, and supervisory messages. Usually, messages were expected to be passed all the way down the line, but there were circumstances when individual stations needed to communicate directly, usually for managerial purposes. The most common, and simplest situation was communication between adjacent stations. Codepoints 722 and 227 were used for this purpose, to get the attention of the next station towards, or away from, the sun, respectively. For more remote stations codepoints 557 and 755 respectively were used, followed by the identification of the requesting and target stations.

Wig-wag
Flag signalling was widely used for point-to-point signalling prior to the optical telegraph, but it was difficult to construct a nationwide network with hand-held flags. The much larger mechanical apparatus of the semaphore telegraph towers was needed so that a greater distance between links could be achieved. However, an extensive network with hand-held flags was constructed during the American Civil War. This was the wig-wag system which used the code invented by Albert J. Myer. Some of the towers used were enormous, up to 130 feet, to get a good range. Myer's code required only one flag using a ternary code. That is, each code element consisted of one of three distinct flag positions. However, the alphabetical codepoints required only two positions, the third position only being used in control characters. Using a ternary code in the alphabet would have resulted in shorter messages because fewer elements are required in each codepoint, but a binary system is easier to read at long distance since fewer flag positions need to be distinguished. Myer's manual also describes a ternary-coded alphabet with a fixed length of three elements for each codepoint.

Cooke and Wheatstone and other early codes
Many different codes were invented during the early development of the electrical telegraph. Virtually every inventor produced a different code to suit their particular apparatus. The earliest code used commercially on an electrical telegraph was the Cooke and Wheatstone telegraph five needle code (C&W5). This was first used on the Great Western Railway in 1838. C&W5 had the major advantage that the code did not need to be learned by the operator; the letters could be read directly off the display board. However, it had the disadvantage that it required too many wires. A one needle code, C&W1, was developed that required only one wire. C&W1 was widely used in the UK and the British Empire. Some other countries used C&W1, but it never became an international standard and generally each country developed their own code. In the US, American Morse code was used, whose elements consisted of dots and dashes distinguished from each other by the length of the pulse of current on the telegraph line. This code was used on the telegraph invented by Samuel Morse and Alfred Vail and was first used commercially in 1844. Morse initially had code points only for numerals. He planned that numbers sent over the telegraph would be used as an index to a dictionary with a limited set of words. Vail invented an extended code that included code points for all the letters so that any desired word could be sent. It was Vail's code that became American Morse. In France, the telegraph used the Foy-Breguet telegraph, a two-needle telegraph that displayed the needles in Chappe code, the same code as the French optical telegraph, which was still more widely used than the electrical telegraph in France. To the French, this had the great advantage that they did not need to retrain their operators in a new code.

Standardisation—Morse code
In Germany in 1848, Friedrich Clemens Gerke developed a heavily modified version of American Morse for use on German railways. American Morse had three different lengths of dashes and two different lengths of space between the dots and dashes in a code point. The Gerke code had only one length of dash and all inter-element spaces within a code point were equal. Gerke also created code points for the German umlaut letters, which do not exist in English. Many central European countries belonged to the German-Austrian Telegraph Union. In 1851, the Union decided to adopt a common code across all its countries so that messages could be sent between them without the need for operators to recode them at borders. The Gerke code was adopted for this purpose.

In 1865, a conference in Paris adopted the Gerke code as the international standard, calling it International Morse Code. With some very minor changes, this is the Morse code used today. The Cooke and Wheatstone telegraph needle instruments were capable of using Morse code since dots and dashes could be sent as left and right movements of the needle. By this time, the needle instruments were being made with end stops that made two distinctly different notes as the needle hit them. This enabled the operator to write the message without looking up at the needle which was much more efficient. This was a similar advantage to the Morse telegraph in which the operators could hear the message from the clicking of the relay armature. Nevertheless, after the British telegraph companies were nationalised in 1870 the General Post Office decided to standardise on the Morse telegraph and get rid of the many different systems they had inherited from private companies.

In the US, telegraph companies refused to use International Morse because of the cost of retraining operators. They opposed attempts by the government to make it law. In most other countries, the telegraph was state controlled so the change could simply be mandated. In the US, there was no single entity running the telegraph. Rather, it was a multiplicity of private companies. This resulted in international operators needing to be fluent in both versions of Morse and to recode both incoming and outgoing messages. The US continued to use American Morse on landlines (radiotelegraphy generally used International Morse) and this remained the case until the advent of teleprinters which required entirely different codes and rendered the issue moot.

Transmission speed
The speed of sending in a manual telegraph is limited by the speed the operator can send each code element. Speeds are typically stated in words per minute. Words are not all the same length, so literally counting the words will get a different result depending on message content. Instead, a word is defined as five characters for the purpose of measuring speed, regardless of how many words are actually in the message. Morse code, and many other codes, also do not have the same length of code for each character of the word, again introducing a content-related variable. To overcome this, the speed of the operator repeatedly transmitting a standard word is used. PARIS is classically chosen as this standard because that is the length of an average word in Morse.

In American Morse, the characters are generally shorter than International Morse. This is partly because American Morse uses more dot elements, and partly because the most common dash, the short dash, is shorter than the International Morse dash—two dot elements against three dot elements long. In principle, American Morse will be transmitted faster than International Morse if all other variables are equal. In practice, there are two things that detract from this. Firstly, American Morse, with around five coding elements was harder to get the timings right when sent quickly. Inexperienced operators were apt to send garbled messages, an effect known as hog Morse. The second reason is that American Morse is more prone to intersymbol interference (ISI) because of the larger density of closely spaced dots. This problem was particularly severe on submarine telegraph cables, making American Morse less suitable for international communications. The only solution an operator had immediately to hand to deal with ISI was to slow down the transmission speed.

Language character encodings
Morse code for non-Latin alphabets, such as Cyrillic or Arabic script, is achieved by constructing a character encoding for the alphabet in question using the same, or nearly the same code points as used in the Latin alphabet. Syllabaries, such as Japanese katakana, are also handled this way (Wabun code). The alternative of adding more code points to Morse code for each new character would result in code transmissions being very long in some languages.

Languages that use logograms are more difficult to handle due to the much larger number of characters required. The Chinese telegraph code uses a codebook of around 9,800 characters (7,000 when originally launched in 1871) which are each assigned a four-digit number. It is these numbers that are transmitted, so Chinese Morse code consists entirely of numerals. The numbers must be looked up at the receiving end making this a slow process, but in the era when telegraph was widely used, skilled Chinese telegraphers could recall many thousands of the common codes from memory. The Chinese telegraph code is still used by law enforcement because it is an unambiguous method of recording Chinese names in non-Chinese scripts.

Baudot code
Early printing telegraphs continued to use Morse code, but the operator no longer sent the dots and dashes directly with a single key. Instead they operated a piano keyboard with the characters to be sent marked on each key. The machine generated the appropriate Morse code point from the key press. An entirely new type of code was developed by Émile Baudot, patented in 1874. The Baudot code was a 5-bit binary code, with the bits sent serially. Having a fixed length code greatly simplified the machine design. The operator entered the code from a small 5-key piano keyboard, each key corresponding to one bit of the code. Like Morse, Baudot code was organised to minimise operator fatigue with the code points requiring the fewest key presses assigned to the most common letters.

Early printing telegraphs required mechanical synchronisation between the sending and receiving machine. The Hughes printing telegraph of 1855 achieved this by sending a Morse dash every revolution of the machine. A different solution was adopted in conjunction with the Baudot code. Start and stop bits were added to each character on transmission, which allowed asynchronous serial communication. This scheme of start and stop bits was followed on all the later major telegraph codes.

Murray code
On busy telegraph lines, a variant of the Baudot code was used with punched paper tape. This was the Murray code, invented by Donald Murray in 1901. Instead of directly transmitting to the line, the keypresses of the operator punched holes in the tape. Each row of holes across the tape had five possible positions to punch, corresponding to the five bits of the Murray code. The tape was then run through a tape reader which generated the code and sent it down the telegraph line. The advantage of this system was that multiple messages could be sent to line very fast from one tape, making better use of the line than direct manual operation could.

Murray completely rearranged the character encoding to minimise wear on the machine since operator fatigue was no longer an issue. Thus, the character sets of the original Baudot and the Murray codes are not compatible. The five bits of the Baudot code are insufficient to represent all the letters, numerals, and punctuation required in a text message. Further, additional characters are required by printing telegraphs to better control the machine. Examples of these control characters are line feed and carriage return. Murray solved this problem by introducing shift codes. These codes instruct the receiving machine to change the character encoding to a different character set. Two shift codes were used in the Murray code; figure shift and letter shift. Another control character introduced by Murray was the delete character (DEL, code 11111) which punched out all five holes on the tape. Its intended purpose was to remove erroneous characters from the tape, but Murray also used multiple DELs to mark the boundary between messages. Having all the holes punched out made a perforation which was easy to tear into separate messages at the receiving end. A variant of the Baudot–Murray code became an international standard as International Telegraph Alphabet no. 2 (ITA 2) in 1924. The "2" in ITA 2 is because the original Baudot code became the basis for ITA 1. ITA 2 remained the standard telegraph code in use until the 1960s and was still in use in places well beyond then.

Computer age
The teleprinter was invented in 1915. This is a printing telegraph with a typewriter-like keyboard on which the operator types the message. Nevertheless, telegrams continued to be sent in upper case only because there was not room for a lower case character set in Baudot–Murray or ITA 2 codes. This changed with the arrival of computers and the desire to interface computer-generated messages or word processor composed documents with the telegraph system. An immediate problem was the use of shift codes which caused a difficulty with computer storage of text. If a part of a message, or only one character, was retrieved, it was not possible to tell which encoding shift should be applied without searching back through the rest of the message for the last shift control. This led to the introduction of the 6-bit TeleTypeSetter (TTS) code. In TTS, the additional bit was used to store the shift state, thus obviating the need for shift characters. TTS was also of some benefit to teleprinters as well as computers. Corruption of a TTS transmitted letter code just resulted in one wrong letter being printed, which could probably be corrected by the receiving user. On the other hand, corruption of an ITA 2 shift character resulted in all the message from that point onwards being garbled until the next shift character was sent.

ASCII
By the 1960s, improving teleprinter technology meant that longer codes were nowhere near as significant a factor in teleprinter costs as they once were. The computer users' wanted lowercase characters and additional punctuation and both teleprinter and computer manufacturers wished to get rid of ITA 2 and its shift codes. This led the American Standards Association to develop a 7-bit code, the American Standard Code for Information Interchange (ASCII). The final form of ASCII was published in 1964 and it rapidly became the standard teleprinter code. ASCII was the last major code developed explicitly with telegraphy equipment in mind. Telegraphy rapidly declined after this and was largely replaced by computer networks, especially the Internet in the 1990s. ASCII had several features geared to aid computer programming. The letter characters were in numerical order of code point, so an alphabetical sort could be achieved simply by sorting the data numerically. The code point for corresponding upper and lower case letters differed only by the value of bit 6, allowing a mix of cases to be sorted alphabetically if this bit was ignored. Other codes were introduced, notably IBM's EBCDIC derived from the punched card method of input, but it was ASCII and its derivatives that won out as the lingua franca of computer information exchange.

ASCII extension and Unicode
The arrival of the microprocessor in the 1970s and the personal computer in the 1980s with their 8-bit architecture led to the 8-bit byte becoming the standard unit of computer storage. Packing 7-bit data into 8-bit storage is inconvenient for data retrieval. Instead, most computers stored one ASCII character per byte. This left one bit over that was not doing anything useful. Computer manufacturers used this bit in extended ASCII to overcome some of the limitations of standard ASCII. The main issue was that ASCII was geared to English, particularly American English, and lacked the accented vowels used in other European languages such as French. Currency symbols for other countries were also added to the character set. Unfortunately, different manufacturers implemented different extended ASCIIs making them incompatible across platforms. In 1987, the International Standards Organisation issued the standard ISO 8859-1, for an 8-bit character encoding based on 7-bit ASCII which was widely taken up.

ISO 8859 character encodings were developed for non-Latin scripts such as Cyrillic, Hebrew, Arabic, and Greek. This was still problematic if a document or data used more than one script. Multiple switches between character encodings was required. This was solved by the publication in 1991 of the standard for 16-bit Unicode, in development since 1987. Unicode maintained ASCII characters at the same code points for compatibility. As well as support for non-Latin scripts, Unicode provided code points for logograms such as Chinese characters and many specialist characters such as astrological and mathematical symbols. In 1996, Unicode 2.0 allowed code points greater than 16-bit; up to 20-bit, and 21-bit with an additional private use area. 20-bit Unicode provided support for extinct languages such as Old Italic script and many rarely used Chinese characters.

International Code of Signals (radiotelegraph)
In 1931, the International Code of Signals, originally created for ship communication by signalling using flags, was expanded by adding a collection of five-letter codes to be used by radiotelegraph operators.

Table 2 notes
An alternative representation of needle codes is to use the numeral "1" for needle left, and "3" for needle right. The numeral "2", which does not appear in most codes represents the needle in the neutral upright position. The codepoints using this scheme are marked on the face of some needle instruments, especially those used for training.

Table 3 notes
When used with a printing telegraph or siphon recorder, the "dashes" of dot-dash codes are often made the same length as the "dot". Typically, the mark on the tape for a dot is made above the mark for a dash. An example of this can be seen in the 1837 Steinheil code, which is nearly identical to the 1849 Steinheil code, except that they are represented differently in the table. International Morse code was commonly used in this form on submarine telegraph cables.

title: Telegraph code


text:
Flotsam, jetsam, lagan and derelict

In maritime law, flotsam, jetsam, lagan, and derelict are specific kinds of shipwreck. The words have specific nautical meanings, with legal consequences in the law of admiralty and marine salvage. A shipwreck is defined as the remains of a ship that has been wrecked, whether it has sunk or is floating on the surface of the water.

Overview
A wreck is categorized as property belonging to no apparent owner that either sinks to the seabed or floats on the surface of the water, whether it be intentionally cast overboard or as the result of an accident. The term encompasses the hull of the vessel and its fixtures as well as any other form of object on board, such as cargo and stores, and personal effects of the crew and passengers. This also encompasses the narrower definition of salvage, that is, property that has been recovered from a wreckage, or the recovery of the ship itself. There are a number of factors that contribute to the formation of a shipwreck, which can be divided into physical and cultural processes. A site can be affected by physical processes, that is, naturally occurring processes, such as the corrosion caused by salinity and ocean currents, or the growth of native and foreign marine organisms. It can also be affected by cultural processes, that is, by human interactions, such as adding or removing materials from the site of the wreck. Any archaeological activity, such as excavation, may also be considered invasive and tampering.

In maritime law, different meanings are attributed to the terms, based on jurisdiction as well as context. For example, a distinction is made between goods that wash ashore and those that are for some reason not salvageable and/or lost at sea.

Law of salvage
Ownership of a wreck is a highly controversial issue, as there are no clear lines within which it is defined. It may be acquired through various means that range from succession to confiscation. There is also a distinction to be made between the ownership of the hull itself and the cargo it contains, as the hull may be abandoned intentionally, whereas the cargo may be out of necessity (in the case of an emergency or the need to shed weight from the vessel). In these parameters, abandonment of the ship by its passengers constitutes a loss of possession, but to abandon the claim on the title itself, intention to relinquish it is required. This affects wrecks by limiting that which is considered "abandoned". Generally, a ship is defined as "abandoned" if there is no hope of recovery, known legally as sine spe recuperandi (which is the Latin phrase for "without hope of recovery"), and this fact must be clearly proven by the salvaging party. It must also occur on navigable waters. The term "salvage" is used to indicate a salvage operation, as well as the subsequent awarded compensation. It is considered a voluntary service rendered in cases such as danger to the wreck, or the surrounding navigable waters. In terms of compensation, it is seen as being awarded to anyone who voluntarily assisted in the recuperation of the wreck, whether it be saved from upcoming danger, or from loss.

The law of salvage has its origins in the Roman practice of negotiorum gestio, which dictated that one who preserved or improved upon the property of another was owed compensation from the owner, even if the service was not requested by the latter. The law did not apply to maritime regulations, but were the basis for following ordinances, such as the Marine Ordinance of Trani, which stated that a "finder" was to be rewarded, whether the owner claimed the goods or not. The laws have evolved since negotiorum gestio, and today, in the United States, a salvor who voluntarily brings the goods back into port may legally lay claim to them, or deliver them to a marshal, in return for a reward.

Flotsam
Flotsam (also known as "flotsan") refers to goods from a sunken vessel that have floated to the surface of the sea, or any floating cargo that is cast overboard.

In maritime law, flotsam pertains to goods that are floating on the surface of the water as the result of a wreck or accident. One who discovers flotsam is allowed to claim it unless someone else establishes their ownership of it. Even when the source is known, items may be considered flotsam claimable by the finder. This occurred with up to 110 cargo containers lost by MSC Zoe in heavy seas in January 2019 off the German shore of Borkum; the lost goods found on the Dutch coast were considered flotsam.

Jetsam
Jetsam designates any cargo that is intentionally discarded from a ship or wreckage. Legally jetsam also floats, although floating is not part of the etymological meaning. Generally, "jettisoning" connotes the action of throwing goods overboard to lighten the load of a ship in danger of sinking.

Per maritime law, one who discovers these artifacts is not required to return them to their rightful owner except in the case where the latter makes a proper claim.

However, according to the U.S. National Oceanic and Atmospheric Administration "flotsam may be claimed by the original owner, whereas jetsam may be claimed as property of whoever discovers it".

Lagan

Lagan (also called "ligan") are goods cast overboard and heavy enough to sink to the ocean floor, but linked to a floating marker, such as a buoy or cork, so that they can be found again by the person who marked the item. Lagan can also be large objects trapped within the sinking vessel.

According to maritime law, a buoy or other floating object constitutes sufficient grounds for laying claim to an artifact. Lagan must be returned to the rightful owner.

Derelict
Derelict can refer to goods that have sunk to the ocean floor, relinquished willingly or forcefully by its owner, and thus abandoned, but which no one has any hope of reclaiming.

In terms of maritime law, derelict is considered property abandoned on navigable waters which has no hope of being recovered, or sine spe recuperandi, and no expectation of it being returned to its owner, or sine animo revertendi.

title: Flotsam, jetsam, lagan and derelict


text:
User:Brentolamas

(b. Fairmont, West Virginia,1977)

Edited article: Family Feud

title: User:Brentolamas


text:
Talk:Hindu (disambiguation)

So what's the connection between Hinduism and Hindi or Hindustani (other than being derived from "Sindhu")? Why're Hindi and Hindustani mentioned in Hindu_(disambiguation)? Ambarish | Talk 06:58, 25 May 2004 (UTC)
 * Hindu_(disambiguation) is not about Hinduism. I've put back Hindi because there is a widely-prevalent misconception of Hindu being the language spoken in India. Also I've replaced Hindustani language with Hindustan, the land of the Hindus. Jay 10:59, 7 Dec 2004 (UTC)
 * I wasn't aware about the misconception about Hindu being an Indian language. Could you provide some references? A Google search didn't provide too many clues - most of the results seem to be (mis-)references to Sanskrit as a Hindu language. Ambarish 21:56, 7 Dec 2004 (UTC)

 * Hindi or Hindu
 * Hindi/Hindu, linked off of Common Errors in English Usage. Personally, I've heard the people make the mistake many times in my presence, as can be seen by this link Innkeepers who speak Hindu off of google:hindu+hindi

 * Arun 20:27, 30 October 2005 (UTC)

title: Talk:Hindu (disambiguation)


text:
User:Marvin the Paranoid Android

Marvin the Paranoid Android

Ultra inteligent android with a very depressive mood featured in the Hitchickers guide to the galaxy series. Also one of the users of Wikipedia. I really must say that I was somewhat forced to use this name since I couldn't find an available name I desired to use. But alas, so is life and I have to live with that.

title: User:Marvin the Paranoid Android


text:
ESC/Java

ESC/Java (and more recently ESC/Java2), the "Extended Static Checker for Java," is a programming tool that attempts to find common run-time errors in Java programs at compile time. The underlying approach used in ESC/Java is referred to as extended static checking, which is a collective name referring to a range of techniques for statically checking the correctness of various program constraints. For example, that an integer variable is greater-than-zero, or lies between the bounds of an array. This technique was pioneered in ESC/Java (and its predecessor, ESC/Modula-3) and can be thought of as an extended form of type checking. Extended static checking usually involves the use of an automated theorem prover and, in ESC/Java, the Simplify theorem prover was used.

ESC/Java is neither sound nor complete. This was intentional and aims to reduce the number of errors and/or warnings reported to the programmer, in order to make the tool more useful in practice. However, it does mean that: firstly, there are programs that ESC/Java will erroneously consider to be incorrect (known as false-positives); secondly, there are incorrect programs it will consider to be correct (known as false-negatives). Examples in the latter category include errors arising from modular arithmetic and/or multithreading.

ESC/Java was originally developed at the Compaq Systems Research Center (SRC). SRC launched the project in 1997, after work on their original extended static checker, ESC/Modula-3, ended in 1996. In 2002, SRC released the source code for ESC/Java and related tools. Recent versions of ESC/Java are based around the Java Modeling Language (JML). Users can control the amount and kinds of checking by annotating their programs with specially formatted comments or pragmas.

The University of Nijmegen's Security of Systems group released alpha versions of ESC/Java2, an extended version of ESC/Java that processes the JML specification language through 2004. From 2004 to 2009, ESC/Java2 development was managed by the KindSoftware Research Group at University College Dublin, which in 2009 moved to the IT University of Copenhagen, and in 2012 to the Technical University of Denmark. Over the years, ESC/Java2 has gained many new features including the ability to reason with multiple theorem provers and integration with Eclipse.

OpenJML, the successor of ESC/Java2, is available for Java 1.8. The source is available at https://github.com/OpenJML

title: ESC/Java


text:
Fenni

The Fenni were an ancient people of northeastern Europe, first described by Cornelius Tacitus in Germania in AD 98.

Ancient accounts
The Fenni are first mentioned by Cornelius Tacitus in Germania in 98 A.D. Their location is uncertain, due to the vagueness of Tacitus' account: "The Venedi overrun in their predatory excursions all the woody and mountainous tracts between the Peucini and the Fenni". The Greco-Roman geographer Ptolemy, who produced his Geographia in ca. 150 AD, mentions a people called the Phinnoi (Φιννοι), generally believed to be synonymous with the Fenni. He locates them in two different areas: a northern group in northern Scandia (Scandinavia), then believed to be an island; and a southern group, apparently dwelling to the East of the upper Vistula river (SE Poland). It remains unclear what was the relationship between the two groups.

The next ancient mention of the Fenni/Finni is in the Getica of 6th-century chronicler Jordanes. In his description of the island of Scandza (Scandinavia), he mentions three groups with names similar to Ptolemy's Phinnoi, the Screrefennae, Finnaithae and mitissimi Finni ("softest Finns"). The Screrefennae is believed to mean the "skiing Finns" and are generally identified with Ptolemy's northern Phinnoi and today's Finns. The Finnaithae have been identified with the Finnveden of southern Sweden. It is unclear who the mitissimi Finni was.

Ethno-linguistic affiliation
Tacitus was unsure whether to classify the Fenni as Germanic or Sarmatian. The vagueness of his account has left the identification of the Fenni open to a variety of theories. It has been suggested that the Romans may have used Fenni as a generic name, to denote the various non-Germanic (i.e. Balto-Slavic and Finno-Ugric) tribes of north-eastern Europe. Against this argument is the fact that Tacitus distinguishes the Fenni from other probably non-Germanic peoples of the region, such as the Aestii and the Veneti.

It has also been suggested that Tacitus' Fenni could be the ancestors of the modern Finnish people. Juha Pentikäinen writes that Tacitus may well have been describing the Sámi or the proto-Finns when referring to the Fenni, noting some archeologists have identified these people as indigenous to Fennoscandia. The context of Fenni has also included the Finnic Estonians throughout different interpretations. Nevertheless, according to some linguists, certain linguistic evidence may be interpreted supporting the idea of an archaic Indo-European dialect and unknown Paleo-European languages existing in north-eastern Baltic Sea region before the spread of Finno-Ugric languages like Proto-Sámi and Proto-Finnic in the early Bronze Age around 1800 BC. However, in Tacitus's time (1st century AD) Finno-Ugric languages (Proto-Sámi and Proto-Finnic) were the main languages in northern Fennoscandia.

Another theory is that Tacitus' Fenni and Ptolemy's northern Phinnoi were the same people and constituted the original Sámi people of northern Fennoscandia, making Tacitus' description the first historical record of them, and the mention of two different "Phinnoi" groups may suggest that there was already a division between Finns and Sámi. But while this may seem a plausible identification for the Phinnoi of northern Scandinavia, it is dubious for Tacitus' Fenni. Tacitus' Fenni (and Ptolemy's southern Phinnoi) were clearly based in continental Europe, not in the Scandinavian peninsula, and were thus outside the modern range of the Sámi. Against this, there is some archaeological evidence that the Sámi range may have been wider in antiquity. Sámi toponyms are found as far as Southern Finland and Karelia

The uncertainties have led some scholars to conclude that Tacitus' Fenni is a meaningless label, impossible to ascribe to any particular region or ethnic group. But Tacitus appears to relate the Fenni geographically to the Peucini and the Venedi, albeit imprecisely, stating that the latter habitually raided the "forests and mountains" between the other two. He also gives a relatively detailed description of the Fenni's lifestyle.

Material culture
Fenni seems to have been a form of the proto-Germanic word *fanþian-, denoting "wanderers" or "hunting folk", although Vladimir Orel viewed its etymology as unclear and listed a couple of alternative proposals (i.e. a derivation from Proto-Celtic *þenn- "hill"). Tacitus describes the Fenni as follows:

"In wonderful savageness live the nation of the Fenni, and in beastly poverty, destitute of arms, of horses, and of homes; their food, the common herbs; their apparel, skins; their bed, the earth; their only hope in their arrows, which for want of iron they point with bones. Their common support they have from the chase, women as well as men; for with these the former wander up and down, and crave a portion of the prey. Nor other shelter have they even for their babes, against the violence of tempests and ravening beasts, than to cover them with the branches of trees twisted together; this a reception for the old men, and hither resort the young. Such a condition they judge happier than the painful occupation of cultivating the ground, than the labour of rearing houses than the agitations of hope and fear attending the defense of their own property or the seizing that of others. Secure against the designs of men, secure against the malignity of the Gods, they have accomplished a thing of infinite difficulty; that to them nothing remains even to be wished."

This description is of a lifestyle much more primitive than that of the medieval Sámi, who were pastoralists living off herds of reindeer and inhabiting sophisticated tents of deer hide. But the archaeological evidence suggests that the proto-Sámi and Proto-Finns had a lifestyle more akin to Tacitus' description.

Ancient

 * Jordanes Getica (ca. 550 AD)
 * Ptolemy Geographia (ca. 150 AD)
 * Tacitus Germania (ca. 100 AD)

Modern

 * Anderson, J.G.D. (1958) Textual note to Tacitus' Germania
 * Bosi, Roberto (1960): The Lapps
 * Hansen, L.I. & Olsen, B. (2004): Samenes Historie fram til 1750
 * Kinsten, Silje Bergum (2000): "The Northern Sami People" (The Norway Post, 19 August 2000)
 * Pirinen, Kauko The settlement of Finland begins in Eino Jutikkala (ed.) A History of Finland (trans. Paul Sjoblom)
 * Tägil, Sven (1995): Ethnicity and nation building in the Nordic world, ISBN 1-85065-239-2

title: Fenni


text:
Archgallo

Archgallo (Welsh: Arthal map Morydd) was a legendary king of the Britons as recounted by Geoffrey of Monmouth. He ruled from 339BC. He was the second son of King Morvidus and brother of Gorbonianus.

Archgallo began as an evil king bent on destroying the nobles and undoing all his brother had done. He gained a fortune of stolen wealth from the nobles. This caused the nobles to rebel and they deposed Archgallo and replaced him with his brother, Elidurus.

Archgallo wandered throughout the neighbouring countries for five years without friends or a home until he returned to Britain. While he was wandering in the Forests of Calaterium, his brother, Elidurus, found him and embraced him as a brother. He took him to a nearby city and hid him in a room. For a year, Elidurus faked sickness and required all the nobles of the kingdom to visit him. Once there, Elidurus demanded each pledge their allegiance to Archgallo again or they would be beheaded. They complied and after the last had pledged, Elidurus took Archgallo to York and removed his own crown and reinstated Archgallo's kingship. This story is told by William Wordsworth in his poem Artegal and Elidure.

During Archgallo's second reign, he ruled peacefully and faithfully never reverting to his former ways. For ten years he gave the deserved their proper wealth and administered justice throughout the realm. Finally, he fell into a coma and died. He was buried in Leicester and succeeded by Elidurus. Two of Archgallo's sons would later become kings of Britain; Marganus II and Enniaunus.

title: Archgallo


text:
Rime

Rime may refer to:

 * Rime ice, ice that forms when water droplets in fog freeze to the outer surfaces of objects, such as trees.

Rime is also an alternative spelling of "rhyme" as a noun:

 * Syllable rime, term used in the study of phonology in linguistics
 * Rime dictionary, type of ancient Chinese dictionary used for writing poetry
 * Rime table, a syllable chart of the Chinese language
 * Rime riche, a form of rhyme using identical sounds

Literature

 * The Rime of the Ancient Mariner, a 1798 poem by Samuel Taylor Coleridge
 * Le Rime, a collection of lyrical poems by Dante Alighieri
 * The Rime of King William, a poetic eulogy of William the Conqueror written in Old English

Other uses

 * Noémi Rime, French opera singer
 * Rimé movement, an ecumenical movement within Tibetan Buddhism
 * RelayNet International Mail Exchange (RIME), an e-mail exchange networking protocol
 * Rime (video game), an action-adventure video game

title: Rime


text:
J. Barkley Rosser

John Barkley Rosser Sr. (December 6, 1907 – September 5, 1989) was an American logician, a student of Alonzo Church, and known for his part in the Church–Rosser theorem in lambda calculus. He also developed what is now called the "Rosser sieve" in number theory. He was part of the mathematics department at Cornell University from 1936 to 1963, chairing it several times. He was later director of the Army Mathematics Research Center at the University of Wisconsin–Madison and the first director of the Communications Research Division of IDA. Rosser also authored mathematical textbooks.

In 1936, he proved Rosser's trick, a stronger version of Gödel's first incompleteness theorem, showing that the requirement for ω-consistency may be weakened to consistency. Rather than using the liar paradox sentence equivalent to "I am not provable," he used a sentence that stated "For every proof of me, there is a shorter proof of my negation".

In prime number theory, he proved Rosser's theorem.

The Kleene–Rosser paradox showed that the original lambda calculus was inconsistent.

Rosser died of an aneurysm September 5, 1989, at his home in Madison, Wisconsin.

Rosser's son, John Barkley Rosser Jr., was a mathematical economist and professor at James Madison University in Harrisonburg, Virginia.

Selected publications

 * A mathematical logic without variables by John Barkley Rosser, Univ. Diss. Princeton, NJ 1934, p. 127–150, 328–355
 * Logic for mathematicians by John B. Rosser, McGraw-Hill 1953; 2nd ed., Chelsea Publ. Co. 1978, 578 p., ISBN 0-8284-0294-9
 * Highlights of the History of Lambda calculus, by J. Barkley Rosser, Annals of the History of Computing, 1984, vol	 6, n 4, pp. 337–349
 * Simplified Independence Proofs: Boolean Valued Models of Set Theory, by J. Barkley Rosser, Academic Press, 1969
 * See Barkley Rosser papers for a complete list of Rosser's publications.

title: J. Barkley Rosser


text:
Rosser

Rosser may refer to:

People

 * Rosser Evans (1867–?), Welsh international rugby union half-back
 * Arthur Rosser (1864–1954), New Zealand builder, local-body politician and trade unionist
 * Mel Rosser (1901–1988), Welsh international rugby centre
 * Richard Rosser, Baron Rosser (born 1944), British former trade union leader and Labour politician
 * Susan Rosser, British professor of synthetic biology
 * Tania Rosser (born 1978), New Zealand-born Irish rugby union player

Americans

 * Rosser Reeves (1910–1984), American advertising executive
 * Dois I. Rosser Jr. (1921–2019), American businessman
 * Eric Franklin Rosser (born 1952), American former keyboardist for John Mellencamp
 * J. Allyn Rosser (born 1957), American poet
 * J. Barkley Rosser (1907–1989), American logician
 * J. Barkley Rosser Jr. (1948–2023), American mathematical economist
 * Joseph Rosser, American politician
 * Khallifah Rosser (born 1995), American hurdler
 * Ronald E. Rosser (1929–2020), American soldier
 * Thomas L. Rosser (1836–1910), Confederate major general during the American Civil War

Australians

 * Bill Rosser (1927–2002), Australian author and union organiser from Palm Island, Queensland
 * Celia Rosser (born 1930), Australian botanical illustrator
 * Hamish Rosser (born 1974), Australian rock musician

Places

 * Rosser Ridge, Antarctic rock ridge
 * Rosser, Texas, American village
 * Rural Municipality of Rosser, in Manitoba, Canada

Other

 * Rosser International, architectural and engineering firm

title: Rosser


text:
Rumpo

Rumpo is a village in Vormsi Parish, Lääne County in western Estonia.

title: Rumpo


text:
Ingenius of Britain

Ingenius (Welsh: Owain map Morydd) is a legendary king of the Britons as recounted by Geoffrey of Monmouth's pseudohistorical work Historia Regum Britanniae (The History of the Kings of Britain), written c. 1138 CE. Ingenius was the fourth son of King Morvidus and the brother of Gorbonianus, Archgallo, Elidurus, and Peredurus. He came to power in 317BC.

Following the return of Elidurus to the kingship of Britain, Ingenius joined with his brother Peredurus and attacked their older brother. They succeeded in capturing him and locked him in a guarded tower in Trinovantum. Instead of fighting over who ruled the island, they split the island, giving Cornwall to Ingenius and Albany to Peredurus. He ruled his portion of the island for seven years then died, giving the whole of the island to his brother, Peredurus. His son Idvallo would later become king of Britain.

title: Ingenius of Britain


text:
Talk:Matsushima

Poem
The Japanese version of this page disputes the attribution of the Matsushima poem.

 * True, it's not a part of Oku no Hosomichi itself... will add a note, thanks. Jpatokal 07:39, 25 May 2004 (UTC)

Tsunami
Does anybody know how much damage was caused in Matsushima? I don't know if the angle of the bay might have protected it somewhat. I visited once in 2007 and hate to think of that waterfront being obliterated. —Preceding unsigned comment added by 193.61.52.154 (talk) 15:12, 14 March 2011 (UTC)
 * Yes, I have been tweeting about it at my twitter stream. It seems Matsushima is largely safe through some miracle. (The word miracle was used by a Japanese twitterer.) A temple is used as refugee shelter. The nearby military airbase is heavily damaged. However, I do not have any verifiable sources, just Japanese twitter streams and photos from the place. With Wikipedia's current guidelines, that kind of info cannot go into the article, I think, no matter how true it is. --Mlewan (talk) 10:59, 16 March 2011 (UTC)
 * Good news. I added an NPR citation of little damage and removed the notice. ★NealMcB★ (talk) 15:51, 18 April 2011 (UTC)

The people didn't went to the shrine. Read this article: http://articles.latimes.com/2012/mar/11/opinion/la-oe-holguin-veras-tsunami-20120311 — Preceding unsigned comment added by 79.218.109.155 (talk) 09:06, 31 March 2012 (UTC)

Ancient Ainu cave dwellers
There is video on youtube "A trip through japan with the ywca ca 1919", and in it at 2:30 - "The famous caves and tombstones of Matsushima, relics of ancient Ainu cave dwellers". If it is really famous, probably it should be mentioned in the article OtroQus (talk) 07:42, 29 June 2024 (UTC)

title: Talk:Matsushima


text:
Elidurus

Elidurus the Dutiful (Welsh: Elidyr map Morydd) was a legendary king of the Britons as recounted by Geoffrey of Monmouth. He reigned in the late fourth century BC. He was the third son of King Morvidus and brother of Gorbonianus, Archgallo, Ingenius, and Peredurus.

Elidurus became king following the deposition of his brother, Archgallo. He found his brother wandering in a forest five years after Elidurus was crowned. He embraced him as a brother and took Archgallo in secrecy to a nearby city. Faking a sickness, he summoned all the nobles of the kingdom to that city to visit him. Once there, Elidurus demanded they all repledge their allegiance to Archgallo under penalty of death. Once done, Elidurus took Archgallo to York and removed his own crown and reinstated Archgallo as king of the Britons. For this, he was surnamed the Dutiful.

Ten years later, Archgallo died and Elidurus became king once again. He reigned for a few years in the manner of his eldest brother, Gorbonianus. Soon after, though, his two younger brothers, Ingenius and Peredurus, built armies and attacked Elidurus. They seized him and locked him in a guarded tower in Trinovantum. He remained locked in the tower for more than seven years.

When his youngest brother, Peredurus, finally died, the realm returned to Elidurus for a third time. He reigned for a short while in justice and virtue then died. He was succeeded by an unnamed son of Gorbonianus. His son, Gerennus, would later become king of Britain.

title: Elidurus


text:
Punjab & Sind Bank

Punjab & Sind Bank is an Indian public sector bank headquartered in New Delhi. the bank has 1553 branches which are widely spread across India out of which 635 branches are in the state of Punjab, and 25 zonal offices located all over India.

History
The bank was established in Amritsar on 24 June 1908 by Bhai Vir Singh, Sir Sunder Singh Majitha, and Sardar Tarlochan Singh to serve the then Sind and Punjab areas of colonial India.

On 15 April 1980, Punjab & Sind Bank was among six banks that the Government of India nationalised in the second wave of nationalisation (the first wave had been in 1969 when the government nationalised the top 14 banks).

In the 1960s Punjab & Sind Bank established a branch in London. In 1991 Bank of Baroda acquired Punjab & Sind Bank's London branch at the behest of the Reserve Bank of India following Punjab & Sind's involvement in the Sethia fraud in 1987.

Since 2004, the bank has shown growth of over 40% year on year, and its IPO was oversubscribed by more than 50 times.

On 16 July 2019, Punjab & Sind Bank disclosed that it detected a fraud, worth inr 2380000000 by the Bhushan Power & Steel Limited.

Products

 * Aadhaar Pay
 * ATM
 * BharatQR
 * BHIM
 * Debit card
 * Internet Banking
 * Mobile Banking
 * POS Machine
 * SMS Banking
 * UPI

Financial performance
In FY 2019-20 Punjab & Sind Bank recorded a Net Loss of Rs.990.80 crore.

 * Total business of the bank stood at Rs. 1,52,231.75 crore.
 * The operating profit for the year ending 2019-20 is Rs. 1097 crores.
 * Gross NPA is 14.18% for the year ending 2019-20 amounting to Rs 8875 crores.
 * Net NPA is 8.03% for the year ending 2019-20 amounting to Rs 4684 crores.
 * Provision Coverage Ratio as on 31 March 2020 stood at 66.74%.
 * The Net Worth of the bank stood at Rs. 2917 crore as on 31.03.2020.
 * Total Income of the bank during the year stood at Rs 8827 crore.

The Capital Adequacy Ratio (Basel III) of the Bank is 12.76% as on 31.03.2020.

title: Punjab & Sind Bank


text:
User:Wasabe3543

Nothin' to see here. User:Wasabe3543/temp

I'm a man, and I'm torn between vengeance and fashion

Contributions

title: User:Wasabe3543