text:
Wikipedia:Featured article candidates/Fractal/archive1

Fractal
I noticed we don't have many featured articles on mathematics. This is one of the few math topics with widespread appeal and lots of pretty pictures. Although it looks a bit short at first, if you follow the links to the specific types of fractals, there's a lot of material. I've verified the image copyrights and they all appear to be GFDL or public domain. --Shibboleth 23:56, 2 Jul 2004 (UTC)
 * Support. Having spent hours upon hour exploring microscopic regions of the Mandelbrot set, I can only say, "It's about time..." Denni ☯ 05:49, 2004 Jul 3 (UTC)
 * (Not a vote). It looks like all of the images are in the public domain (created by Wikipedians), but some fail to note so explicitly. Jeronimo 11:31, 3 Jul 2004 (UTC)
 * Now the only picture that does not explicitly specify public domain or GFDL is the Koch snowflake picture. Unfortunately the user who added it is not around anymore, so we cannot ask him to add the label.  But I am inclined to think an elementary mathematical illustration like this cannot be copyrighted anyway.  If it really bothers someone, it should be easy to re-create. --Shibboleth 21:38, 4 Jul 2004 (UTC)

 * Object. 1) The lead section needs to be longer, including a mention that "fractal"s is derived have "fractional dimension", amongst other things. 2) We should discuss Fractal art in this article to some extent, given that most laymen encounter fractals in that form. 3) Similarly there needs to be a much more in-depth discussion of applications: Fractal landscape, Fractal compression...; we currently have "Fractal techniques have also been employed in fractal image compression, as well as a variety of scientific disciplines." 4) The article emphasises self-similarity; an image sequence would be one obvious way to illustrate this concept, e.g. a sequence of zooms on a fractal, showing self-similarity on different scales. 5) You can't read much about fractals without bumping into a discussion of chaos theory; what's the link? The article doesn't discuss this. — Matt 16:39, 3 Jul 2004 (UTC)
 * [Etymology of fractal: although some web sources say fractal is derived from "fractional dimension", Mandelbrot himself says he coined it from the Latin fractus - see, for example, Mandelbrot's essay "Fractals - a geometry of nature" in "The New Scientist Guide to Chaos". I have added this to the article.Gandalf61 11:41, Jul 4, 2004 (UTC)]
 * Ah, great. Maybe it's worth mentioning the mis-etymology of "fractal" as well, since it's quite common? — Matt 15:36, 4 Jul 2004 (UTC)
 * I've added a sequence of images demonstrating self-similarity. [[User:Sverdrup|❝Sverdrup❞ ]] 13:54, 4 Jul 2004 (UTC)
 * Thanks, spot on. — Matt 15:36, 4 Jul 2004 (UTC)
 * This is good but I don't find the sequence of images quite clear enough as it is. The problem is that since they all look so similar, it's hard to understand at first sight that the fourth image is a 100x (or whatever) magnification of the first: it looked to me at first like just a big rotated chunk of the first, until I understood that your red squares meant "zoom".  I would like a label added to the top of each image saying "Magnification: 1x", "Magnification: 5x", "Magnification: 25x" (or whatever the exact numbers are).  Or even better, nice arrows linking the red square of one image with the next image.  Though come to think of it I don't really know which would work better. --Shibboleth 21:59, 4 Jul 2004 (UTC)

 * Support Avala 19:34, 4 Jul 2004 (UTC)
 * Neutral - the article looks fantastic and reads fine but it does seem to be a bit short. I think some basic expansion is needed, but since I don't know much about this topic, I don't know what to suggest (and thus my non-vote). :( --mav 10:11, 10 Jul 2004 (UTC)

Jules Ruis says: I want to add some information about the Julius Ruis Set, being a smart presentation of 400 Julia sets, showing that the Mandelbrot set is the parameter basin of all closed Julia sets.


text:
User:Sbb

Quick text for some common table edits

 * Side-by-side tables : Wrap table in DIV with:
 * Nowrap :  in a non-header cell.

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

title: User:Sbb


text:
VVT-i

VVT-i, or Variable Valve Timing with intelligence, is an automobile variable valve timing petrol engine technology manufacturer by Toyota Group and used by brands Groupe PSA (Peugeot and Citroen), Toyota, Lexus, Scion, Daihatsu, Subaru, Aston Martin, Pontiac and Lotus Cars. It was introduced in 1995 with the 2JZ-GE engine found in the JZS155 Toyota Crown and Crown Majesta. The VVT-i system replaces the previous Toyota VVT system introduced in 1991 with the five-valve per cylinder 4A-GE "Silver Top" engine found in the AE101 Corolla Levin and Sprinter Trueno. The VVT system is a 2-stage hydraulically controlled cam phasing system. VVT-i varies the timing of the intake valves by adjusting the relationship between the camshaft drive (belt or chain) and intake camshaft. Engine oil pressure is applied to an actuator to adjust the camshaft position. Adjustments in the overlap time between the exhaust valve closing and intake valve opening result in improved engine efficiency. Variants of the system, including D4 (VVT-i D4), D4-S, VVTL-i, Dual VVT-i, VVT-iE, VVT-iW and Valvematic have followed.

D4
D4 (stands for Direct Four Line), are Toyota's atmospheric engines with petrol direct injection. This engine is sometimes referred to as VVT-i D4 in sources. Commonly used in Toyota Avensis and Toyota RAV4.

D4-S
D4-S (stands for: Direct Four Line Supercharged) are Toyota's supercharged engines with petrol direct injection. This engine was developed in collaboration with Subaru and was used in the Toyota 86 and Subaru BRZ models.

VVTL-i

VVTL-i (Variable Valve Timing and Lift intelligent system) (also sometimes denoted as VVT-iL or Variable Valve Timing and Intelligence with Lift) is an enhanced version of VVT-i that can alter valve lift (and duration) as well as valve timing. In the case of the 16-valve 2ZZ-GE, the engine head resembles a typical DOHC design, featuring separate cams for intake and exhaust and featuring two intake and two exhaust valves (four total) per cylinder. Unlike a conventional design, each camshaft has two lobes per cylinder, one optimized for lower rpm operation and one optimized for high rpm operation, with higher lift and longer duration. Each valve pair is controlled by one rocker arm, which is operated by the camshaft. Each rocker arm has a slipper follower mounted to the rocker arm with a spring, allowing the slipper-follower to freely move up and down with the high lobe without affecting the rocker arm. When the engine is operating below 6000-7000 rpm (dependent on year, car, and ECU installed), the lower lobe is operating the rocker arm and thus the valves, and the slipper-follower is freewheeling next to the rocker arm. When the engine is operating above the lift engagement point, the ECU activates an oil pressure switch which pushes a sliding pin under the slipper-follower on each rocker arm. The rocker arm is now locked into the slipper-follower's movements and thus follows the movement of the high rpm cam lobe and will operate with the high rpm cam profile until the pin is disengaged by the ECU. The lift system is similar in principle to Honda's VTEC operation. The system was introduced in the 2ZZ-GE found in the 1999 Toyota Celica. Toyota has ceased production of its VVTL-i engines in most markets, because the engine does not meet Euro IV specifications for emissions regulations. As a result, this system has been discontinued on some Toyota models, including the Corolla T-Sport (Europe), Corolla Sportivo (Australia), Celica, Corolla XRS, Matrix XRS, and the Pontiac Vibe GT, all of which had the 2ZZ-GE engine fitted. The Lotus Elise and Exige continued to offer the 2ZZ-GE engine until 2011, with the Exige offering the engine with a supercharger.

Dual VVT-i

The Dual VVT-i system adjusts timing on both the intake and exhaust camshafts. It was introduced in 1998, on the Altezza RS200's 3S-GE engine. Dual VVT-i is also found in Toyota's 3.5-litre 2GR-FE V6 engine, first appearing on the 2005 Avalon. This engine can be found on numerous Toyota and Lexus models. By adjusting the valve timing, engine start and stop occurs almost unnoticeably at minimum compression. Fast heating of the catalytic converter to its light-off temperature is possible, thereby reducing hydrocarbon emissions considerably. Most Toyota engines including the 1LR-GUE (V10, used in the Lexus LFA), UR engines (V8), GR engines (V6), AR engines (large I4), ZR engines (medium I4), and NR engines (small I4) use this technology.

VVT-iE

VVT-iE (Variable Valve Timing - intelligent by Electric motor) is a version of Dual VVT-i that uses an electrically operated actuator to adjust and maintain intake camshaft timing. The exhaust camshaft timing is still controlled using a hydraulic actuator. This form of variable valve timing technology was developed initially for Lexus vehicles. This system was introduced on the 1UR-FSE engine in the 2007 Lexus LS 460. The electric motor in the actuator spins together with the intake camshaft as the engine runs. To maintain camshaft timing, the actuator motor will operate at the same speed as the camshaft. To advance the camshaft timing, the actuator motor will rotate slightly faster than the camshaft speed. To retard camshaft timing, the actuator motor will rotate slightly slower than camshaft speed. The speed difference between the actuator motor and camshaft timing is used to operate a mechanism that varies the camshaft timing. The benefit of the electric actuation is enhanced response and accuracy at low engine speeds and at lower temperatures as well as a greater total range of adjustment. The combination of these factors allows more precise control, resulting in an improvement of both fuel economy, engine output and emissions performance.

VVT-iW

VVT-iW (Variable Valve Timing - intelligent Wide) was introduced with the 2.0L turbocharged direct-injected 8AR-FTS fitted to the Lexus NX 200t. VVT-iW uses VVT-iW on the intake valves and VVT-i on the exhaust valves. The intake cam has mid-position cam lock mechanism that retards the continuously variable timing. It offers expanded valve opening angles (Wide) which enables the engine to operate in a modified-Atkinson cycle at low rpm for improved economy and lower emissions, and in the Otto cycle at high rpm for better performance, while delivering high torque throughout the rpm band.

Valvematic

The Valvematic system offers continuous adjustment to valve lift and timing and improves fuel efficiency by controlling the fuel/air intake using valve control rather than conventional throttle plate control. The technology made its first appearance in 2007 with the 3ZR-FAE engine in the Noah and later in early-2009 in the Avensis. This system is simpler in design compared to Valvetronic and VVEL, allowing the cylinder head to remain at the same height.

VVT-i oil supply hose issues
In 2010, Toyota USA announced a Limited Service Campaign (LSC 90K) to replace the rubber portion of the oil supply hose for the VVT-i actuator on the 2GR-FE (V6) engine, which were found to be defective. In all, approximately 1.6 million vehicles manufactured prior to 2008 were affected. The defective oil supply hoses were prone to degradation and eventual rupture, causing oil to rapidly leak and resulting in permanent engine damage. In 2014, the LSC 90K Campaign was extended to 31 December 2021 on 117,500 Toyota brand vehicles that were "missed" during the initial campaign.

title: VVT-i


text:
List of German corps in World War II

List of German corps in World War II

This is a list of German Army corps that existed during World War II.

I–IX

 * I Army Corps
 * II Army Corps
 * III Army Corps
 * IV Army Corps
 * V Army Corps
 * VI Army Corps
 * VII Army Corps
 * VIII Army Corps
 * IX Army Corps

X–XIX

 * X Army Corps
 * XI Army Corps
 * XII Army Corps
 * XIII Army Corps
 * XIV Army Corps
 * XV Army Corps
 * XVI Army Corps
 * XVII Army Corps
 * XVIII Army Corps
 * XIX Army Corps

XX–XXIX

 * XX Army Corps
 * XXI Army Corps
 * XXII Army Corps
 * XXIII Army Corps
 * XXIV Army Corps
 * XXV Army Corps
 * XXVI Army Corps
 * XXVII Army Corps
 * XXVIII Army Corps
 * XXIX Army Corps

XXX–XXXIX

 * XXX Army Corps
 * XXXI Army Corps
 * XXXII Army Corps
 * XXXIII Army Corps
 * XXXIV Army Corps
 * XXXV Army Corps
 * XXXVI Army Corps
 * XXXVIII Army Corps
 * XXXIX Army Corps

XXXX–XXXXIX

 * XXXX Army Corps
 * XXXXI Army Corps
 * XXXXII Army Corps
 * XXXXIII Army Corps
 * XXXXIV Army Corps
 * XXXXVI Army Corps
 * XXXXVII Army Corps
 * XXXXVIII Army Corps

L–LIX

 * L Army Corps
 * LI Army Corps
 * LII Army Corps
 * LIII Army Corps
 * LIV Army Corps
 * LV Army Corps
 * LVI Army Corps
 * LVII Army Corps
 * LIX Army Corps

LX–LXIX

 * LXII Army Corps
 * LXIII Army Corps
 * LXIV Army Corps
 * LXV Army Corps
 * LXVI Army Corps
 * LXVII Army Corps
 * LXVIII Army Corps
 * LXIX Army Corps

LXX–LXXIX

 * LXX Army Corps
 * LXXI Army Corps
 * LXXII Army Corps
 * LXXIII Army Corps
 * LXXIV Army Corps
 * LXXV Army Corps
 * LXXVI Army Corps
 * LXXVIII Army Corps

LXXX–LXXXIX

 * LXXX Army Corps
 * LXXXI Army Corps
 * LXXXII Army Corps
 * LXXXIII Army Corps
 * LXXXIV Army Corps
 * LXXXV Army Corps
 * LXXXVI Army Corps
 * LXXXVII Army Corps
 * LXXXVIII Army Corps
 * LXXXIX Army Corps

LXXXX–CI

 * XC Army Corps
 * XCI Army Corps
 * XCVII Army Corps
 * CI Army Corps

Motorised corps

 * III Motorised Corps
 * XIV Motorised Corps
 * XV Motorised Corps
 * XVI Motorised Corps
 * XIX Motorised Corps
 * XXII Motorised Corps
 * XXXIX Motorised Corps
 * XXXX Motorised Corps
 * XXXXI Motorised Corps
 * XXXXVI Motorised Corps
 * XXXXVII Motorised Corps
 * XXXXVIII Motorised Corps
 * LVI Motorised Corps
 * LVII Motorised Corps

Panzer corps

 * III Panzer Corps
 * IV Panzer Corps
 * VII Panzer Corps
 * XIV Panzer Corps
 * XIX Panzer Corps
 * XXIV Panzer Corps
 * XXXVIII Panzer Corps
 * XXXIX Panzer Corps
 * XL Panzer Corps
 * XXXXI Panzer Corps
 * XLVI Panzer Corps
 * XLVII Panzer Corps
 * XXXXVIII Panzer Corps
 * LVI Panzer Corps
 * LVII Panzer Corps
 * LVIII Panzer Corps
 * LXXVI Panzer Corps
 * Panzer Corps Feldherrnhalle
 * Panzer Corps Großdeutschland

Mountain corps

 * XV Mountain Corps
 * XVIII Mountain Corps
 * XIX Mountain Corps
 * XXI Mountain Corps
 * XXII Mountain Corps
 * XXXVI Mountain Corps
 * XXXXIX Mountain Corps
 * LI Mountain Corps
 * Norwegen Mountain Corps

Reserve corps

 * LXI Reserve Corps
 * LXII Reserve Corps
 * LXIV Reserve Corps
 * LXVI Reserve Corps
 * LXVII Reserve Corps
 * LXIX Reserve Corps

Miscellaneous corps

 * Afrika Korps
 * I Cavalry Corps
 * I Military Police Corps
 * II Military Police Corps
 * III Military Police Corps

Höheres Kommando z.b.V.

 * Höheres Kommando z.b.V. XXXI
 * Höheres Kommando z.b.V. XXXII
 * Höheres Kommando z.b.V. XXXIII
 * Höheres Kommando z.b.V. XXXIV
 * Höheres Kommando z.b.V. XXXV
 * Höheres Kommando z.b.V. XXXVI
 * Höheres Kommando z.b.V. XXXVII
 * Höheres Kommando z.b.V. XXXXV
 * Höheres Kommando z.b.V. LIX
 * Höheres Kommando z.b.V. LX
 * Höheres Kommando z.b.V. LXV
 * Höheres Kommando z.b.V. LXX
 * Höheres Kommando z.b.V. LXXI

SS infantry corps

 * VI SS Corps
 * X SS Corps
 * XI SS Corps
 * XII SS Corps
 * XIII SS Corps
 * XIV SS Corps
 * XVI SS Corps
 * XVIII SS Corps

SS Panzer corps

 * I SS Panzer Corps
 * II SS Panzer Corps
 * III (Germanic) SS Panzer Corps
 * IV SS Panzer Corps
 * VII SS Panzer Corps

SS miscellaneous corps

 * SS Medical Corps
 * V SS Mountain Corps
 * VIII SS Cavalry Corps – planned in 1945 but not formed
 * IX SS Mountain Corps
 * XV SS Cossack Cavalry Corps
 * XVII Waffen Corps of the SS (Hungarian)

Fliegerkorps (air corps)

 * I Fliegerkorps
 * II Fliegerkorps
 * III Fliegerkorps
 * IV Fliegerkorps
 * V Fliegerkorps
 * VI Fliegerkorps
 * VII Fliegerkorps
 * VIII Fliegerkorps
 * IX Fliegerkorps
 * X Fliegerkorps
 * XI Fliegerkorps
 * XII Fliegerkorps
 * XIII Fliegerkorps
 * XIV Fliegerkorps
 * Fliegerkorps Tunis

Jagdkorps

 * I Jagdkorps
 * II Jagdkorps

Flak corps

 * I Flak Corps
 * II Flak Corps
 * III Flak Corps
 * IV Flak Corps
 * V Flak Corps
 * VI Flak Corps

Parachute (Fallschirmjäger) corps

 * I Parachute Corps
 * II Parachute Corps
 * Fallschirm-Panzerkorps Hermann Göring

Field corps

 * I Luftwaffe Field Corps
 * II Luftwaffe Field Corps
 * III Luftwaffe Field Corps
 * IV Luftwaffe Field Corps

title: List of German corps in World War II


text:
Talk:Thompson sporadic group

Re the question of whether this article should be merged with "Thompson groups", I would say definitely not. The sporadic Thompson group and the infinite Thompson groups are about as unrelated as two concepts in group theory can be, and are named completely independently after two different people both called Thompson. Best wishes, Cambyses 14:36, 21 Jul 2004 (UTC)

Title
"(mathematics)" seems like the wrong disambiguation; see Talk:Suzuki group (mathematics) --GodMadeTheIntegers (talk) 18:18, 28 April 2015 (UTC)
 * There are three sporadic groups with names that need disambiguation. McLaughlin group (mathematics), Suzuki group (mathematics), and Thompson group (mathematics).  This disambiguation seems the most consistent choice to me.--Foobarnix (talk) 21:23, 28 April 2015 (UTC)

title: Talk:Thompson sporadic group


text:
Central Flying School SAAF

The Central Flying School is a flight school of the South African Air Force. It is an ab initio flight training school. The unit was formed as the central point of flying training after closure of all Air Force flying schools in South Africa. The unit operates a fleet of 55 aircraft and qualifies approximately 50 students and 20 instructors per annum.

title: Central Flying School SAAF


text:
Wikipedia:Featured article candidates/Middle-earth/archive1

Middle-earth
Self nomination (I worked on it a bit, and a lot on other Middle-earth articles). A good starting page for Wikipedian Tolkienists. Ausir 20:57, 4 Jul 2004 (UTC)

 * It's a good article, but too much of it is lists, really. Oh, and there is too much text before the TOC.  Morwen - Talk 21:16, 4 Jul 2004 (UTC)
 * Way, way, way, way too much list - that's 80% of the article. →Raul654 21:18, Jul 4, 2004 (UTC)
 * I agree, much of it reads as though it's trying to perform the role of a Category. Oppose, for now, at least. — OwenBlacker 11:11, Jul 5, 2004 (UTC)
 * these objections are now irrelevant ;) Morwen - Talk 11:12, 8 Jul 2004 (UTC)

 * I've moved the whole list to List of Middle-earth articles by category. Ausir 11:42, 5 Jul 2004 (UTC)
 * Well, thats sort of an improvement I suppose. However now its rather shorter.  It needs a detailed summary of the whole creation myth; the Ages; who the principal races are - that sort of thing.  Summaries of the plots of the Hobbit and LOTR perhaps.   Morwen - Talk 14:50, 5 Jul 2004 (UTC)

 * Object. The map image is copyrighted, per the website from which it was taken. Jeronimo 17:55, 5 Jul 2004 (UTC)
 * The website's conditions of use indicate that items can be used for non-commercial purposes, under certain conditions, which are, in this case, met. See Snowspinner 18:10, Jul 5, 2004 (UTC)

 * I'll support. Could use another image. [[User:Meelar|Meelar (talk)]] 18:24, 5 Jul 2004 (UTC)
 * Specifically, it could use an image of Middle-earth as a whole- at the moment there are only parts. Markalexander100 07:03, 6 Jul 2004 (UTC)
 * There's an image of the whole world of Arda in "The world" section. The action of the books never takes place in other areas of Middle-earth than the north-western part, so there is not much info about the east of Middle-earth. Ausir 07:39, 6 Jul 2004 (UTC)
 * I've added a wodge of summary of history. Support.  Morwen - Talk 22:08, 5 Jul 2004 (UTC)
 * Object. Needs a lead section. — Matt 23:43, 8 Jul 2004 (UTC)
 * How is that? Morwen - Talk 18:20, 10 Jul 2004 (UTC)
 * Support (partial self-nomination). I have helped put in a bit of work coping with concerns raised above and believe they have now been addressed. Anarion 08:40, 7 Jul 2004 (UTC)
 * Support - excellent article, informative. --[[User:OldakQuill|Oldak Quill]] 13:55, 8 Jul 2004 (UTC)
 * Support. Hmm, can you throw some bones to the LotR movie fans who'll be reading? - David Gerard 23:22, 8 Jul 2004 (UTC)
 * Object - overwhelming TOC and article triggers a page size warning. I suggest summarizing the history and moving the detail to a separate article. Also does not follow MoS by having links in headings. --mav 06:18, 10 Jul 2004 (UTC)
 * Bah. Do you realise how hard it was to get the history that short already?   Morwen - Talk 10:49, 10 Jul 2004 (UTC)
 * Better now? I don't think it can be made any shorter and still make sense. Ausir 11:04, 10 Jul 2004 (UTC)
 * I've also done some removal of headers so the TOC is not so bad now.. Morwen - Talk 18:20, 10 Jul 2004 (UTC)
 * Great work - support. --mav 05:24, 11 Jul 2004 (UTC)


text:
Wikipedia talk:Naming conventions (Old Norse/Old Icelandic/Old English)/Archive 1

Proposal
In articles dealing with Old Norse mythology the spelling of names should be that of standardized 13th century Old Icelandic as found in, for example, the Íslenzk fornrit edition of Snorri Sturluson's Heimskringla.

In accordance with the English Wikipedia convention to use forms familiar to English speakers the following exceptions are made:

1. The English familiar form Thor should be used instead of the Old Icelandic form Þórr.

2. The English familiar form Odin should be used instead of the Old Icelandic form Óðinn.

3. In other cases when someone proposes that a familiar English form exists, this can be discussed on an individual basis on the relevant talkpage.

Due to current technical limitations the letter oe-ligature (œ) cannot properly be used in article titles. For purposes of article titles it should be replaced with 'oe' while œ can used throughout the article. Since o-ogonëk will not display correctly on many systems it should be replaced throughout with 'ö'. This is unambiguous since 'ö' does not otherwise occur in standardized Old Norse spelling, and it is a common replacement for o-ogonëk.

Reasoning
As described in Old Norse orthography there is currently no generally accepted standard for the use of Old Norse names within an English text, inside or outside Wikipedia. One source may use the anglizised form Balder while the next employs the modern Icelandic form Baldur and the third uses the standardized Old Icelandic form Baldr. The mainland Scandinavian languages have their own familiar forms of the names and those sometimes also make their way into English prose. Current examples on Wikipedia include the Swedish form 'Väderfölni (seen on Norse mythology) and the Norwegian form Vêrfolne (seen on Vêrfolne) for the being known in Old Norse as Veðrfölnir.

It is the hope of the authors that this standard establishes a consistent and accurate convention to use within Wikipedia.

Examples

 * Loki
 * Baldr
 * Freyja
 * Freyr
 * Heimdallr
 * Angrboða
 * Svaðilfari
 * Höðr
 * Þrymr
 * Veðrfölnir
 * Hoenir as article title, Hœnir within the article

Activation
This standard was proposed by Wiglaf and Haukurth on May 21st 2005. It will become active one month from that date if no objections have surfaced by then.

=Old discussion below=

The articles on Norse mythology show a variety of forms: Old Norse, Modern Scandinavian and modern Icelandic.

The main page says: Generally, article naming should give priority to what the majority of English speakers would most easily recognize with a reasonable minimum of ambiguity, while at the same time making linking to those articles easy and second nature.

Concerning names such as Loki, Odin and Thor, there are standard forms. You will however find other forms that may seem confusing for some less knowledgeable readers, such as Þórr. such forms should be standardised (within articles) to make the reading easier. A limit to this standardisation should be when there are non-Scandinavian forms, such as Thunor or Woden.

Should there be a rule, such as

 * 1) If there is a standard form in English, then that form is used.
 * 2) If there is no such standard form a modern Scandinavian form should be used (I don't mean this as an offense to Icelanders but Wikipedia is a work of reference and there are about 80 times more Scandinavians than Icelanders.)
 * 3) If there is no modern Scandinavian form, the Old Norse form is used.

Any opinions? Wiglaf

 * Here's one opinion. I agree with the above. Personally, I wouldn't dream of imposing modern Icelandic on the world. :-) But I have a question about:

 * If there is no such standard form a modern Scandinavian form should be used.

 * Which modern Scandinavian? AFAIK, there's no standard form for most of the names, and there are at least four Scandinavian languages (here meant to be synonymous with continental North-Germanic). Is there some work in the field which can be supposed to be known to most educated Scandinavians? If so, I'd suggest using that.

 * In any case, I support Wiglaf on this with the following addition:

 * If names from mythology are given in an English or Scandinavian form, it should be permitted as a matter of course, without anyone taking offence, to add the standardized Old Norse names in parentheses where appropriate. See Baldur and Valkyrie for examples of what I mean. Furthermore, that the Old Norse names, where supplied, should conform to the standard as applied in the standard Icelandic scholarly editions (samræmd stafsetning forn). I'm not suggesting that out of nationalism, but because, AFAIK, that is the only standard there is. Editors outside Iceland largely follow their personal conventions. Cheers Io 16:33, 21 Jul 2004 (UTC)

 * PS: I'm wondering, since Wikipedia is a work of reference, whether it might be a good idea to create a page called Norse_Mythology_(names), where the English or Scandinavian names are listed with their Old Norse equivalents. Readers want to read about who Oden/Odin/Óðinn was of course, but they might also want to know what he was actually called. I'd be willing to this, if it is believed to be woth the while. Any comments? Io 16:47, 21 Jul 2004 (UTC)

 * I'll do it. It will take a while, but I think we have a solution to make everyone happy. And the best of luck with your thesis. Io 20:33, 21 Jul 2004 (UTC)

Certainly my understanding of the correct English spelling of Baldur was, er, Baldur. But let us not trivialise or demean the deities by transliterating them slavishly; let us have our Jords, Manis et al. It retains the charm, allure and mystique of a charming and beautiful mythos. Sjc 19:49, 21 Jul 2004 (UTC)

More Information
No, particular site that I know of that uses Cassell especially. Everyone's use is probably slightly different.

Joseph Campbell used no diacritics and ae for æ, at least in his popular writing. He similarly generally avoided fancy diacritics and spellings for Hindu or Semitic names.

In Poul Anderson's War of the Gods he used no diacrtics and æ as ae. But in Poul Anderson's more recent novel Mother of Kings though he continued to use ae rather than æ and no acute marks, o-ogonek or o-dieresis was represented by ö. As I mentioned previously, the practise of dropping the acute accent but retaining ö has been a common one. This seems to be what the web Encyclopædia Britannica mostly intended to do, as it has forms such as Jörd, Njörd, Jörmungand, Höd, Mjölnir, Ragnarök, and Völuspá. The use of á here is unusual for Britannica. I don't find any other acutes in Norse forms except where it is specifically giving the genuine Old Norse forms as opposed to its Anglicized versions. Another recent example that retainins only ö of vowels with diacritics is Barbara Leonie Picard's Tales of the Norse Gods.

An old example of this method of Anglicization is found in H. A. Guerbir's Myths of the Norsemen from the 1920s. (Guerbir also generally uses i instead of j, something not much found any more though not entirely dead.).

The humorous Norse Mythology ... according to Uncle Einar drops all diacritics but keeps æ, following the Penguin norm.

Microsoft Encarta drops all diacritics. But it lists Freyr as Frei and Freya as his wife!!! See Encarta: Frei. People pay for this?

On the other side, John Lindow's Norse Mythology: A Guide to the Gods, Heroes, Rituals and Beliefs (which contains a short dictionary/encyclopedia of Norse gods and heroes) uses full diacritics (only replacing o-ogonek by ö), using either the same system as the Cassels's Dictionary of Norse Myth & Legend'' or something very close to it. I presume the same method appears in Handbook of Norse Mythology by the same author. Jean Young's translation: Prose Edda of Snorri Sturluson: Tales from Norse Mythology from 1954 does the same, except that even ð is retained, so Óðnn is just 'Óðin.

For the ultimate extreme, The Oxford History of the Vikings contains only Old Norse and other original forms, no Anglicizations whatsoever.

I may be overdoing it, but I would like a clear record as to the justification for whatever system is decided on.

I personally agree with Wiglaf on generally retaining diacritics, even though they are more often dropped in translations or appearances in modern fictional works, because an encyclopedia is in a somewhat different category, the diacritics are not always dropped in English translations, and scholarly works of a popular sort often retain them. However one would still often want to list the actual supposed standard Old Norse form to provide case ending information.

To play devil's advocate, since Anglicized forms using only strict US-ASCII spellings are so very common in English use (including many scholarly translations) a case could be made that generally only two forms should be listed, the extremely Anglicized form (as the norm) and the full standard Old Norse form with diacritics, this form to be listed in the header paragaph of names that have their own entry and on the first mention in an article for other names. From these two forms all other forms can be extrapolated, though where in common use they might be listed separately.

For example, if fully Anglicized forms are standard, then we have articles entitled Aesir and Njord and Thor which mention in the header paragraph that the genuine Old Norse forms are Æsir and Njǫrðr and Þórr. If Anglicized forms with diacritics and with æ retained are to be standard, then we have articles entitled Æsir and Njörd and Thór but with the same mention of genuine Old Norse forms. (For a few names like Thor, where a particular form is very common, we would however make an exception as is done by Brodeur and by Cassell's.) The reader is to understand that diacritics are often removed. But the numerous alternate forms can be and probably should be listed by template, for example: Njörd (Old Norse Njǫrðr), the Norse god of .... etc. etc. Alternate renderings in English: Nr(r) Or is this listing superior?: "Other renderings in English: Njord, Niord, Niörd, Njordr, Njördr, Njörð, Njördhr, Njordhr, Njorth, etc." Both rendering methods are messy, yet all forms given here in the second method are found in English for this one single-syllable name. Perhaps use the template format only when there are more than four possibilities. Many have far less, for example Balder has only three: Baldr, Balder, and Baldur. But that could be represented by the template Bald(e/u)r.

I set forth here what seem to be the common ways in which English forms should differ from standard Old Norse forms in extreme Anglicization:
 * 1) The letters þ, ð and ǫ should be represented respectively by th, d, and ö (not considering in this point whether ö should be retained as ö or changed to o which is the subject of point 4). Y/N
 * 2) Nominative case endings should normally be dropped (setting aside for the moment any exact rules about when they might be occasionally retained). Y/N
 * 3) The acute accent should be dropped. Y/N
 * 4) The dieresis accent should be dropped. Y/N
 * 5) The letters æ and œ should be represented respectively as ae and oe. Y/N

I believe we have consensus on point 1 and 2. What of the other points? How far do we go in towards extreme Anglicization. I currently prefer, as does Wiglaf, I believe, that the answer should be no to points 3–4 and that we standardize on the more technical usage found most recently in Cassel's and in John Lindow's writing (and in older usage in Brodeur among others). But is there consensus? Jallan 04:03, 25 Jul 2004 (UTC)

 * Since this page is running over 35 kb and is getting rather long, I have taken the liberty of shortening it considerably. I hope I don't offend anyone by doing so.

 * I think we're arriving at something here. Thanks for the interesting review!

1. Yes. The letters þ, ð and ǫ should be represented respectively by th, d, and ö (not considering in this point whether ö should be retained as ö or changed to o which is the subject of point 4). 2. Yes, the dropping of case endings should be acceptable to most people. I don't understand why a case ending should be retained in a non-case language, even if it is in the nominative. With exceptions for certain well-known and monosyllabic names, such as Baldr, Hödr and perhaps Freyr. For pronunciation reasons I suggest "Balder" and "Höder" to be the exceptions to this rule. Moreover, "Balder" is the most common English and Scandinavian form, and there's no reason to exclude his brother Höder from this, as they most famously appear in the same story.
 * For what it is worth, in their definitions on Balder the Oxford English Dictionary gives the name as Hödur but Webster and Britannica both give Höd. Höd is even a short stub entry in Britannica. :-(  Jallan 21:49, 25 Jul 2004 (UTC)

3. I hesitate. Odin and Thor are household forms in English language popular culture. The accute accent should be noted in the articles, though.
 * If acuate accents were generally represented, Odin and Thor would come under the rule of keeping forms that had become common irrespective of what rules are otherwise applied. For that reason Brodeur and Cassel's also leave the acute accent off these names though applying acute accents otherwise. Jallan 21:49, 25 Jul 2004 (UTC)

4. No. Ö is too well-known in popular culture to be dropped.It also has Nordic and Germanic connotations.
 * The English dictionaries I consulted don't provide any entries for an Old Norse ö name that I could discover. But as mentioned above I did find Hödur and Höd in entries on Balder, which suggests a similar feeling that one should retain ö at least. Jallan 21:49, 25 Jul 2004 (UTC)

5. Yes, I suggest that for typing reasons, the letter æ should be represented as ae. œ should be represented by Ö.
 * I'm not sure that typing reasons are relevant. For people using the US Windows keyboard ö is just as much a problem as æ is. But the æ digraph is not especially common and in any case, whatever is decided, there should be redirects for alternative forms. That is, even if we use Æsir and Ægir, a user should be able to get to the entry by typing aesir and aegir respectively. One should also be able to ignore diacritics in typing. For example, I just tried to reach the article Chrétien de Troyes by entering Chretien de Troyes and it worked, because someone had created the expected redirect. The æ question also effects Old English names, indeed much more so as it is more common in Old English than in Old Norse. Some histories and translations have forms like Ælle and Æthelfrith and some use Aelle and Aethelfrith. The Wikipedia entry Aethelfrith has two occurrence of Æthelfrith in the text, one being the first mention of the name. The original article had Æthelfrith  throughout but editors have been, perhaps unwittingly, changing forms. The article called Aelle of Sussex uses the Ælle form throughout. One would expect sources to be consistant on using æ or ae, that is, a text using the form Ælle would also use Æsir and a source using Aelle would use Aesir.  However the Columbia Encyclopedia uses æ in Old English names as in Ælle at Sussex, Kingdom of but uses ae in Aesir in Germanic religion. Jallan 21:49, 25 Jul 2004 (UTC)
 * I'd like to add:
 * 6) The Scandinavian Å is to be dropped, if it appears, as it neither existed in Old Norse nor exists in English. It does appear in modernised Scandinavian forms, but should not in English Wikipedia.
 * That leter å doesn't appear in standard Old Norse or any Anglicizations of medieval Scandinavian forms that I've seen. So that fortunately is not an issue. :-)  Jallan 21:49, 25 Jul 2004 (UTC)

 * It would be interesting to know what others have to say about these points.-- Wiglaf 09:01, 25 Jul 2004 (UTC)
 * I think I will drop out of the discussion for now. The discussion about spelling in the main body of articles isn't really relevant to what I am going to do, and consensus should be reached by speakers of the language in question. I did, however, edit Freyja according to Old Norse convention to see how it looked and which reaction it would get. Feel free to edit back. :-) Cheers Io 11:57, 25 Jul 2004 (UTC)
 * I have no personal problems with this editing which is pure Brodeur. I'd personally favour just removing the case endings, as you also suggest. But one can't impose one's own personal tastes here. Unfortunately once I began to investigate carefully rather than rely on impressions I found that extreme Anglicization of Old Norse names was far more common than I had realized, and that more often than I would have thought extreme Anglicization of Old Norse name was done by choice rather than forced by typographical constraints. (But the expense of using special characters and fancy typography increased exponentially throughout most of the twentieth century and that probably played a part in forming this aesthetic, or as the 1913 Webster Dictionary gave the spelling, æsthetic. Even less than a century ago use of æ was the correct spelling in standard American English for ae in most Latin-derived words. Only the invention and spread of TeX in the middle 1980s began to counteract the increasing inability of printing systems to handle an extended character set or typographical complexity and only within about the last three years have people begun to be confident about exchanging characters electronically that were not part of invariant ASCII. Even two years ago people would have been more leary about exchanging æ or any accented characters because some browers might not support them properly.)
 * The current Webster's College Dictionary gives Aesir as the spelling, as does the Collins Dictionary. However the Oxford English Dictionary (2003) has the form Æsir. Oxford also explains in other entries that Balder was god of the midsummer sun (a somewhat outdated POV theory) that Thor was son of Odin by Frigg, and that Freyja was goddess of the night. There is garbage everywhere. :-(
 * Jallan 21:49, 25 Jul 2004 (UTC)

OK, what about the following standard:
 * 1) The letters þ, ð and ǫ should be represented respectively by th, d, and ö.
 * 2) Nominative case endings should normally be dropped (except for certain one-syllable names. Since the most common one is Baldr, "Balder" is suggested to be the standard. For consistency this would apply to his brother Hödr as well.)
 * 3) The acute accent should not be dropped unless we are dealing with common forms in the English language, such as Odin and Thor.
 * 4) The dieresis accent should be kept.
 * 5) The letter æ should be retained. The letter oe could be rendered as Ö.--Wiglaf 14:12, 27 Jul 2004 (UTC)

Yet more information
I am personally mostly agreed you, Wiglaf, other than on the matter of Höder and œ. Höder doesn't appear much used as far as I can see, Balder being now an isolated occurrences of what seems to have been a long obsoleted custom of adding e before an -r nominative case ending. Cassell's gives Höd for example. As to œ, the name Hoenir is fortunately unusual enough under any spelling that forms can be searched in Google. I've done this both with Hoenir and Aesir, both with Google set for any language and for English only. Results are ordered by English hits.

Search pattern              Any language  English only Hœnir                                218           111 Haenir                               781           607 Honir                              1,650           650 Hænir                              1,070           689 Hoenir                             2,280         1,670 Hönir                              3,640         1,790 Aesir                             47,600        34,100 Æsir                              49,100        38,700

Unfortunately a look at the entries found indicates oddities in Googles identifications of vowels. A search using æ finds also any words using ae but the opposite is not true. Similarly a search using ö find any words using oe or o, a search using o also finds ö, but a search using oe finds neither ö or o.

I repeated the search using the negativising hyphen to remove false matchines, though articles giving more than one form will also be dropped. Results are again sorted by English usage.

Search pattern              Any language  English only Hönir -Hoenir -Honir -Hœnir        1,150            63 Hænir -Haenir                        285            82 Hœnir -Hoenir -Hönir -Honir          190            90 Honir -Hoenir -Hönir -Hœnir        1,490           213 (In place of buggy result 3,570) Haenir -Hænir                        765           603 Hoenir -Hönir -Honir -Hœnir        2,120         1,590 Æsir -Aesir                        5,700         4,480 Aesir -Æsir                       42,400        32,800

For some reason when searching on Honir -Hoenir -Hönir -Hœnir an obviously wrong figure occurs. Checking the actual pages of entries returned indicates the true tally is 213.

The standard internet forms in English are definitely Aesir and Hoenir. Use of the form Hönir is indeed very common, but only outside English according to the results. I imagine it is used especially in modernized forms in some Scandinavian languages and in German, which is quite understandable. But it is not at all the common form in English usage.

The net is somewhat conservative in respect to special characters compared to printing which partly explains low usage of æ in Æsir and even more so low usage of œ in Hœnir as that character does not even occur in the Latin-1 character set. But the results do accurately indicate that US-ASCII forms are more common in Engilsh than forms which represent the original Old Norse more closely. However common use is not necessarily best encyclpedic use, othwise Cassel's and John Lindow and others would not also be providing more accurate forms of the names, especially in encyclopedia/dictionary kinds of works.

I recommend waiting for at least 30 days for possible further input. There haven't been enough participants so far to make clear that there is group consensus on Wikipedia (by those who care at all one way or the other). But if no opposition arises before September 1, I would think it then fair to consider the matter decided, that people other agree or don't care one way or there other. We should then (or preferably before) draw up a short explanatory Wikipedia standard recommending use of diacritics and digraphs for Old Norse names giving reasons and should also recommend the use of digraphs as standard in Old English names. Then one can begin standardizing articles with a clear conscience.

The Cassell's rules, which I cited, seem simple enough and can be adopted. But usage does not have to be entirely consistant between articles. I would also be willing to go with ultra-English if a majority appeared to push it, but if no-one cares cares one way or the or people are tacitly happy with what we have tentatively agreed to, then I think it reasonable to take that as a mandate.

Jallan 02:54, 28 Jul 2004 (UTC)

I completely agree that we'd better wait until september 1st, before establishing some kind of standard. Two people aren't enough to establish a consensus at Wikipedia :).--Wiglaf 10:07, 28 Jul 2004 (UTC)

 * I'll add a third voice here, then. :) I believe that since we're in an English Wikipedia, if an English spelling exists we should use it. Admittedly, redirects are wondrous things, but I just popped up at a page on the Alþingi and if I weren't a linguist, I'd have no way of recognising the word as Althing, the Icelandic parliament. Thorn and eth are no longer letters that the average person is familiar with the pronunciation of, so I think while we should retain the proper Norse-style spelling within the body of the article, the titles of the pages should be Anglicised. thefamouseccles 04:47, 03 Oct 2004 (UTC)

 * I agree with thefamouseccles. If an English version of the name exists, it should be the primary name on the English Wikipedia, with the non-English forms as redirects. Jonathunder 18:17, 2005 September 8 (UTC)

normalization
I like Jallan's normalization effort. Consistency will of course be almost impossible to achieve, since users will add stuff all the time without bothering to search for conventions first, but it is pleasant to even have such conventions. One point though, I find it strange to preserve length marks (acutes), but to drop thorn and eth, e.g.:
 * Hrafnagaldur Ódins (Hrafnagaldur Óðins) 'Odins's Raven Song'

I think this could as well be
 * Hrafnagaldur Odins (Hrafnagaldur Óðins) 'Odins's Raven Song'

since we give the precise spelling in italics anyway. i.e. I think both Óðins and Odins are fine, but Ódinsseems a bit strange. A minor point of course, and not really an objection. dab (ᛏ) 09:57, 2 Jan 2005 (UTC)

 * I tend to agree. I'd rather have diacritic marks AND thorns and eths or no such frills at all.
 * My suggestion at the moment is to have a hypercorrect naming such as Óðin inside texts, but Odin as the name of the article. --Wiglaf 19:18, 2 Jan 2005 (UTC)

Response to initial comments
Reduction of Norse names to the 26-letter alphabet with no diacritics is common in English. I will go along with that, if that is indeed what other people really want here.

Personally I don't prefer such lowest common denominator renderings.

The opposite idea, using the full Old Norse forms throughout is just not English practice. Rudolf Simek's A Dictionary of Norse Mythology (translated from German) is the most extreme example I am aware of in the direction of using Old Norse forms without change in a work on Norse mythology. That work uses the hooked-o, and ð throughout, still retains case endings on names, and always renders thorn as th where it occurs. But even this text still uses the English spellings Odin and Thor. Only some scholarly articles in international journals are more or equally extreme. Jean Young's partial translation of Snorri's Edda also used ð, but dropped the case endings and used ö rather than hooked-o. These works are the unsual exceptions. Normally, in translation after translation, commentary after commentary, you get ð rendered d or more rarely th or occasionally dh, diacritics more often dropped than included, and æ sometimes retained and sometimes rendered ae, and various things done with œ when it is not retained as is. I could personally accept following Simek, except that I don't think that such usage fits the general Wikipedia principle of using the form of a name most common in English. Which forms are most common in English for names from Norse mythology is very debatable, but they are certainly, and perhaps unfortunately, not the Old Norse forms with case endings and all the "frills". And in general the policy of using the most common names serves Wikipedia well, even though I'd love to start using more correct forms like Mōšeh or Mōsheh instead of Moses and Akhilleus instead of Achilles. I tend to be a pedantic purist. But the current policy rightly keeps pedantic purists from being able to replace accustomed English forms with more correct forms, at least until other works start doing the same thing. Don't come here to change the standards, even if the change would be for the better. And it keeps those who want to use non-standard systems from fighting over which non-standard system. Unfortunately there is no standard system for Old Norse, but there are features of adapting the names that are more common than others.

I was using the forms used by Lindow and Orchard because they represent the most normal English letter spellings (j not i, d not th or dh for ð) and their rules mostly provide naturally the forms found normally in English, for example, Sigurd, not Sigurth or Sigurð. The diacritics are also found in many translations and are the kind of extra one expects in more scholarly works. Brodeur used the same forms, but kept the case endings. Hollander used the same forms except for rendering ð as th and ö as o; but he kept the other diacritics. Faulkes and Larrington use the same forms, but drop the diacritics and represent j by i. Lindow and Orchard represent a reasonable common denominator rendering which is yet not a lowest common denominator rendering. They keep æ rather than using ae and keep œ rather than rendering it as oe. They keep the diacritics, which readers can mentally filter off, if they wish, but can't filter on again if they aren't there. And they provide an external standard that can be followed without niggling over whether a name is well-known enough in an English form or unaccented form to appear that way. Óláf or Olaf? Just see what they do and copy it. And because they have written encyclopedic works, they have far more forms than those found in most individual translations. I could compile a list of the name which are exceptions to their normal rules for the Manual of Style. There aren't many: Odin, Thor, Halfdan, Olaf are the only ones that spring to mind. Orchard only identifies Odin and Thor and just mentions there are others where he has used forms "more familiar to the general reader". When discussing Old Norse words as technical terms, both Orchard and Lindow do use accurate Old Norse forms.

I don't like the suggestion of different forms as article headers and as standard forms within articles, except for technical reasons. If we adopt a standard form of a name for Norse mythology in Wikipedia, it should normally be the standard form in both the title and article. It seems to me there would be something philosphically wrong with a policy in which almost all links would be piped links. If the common Wikipedia spelling of the Norse king of the gods is decided to be Óðin, then the article should also be Óðin, with redirects from the forms Oðin, Óðinn, Odin, Ódinn, Othin, Óthinn, Odhin, and Ódhinn. If we can't justify Óðin as the proper title for an article, then it shouldn't be the normal form in the text either.

I do see reason for making a partial exception in the case of anglicized titles of Norse literary works. In an article they might more often be referred to by their Old Norse form, for some more than others. Voluspa doesn't look too bad. Fra daud Sinfjotli looks like carelessly rendered Old Norse. However Thrymskvida or Thrymskviða seems far better to me than Þrymskviða in a casual reference in English. Such differences is the impression such forms make is probably one reason there is no consistancy in Wikipedia. One could also make an exception that titles of works, but not other names, do not follow the Orchard/Lindow rules, but appear in Old Norse forms following Simek's rules, that is substitute th for thorn but otherwise follow the Old Norse spelling, even to the use of the hooked-o, though currently in article titles ö would have to be used as a substitution. I think it would be simpler just to stick to Orchard and Lindow's reasonable and consistant anglizations. Different forms tend to look strange, pedantic, or dumbed down to different readers.

I have already been doing a fair amount of standardization based on what I believed was consensus. If consensus has changed now, fair enough. I am willing to change what I've done. But consensus should not keep changing. One way is often as good as another and there are thousands of divergent forms now regardless of what standard is used. For search purposes I want to continue providing alternate forms at the bottom of articles, (see Halfdan the Old as example). Doing this partly depends on having standard forms within an article, whatever that standard is. A change of standard away from Lindow and Orchard now will require quite a bit of work on my part to fix up what I've already done. But I'd rather this happen now than six months from now after making many more such lists of variant forms, which is why I am bringing up the matter after producing a concrete example of what I have in mind. I want to get things started, if possible, and I want what I am doing to have support by those who are currently working in this area, otherwise it won't be done. And it should be a standard that others cannot lightly change in the future, if only because it has become, hopefully, so entrenched by it being followed that the work involved in changing it would be enough to put people off.

We're past the point where we can just change a standard lightly and start fresh with new rules every few months. And the mess of having no rules is becoming more and more annoying. We must decide. And we must start using whatever standard is decided on, or watch the anarchy increase, and face the possibility of silly edit wars over spelling. Generally, it is better to be using a standard for names that one does not particularly like than to be forced to fight again and again on article after article to get spellings accepted, which is why such standards exist. It enables one to fight instead about what is worth fighting over, the content. I far prefer Ægir to Aegir (and use of æ does appear in some translations which don't use diacritics.) But if I am outvoted, it is not worth fighting about compared to the time taken to actually improve an article about Ægir or Aegir. But if we don't decide, we are making more and more work for ourselves in the future.

Jallan 01:02, 3 Jan 2005 (UTC)

There is no perfect solution - here's what I do and why
Personally I prefer the following standard:

1. Using no characters outside the common ISO-8859-1 (a.k.a. Latin-1). Instead of o-with-tail we can use 'ö'. Instead of 'oe-ligature' we can use 'oe'. Instead of 'o-with-tail-and-accent' we can use 'á' (representing a slightly later stage in the language).

I think that using characters outside of Latin-1 is just raising the bar unnecessarily high. I can't read those letters on my personal computer system nor on other systems I habitually use.

2. Using all other ON characters, including 'þ', 'ð' and 'æ'.

These characters, on the other hand, are readable by a large part of the computer systems of the world.

3. Retaining nominative endings.

One argument for this, as well as point 2, is to maintain consistency with Modern Icelandic within Wikipedia. I don't think many would argue that a modern person named, say, "Freyr Þorláksson", should get an entry under "Frey Thorlaksson" on the English Wikipedia.

Examples:

 * Ørlög
 * Hallfrøðr
 * Freyr
 * Höðr
 * Þorbjörn
 * Óðinn
 * Hoenir
 * Öku-Þórr
 * Alþing
 * Áss inn hvíti
 * Æsir
 * Hildr

This is what I have done in the articles I have written. Here's a work in progress: Hrafnkels_saga

It is also the standard I apply in my Old Norse for Beginners course:

http://www.hi.is/~haukurth/norse/

I originally wrote Old_Norse_orthography to help clear the matter up. Ultimately the only possibility for beginners to make sense of the various possibilities is to read articles like that.

I'd like to clear up a misunderstanding I see in some of what's written above. The 'r' in Baldr is not a nominative ending. The accusative is Baldr, not **Bald. The accusative of Höðr is Höð, on the other hand.

Haukurth 01:04, 20 Jan 2005 (UTC) (edited a few minutes later)
 * Are you aware of the   template? This allows you to specify that characters or words should be rendered in a unicode-capable font. An example from above might be "Njörd (Old Norse Njǫrðr)" which now renders fine on my browser. (The template specifies freely-available fonts BTW so we're not asking people to spend money.) --Phil | Talk 08:34, Jan 20, 2005 (UTC)

 * That actually seems to have worked :) I'm seeing some ǫ's on my screen now. I'm guessing this is not possible to employ in page titles? Now I'm wondering if I should switch to using this letter (as well as oe-ligature). When listing my sources in the Hrafnkels_saga article I had a book with an ǫ in its title. Normally I would have transcribed it with 'ö' (as would be done in any Icelandic library system) but now I tried using the o-with-tail character. Haukurth 18:03, 20 Jan 2005 (UTC)

No Agreement
Well, obviously there is no agreement among any of those commenting here. Accordingly there is no point in my doing any further standardization work. I will note that I cannot offhand think of any English source which uses modern Icelandic spellings of Old Norse names. They either use Old Norse forms more or less Anglicized or Anglicized forms based on modern Icelandic forms.

 * If you come to Iceland as a tourist you can find texts on "Ingólfur Arnarson" in English. I'm not suggesting we do that, though. It may not be that easy to draw the line, however. What about a 15th century Icelander? How do we spell his name here? - Haukur

I have not been able to locate any style guide indicating how modern Icelandic names should appear in Modern English. One sees them also in various formats, especially with þ rendered th and often with ð rendered as d. I don't know to what extent such uses are based on actual style guides and to what extent they are ad hoc. For example, after setting Google to English, I find 82 hits for ["Þorgerður Katrín Gunnarsdóttir"], 26 hits for "Thorgerdur Katrín Gunnarsdóttir" -"Thorgerdur Katrin Gunnarsdottir"], and 27 hits for ["Thorgerdur Katrin Gunnarsdottir" -"Thorgerdur Katrín Gunnarsdóttir"]. English translations without þ and ð and without diacritics are used on the Icelandic govenment website. See http://government.is. But some other pages on the same site use Icelandic spellings.

 * Indeed. This is unfortunate. Various systems are in use and it is often difficult to make people even understand the problem. Most seem to think that the way they do it is the obvious and only way to do it. - Haukur

The difficulty in arguing that we should follow modern Icelandic use, is that most English translations of sagas and other Norse texts do not so. That is, such translations indeed normally use Frey, but would, if referring to a modern Icelander named Freyr in an introduction or bibliography, indeed use the form Freyr in that case. The inconsistancy is commonly recognized. Also œ is replaced by æ in modern Icelandic and nominative -r by -ur in most cases. Accordingly Þorgerðr in modern Icelandic is Þorgerður and Baldr is Baldur.

Some English translations and commentaries do favor modern Icelandic forms of Old Norse forms. Most do not, or if they do so, do so, use them without case endings.

Haukurth's method seems to me to be yet another idiosyncratic rendering system, but as it is used, as far as I know, in no published texts, it should not be the basis of a standard in Wikipedia. It is an original research transliteration system.

 * Not quite. Icelanders very commonly substitute ö for o-with-tail. Try searching for "Austfirðinga sögur" in a computerized library system. See if "sögur" is spelled with ö or with o-with-tail like in the actual publication. See www.hi.is/~eybjorn for another example. He may use the oe-ligature character, however. I also use this system outside of Wikipedia and <tongue-in-cheek> since my website is the number one Google hit for "Old Norse" it is obviously the de-facto standard</tongue-in-cheek>. - Haukur

As to raising the bar too high in using special characters, the œ character, at least when entered as &oelig;, should be available under 99% of browsers in current use (and those that won't show it also won't properly display true dashes, such as those used throughout the Main Page).

 * When I'm working on Linux I often don't see the oe-ligature. But the problem isn't limited to seeing or not seeing. Now I'm working under a Microsoft operating system. When I copy text including an oe-ligature from Wikipedia and paste it into Notepad (surely not an unreasonable thing to do) I get a black box where the oe-ligature letter was. I like being able to copy text without having to hand-modify it afterwards. - Haukur

Limitation to Latin-1 is very much not a Wikipedia policy. There are thousands and thousands of English Wikipedia articles using Chinese/Japanese/Korean characters, International Phonetic Alphabet characters, Hebrew characters, Arabic characters, special Latin letter transliteration characters and so forth. Some of these articles have been featured articles.

 * Of course. But that's inevitable. We can get around it in Old Norse. - Haukur

The o-hook character is more arguable (because not available in most Latin letter fonts), and in any case is never used in Anglicized versions of Old Norse characters (and not used in modern Icelandic). Generally it appears in English works in italicized forms only, the italics indicating that this is a genuine Old Norse form as opposed to an Anglicized form. (The main exception is in scholarly journals.) To produce o-hook with an acute accent the proper Unicode method is ǫ́. This may look clumsy on your browser.

 * Yes, or it may not show up at all. Like on mine. Now. Under Internet Explorer. - Haukur

(On my browser, using the font it chose, the acute is far too high.) In theory the acute accent, by Unicode rules, should be positioned properly over the base character. In fact most fonts do not support variable positioning of combining characters, so the result may look poor, unless your browser happens to choose a font which by default positions the combining acute in the proper position or chooses an intelligent font that automatically adjusts the position of the acute to fit the base character. But this is the proper Unicode method. Unicode's policy from the beginning was that using combining diacritics was preferrable to using precombined characters which were included for compatibility reasons. But font technology has lagged behind. However Unicode's policy is now to include no more characters which represent a combination of a base character and one or more diacritics, in part because there is no end to such combinations.

In any case, I now do not expect to be active in Wikipedia for some time (if ever), and accordingly would not have been able to get on with immediate standardization in any case.

Jallan 18:30, 23 Jan 2005 (UTC)

Okay. I think we can agree that there is no agreement. I could personally live with Anglicized names used throughout the text if the full form of the Old Norse name is given at each name's first occurrence. So, what's your favorite standard for Anglicizing names? I don't see any agreement on that. How do you, for example, handle oe-ligature? It would seem logical to replace it with "oe" but I'm not sure that's widely done. And should we drop nominative-r? Should I spell "Sámr" as "Sam" in the Hrafnkels_saga article? It seems silly and unnecessary but if that's what people want I'll go along with it in the name of having a standard. Haukurth 20:52, 23 Jan 2005 (UTC)

I had forgotten that Jallan had already done some research on replacements for oe-ligature. Apparently the most common thing on the web is to replace it with "oe" (which is what I was originally advocating).

I guess this whole thing is somewhat more personal for me than some of you. I actually have a thorn in my patronym (which is not a surname). My full name is Haukur Þorgeirsson. When I'm forced to replace the thorn with something I choose 'th' (like in my user-name). I do this consistently but that doesn't mean I like it. Imagine if Icelandic was a standard computer language and English wasn't. We might not bother with silly "frills" we don't use like the letter 'w', which after all is not a part of the original Latin alphabet. Imagine Mr. Wilson having to write his name VVilson (and then arguing with other VVikipædians on the relative merits of 'VVilson' vs. 'Vvilson' vs. 'UUlson' etc.). Haukurth 23:24, 23 Jan 2005 (UTC)

I've been experimenting a bit in the sandbox and it doesn't seem possible to get oe-ligature or o-with-tail to show up properly in page titles. Is there a way around this, is it a problem with my system or do we have to avoid these characters in page titles? Haukurth 10:11, 24 Jan 2005 (UTC)

I'm editing some mythological articles now and generally I use the standardized ON spelling for the names. I make an exception by using "Odin" and "Thor" instead of "Óðinn" and "Þórr" since I think these names are actually familiar to English speakers.

I still don't know if it's possible to create page titles with o-with-tail and oe-ligature.

Does anyone out there want to talk about this? Haukurth 12:35, 18 May 2005 (UTC)

 * Well, yes, but I wonder whether it is possible to arrive at a naming convention.--Wiglaf 12:39, 18 May 2005 (UTC)

Category:Wikipedia naming conventions

No original research
It seems to me that some of the things talked about on this page are in danger of breaking the WP:NOR. Perhaps a constructive way forward is to list some of the options which have been used by various people who have translated and published a lot of texts for the general public to read (not specialist to specialist) and comment on how they have translated the names etc. It there is one person, or School of people, which has a substantial body of work that covers a wide area, and it is a close fit to the Naming convention then perhaps that could be used as a standard.

Even if nothing else comes of such a survey it it would at least produce enough information to help make a more informed choice on how Wikipedia editors could progress the issue and probably produce enough information for a page on the history of translations. Philip Baird Shearer 17:28, 7 October 2005 (UTC)

WP:NOR is surely not intended to prohibit Wikipedia from deciding its own naming conventions. In any case there's nothing wrong with following an external standard. That's basically what we're doing. We've taken the spelling used in works like Ursula Dronke's translation of the Poetic Edda (the best English translation there is, no competition) and Richard North's recent book on Haustlöng (an excellent and very accessible work) and made some minor adaptations. Those are the use of 'ö' instead of o-with-hook and the use of familiar English forms where those exist (like Odin and Thor) in accordance with Naming conventions (use English).

Of course other external standards are possible. Jallan proposed the use of the forms in John Lindow's Handbook of Norse Mythology. Those can be seen at User:Haukurth/Handbook. This proved somewhat unpopular because, well. Let's take an example:

We have a Lindow name like "Ögmundar tháttr dytts ok Gunnars Helmings" and Jallan's proposal was to use that in the title. But we also wanted the full ON form with 'þ' so we'd list that too right after the other:

Ögmundar tháttr dytts ok Gunnars Helmings (Old Norse: Ögmundar þáttr dytts ok Gunnars Helmings)

But that looks somewhat confusing. Readers are unlikely to realize that the first version (which includes such characters as 'ö' and 'á') is actually the anglicized form. They'll be likely to incorrectly assume that a spelling which includes 'ö' and 'á' is the original spelling.

The basic problem is that just about every translator or editor uses her own spelling system. I could stay up all night showing you the myriad of systems in use. The only really standard forms are the un-anglicized Old Norse versions, as used in any number of English works. Many of them are scholarly, granted, but then many of us feel that Wikipedia should be somewhat scholarly as well so we're not troubled by that. Of course we should make allowance for Odin and Thor, use redirects liberally, list alternative anglicizations (see Lóðurr) and generally try to please everyone. Please tell us how we can please you. I know you want to see alternative anglicized forms and ascii forms in the lead and I agree with that. How about sound files with the pronunciation of those tough names? IPA transcriptions? A more organized effort to create redirects? - Haukur Þorgeirsson 18:02, 7 October 2005 (UTC)

THIS IS AN ARCHIVE. PLEASE DO NOT POST HERE. GO TO Wikipedia talk:Naming conventions (Old Norse/Old Icelandic/Old English) INSTEAD.


text:
VANOS

VANOS is a variable valve timing system used by BMW on various automotive petrol engines since 1992. The name is an abbreviation of the German words for variable camshaft timing (variable Nockenwellensteuerung).

The initial version (retrospectively renamed "single VANOS") was solely used on the intake camshaft, while the later "double VANOS" systems are used on intake and exhaust camshafts. Since 2001, VANOS is often used in conjunction with the Valvetronic variable valve lift system.

Operation
VANOS is a variator system that varies the timing of the valves by moving the position and the camshafts in relation to the drive gear. The relative timing between inlet and exhaust valves is changed.

At lower engine speeds, the position of the camshaft is moved so the valves are opened later, as this improves idling quality and smooth power development. As the engine speed increases, the valves are opened earlier: this enhances torque, reduces fuel consumption and lowers emissions. At high engine speeds, the valves are opened later again, because this allows full power delivery.

Single VANOS
The first-generation single VANOS system adjusts the timing of the intake camshaft to one of two positions — e.g. the camshaft is advanced at certain engine speeds. VANOS was first introduced in 1992 on the BMW M50 engine used in 3 and 5 Series. In 1998 single infinitely variable VANOS was introduced on the BMW M62 V8 engine.

Double VANOS
The second-generation double VANOS system adjusts the timing of the intake and exhaust camshafts with continuously variable adjustment, based on engine speed and throttle opening. The first double VANOS system appeared on the S50B32 engine in 1996.

title: VANOS


text:
Nissan VVL engine

Nissan Ecology Oriented Variable Valve Lift and Timing (commonly known as VVL & VVT) is an automobile variable valve timing technology developed by Nissan. VVL varies the duration, and lift of valves by using hydraulic pressure switch between two different sets of camshaft lobes. VVT varies the valve timing throughout the RPM range. Together they function similarly to Honda's VTEC system.

The SR20VE is the most common engine with NEO VVL. There have been two main versions of this engine. The first version made 187 hp and 145 lbft torque. This engine was used by Nissan from 1997 to 2001. It is found in the Nissan Primera, Nissan Bluebird, and the Nissan Wingroad.

The second variant of the SR20VE is found only in the 2001 and later P12 Nissan Primera. This version of the SR20VE makes 204 hp, and 152 lbft torque. This engine is commonly known as the SR20VE '20V'. Although, in automotive terms, '20V' would normally be interpreted as having twenty valves, this is incorrect. The name '20V' is the name of the trim level of the Nissan Primera that it is found in. It is also a shortened version of the name SR20VE. This engine has 16 valves like the rest of the SR20 engines. This newer '20V' engine, along with the SR20VET, were the only SR20 engines to get restyled valve covers. It also came with an upgraded intake manifold, which has longer runners and a larger 70 mm throttle body (earlier SR20VE has 60 mm).

Another version of the VVL SR engines, is the 1.6 L SR16VE. The engine block for the SR16VE is the same as the SR20VE; it also has the same cylinder bore. The crankshaft has a shorter stroke, which lowers the displacement, but allows the engine to safely rev to higher RPM. Although this engine has 1.6 L of displacement, it has more aggressive camshaft specifications. It manages to make 173 hp. The camshafts from this engine are considered to be an upgrade for SR20VE owners.

From 1997 to 1998, Nissan produced 500 limited-edition SR16VE N1 engines. These engines made 197 hp. They had further upgraded camshafts, upgraded intake manifold using eight injectors and a larger 70 mm throttle body. These engines were found in the limited-edition Nissan Pulsar VZ-R N1. They were only sold in Japan.

The most powerful VVL engine so far is the SR20VET. The SR20VET is a turbocharged '20V' SR20VE. It uses a Garrett GT2560LS, and makes 280 PS. Nissan's technical information about this engine states that it is 9:1 compression ratio, but it really adds up to 8.8:1. Compared to the SR20DET (used in the Nissan Silvia, and Bluebird), the SR20VET (aside from having VVL technology) has improved airflow in the cylinder head, higher compression, and also improved coolant passages.

In 1998 Nissan's RB engine was also improved using the NEO Head Technology (but no VVL), which provided the motor better fuel economy and lower exhaust emissions to keep up with emission standards.

One difference from Honda's VTEC system is that NEO VVL engages the change of intake and exhaust cams independently for a flatter, more consistent power band. On the SR20VE, the intake camshaft is switched at 5000 rpm, and the exhaust at 6500 rpm. However this trait was not included on the newer '20V' version, as both camshafts engage at the same RPM.

title: Nissan VVL engine


text:
VarioCam

VarioCam is an automobile variable valve timing technology developed by Porsche. VarioCam varies the timing of the intake valves by adjusting the tension on the timing chain connecting the intake and exhaust camshafts. VarioCam was first used on the 1992 3.0 L engine in the Porsche 968.

Porsche's more recent VarioCam Plus combines variable valve timing with two-stage lift on the intake side. The two-stage valve-lift function is performed by electro-hydraulically operated switchable tappets. Each of these 12 tappets consists of concentric lifters which can be locked together by means of a pin. The inner lifter is actuated by a small cam lobe, while the outer ring element is moved by a pair of larger-profile lobes. The timing of each valve is seamlessly adjusted by means of an electro-hydraulically operated rotary vane adjuster at the head of each intake camshaft.

Valve timing and the valve profile are continuously altered according to conditions and engine load. For improved responsiveness on cold starts, VarioCam Plus raises the amount of lift and retards valve timing. At medium revs with minimal loads, the valve lift is lowered and timing advanced to help minimize fuel consumption and emissions. For maximum power and torque, the lift is raised and the timing is advanced. This system debuted on the 1999 Porsche 996 Turbo.

A system similar to the VarioCam Plus system was developed by Subaru for the redesigned EZ30R H6 engine, which debuted in 2003 in the Legacy and Outback.

title: VarioCam


text:
Kish Island

Kish (, is a 91.5 km2 resort island in Bandar Lengeh County, Hormozgan Province, off the southern coast of Iran in the Persian Gulf. Owing to its free trade zone status, the island is touted as a consumer's paradise, with numerous malls, shopping centers, tourist attractions, and resort hotels. It has an estimated population of around 140,000 residents and about 12 million visitors annually.

History
Kish Island has been mentioned in history variously as Kamtina, Arakia (Αρακία), Arakata, and Ghiss.

In 325 BC, Alexander the Great commissioned Nearchus to set off on an expeditionary voyage to the Sea of Oman and the Persian Gulf. Nearchus's writings on Arakata contain the first known mention of Kish Island in antiquity. When Marco Polo visited the Imperial court in China, he commented on the Emperor's wife's pearls; he was told that they were from Kish.

In March 2007, the retired FBI agent turned private eye Robert A. Levinson disappeared on Kish Island where he was meeting with an American fugitive known as Dawud Salahuddin.

In 2019, the singer Joss Stone was deported from the island by the Iranian customs. Iranian officials claimed the British singer did not have the proper documentation to enter the country, but Joss Stone claimed the Iranian authorities were afraid a woman singer would perform a public show in the country.

Geography
Kish is located in the Persian Gulf, 19 km from mainland Iran, and has an area of approximately 91 km2 with an outer boundary of 40 km and a nearly elliptical shape.

Climate, nature, and geobotany
Kish is located on a narrow strip of tropical vegetation in the Northern Hemisphere, with the Persian plateau to the north and the Arabian Peninsula to the south.

Weather
Kish has a very dry semi-equatorial climate. Over an 8-year span, the median annual rainfall in Kish was 145 mm (54% in winter, 28% in autumn, and 14% in summer) and the median annual temperature was 26.6 °C. The relative atmospheric humidity in Kish makes it like a sea island except in cold seasons. The humidity is approximately 60% for most of the year. In the months from October to April, Kish's weather is mild, ranging from 18 °C to 25 °C. The statistical data in the Kish free zone's archives shows that the island's temperature varies from very hot to moderately hot, accompanied by relatively high humidity, often interspersed by heavy rains of short durations in certain seasons. With the exception of some southeastern coastal areas and a few other islands in the Persian Gulf, Kish Island has the most sunny hours in the region, roughly 3,100 hours per year. Based on climatological classification and general weather conditions, Kish's proximity to the Tropic of Cancer and its exposure to high tropical pressure systems, as well as its position amidst hot and shallow waters, means the island tends to be hot and humid most of the year.

Tourist attractions
The Greek Ship is the wreck of a 1943 cargo steamship, the Koula F, on a beach on Kish's southwest coast. She was originally a British ship, Empire Trumpet, and was built in Scotland. In 1966, she ran aground and all attempts to salvage her failed.

Economy
Since the mid-1990s, the Iranian government has embarked on an aggressive promotional and developmental campaign to position Kish as a rival to Dubai and to Doha. The campaign has included massive construction projects and programs designed to attract foreign investment and trade. Within the area of the Kish Free Zone, as it is known, the standard laws of the Islamic Republic of Iran are far more relaxed than on the mainland. This has resulted in significant increases in mostly domestic tourism, as well as the abundance of international trade on the island. Kish's population includes significant numbers of both Muslims and Christians. In 2009, the total foreign trade of the Kish Free Zone was approximately $9.2 billion per annum. Fifteen percent of all imports to Iran are through Kish.

Investment incentives in the Kish free trade zone include:
 * 15 years tax-exemption;
 * no entry visa requirement;
 * 100% foreign ownership possible;
 * flexible monetary & banking services;
 * extended legal guarantees & protection.

Besides the existing Iranian Oil Bourse, a new exchange, the Kish Stock Exchange was inaugurated in 2010 to facilitate foreign investment and monetary activities.

Education
Sharif University of Technology-International Campus-Kish was established in 1995. Kish International Campus, University of Tehran was established in 2007.

To promote the quality and quantity of education, KFZO, the Kish Free Zone Organization, has created educational spaces by building new schools and giving priority to technical and vocational courses. They include:

 * Kish Institute of Arts and Sciences (teaching foreign languages);
 * Kish Institute of Graph-Rayaneh (teaching computing);
 * Parto Institute (teaching English);
 * Sadaf Cultural Centre;
 * Mir Mohana Cultural Centre;
 * Sana'ei Cultural Centre; and
 * Kish Institute of Science and Technology.

Transportation
The connection with Kish is carried out either by sea or by air through Kish airport and Kish port. Kish International Airport serves as the entry point for tourists who come to Kish Island.

Sports
Kish Island hosts the Fajr International Squash Championship, which is part of the Professional Squash Association's annual tour. Kish also holds Iran's Traditional and Heroic Games Contests. Kish is home to a multi-purpose stadium seating 1,200 spectators. Water sports are offered in Kish. Kish Island has hosted the 2006 Asian Beach Volleyball Championship.

Kish was host to an officially sanctioned FIVB beach volleyball event, the Kish Island Open 2016. Qualification rounds at the 2017 FIVB Beach Volleyball World Tour event took place on Kish.

International Oil Bourse
The International Oil Bourse is a commodity exchange which opened in 2008.

Ocean Water Park
Ocean Water Park is a 5.6 hectare water park.

Kish Dolphin Park
The Dolphin Park is a 70 ha park located at the southeast corner of Kish Island. It is surrounded by over 22,000 palm trees and includes a dolphinarium, butterfly garden, silkworm compound, bird garden, artificial rain forest, volcanic mountain, orchid garden, and cactus garden. The dolphinarium includes the largest man-made pool on the island and it exhibits dolphins, sea lions, and white whales. The Bird Garden in the park is home to more than 57 species of birds and other animals from around the world, including pelicans, ostriches, blue-and-yellow macaws, storks, toco toucans, turacos, swans, African penguins, and marsh crocodiles.

Kish Aquarium
The Art Center on the island includes an aquarium that displays marine species unique to the Persian Gulf.

Twin towns – sister cities

 * Langkawi, Malaysia (since 2009)
 * Dubai, United Arab Emirates (since 2002)

title: Kish Island


text:
Options for Change

Options for Change was a restructuring of the British Armed Forces in summer 1990 after the end of the Cold War.

Until this point, UK military strategy had been almost entirely focused on defending Western Europe against the Soviet Armed Forces, with the Royal Marines in Scandinavia, the Royal Air Force (RAF) in West Germany and over the North Sea, the Royal Navy in the Norwegian Sea and North Atlantic, and the British Army in Germany.

With the collapse of the Soviet Union and the Warsaw Pact occurring between 1989 and 1991, the threat of a Soviet invasion of Western Europe fell away. While the restructuring was criticised by several British politicians, it was an exercise mirrored by governments in almost every major Western military power, reflecting the so-called peace dividend.

Total manpower was cut by approximately 18 per cent to around 255,000 (120,000 army; 60,000 navy; 75,000 air force).

Other casualties of the restructuring were the UK's nuclear civil defence organisations, the United Kingdom Warning and Monitoring Organisation, and its field force, the Royal Observer Corps (a part-time volunteer branch of the RAF), both disbanded between September 1991 and December 1995.

British Army

 * Halving the troop strength in Germany by replacing the British Army of the Rhine with British Forces Germany in 1994.
 * Several British Army regiments amalgamated:   (Those new units which were formed are in bold, not all units are shown, only those which changed, for full list see: List of British Regular Army regiments (1994))
 * Brigade of Gurkhas:
 * Regimental Headquarters, The Gurkha Engineers disbanded
 * The Royal Gurkha Rifles formed by amalgamation of: 2nd King Edward VII's Own Gurkha Rifles (The Sirmoor Rifles), 6th Queen Elizabeth's Own Gurkha Rifles, 7th Duke of Edinburgh's Own Gurkha Rifles, and 10th Princess Mary's Own Gurkha Rifles, 3 Battalion establishment
 * The Queen's Own Gurkha Transport Regiment formed by grouping of former independent Gurkha transport squadrons

Royal Corps of Signals

 * 1st Armoured Division Headquarters and Signal Regiment disbanded and concurrently reformed from 4th Signal Regiment as Lower Saxony Signal Regiment, then re-titled as 1st (United Kingdom) Armoured Division Headquarters and Signal Regiment
 * 4th Armoured Division Headquarters and Signal Regiment disbanded to help reform 1st Signal Regiment
 * 8th Signal Regiment absorbed into 11th (Royal School of Signals) Signal Regiment, Royal Corps of Signals
 * 13th (Radio) Signal Regiment reduced to cadre and later disbanded
 * 15th Signal Regiment and Headquarters Northern Ireland formed to administer those signal squadrons in Northern Ireland
 * 22nd Signal Regiment disbanded
 * 28th (British) Signal Regiment (Northern Army Group) reduced to 280 (United Kingdom) Signal Squadron
 * Berlin Headquarters and Signal Regiment reduced to 229 Signal Squadron

Royal Armoured Corps
Overall the Royal Armoured Corps was a merger of 18 regiments, this was achieved by the formation of 10 new regiments through amalgamations and new formations.

Bands
 * Band of the Dragoon Guards formed by amalgamation of: 4th/7th Royal Dragoon Guards Band, 5th Royal Inniskilling Dragoon Guards Band, Royal Scots Dragoon Guards Band, and 1st The Queen's Dragoon Guards Band
 * The Royal Tank Regiment Cambrai Band formed by amalgamation of: Cambrai Band of the Royal Tank Regiment, Alamein Band of the Royal Tank Regiment, Rhine Band of the Royal Tank Regiment
 * Band of the Hussars and Light Dragoons formed by amalgamation of: 13th/18th (Queen Mary's Own) Royal Hussars Band, 15th/19th The King's Royal Hussars Band, The Queen's Own Hussars Band, The Queen's Royal Irish Hussars Band, The Royal Hussars (Prince of Wales's Own) Band, 14th/20th King's Hussars Band
 * Band of the Royal Lancers formed by amalgamation of: 9th/12th (Prince of Wales's) Royal Lancers Band and The Queen's Royal Lancers Band

Regulars
 * Household Cavalry Regiment formed by union The Life Guards and The Blues and Royals (Royal Horse Guards and 1st (Royal) Dragoons)
 * The Royal Dragoon Guards formed by amalgamation of 4th/7th Royal Dragoon Guards and 5th Royal Inniskilling Dragoon Guards as cavalry county regiment of: Belfast, Fermanagh, Cumbria, Wirral, Cheshire, and Yorkshire, formed Pipes and Drums of the Royal Dragoon Guards in September 1993, RHQ in York
 * The Queen's Royal Hussars (The Queen's Own and Royal Irish) formed by amalgamation of The Queen's Own Hussars and The Queen's Royal Irish Hussars as cavalry county regiment of: Northern Ireland (minus Belfast and Fermanagh), Warwickshire, Worcestershire, West Midlands, Surrey, and Sussex, formed Pipes and Drums of the Queen's Royal Hussars, RHQ in London
 * The King's Royal Hussars formed by amalgamation of The Royal Hussars (Prince of Wales's Own) and 14th/20th King's Hussars as county cavalry regiment of: Buckinghamshire, Berkshire, Gloucestershire, Hampshire, Oxfordshire, Wiltshire, Isle of Wight, Channel Islands, Lancashire, Cumbria, and Greater Manchester, two regimental depots; North Depot in Preston and South Depot in Winchester
 * Light Dragoons formed by amalgamation of 13th/18th (Queen Mary's Own) Royal Hussars and 15th/19th The King's Royal Hussars as cavalry county regiment of: Tyne and Wear, County Durham, Northumberland, and North Yorkshire, depot in Newcastle upon Tyne
 * The Queen's Royal Lancers formed by amalgamation of 16th/5th The Queen's Royal Lancers and 17th/21st Lancers as cavalry county regiment of: Staffordshire, West Midlands, Nottinghamshire, Lincolnshire, and South Humberside, depot in Grantham
 * Royal Tank Regiment
 * Pipes and Drums of the Royal Tank Regiment formed from transfer from 4th RTR
 * 1st Royal Tank Regiment and 4th Royal Tank Regiment amalgamated without change of title, recruiting from: Scotland and Merseyside
 * 2nd Royal Tank Regiment and 3rd Royal Tank Regiment amalgamated without change of title, recruiting from: South East London, Somerset, Devonshire, Dorset, and Cornwall

Territorial Army
 * The Royal Mercian and Lancastrian Yeomanry formed by amalgamation of The Queen's Own Mercian Yeomanry and The Duke of Lancaster's Own Yeomanry as county yeomanry regiment of: Shropshire, Warwickshire, Worcestershire, Staffordshire, Lancashire, and Greater Manchester
 * The Scottish Yeomanry new formed regiment: resuscitation of old yeomanry units, country yeomanry of Scotland

Infantry

 * Guards Division based at Wellington Barracks
 * Grenadier Guards' 2nd Battalion placed in suspended animation and reduced to Nijmegan Company, and became independent, and Inkerman Company transferred from 2nd Btn to 1st as No.3 Company
 * Coldstream Guards' 2nd Battalion placed in suspended animation and reduced to No.7 Company, and became independent
 * Scots Guards' 2nd Battalion placed in suspended animation and reduced to F Company, and became independent, Corps of drums also disbanded
 * Scottish Division based at Glencorse Barracks covering the areas: Scotland.
 * All regimental bands amalgamated to form The Lowland Band and The Highland Band
 * The Royal Highland Fusiliers (Princess Margaret's Own Glasgow and Ayrshire Regiment): 1st Btn, 52nd Lowland Volunteers re-designated as 3rd (V) Battalion
 * The Black Watch (Royal Highland Regiment): 1st Btn, 51st Highland Volunteers re-designated as 3rd (V) Btn
 * The Highlanders (Seaforth, Gordons and Camerons): formed by amalgamation of the Queen's Own Highlanders (Seaforth and Camerons) and the Gordon Highlanders former as county regiment of: Caithness-shire, Elginshire, Nairnshire, Ross-shire, Sutherland, Orkney, Inverness-shire, Aberdeenshire, Banffshire, and Shetland. 1st Btn Regular, 2nd Btn, 51st Highland Volunteers re-designated as 3rd (V) Btn, RHQ in Inverness with outstation in Aberdeen
 * The Argyll and Sutherland Highlanders (Princess Louise's): 3rd Btn, 51st Highland Volunteers re-designated as 7th/8th (V) Btn
 * The Queen's Division based at Warminster covering the areas of: London, Kent, Surrey, Sussex, Hampshire, Middlesex, Isle of Wight, and the Channel Islands, Northumberland, Norfolk, Suffolk, Essex, Northamptonshire, Lincolnshire, Rutland, and Cambridgeshire.
 * The Duke of Kent's Band and Saint George's Band of The Royal Regiment of Fusiliers amagalamated to form The Normandy Band of the Queen's Division
 * Bands of the 1st and 2nd Btns, Princess of Wales's Royal Regiment and 1st and 2nd Btns The Royal Anglian Regiment amalgamated to form The Minden Band of the Queen's Division
 * The Princess of Wales's Royal Regiment: formed by amalgamation of The Queen's Regiment and The Royal Hampshire Regiment as regular county regiment of: London, Kent, Surrey, Sussex, Hampshire, Middlesex, Isle of Wight, and the Channel Islands, RHQ & Depot in Canterbury part of Queen's Division
 * The Royal Regiment of Fusiliers' 3rd Btn disbanded
 * The Royal Anglian Regiment's 3rd Btn amalgamated with 1st and 2nd Btns
 * The King's Division based at Imphal Barracks covering the areas of: Cumbria, Westmorland, Greater Manchester, Lancashire, Merseyside, East Riding of Yorkshire, North Yorkshire, and West Riding of Yorkshire.
 * Bands of the King's Own Royal Border Regiment, King's Regiment, and Queen's Lancashire Regiment amalgamated to form The Normandy Band
 * Bands of The Prince of Wales's Own West Yorkshire Regiment, The Green Howards (Alexandra, Princess of Wales's Own Yorkshire Regiment), and The Duke of Wellington's Regiment (West Riding) amalgamated to form The Waterloo Band
 * The Prince of Wales's Own Regiment of Yorkshire: 2nd Btn, Yorkshire Volunteers re-titled as 3rd (Yorkshire Volunteers) Btn,
 * The Green Howards (Alexandra, Princess of Wales's Own Yorkshire Regiment): 1st Btn, Yorkshire Volunteers re-titled as 4th/5th Btn
 * The Prince of Wales's Division based at Whittington Barracks covering the areas of: Devonshire, Dorsetshire, Cheshire, Wales, Gloucestershire, Worcestershire, Staffordshire, Berkshire, and Wiltshire.
 * All regimental bands of the division amalgamated to form The Clive Band and The Lucknow Band
 * Royal Regiment of Wales: 3rd (V) and 4th (V) Btns amalgamated to form 2nd (V) Btn
 * The Royal Gloucestershire, Berkshire and Wiltshire Regiment: formed by amalgamation of the Gloucestershire Regiment and the Duke of Edinburgh's Royal Regiment (Berkshire and Wiltshire) as county regiment of: Gloucestershire, Berkshire, and Wiltshire with regimental depot in Gloucester with 1st Btn and 2nd (V) Btn
 * The Worcestershire and Sherwood Foresters Regiment (29th/45th Foot)'s 4th (V) Btn disbanded
 * The Light Division based at Battlesbury Barracks covering the areas of: Somerset, Cornwall, South Yorkshire, Shropshire, County Durham.
 * The Light Infantry's 3rd Btn disbanded
 * The Royal Green Jackets' 3rd Btn disbanded
 * Royal Irish Regiment (27th (Inniskilling), 83rd, 87th and Ulster Defence Regiment) formed by amalgamation of Ulster Defence Regiment and Royal Irish Rangers, while territorials retained Royal Irish Rangers title
 * The Parachute Regiment: 15th (Scottish) Btn reduced to 15 (Scottish) Company in the 4th (V) Btn

Royal Artillery

 * 2nd Field Regiment Royal Artillery placed in suspended animation, batteries transferred to: 1st RHA, 3rd RHA, and 32nd RA
 * The Depot Regiment Royal Artillery placed in suspended animation
 * 27th Field Regiment Royal Artillery placed in suspended animation, battery transferred to 29th RA

Corps of Royal Engineers
Regulars
 * Commander Royal Engineers (Airfields) formed to control non-deployable royal engineer airfield elements at RAF bases in the UK
 * 29th (Volunteer) Engineer Brigade along with its signal troop disbanded
 * 30th (Volunteer) Engineer Brigade along with its signal troop disbanded
 * 26th Engineer Regiment disbanded
 * 1st Royal School of Military Engineering Regiment formed by amalgamation of the Depot Regiment, Royal Engineers and 12th Royal School of Military Engineer Regiments, Royal Engineers
 * 3rd Royal School of Military Engineering Regiment formed by amalgamation of 1st Training and 3rd Training Regiments, Royal Engineers

Territorial Army
 * 74th (Antrim Artillery) Engineer Regiment reduced to 74 Independent Field Squadron
 * 76th Engineer Regiment formed to control existing airfield damage repair squadrons in: Scotland and North of England
 * 77th Engineer Regiment formed to control existing airfield damage repair squadrons in: Eastern and Southern England
 * 78th (Fortress) Engineer Regiment formed to provide a new support regiment for the 3rd (United Kingdom) Mechanised Division
 * 111th Engineer Regiment disbanded

Other Corps

 * Royal Logistic Corps
 * Royal Corps of Transport
 * Royal Army Ordnance Corps
 * Royal Pioneer Corps
 * Army Catering Corps
 * Postal and Courier Service, Royal Engineers
 * Adjutant General's Corps
 * Royal Army Educational Corps
 * Royal Army Pay Corps
 * Women's Royal Army Corps
 * Army Legal Corps
 * Corps of Royal Military Police
 * Military Provost Staff Corps
 * Army Medical Services
 * Royal Army Medical Corps
 * Queen Alexandra's Royal Army Nursing Corps
 * Royal Army Dental Corps
 * Royal Army Vetinerary Corps

Strike Command

 * Withdrawal of the Blackburn Buccaneer strike aircraft and the disbandment of the RAF Lossiemouth-based No's 12 and 208 Squadrons and No. 237 Operational Conversion Unit (OCU).
 * Closure of RAF Wattisham and transfer to the British Army, together with the withdrawal of the McDonnell Douglas Phantom from service and the disbandment of No's 56 and 74 Squadron's and the Leuchars-based No. 228 OCU.
 * Closure of RAF Honington as a flying station with it to become the depot for the RAF Regiment replacing RAF Catterick which was transferred to the British Army. The Panavia Tornado's of No. 13 Squadron and the Tornado Weapons Conversion Unit relocating to RAF Marham and Lossiemouth respectively.
 * The relocation of the Tornado's of No's 27 (later renumbered to No. 12 Squadron) and 617 Squadron's from Marham to Lossiemouth and the modification of 28 aircraft to use the Sea Eagle anti-ship missile.
 * Closure of RAF Brawdy and transfer to the British Army as Cawdor Barracks, and the disbandment of 1 Tactical Weapons Unit.
 * Withdrawal of the remaining Handley Page Victor tankers, and the disbandment of No. 55 Squadron.
 * A reduction of three Nimrod maritime patrol aircraft, together with the disbandment of No. 42 Squadron which merged with No. 236 OCU and relocated from RAF St Mawgan to RAF Kinloss.
 * Withdrawal of the Bloodhound SAM and the disbandment of No. 85 Squadron.

RAF Germany

 * Closure of RAF Wildenrath in April 1992 and RAF Gutersloh in March 1993, halving the number of RAF bases in Germany.
 * Disbandment of Wildenrath's two Phantom air defence squadrons (No's 19 and 92 Squadrons).
 * Disbandment of the three RAF Laarbruch Tornado strike/attack squadrons (No's XV, 16, and 20 Squadrons), and the transfer of No. II Squadron to Marham.
 * Transfer of the Harriers of No's 3 and 4 Squadrons and the Chinooks of No. 18 Squadron from Gutersloh to Laarbruch, and the transfer of No. 230 Squadron from Gutersloh to RAF Aldergrove.

RAF Germany itself was disbanded on 1 April 1993, being downgraded to group-level and becoming No. 2 Group of Strike Command.

Procurement

 * Cancelling the Brimstone air-to-surface missile project (later restarted).

Royal Navy

 * Cutting the number of frigates and destroyers from around 50 to 40. This was largely achieved through the decommissioning and disposal of aging types such as the remaining Leander-class frigates, as well as the sale of the remaining Type 21 frigates to Pakistan and the early Type 22 frigates to Brazil.

On television
A dramatisation of the effects that Options for Change had on the ordinary men and women serving in the armed forces came in the ITV series Soldier Soldier. The fictional infantry regiment portrayed in the series, the King's Fusiliers, was one of those selected for amalgamation. It showed the whole process of negotiation over traditions, embellishments, etc. between the two regiments involved, and the uncertainty that many of those serving felt for their jobs in the light of two separate battalions merging into one, with the resulting loss of manpower.

title: Options for Change