This page compares the US English national layout with different national layouts used in other countries. For the obvious reason, these comparisons are limited to keyboard layouts based on the Latin alphabet.
Each comparison focuses on the differing arrangements of the alphabetical, numerical and typographical symbols in each national layout; due to this, all of them are presented within the same regular alphanumeric or “alpha” block, ignoring the remaining parts of a keyboard (namely: function row, navigation cluster and numeric keypad).
In each section, the base US English over ANSI layout and a different national layout are presented side by side, with the differing keys highlighted.
This document is comprised of the following sections:
Notes:
Considered the base layout for historical reasons.
Official in the United States of America; used in several other English-speaking countries with differing degrees of officiality (including, strangely, the Netherlands? See below.).
This is the only major layout that does not use the tertiary (AltGr) or quaternary (AltGr‑Shift) layers. In fact, the RALT key is simply the right-side Alt key and not AltGr.
The standard for this layout was codified back when both main versions of the Enter key were common in keyboards sold and used within the United States of America (horizontal, nowadays called “ANSI Enter”, and vertical, nowadays called “ISO Enter” — both nicknames, though, are serious misnomers) and due to this, they were both taken in consideration in it; because of this, both are still valid, even if the horizontal Enter key is now ubiquitous within said country.
The above also means that the \| (“backslash‑pipe”) key has two valid places to be assigned to: in row 2, with a size of 1.5U, if the keyboard has a horizontal (“ANSI”) Enter key, and in row 3, with a size of 1.0U, if the keyboard has a vertical (“ISO”) Enter key instead; therefore, a keycap set that supports the English (USA) layout and contains both versions of the Enter key, also needs to provide both versions of the \| key, independently of whichever other national layouts might be additionally supported.
The standard does not define the presence of a key between LSHIFT and Z, much less assign characters to it; when said key is present (in ISO or ISANSI keyboards), there are two main traditions about what characters should be assigned to it, one coming from personal computer keyboards and the other from terminal keyboards (see above).
Sources and non-sources:
See also:
Notes:
IBM, not Microsoft, created this layout. The initial version had only a few extra key assignments, with several additions made later on; Microsoft forked an early version and made further incompatible changes. IBM’s version of this layout died with OS/2, while Microsoft’s branch survives to this day.
A true extended layout adds new capabilities without modifying any of the original layout’s assignments (see the Finnish Multilingual and the Spanish Extended layout for two examples of this); this layout, instead, is a pseudo-extended version of the regular English (USA) layout, as it turns the key assignments of five typographical symbols into diacritic dead keys.
Despite its moniker, this layout’s real coverage is limited to a few Germanic and Western European languages, with inexplicable omissions even among this limited set; the OE ligature (Œ/œ), the middle dot (·) and the single low quotation mark (‚) are the most obvious ones. It does not help matters that some typographical symbols that are commonly used while writing in English in the United States (like “, ”, ±, — and –) are missing as well.
The arrangement of the extra characters that this layout does add is rather problematic, too; while some of them are fine [for example: the vowels with acute accents, the letter eñe (Ñ/ñ) and the angle quotation marks (« »)], others have been assigned in an inconsistent manner [like the three vowels with diaeresis/umlauts], even others have been placed where they clearly don’t belong [see where the letter C with cedilla (Ç/ç) is], and still others are placed in hard-to-reach assignments that are not in line with the high degree of usage they would be expected to have [like the pound (£), section (§) and degree (°) signs], despite readily available space remaining in the tertiary (AltGr) layer.
The addition of the five dead keys mentioned above is undeniably poorly done and further complicates actual usage: the grave (◌̀), tilde (◌̃) and circumflex (◌̂) accents take the places of the commonly used symbols backquote (`), tilde (~) and caret (^), respectively, while the acute accent (◌́) and the diaeresis/umlaut (◌̈) take the place of the extremely highly used symbols (adirectional) apostrophe (') and (adirectional) quotation mark (") (which, to boot, don’t have an actual relation to said diacritics), forcing the usage of two-keystroke combos to get the proper symbols: (`+space for `, Shift‑'+space for ", etcetera). This is so uncomfortable, private individuals have created variations of this layout that either remove those diacritics or move them elsewhere.
As if the above wasn’t enough, Microsoft’s implementation tacks on the cedilla diacritic (◌̧ ) to the apostrophe dead key for no good reason (it’s only used for the letter C with cedilla (Ç/ç), which already has a direct assignment). Implementations in Linux produce a C with acute accent (Ć/ć) instead, which at least makes sense.
All known implementations follow the PC style tradition for the key between LSHIFT and Z.
Sources and non-sources:
See also:
Notes:
Official in the United Kingdom, Ireland and Hong Kong; also used in some other English-speaking countries, with differing degrees of officiality.
The BS 4822 standard (published in 1994) mandated the layout seen in the top right alphanumeric block, but was withdrawn in 2008 without having ever been updated or superseded by a new document; current usage has flipped the characters | (U+007C, VERTICAL LINE) and ¦ (U+00A6, BROKEN BAR) and assigned the character € (U+20AC, EURO SIGN) to AltGr‑4, as seen in the bottom right alphanumeric block; the IBM specification was updated in 2000 with the latter change but not the former.
Microsoft’s implementation adds the accented vowels Á, É, Í, Ó and Ú, but not Ẃ or Ý.
Sources and non-sources:
See also:
Notes:
This is a superset of the standard English (UK) national layout (with an exception — see below); it adds support for Welsh, Cornish and (modern) Irish.
As far as can be determined, this layout was actually created by Microsoft; it follows the current usage version of the English (UK) national layout, despite the BS 4822 standard having been still in vigour at the time of its creation.
The specification, as transcribed by IBM, includes a macron (◌̄) dead key for the benefit of Cornish. However, Cornish does not use it — it relies on circumflex and grave accents instead. This is probably the reason why Microsoft’s implementation omits the macron and replaces the backquote with a grave accent (◌̀) dead key.
Given the described discrepancy and what the Standard Written Form of Cornish actually mandates, this document opts to register Microsoft’s choice of dead keys instead of what the IBM document states.
Sources and non-sources:
See also:
Notes:
This Microsoft-made layout is an intermediate version between the English (UK) and English (UK) Extended layouts, with (presumably) little actual research about the needs of the Irish language — most notably, the complete absence of the overdot diacritic.
Private individuals have created several alternative layouts with the requirements of the Irish language in mind; all of them are better than this half-baked effort, which strongly looks like it was made to satisfy a whim or quickly check a box.
Sources and non-sources:
See also:
Notes:
This is the old standard keyboard layout in Canada; it was created to satisfy the legal requirements derived from the country’s recognition of both English and French as official languages. Even today, its presence in Quebec and other Francophone areas is ubiquitous, due to the limited adoption rate of the Canadian (multilingual) layout, but in the regions of the country with little or no French presence, the English (USA) layout is preferred.
Despite having been created with bilingualism in mind, this layout is generally known as “French Canadian” (or “Canadian French”, “French (Canada)”, etcetera). This term is also applied to the Canadian (intermediate) layout and (although to a much lesser degree) to the Canadian (multilingual) layout, further muddling the issue. This document prefers the name “Canadian (bilingual)” to help reduce confusion.
It does not help matters that a common sight in Canada are binational keyboards, containing the printed legends for both English (USA) layout and either the Canadian (bilingual) or the Canadian (intermediate) layout, and those are marketed and sold as “bilingual keyboards”.
This layout is obviously derived from the English (USA) layout; while it’s certainly nowhere as bad as the French (France) layout, a better job could have been done of it; the most glaring problems are: the inclusion of a dead key for the cedilla makes little sense if it’s only used to produce the Ç letter; the displacement of the apostrophe ('), less-than (<) and greater-than (>) signs comes off as unnecessary and detrimental to the overall layout... but not as bad as the displacement of the slash (/) sign actually is; the superscript characters ² and ³ could have been easily placed under AltGr‑2 and AltGr‑3.
This is one of very few national layouts that include the overline sign (¯).
Keyboards with this layout generally have legends in French in their modifier keys, but it’s unclear whether this is a requirement of its standard or is simply a common practice.
Sources and non-sources:
See also:
Notes:
This layout was seen on keyboards sold during the mid ’90s, before units with the hexalayered Canadian (multilingual) layout appeared. Actually, it looks like this layout is an early version of what became the Canadian (multilingual) layout, before the quinary and senary layers were added; the fact that said layout is a superset of this one reinforces this theory.
This layout is commonly referred to as “French Canadian”, as well as “ACNOR keyboard”, to distinguish it from the CSA keyboard (despite ACNOR and CSA being the same organization and both layouts quite probably coming from different versions of the same standard). This document prefers the name “Canadian (intermediate)” to help reduce confusion.
No PC keyboards with this layout are sold currently, but old units can be found with relative ease. Weirdly, however, a significant minority of the binational (USA+Canada) keyboards presently for sale use this layout for the Canadian legends.
On the other hand, Apple’s current “French (Canada)” layout is a lightly Apple-warped version of this layout, instead of either of the other two Canadian layouts. Apple’s old (“old” as in “M0110 keyboard”) layout, actually called “W. French”, was a heavily Apple-warped version of the Canadian (bilingual) layout; it was so horribly inadequate that Apple itself took the rare step of replacing it with its current layout.
Sources and non-sources:
See also:
Notes:
This is the current standard keyboard layout in Canada, developed with the intention of supporting both English and French and several other languages (with a clear bias towards Northwestern and Northern Europe); it’s governed by the CAN/CSA Z243.200-92 standard, which, unlike several other national layout standards, has been periodically revised by the CSA Group (formerly the Canadian Standards Association, known by its abbreviations CSA [English] and ACNOR [French]).
Not that the above matters, as this layout, despite being official in Canada, promoted by its government, and mandatory in the public sector, is not well liked; French-speakers prefer the Canadian (bilingual) layout, while the English (USA) layout is used wherever in the country there is little or no French presence.
The poor reception of this layout is evidently a result of its rather questionable design; quinary and senary layers are added for no real reason (as the ternary layer remains mostly empty and the quaternary layer entirely so), which require the transformation of the right Control key into a (right-side only) Shift2 modifier key to access them. Many of the character assignments within these superfluous layers are unintuitive and were clearly piled on gradually wherever space happened to be available, with little thought given to the overall design of the layout as a whole (and correctness, in a few glaring cases); this makes hard it to remember when exactly either of AltGr, Shift2 or Shift2‑Shift should be pressed to produce a particular symbol. Furthermore, the loss of the right Control key hinders general usability and produces unexpected results with some programs (not to say anything of some “custom” keyboards that lack that key because their designers think that if they themselves don’t use it, then no one else does, either, and can thus be omitted).
It would not be difficult to make a new, better “Canadian multilingual” layout that fixes the many problems this one has, and removes the unneeded quinary and senary layers... or actually keeps them, but reserved exclusively for a unified Syllabics layout.
IBM’s specification, pictured above, represents what the standard mandated in the late ’90s; that is quite outdated, as the current version, also pictured above, contains many later additions to the quinary and senary layers (while barely touching the ternary layer). Although not for sale anymore, older keyboards with the IBM-frozen version of the layout printed on their keycaps are not hard to find.
Uniquely, the standard mandates using icons instead of text legends for the modifier keys.
A commonly used name for keyboards with this particular layout is “CSA keyboard”.
Sources and non-sources:
See also:
Notes:
The Dvorak layout was created in 1936 as an (alleged) improvement over the QWERTY layout. Over the years, it has been subjected to several changes and has been standardized into the version seen above.
Despite its claims, its level of adoption has been limited, even among enthusiasts.
Given the scant usage this layout sees, there’s pretty much nothing established about what to do with the key between LSHIFT and Z if it should be present. Microsoft’s implementation of this layout simply places an extra \| (“backslash‑pipe”) key, following the PC style, as it already does in the regular (QWERTY) English (USA) layout.
Row 1 is mostly unaltered with respect to the regular (QWERTY) English (USA) layout (this wasn’t the case in the original version of the Dvorak layout!). On the other hand, in rows 2, 3 and 4, most keys have been moved around: only three remain in the same positions, and ten others remain in the same row but have have been displaced to the left or to the right.
The homing keys become U and H, instead of F and J.
Sources and non-sources:
See also:
Notes:
The Colemak layout was created in 2006 as another improvement over the QWERTY layout, that would also be less drastic of a change than the Dvorak layout is.
Only one non-letter alphanumeric key is moved around; the rest of the reassignments is restricted to the letter keys.
The homing keys become T and N, instead of F and J.
The Caps Lock key becomes another Backspace key.
Sources and non-sources:
See also:
Notes:
Official in Denmark.
This layout is extremely similar to the Norwegian one.
Several implementations, including Microsoft’s, assign the character € (U+20AC, EURO SIGN) to AltGr‑5 in addition to AltGr‑E.
Sources and non-sources:
See also:
Notes:
This used to be the standard keyboard layout in the Netherlands, but at some point (seemingly, during the late ’90s), it was abandoned in favor of the English (US international) layout, laid on top of ISO keyboards (although ANSI units are a common sight). Worse, the keyboards commonly sold in that country only print the legends for the regular English (USA) layout, with the lone addition of the euro sign (€) on the bottom-right corner of the 5 % keycap. Why aren’t the rest of the tertiary (AltGr) and quaternary (AltGr‑Shift) layer assignments printed is a mystery, but cost-saving and laziness are quite probably to blame.
It remains unknown whether the Dutch layout was explicitly abandoned in favor of the English (US international) layout, or if this switch occured due to some sort of gradual market force (or abuse of it!) in action. For that matter, it also remains unknown the true degree of officiality the Dutch layout did have in the past within the country; no (government) standards document regarding this matter has been discovered so far.
Logical layouts, PC-based or terminal-based, that pair opening and closing symbols in the same key (curly braces, less-than and greater-than signs, angle quotation marks, etcetera), always place the former in the base layer and the latter in the secondary (Shift) layer; the Dutch layout goes the other way around with the brackets for no apparent reason: ] is on the base layer, while [ goes up to the secondary (Shift) layer. Why on Earth was this done (especially considering that the < and > symbols are placed normally) might be one of those mysteries that shall never be solved.
Sources and non-sources:
See also:
Notes:
The Faroe Islands are an autonomous territory within the Kingdom of Denmark; it’s no surprise, then, that this subnational layout is based directly on the Danish layout.
When and where this layout was created is not clear; Microsoft seems to have implemented it before 2003, yet IBM does not have a specification for it.
Microsoft’s implementation assigns the character € (U+20AC, EURO SIGN) to AltGr‑5 in addition to AltGr‑E. In the same manner, the presence of µ (U+00B5, MICRO SIGN) under AltGr‑M seems to be another quirk of this implementation instead of something that would be in the standard, if one actually exists.
Sources and non-sources:
See also:
Notes:
This layout was created by the Finnish IT Center for Science, with the goal of having complete support for the Finnish language and minority languages spoken in Finland, plus support for many other languages that use the Latin alphabet. In 2008, the Finnish Standardization Association released it as the SFS 5966 standard and declared it the official national layout for Finland, superseding the Swedish and Finnish layout. In 2019, a few small changes were made and a revised standard was published.
This layout is a (true) extended version of the Swedish and Finnish layout. It adds support for the letters Š and Ž, required by the Finnish ortography for loanwords, several typographical symbols (following Finnish usage, such as placing the angled quotes “backwards”), a few extra letters used in languages other than Finnish, and thirteen dead keys for diacritics, in addition to the previously extant five.
Despite being a well-designed layout that should not pose any problems for adoption (as it’s a strict superset of the previous official layout, and corrects several of its omissions), its usage levels remain low; while it was immediately implemented in Linux, it has not been so, to this day, by Microsoft and Apple; this omission is particularly inexplicable in the case of Microsoft, which at the time the standard was published was keen on implementing a multitude of national layouts, including several dedicated to minority languages with very small amounts of speakers.
Private individuals have built their own implementations of this layout for Windows and MacOS to wade around this problem.
There is little to criticize in this layout: the only omissions of note are the Turkish dotted uppercase letter I (İ), given that the dotless lowercase non-counterpart (ı) is present, and the backquote (`), tilde (~) and caret (^) characters as directly available assignments instead of through a dead key, given the importance programming has in keyboard usage in Finland; AltGr‑1, AltGr‑Q and AltGr‑W are unused, so they could be placed there without issue.
Another further improvement would be to move the single, double and angled quotes to more sensible positions in the tertiary (AltGr) layer in the still available central area of the keyboard (this would also allow moving the comma dead key from AltGr‑Shift‑- to AltGr‑,, a much more intuitive position).
This is one of very few layouts that places the character (U+00A0, NO-BREAK SPACE) in AltGr‑space. Uniquely, the 2019 revision added the (U+202F, NARROW NO-BREAK SPACE) character as well, in AltGr‑Shift‑space.
The character – (U+2013, EN DASH) is located at AltGr‑-, while the character — (U+2014, EM DASH) is located at AltGr‑Shift‑M.
The stroke (not “bar” or “slash”) dead key is located under AltGr‑§, with an alternative placement under AltGr‑L, to cover the possibility of the corner alpha key being unavailable (another piece of evidence of the importance that programming has in Finnish keyboard usage). This is not a true diacritic — instead, this dead key allows typing a few unrelated stroked letters: Đ/đ (not to be confused with the letter eth, Ð/ð, placed under AltGr‑D), Ǥ/ǥ, Ħ/ħ, Ł/ł and Ŧ/ŧ, plus Ø/ø (which is already available under, AltGr‑Ö).
Sources and non-sources:
See also:
Notes:
Official in Germany and Austria.
The IBM specification (last updated in 1998) declares AltGr‑+ to be a dead key, but all known implementations make it instead into a regular key, which produces the (non combining, non diacritic) character ~ (U+007E, TILDE). To compound the issue, the DIN 2137 document (the current standard governing this layout in Germany) has declared it as a regular key since at least its 2012 edition; it’s not known if this was a de facto change that was adopted at some point by the standard, or if the IBM specification was wrong in the first place. The confusion is further deepened after studying the German-derived national layouts that place the tilde in the same physical key combination: most of the Nordic layouts (with the possible exception of the Icelandic one) keep it as a dead key, while Spanish (Latin America) and (perhaps) Icelandic have made it into a regular key (as German seems to have).
The character under AltGr‑M is µ (U+00B5, MICRO SIGN) and not μ (U+03BC, GREEK SMALL LETTER MU) (albeit the symbol is evidently derived from the letter).
In 2008, Unicode added the uppercase form of the eszett ligature ẞ (U+1E9E, LATIN CAPITAL LETTER SHARP S). The standard for the German layout was rewritten in 2012; the new version kept the then-extant layout as “T1”, but did not add this character, and created “T2” and “T3” extended/specialized layouts, which do add it under AltGr‑H. Meanwhile, Microsoft added the uppercase eszett to its implementation of the German layout (now “T1”), under AltGr‑Shift-ß, and has kept it there instead of moving it so it will be in accordance to the DIN standard.
Although this is at its core a national layout based on the ISO physical layout variant, ISANSI versions of this layout exist, thanks to the “HADapter kit”, which provides a replacement 1.5U #' key in row 2 (plus a 1.0U #' key in row 1, for keyboards with an HHKB-style physical layout).
This is one of the few layouts that require the modifier keys to have legends in its own language instead of allowing them to remain in English («Strg» for “Ctrl”, «Einfg» for “Ins”, etcetera).
Sources and non-sources:
See also:
Notes:
Official in Iceland.
Unusually, this national layout, at least as defined in the IBM specification (last updated in 2000), places the acute accent dead key in both the base layer and the secondary (Shift) layer of the same key. Microsoft’s implementation seems to get this wrong, putting an unneeded apostrophe in the secondary (Shift) layer assignment; however, this and other differences (notably, tilde ceases to be a dead key, while the backquote becomes one) could be derived from the 2015 standard, the text of which has not been obtained yet.
Several implementations, including Microsoft’s, assign the character € (U+20AC, EURO SIGN) to AltGr‑5 in addition to AltGr‑E.
The -_ key is displaced one position to the right with respect to the English (USA) keyboard, but remains in row 1.
Sources and non-sources:
See also:
Notes:
Official in Norway.
This layout is extremely similar to the Danish one.
Several implementations, including Microsoft’s, assign the character € (U+20AC, EURO SIGN) to AltGr‑5 in addition to AltGr‑E.
Sources and non-sources:
See also:
Notes:
The Sami languages are spoken in the northern reaches of the Scandinavian Peninsula and the neighboring Kola peninsula; they have been recognized as minority languages in Norway, Sweden and Finland.
This Microsoft-made layout is a (true) extended version of the Norwegian layout, to which the extra letters and letters with diacritics required to write in almost all the known Sami languages (not just the ones spoken in Norway) have been added in the tertiary (AltGr) and quaternary (AltGr‑Shift) layers; the letter Ü, used in Ume Sami, is inexplicably missing.
Sources and non-sources:
See also:
Notes:
Official in Sweden; official in Finland until 2008, when it was replaced by the Finnish Multilingual layout, although this one continues to be the majority option in the country.
Several implementations, including Microsoft’s, assign the character € (U+20AC, EURO SIGN) to AltGr‑5 in addition to AltGr‑E.
Sources and non-sources:
See also:
Notes:
The Sami languages are spoken in the northern reaches of the Scandinavian Peninsula and the neighboring Kola peninsula; they have been recognized as minority languages in Norway, Sweden and Finland.
This Microsoft-made layout is a (true) extended version of the Swedish and Finnish layout, to which the extra letters and letters with diacritics required to write in almost all the known Sami languages (not just the ones spoken in Sweden or Finland) have been added in the tertiary (AltGr) and quaternary (AltGr‑Shift) layers; the letter Ü, used in Ume Sami, is inexplicably missing.
Sources and non-sources:
See also:
Notes:
The Swiss national layout was designed to support one Germanic language (German) and three Romance ones (French, Italian and Romansh); it’s listed in this section because it was evidently derived from the German layout.
This layout’s specification, governed in its latest revision by the SN 074021:1999-01 document, defines two “modes” of operation: in the “German” mode, the keys in the positions D11, C10 and C11 (see above) have the characters ü, ö and ä, respectively, in the base layer, while the characters è, é and à, respectively, are in the secondary (Shift) layer; in the “French” mode, those assignments are flipped (è, é and à, respectively, are in the base layer, while ü, ö and ä, respectively, are in the secondary (Shift) layer).
This modes shenanigan is so far off the regular behaviour of a keyboard, that all known implementations in differing operating systems simply split the Swiss layout into two separate ones: “Swiss (German)” and “Swiss (French)”.
To further muddle the issue, keyboards sold in Switzerland print both varieties in the aforementioned three keycaps, leading to visually confusing labels:
Note how in the first keyboard, symbols in the tertiary (AltGr) layer are consistently front-printed, while in the second one, some are printed in the bottom right corner (this is the correct position) and others in the top right one (falsely implying they’re part of the quaternary (AltGr‑Shift) layer).
Problems don’t stop there, though: in both “modes”, those three keys produce said six vowels with diacritics... but only in their lowercase forms; to produce them in uppercase, Caps Lock must be turned on. To mitigate this limitation, and to allow typing the remaining accented letters, dead keys for every major diacritic (diaeresis/umlaut, and the acute, grave and circumflex accents... plus the tilde, which is not used in any language spoken in Switzerland) are included...
... but don’t let the letter C with cedilla hear about it, as its uppercase version (Ç) can’t be typed at all using this layout.
This is an unequivocally poorly designed layout — it would have been much better to assign the diacritic dead keys directly to the D11, C10 and C11 keys (where they would have been more comfortable to use), get rid of the nonsensical vowel dualities and take advantage of the freed-up space in the remaining keys to include other symbols: besides the incompetent treatment of the C with cedilla, there is no good excuse for not having included, at the very least, the angle quotes or guillemets (used in German and French) and the Æ/æ (used in Italian and French), Œ/œ (used in French) and even ẞ/ß (used in German, even if Swiss Standard German doesn’t) ligatures.
Despite its serious flaws and omissions, this is (are) the official layout(s) in Switzerland. Weirdly, but not surprisingly, the Swiss (German mode) layout is also official in Liechtenstein; in addition to that, the Swiss (French mode) layout is, unbelievably, official in Luxembourg, although a large percentage of its population prefers using the French (Belgium) layout.
Linux’s implementations of most national layouts include the lowercase eszett ligature (ß) under AltGr‑S; this is the case of the Linux implementation of the Swiss layouts, too.
Microsoft’s implementations of the Swiss layouts are particularly deficient. To wit:
Sources and non-sources:
See also:
Notes:
Official in Estonia.
Several implementations, including Microsoft’s, assign the character € (U+20AC, EURO SIGN) to AltGr‑5 in addition to AltGr‑E.
Sources and non-sources:
See also:
Notes:
IBM’s specification defines two different layouts for the Latvian language: “QWERTY” and “Ergonomic”; they follow, respectively, the Latvian standards LVS 24-93 and LVS 23-93 (note that despite their numbers, the former is older than the latter by a few months). The “QWERTY” layout is generally used in the country, while the latter is barely utilized.
The “QWERTY” layout is essentially the same as the English (USA) layout, PC style, to which the specific requirements of the Latvian language have been added on to the tertiary (AltGr) and quaternary (AltGr‑Shift) layers; the only changes in the primary (base) and secondary (Shift) layers are the apostrophe/quote key ('/"), for which both assignments are now dead keys, and the (home row) backlash/pipe key (\/|), which now contains the degree sign and the broken bar character (A remnant from a layout for old terminals? That seems to be the least implausible explanation); the backslash and pipe characters are still available in the extra alpha key.
The inescapable oddities and anomalies present in this layout suggest that rather little care was put into it, allowing egregious errors to pass through: the apostrophe and quote signs are now dead keys, but are duplicated as-is in the AltGr layers of the same key; there is no logical reason for having taken the backslash and pipe characters off from... the backslash/pipe key; in the number row, several symbols have been added to the quaternary (AltGr‑Shift) layer, even though space in the tertiary (AltGr) layer is readily available; the degree sign is duplicated; the multiplication sign is present but the division sign is nowhere to be seen; AltGr‑- and AltGr‑Shift‑- are supposed to be, respectively, the en dash and the em dash (in THAT order), but the chart shows, instead of an en dash, what is clearly an overline sign... which is something that would actually make sense, given the Latvian language uses the macron diacritic. In light of these problems, the fact that the no-breaking space has been placed at AltGr‑1 instead of AltGr‑space looks more like a whimsical choice rather than the error it probably actually is.
The “Ergonomic” layout (also known as “ŪGJRMV”, following the usual layout-naming formula) has been, allegedly, designed to optimize writing in Latvian. The rather radical rearrangement of the letters (out of thirty nine letters, only two remain in the same position, and barely five more manage to stay in the same row and pair of layers) may well be perfect in this regard (G with comma and K with comma notwithstanding), but its handling of typographical symbols leaves a lot to be desired — barely any errors in the “QWERTY” layout have been corrected here, and some further mistakes have been commited, the worst one being the inexcusably sinful displacement of the curly braces to the quaternary (AltGr‑Shift) layer.
Okay, I’ll say it: who is Šusilda, and why was her name sneaked onto the home row?
It’s important to note that the Latvian language uses a diacritic comma on its letters G, K, L and N (plus, formerly, R), not a diacritic cedilla; both layouts opt for the latter instead of the former because the Unicode Consortium still has not disunified both diacritics. If that ever happens, both layouts will need to be updated, to produce the correct characters (and perhaps add the still missing D with comma, required to write in Livonian).
Microsoft offers two different implementations of the “QWERTY” layout, both slightly different than what the specification for it declares, and one more for the “Ergonomic” layout, which is almost identical to its corresponding specification, but with an error so grievous, it has to be seen to be believed (hint: look at the key F in the number row).
Sources and non-sources:
See also:
Notes:
The Lithuanian National Standard LST 1582:2000 makes official and mandates the layout seen in the top right alphanumeric block, but the actual degree of usage of this layout is rather lower than it should be (see below).
Unlike other languages with a convoluted mess of conflicting layouts, the ones used in Lithuania are well-known and well-documented enough to clear up their history.
When personal computers started showing up in Lithuania (at about the same time the USSR was collapsing, which allowed the country to declare its independence), support for the Lithuanian language on (Western) software and hardware was extremely limited. At first, given that the keyboards imported to the country were units with the English (USA) layout, the first Lithuanian layout was made by simply replacing the keys 1 through 8 and =+ in the number row with dedicated keys for the required letters with diacritics (ogonek, caron and overdot).
This first layout came to be colloquially known as “numeric” (probably in a display of contrarian humor, because it lacked most of the numbers in the main alphanumeric block). Unsuprisingly, it was generally regarded as defficient, as it was uncomfortable for writing in Lithuanian (due to the high number of letters in the number row), required the presence of a numeric keypad to type numbers, and lacked many heavily used typographical symbols. It should be noted that the “weird” placement of the letter Ž followed the placement of the letter X, as was the standard in Lithuanian typewriters.
The “numeric” layout never was a documented standard to begin with — it simply won out through inertia and lack of true competition through the then-small user base.
In 1989, the first standard for a Lithuanian keyboard, LST 1092-89, was published. This layout (not pictured above) was complex and convoluted and gained no traction whatsoever, ending up no more than an obscure footnote.
A new standard, LST 1205-92, published in 1992, attempted to replace the “numeric” layout; it was directly derived from the preexisting standard for Lithuanian typewriters, which places the numbers in the secondary (Shift) layer of the number row, has a rather particular arrangement of the basic typographical symbols in its base layer (albeit not pointlessly chaotic, as the French layouts do have), and places all the letters with diacritics in the main rows. The only notable differences between the 1992 standard and its source (the typewriter standard) are that it swapped the letters F and Š, so the former would retain the same placement as in Western keyboards, and eliminated the letter X (in Lithuanian, the letter F is used only on loanwords; Q, W and X are entirely absent, and the first two of those had already been expelled from typewriters).
The 1992 standard was also deemed to be insufficient, as the lack of three Latin letters made it rather challenging to write in English and other European languages (or, for that matter, to une_uivocally e_plain the _eirdly _ui_otic _ays of the layout itself), and the absence of several important typographical symbols impeded programming.
It does not escape notice that not just the numbers and symbols are swapped in the number row — the same was done to the -_, =+ and \| keys, which became, respectively, _-, += and |\. Information regarding the 1992 standard is scant, but the few extant signs suggest that it was made with BAE keyboards in mind. EEEEWWWW! Another good reason for its repeal!
In 2000, the LST 1582:2000 standard superseded the previous one and corrected its mistakes. Notably, it swapped the letters F and Š, in accordance with the typewriter standard.
With all the above said, the 2000 layout should be the mainly used one, with all other options left behind... but inertia and the misguided support of major OS manufacturers have allowed the “numeric” layout to continue to be the most popular one in the country, despite its serious shortcomings and problems.
Windows provides implementations of the three Lithuanian layouts: the “numeric” layout is called “Lithuanian”, the 1992 standard is inexplicably called “Lithuanian (IBM)” and the 2000 standard gets referred to as “Lithuanian Standard”. Linux distributions vary, but they generally provide the same options, copying whatever Microsoft may have done before. Apple, on the other hand, provides only one “Lithuanian” layout, which is an Apple-warped version of the “numeric” layout.
OS/2 had a rather unique implementation (essentially the same as the English (USA) layout, upon which the Lithuanian letters with diacritics were added to an entirely separate "language" layer for the corresponding keys, as dictated by the 1992 layout). Its chart id is 456, which strongly suggests that it indeed corresponded to the IBM’s specification of the 1992 standard, one that was later rescinded in favor of the specification for the 2000 standard.
Microsoft’s implementation of the “numeric” layout solves its omissions by adding the numbers and the missing typographical symbols to the respective keys in the tertiary (AltGr) and quaternary (AltGr‑Shift) layers, in the same respective order as in the English (USA) layout; it can not be overstated how incredibly impractical this is for regular usage.
The euro sign is also added, in AltGr‑E.
The 2000 standard has some further peculiarities to comment on:
The 2000 standard layout is, certainly, good enough for the Lithuanian language, but it does look somewhat weird; its absolute lack of dead keys is surprising, considering how heavily does Lithuanian use diacritics, and its rather particular placement of common typographical symbols makes it difficult for foreigners to use. If the demand for a “real QWERTY” keyboard layout came, one could be crafted without too much trouble, by placing the letter Ė in the D10 key and adding dead keys for the ogonek and the caron in the C10 and C11 keys, respectively; a few further adjustments would be needed so the layout would be closer in its general arrangements to what’s common in the neighboring European layouts (the keys ,;, .: and -_ in B08, B09 and B10, for example).
Sources and non-sources:
See also:
Notes:
The initial layout that IBM compiled was given the ID 141; it was superseded in 1991 by an improved layout (ID 142), which modified the assignments of a few typographical symbols under the tertiary (AltGr) and quaternary (AltGr‑Shift) layers, and added the previously missing backquote (`) and tilde (~) characters.
Despite the aforementioned improvements, the older layout is the one actually used in Italy, while the newer, better one remains almost unknown. History is lacking in this, but it seems that the 142 layout was engulfed in the disaster that sank OS/2, and vendors never bothered to update their offerings... despite Microsoft itself actually adding support for the newer layout not that much later; to this day, Microsoft lists the older layout (141) as the main Italian layout and offers the new one (142) as an alternative.
Several implementations, including Microsoft’s, assign the character € (U+20AC, EURO SIGN) to AltGr‑5 in addition to AltGr‑E.
This is one of the few layouts that require the modifier keys to have legends in its own language instead of allowing them to remain in English («Fine» for “End”, «Invio» for “Enter”, etcetera).
Sources and non-sources:
See also:
Notes:
Official in Brazil.
The ABNT NBR 10346:1991 standard mandates one extra key in row 4, between the ;: key (placed where the /? key is in an English (USA) keyboard) and RSHIFT; indeed, plenty of keyboards with this extra key do exist. Some implementations, Microsoft’s included, provide a workaround for keyboards that lack it by making extra assignments under the tertiary (AltGr) layer for the three symbols (slash, question mark and degree sign) that would otherwise be inaccessible.
Sources and non-sources:
See also:
Notes:
Official in Portugal. Its degree of usage in other Portuguese-speaking countries (besides Brazil) is unknown.
Several implementations, including Microsoft’s, assign the character € (U+20AC, EURO SIGN) to AltGr‑5 in addition to AltGr‑E.
Sources and non-sources:
See also:
Notes:
Official in all(*) the Spanish-speaking countries in the American continent... although this officiality is probably not much more than some IBM employee in an Armonk office declaring so back in the day, something that no one has ever bothered to question ever since.
(*) IBM’s specification lists explicitly every Spanish-speaking country in the American continent, Puerto Rico included... with the surprisingly surprising omission of Cuba; why something like this might have happened in a large, resourceful, known for its high quality work, company headquartered in the United States of America... may be one of those confusing mysteries that is never, ever satisfyingly explained. Or not. Whatever.
The “Latin America” moniker is a serious misnomer: support for Portuguese (and French, for that matter) is worryingly incomplete — the characters Ç (U+00C7, LATIN CAPITAL LETTER C WITH CEDILLA) and ç (U+00E7, LATIN SMALL LETTER C WITH CEDILLA) are nowhere to be seen, while the extra diacritics are present but look like they were tacked on for occasional usage only. It doesn’t help matters that the IBM specification itself states “Spanish speaking Latin America” in its description!
The IBM specification declares ~ (U+007E, TILDE) to be a dead key, but all known implementations make it into a regular key instead, further degrading Portuguese support.
This is one of the few layouts that require the modifier keys to have legends in its own language instead of allowing them to remain in English («Bloq Mayús» for “Caps Lock”, «Intro» for “Enter”, etcetera).
Sources and non-sources:
See also:
Notes:
Official in Spain; also sees varying degrees of usage in other Spanish-speaking countries.
The letter C with cedilla (Ç/ç) was added for the benefit of the Catalan language (acting as a replacement for the proper ce trencada). For the longest time, this layout completely lacked the tilde (~) character (!!!), either as a regular or as a dead key, making this layout nigh-useless for writing in Portuguese and for computer programming and administration; it was finally added recently, as a dead key under AltGr‑4.
Tilde absence or not, the Spanish (Spain) layout is generally considered to not be as well suited for usage in programming as the Spanish (Latin America) layout is, which may be a good part of the reason the latter has managed to avoid abandonment.
This is one of the few layouts that require the modifier keys to have legends in its own language instead of allowing them to remain in English («Supr» for “Del”, «Av Pág» for “Page Down”, etcetera).
Several implementations, including Microsoft’s, assign the character € (U+20AC, EURO SIGN) to AltGr‑5 in addition to AltGr‑E.
Sources and non-sources:
See also:
Notes:
Guarani is a language mainly spoken in Paraguay, where it’s official along with Spanish; it also has presence in parts of Brazil, Argentina and Bolivia.
This layout is a superset of the Spanish (Latin America) layout (with an exception — see below) that adds incomplete support for the Guarani language.
This layout was actually created by Microsoft, with the name “Guarani”. It’s listed here instead as “Spanish-Guarani”, because it’s still a layout made for Spanish, and to which support for Guarani has been added later, instead of being a layout designed from the ground up with the primary objective of supporting Guarani, or even of supporting both languages with equal weight.
This layout adds tertiary (AltGr) and quaternary (AltGr‑Shift) layer assignments for the tilded letters that Guarani uses: Ã/ã, Ẽ/ẽ, Ĩ/ĩ, G̃/g̃, Õ/õ, Ũ/ũ and Ỹ/ỹ (G̃/g̃ was actually forgotten in the initial version of this layout, released in Windows 8.1; this omission was corrected when Windows 10 came out), and pointlessly turns the tilde symbol (in AltGr‑+) into a dead key (it can only produce the six vowels that already have direct assignments in the tertiary and quaternary layers).
This layout was created relatively recently, and was revised at least once... yet it still lacks the letter puso or saltillo (Ꞌ/ꞌ) for no good reason. While we’re at this, it would have been pretty neat to have also added the letter C with cedilla (Ç/ç), turn back the tilde symbol into a regular key assignment, and perhaps even add the euro sign (€).
It’s unknown whether this layout has been adopted as official in Paraguay, or if it even sees a significant degree of usage.
Sources and non-sources:
See also:
Notes:
Maltese is a Semitic language, with no relation to English other than loanwords; however, the Maltese national layout is evidently derived from the English (UK) layout.
The Maltese national layout is governed by the standard MSA 100:2002, still in vigour. Uniquely, this document defines a main layout, designed for ISO keyboards, and an alternative one, designed for ANSI keyboards (and more in line with the English (USA) layout); as would be expected, the former sees much more usage than the latter.
This is the only known layout that places the character € (U+20AC, EURO SIGN) in the secondary (Shift) layer instead of the tertiary (AltGr) layer.
In both its implementations, Microsoft fails to include the characters © (U+00A9, COPYRIGHT SIGN), ® (U+00AE, REGISTERED SIGN) and ™ (U+2122, TRADE MARK SIGN). The 47-key layout implementation also inexplicably omits the character # (U+0023, NUMBER SIGN), retaining the pound sign in its place (on the other hand, it places the character ~ (U+007E, TILDE) under AltGr‑Ċ instead of keeping the negation sign, which is undoubtedly better).
Sources and non-sources:
See also:
Notes:
Official in France; used in several other French-speaking countries with differing degrees of officiality.
Generally regarded as a deficient layout; While the reordering of the letters A, M, Q, W and Z (done intentionally in the first French typewriters, as a variation on the QWERTY layout, and kept ever since) and the placement of numbers in the secondary (Shift) layer are its most obvious changes, those are actually the least of its problems: the seemingly chaotic arrangement of most symbols make it difficult to type comfortably, and the clashing placement of accented letters make it almost impossible to write correctly in the language it was designed for. Even the French Ministère de la Culture acknowledged as much in 2016.
Of all extant national layouts, this is the one that has been subjected to more replacement projects; it has survived so far because of inertia and a dose of misdirected chauvinistic pride.
The character in the rightmost alphanumeric key of row 3 is µ (U+00B5, MICRO SIGN) and not μ (U+03BC, GREEK SMALL LETTER MU) (albeit the symbol is evidently derived from the letter).
French keyboards are commonly seen with the modifier keys sporting legends in the same language instead of in English («Échap» for “Esc”, «Entrée» for “Enter”, etcetera; sometimes even with «Alt Car» for “AltGr”); surprisingly, this is not mandated by a standard, as is the case with the German, Italian, Lithuanian, Spanish (Spain) and Spanish (Latin America) layouts.
In old French keyboards formerly sold in Morocco, Algeria and Tunisia, the characters % (U+0025, PERCENT SIGN) and * (U+002A, ASTERISK), printed in the rightmost alphanumeric keys in row 3, were replaced by ٪ (U+066A, ARABIC PERCENT SIGN) and ٭ (U+066D, ARABIC FIVE POINTED STAR). This was solely a visual distinction, and has been completely abandoned.
Sources and non-sources:
See also:
Notes:
Used in Belgium and Luxembourg. Created as a variation of the original French (France) layout.
The character in the rightmost alphanumeric key of row 3 is µ (U+00B5, MICRO SIGN) and not μ (U+03BC, GREEK SMALL LETTER MU) (albeit the symbol is evidently derived from the letter).
The -_ key is displaced one position to the right with respect to the English (USA) keyboard, but remains in row 1.
Sources and non-sources:
See also:
Notes:
Official in Albania.
Most of the layouts in this section, including this one, are clearly derived from a single root, which in turn was based on the German layout; this can be seen in the features they all share:
This layout contains further influence from the English (UK) layout, as is evident from the placement of most of the basic typographical symbols.
Microsoft’s implementation contains three serious bugs that have never been corrected:
Sources and non-sources:
See also:
Notes:
Official in Czechia.
Most of the layouts in this section, including this one, are clearly derived from a single root, which in turn was based on the German layout; this can be seen in the features they all share:
The Slovak layout is extremely similar to this one; it’s rather obvious, from the content of both, and from the ID numbers IBM assigned to them (243 and 245), that this layout was developed first, and a few adjustments were made immediately afterwards to create the Slovak layout.
This layout takes a misguided cue from the French layouts and moves the digits to the secondary (Shift) layer in the number row; the space left behind is filled with letters with diacritics, albeit only in their lowercase forms; two more letters with diacritics take primary (base) layer assignments in the same fashion in the second and third rows.
The heavy use of dedicated keys for accented letters comes off as detrimental, as too many important characters are pushed to the tertiary (AltGr) layer. The clashes between accented letters and numbers or symbols, which force the usage of convoluted mechanisms to allow typing the uppercase forms of said letters, further deepens the problem.
As if the above wasn’t bad enough, dead keys for four diacritics have duplicated assignments in the primary (base) and secondary (Shift) layers: the acute accent and the diaeresis in the former, the caron and the ring in the latter. Forgetting for a moment that they are already present in the tertiary (AltGr) layer of the number row, the first and third are absolutely needed, as otherwise this layout would not be able to produce the letters Ď/ď, Ň/ň, Ó/ó and Ť/ť, all of them used in Czech; the fourth one isn’t really needed to obtain ů (but kind of is for Ů); the diaeresis isn’t used in Czech... but is so in Slovak and in a certain other neighboring language.
The acute and caron diacritics are frequently used when writing in Czech, so their respective dead keys are pretty important... yet they are located in the farthest key (E12), with the latter not even in the primary (base) layer — it’s actually easier to type the diaeresis dead key.
Seeing all of this, the inescapable conclusion is that this is a deficient, poorly designed layout. It would not be difficult to fix this mess, though! This would be how:
Microsoft’s implementation has major differences with respect to the official specification. Some of the changes are good, some... are definitely not so.
Microsoft offers two alternative implementations, both of which are quite poorly executed.
Sources and non-sources:
See also:
Notes:
Official in Hungary.
Most of the layouts in this section, including this one, are clearly derived from a single root, which in turn was based on the German layout; this can be seen in the features they all share:
The heavy use of dedicated keys for accented vowels comes off as detrimental, as too many important characters are pushed to the tertiary (AltGr) layer. It would have been much better to place the dead keys for the acute, diaeresis and double acute accents in the primary (base) layer in, respectively, the C10, C11 and D11 keys, and fill all the freed-up space with frequently used typographical symbols.
Microsoft’s implementation includes additional direct assignments for Ä/ä and Í/í under, respectively, AltGr‑E/AltGr‑A [sic] and AltGr‑I/AltGr‑J.
One of the historical annoyances of the original QWERTY layout is the poor placement of the 0 digit (to the right of 9 instead of the left of 1), but this has proven to have more inertia power than everything else in the entire arrangement — not even the most aggressively different alternative layouts dare changing the placement of the digits 1..0.
But the Hungarians went there. Sadly, they didn’t go far enough and instead of shifting the digits 1..9 one key to the right and place 0 where 1 used to be, they put it in the corner key, which constitutes a problem of its own class.
But wait, it gets worse! The Hungarian layout was evidently designed with ISO keyboards in mind; Microsoft provides an alternative layout for the benefit of ANSI keyboards, where the Í/í letter is moved from the primary (base) and secondary (Shift) layers of the now missing extra key to (Get ready for this!) the same places in the corner key; 0 is shoved to the tertiary (AltGr) layer under the same key and the section sign (§) is moved to AltGr‑R.
Let’s repeat that: the digit 0 is in the tertiary (AltGr) layer, as the AltGr‑Í combination. Oh, by the way, just like in the main implementation, that letter is also available under AltGr‑I and AltGr‑J. WHAT THE HELL?!
This alternative layout also swaps back Y and Z, removes some dead keys and turns the rest into regular keys that produce the non-combining versions of each diacritic... but all of that is rather minuscule, compared to the fact that the digit 0 is in the tertiary (AltGr) layer. What WERE they smoking?
Both Microsoft’s implementations contain a serious bug that has never been corrected: the ring above diacritic (◌̊) is conflated with the degree sign (°) for no good reason.
Sources and non-sources:
See also:
Notes:
Official in Poland, at least on paper; IBM’s documentation from the recent past mentions this layout being required for government contracts, and presumably this has not changed. Despite this, the Polish (programmers) layout is undisputedly the de facto standard, although the ease with which new keyboards with the Polish (standard) layout can be bought suggests it still sees a significant degree of usage.
Most of the layouts in this section, including this one, are clearly derived from a single root, which in turn was based on the German layout; this can be seen in the features they all share:
Note the duplicated entries for two of the diacritics that are used in Polish.
IBM’s internal identification number for this layout is 214, a number that has been used as its moniker in quite a lot of contexts, despite “standard” being the proper term when making a distinction between it and other keyboard layouts for the Polish language.
Microsoft’s implementation contains several serious bugs that have never been corrected:
Sources and non-sources:
See also:
Notes:
De facto official layout in Poland. Proof of its ubiquitousness is that Microsoft implemented this layout, with the name “Polish”, since at least the days of Windows NT 3.1; it was renamed to “Polish (programmers)” when the company finally added the Polish (standard) layout (with the name “Polish (214)”).
As a counterpoint to the above, OS/2 (since at least the initial release of OS/2 Warp) contained both Polish layouts, without forgetting to include the brackets and the vertical bar!
IBM’s internal identification number for this layout is 457, a number that has been used as its moniker in a few contexts, despite “programmers” being the preferred term when making a distinction between it and other keyboard layouts for the Polish language.
This layout is a straight-up extended version of the English (USA) layout, PC style, to which the specific needs of the Polish language, plus the euro symbol, have been added to the tertiary (AltGr) and quaternary (AltGr‑Shift) layers. All character assignments in the Polish (standard) layout that are neither present in the English (USA) layout nor required by the Polish language have been dropped.
Microsoft’s earlier implementations followed this specification without issue. However, recent implementations turn the tilde (~) into a pointless dead key that agglomerates all the Polish letters with diacritics (ogonek, stroke, acute accent and dot above), to the chagrin of the programmers who do use the tilde character as a... tilde character. Has the company forgotten the name of this layout?
Sources and non-sources:
See also:
Notes:
This used to be the official keyboard layout in Romania; it should not be used anymore, as it’s been superseded by an improved standard (see the Romanian (current) national layouts); it’s listed here for completeness’ sake.
Older versions of several operating systems, preceding the new standard, listed this layout as “Romanian”; after the publication of said document, this layout is now referred to as “Romanian (legacy)” or some other similar term, while the new one is called “Romanian” or “Romanian (standard)”.
Most of the layouts in this section, including this one, are clearly derived from a single root, which in turn was based on the German layout; this can be seen in the features they all share:
Sources for this layout are conflicting: IBM’s implementation differs quite a bit from what the specification ought to look like, and it strongly seems the available document from the company refers to a heavily revised version of the layout, created for OS/2. On the other hand, Microsoft’s implementation, quirks and all, looks much closer to what the actual specification should be. Because of this, and unusually for this document, Microsoft’s implementation is the preferred reference (until, if ever, the formal specification document shows up).
The above said, both implementations surely follow the original specification regarding what to do about the letters S and T with a comma diacritic (Ș/ș and Ț/ț), and instead use the precomposed characters with cedillas: Ş/ş and Ţ/ţ (marked in purple in the above graphic). Correcting this rather insulting misrepresentation was probably one of the factors driving the adoption of a new standard, after the Unicode Consortium got off its ass and disunified the cedilla and comma diacritics (a conflation that should have never occurred in the first place).
Microsoft’s implementation contains two serious bugs that have never been corrected (not that it matters anymore, as this layout should not be used): the ring above diacritic (◌̊) is conflated with the degree sign (°) for no good reason, and the dot above diacritic (◌̇) is conflated with the middle dot (·).
Sources and non-sources:
See also:
Notes:
Official in Romania (and surely in Moldova as well).
The Romanian National Standard SR 13392:2004 actually defines two layouts, both evidently based on the English (USA) layout, PC style:
The “standard” layout imports the Central/Southeastern European and Romanian elements from the older Romanian layout (diacritic dead keys row, letters with diacritics, etc.), adds a few typographical symbols and the euro sign, and replaces the inappropriate letters with cedillas (Ş/ş and Ţ/ţ) with the proper versions with diacritic commas (Ș/ș and Ț/ț); the letters with diacritics used by the Romanian language are kept in the same key assignments in the primary (base) and secondary (Shift) layers.
The “programmers” layout is a straight-up extended version of the English (USA) layout, to which the same elements are all imported into the tertiary (AltGr) and quaternary (AltGr‑Shift) layers, with no changes whatsoever to the primary (base) and secondary (Shift) layers.
Both Microsoft’s implementations continue to contain the same bug as the older layout, that remains uncorrected: the ring above diacritic (◌̊) is conflated with the degree sign (°) for no good reason.
Sources and non-sources:
See also:
Notes:
Official in Slovakia.
Most of the layouts in this section, including this one, are clearly derived from a single root, which in turn was based on the German layout; this can be seen in the features they all share:
The Czech layout is extremely similar to this one; it’s rather obvious, from the content of both, and from the ID numbers IBM assigned to them (243 and 245), that the Czech layout was developed first, and a few adjustments were made to it immediately afterwards to create this one.
This layout takes a misguided cue from the French layouts and moves the digits to the secondary (Shift) layer in the number row; the space left behind is filled with letters with diacritics, albeit only in their lowercase forms; four more letters with diacritics take primary (base) layer assignments in the same fashion in the second and third rows.
The heavy use of dedicated keys for accented letters comes off as detrimental, as too many important characters are pushed to the tertiary (AltGr) layer. The clashes between accented letters and numbers or symbols, which force the usage of convoluted mechanisms to allow typing the uppercase forms of said letters, further deepens the problem.
A ripple efect of the above is that the apostrophe (') is moved to the tertiary (AltGr) layer, under AltGr‑9, which is the baseline regional assignment for the acute accent dead key... not that it matters too much, because it’s present, just like in the Czech layout, in the primary (base) layer of the E12 key; if it were absent, there would be no way to obtain the letters Ĺ/ĺ, Ó/ó and Ŕ/ŕ, all used in Slovak.
Compounding the needless complexity, there are duplicated dead keys for the caron and ring diacritics in the secondary (Shift) layer. Forgetting for a moment that they are already present in the tertiary (AltGr) layer of the number row, the caron dead key is needed to produce the letter Ď/ď, used in Slovak; the ring is needed to obtain Ů/ů... but that letter is used in Czech, not in Slovak.
The acute and caron diacritics are frequently used when writing in Slovak, so their respective dead keys are pretty important... yet they are located in the farthest key (E12), with the latter not even in the primary (base) layer.
Seeing all of this, the inescapable conclusion is that this is a deficient, poorly designed layout. It would not be difficult to fix this mess, though! This would be how:
Microsoft’s implementation has a few differences with respect to the official specification.
Unlike what the implementation of the Czech layout does, the Caps Lock trick for the letters with diacritics is not present here.
Microsoft offers an alternative implementation that swaps the Y and Z letters.
Sources and non-sources:
See also:
Notes:
The keyboard layout for the Serbo-Croatian language, as written in the Latin script, was standardized and codified by IBM back in the early-to-mid ’80s, when the country of Yugoslavia still existed, and during a time when support for Cyrillic scripts by Western companies was pretty scant. Because of these factors, this layout was named simply “Yugoslav” and marked as official for Yugoslavia.
After the wars that ended with the dissolution of Yugoslavia, each successor country kept using the same keyboard layout (again, as it pertains to the Latin script; Cyrillic had gotten its own layout at this point), but its name became a point of contention — “Yugoslav” was not appropriate anymore. Each major operating system handled the problem in its own inconsistent way:
Ultimately, one way or another, one name or another, all the countries that used to be part of Yugoslavia continue to use the same keyboard layout (once more, as it pertains to the Latin script); the names with which is generally known in the present are, from north to south, “Slovenian”, “Croatian” and “Serbian (Latin)”, which is why they have been listed that way in the title of this entry.
In 2009, Slovenia tried to make its own keyboard layout; it was an update to this one, where its main change was moving the letters Ć/ć and Đ/đ (unused in Slovenian) to the tertiary (AltGr) and quaternary (AltGr‑Shift) layers, with the euro (€) and at (@) signs taking the space left behind. It was formally published as the standard SIST 1044:2009 and promoted as such, but its adoption was nil and was quickly forgotten, to the point that seemingly only the Internet Archive (!) keeps a copy of the document.
Most of the layouts in this section, including this one, are clearly derived from a single root, which in turn was based on the German layout; this can be seen in the features they all share:
Note the duplicated entries for two of the diacritics... that are not used in any of the South Slavic languages (whoever originally designed the layout seems to have been pandering to Turkish, German and Albanian interests).
Microsoft’s implementations contain several bugs that have never been corrected:
Sources and non-sources:
See also:
Notes:
The Azeri (or Azerbaijani, or Azeri Turkic) language is spoken in Azerbaijan, where it’s official, and in neighboring areas within Iran, Russia and Georgia.
Azeri was written in the Persian script until 1929, when the USSR replaced it with a variation of the Latin alphabet, which was in turn replaced with the Cyrillic alphabet in 1938. After the (quite deserved) collapse and fall of the USSR, the newly independent Republic of Azerbaijan replaced the latter script with another variation of the Latin alphabet, still in use today (albeit subjected to several refinements over the years).
This layout is composed of the usual QWERTY assignments for the basic letters A to Z, with additional letters with diacritics placed to their right, where most typographical symbols are usually located. The most notable difference is the letter W, unused in Azeri, which this layout entirely discards in favor of Ü/ü.
Like the Turkish alphabet, the Latin-derived Azeri alphabet has two I vowels — dotted (İ/i) and dotless (I/ı); unlike the (several decades older) Turkish Q layout, the former retains the position of the I letter in the QWERTY layout, while the latter is placed on the home row.
Discounting the E00 key, which contains the backquote and tilde characters, the selection and arrangement of typographical symbols in the number row and the keys C12 and D10 coincide with what’s found in keyboard layouts based on the Cyrillic alphabet, as used in Russia and former USSR domains (Cyrillic-based layouts elsewhere, like the Balkan Peninsula, do differ in this regard).
This layout lacks many commonly used typographical symbols. At some point, Microsoft revised it to include the at sign (@) and the manat sign (₼) in the tertiary (AltGr) layer, in AltGr‑2 and AltGr‑4, respectively, but this was nowhere close to what was needed to make this layout truly usable... not to say anything _oeful about the _eird _ays _ith _hich the Azeris have to _ade around the absence of that _hacky letter those _easely _esterners continue to use _henever they _ant to.
It’s not known if this layout was actually official in Azerbaijan until 2013 (when the Azeri (standard) layout was introduced). Its degree of actual usage remains unknown as well.
This layout was created by Microsoft, not IBM; IBM’s specification explicitly defers to the implementation by the former company.
IBM’s specification contains a serious error: the character in Shift‑3 is listed as Ⅶ (U+2166, ROMAN NUMERAL SEVEN), although it’s evident that it should be № (U+2116, NUMERO SIGN) instead.
It’s not clear whether this national layout was designed with ANSI or ISO keyboards in mind; IBM’s specification lists it as an ANSI layout, while Microsoft’s implementation shows an ISANSI physical layout... but this may be an error in the diagram, as other documents by the same company show it on an ISO layout. In the diagram above, the latter has been used, due to the necessity of keeping some form of sanity, which will be quite necessary to review the Azeri (standard) layout.
Sources and non-sources:
See also:
Notes:
This layout was designed jointly by the Azeri government and Microsoft (Heaven help us!) and released in 2013, as the new official keyboard layout for the country.
This layout was designed to allow fast typing in Azeri and... seemingly nothing else. All of the letters have been rearranged according only to usage frequency (to the point that Ü and O are the only letters that retain the position they had in the Azeri (Latin) layout), while the numbers and typographical symbols remain almost entirely unaltered.
As described in the previous entry, Azeri is a Turkic language, mutually intelligible with Turkish to a high degree... yet this layout is quite different from the Turkish F layout. The high influence of both Persian and Russian in modern Azeri is part of the reason for this (as it will alter the usage frequency of all letters), but the main factor is that the design for the Turkish F layout took usage frequency as one important factor, but not the only one, as was done in this layout.
Worse yet, this layout is still missing far too many typographical symbols, an inexcusable omission in 2012-2013, the time period when it was concocted. The addition of the (Western) number sign (#) [Thanks, Twitter lobbyists?] is more than negated by the entirely gratuituous removal of the backquote (`), slash (/) and backslash (\) characters, even though the tertiary (AltGr) and quaternary (AltGr‑Shift) layers are almost entirely free.
Even worse, and bordering on the unbelievable, the letter W is still missing, even though two alpha keys are entirely unused! WHY?! I mean... _HY?! _hy _ould anyone in the _orld think this _as a _orkable idea? This does not make any sense at all — not even if, somehow, the entire country had BADBAE keyboards (so neither the B00 alpha key nor either of C12 and D13 were available to anyone) as, again, the tertiary (AltGr) and quaternary (AltGr‑Shift) layers are almost entirely free.
Ever since it was released, the viability and adoption of this layout has been cast into doubt. Even if its arrangement of letters were perfect for typing in Azeri (it probably is not, as described above), that won’t be enough to overcome QWERTY inertia, and the layout’s evident defficiencies will surely make users prefer something else.
Sources and non-sources:
See also:
Notes:
This layout is an adaptation from the original QWERTY layout, to serve the needs of the Turkish language; it contains obvious influences from the German layout.
The “Q” moniker is meant to distinguish this layout from the Turkish F layout, which also serves the needs of the Turkish language.
The Turkish alphabet has two I vowels — dotted (İ/i) and dotless (I/ı); the latter retains the position of the I letter in the QWERTY layout, while the former is placed on the home row.
The -_ key is displaced one position to the right with respect to the English (USA) keyboard, but remains in row 1.
The Turkish language does not use the acute accent at all — the presence of the é letter (in lowercase form only, to boot) looks like an addition to ease typing in French (something that would have made sense during the time period in which this layout was probably codified).
This layout has been revised twice, to add the euro (€) and Turkish lira (₺) currency signs.
The Turkish government has issued a replacement, the Turkish F layout, and mandates its usage in the public sector. Despite that, the Q layout (this one) still sees majority usage and is expected to continue to do so for the foreseeable future. As a matter of fact, Microsoft still marks this layout as the default for the Turkish language.
Sources and non-sources:
See also:
Notes:
This layout was designed in 1955, as a replacement for the QWERTY-based Turkish Q layout, with the intention of allowing fast typing in Turkish; it’s no surprise, then, that all the letters have been rearranged, and so have been about half of the typographical symbols (the diacritic dead keys have not been touched, however); the keycaps marked in green are those few that have been displaced within the same row and have not otherwise changed.
The Turkish government has codified this layout into a standard and promoted its usage, even making it mandatory in the public sector; however, the Turkish Q layout still sees majority usage and is expected to continue to do so for the foreseeable future.
Uniquely, the standard governing this layout specifies that the characters marked in green must be implemented in the software driver, but do not need to be printed on the keyboard itself.
Sources and non-sources:
See also:
Notes:
The Turkmen language is spoken in Turkmenistan, where it’s official, and in neighboring areas within Iran and Afghanistan, as well as Pakistan, Russia and Turkey.
In what is today Turkmenistan, Turkmen was written in the Arabic script until 1929, when the USSR replaced it with a variation of the Latin alphabet (similar to the one developed for the Azeri language), which was in turn replaced with the Cyrillic alphabet in 1940. After the (quite deserved) collapse and fall of the USSR, the newly independent Republic (okay, “republic”) of Turkmenistan replaced the latter script with another variation of the Latin alphabet, still in use today.
This layout was created by Microsoft and released in 2007; it was built by taking the English (USA) layout, PC style, and carelessly plastering on top the letters with diacritics specific to the Turkmen language. This mess of a layout omits entirely the four letters (C, Q, V and X) that aren’t used in the Turkmen alphabet... even though they are used in other Turkic languages, not to say anything of the rest of the languages that use the Latin alphabet; it also erases several typographical symbols (backquote, tilde, caret, brackets and braces), despite the tertiary (AltGr) layer remaining available... with the exception of the backslash and pipe symbols, displaced by the letter Ş, which have been moved to alternate arrangements, even though they are also present, untouched, in the extra alpha key. It’s, _ertainly, _ery naï_e to e_pe_t e__ellent results if draft layouts won’t be _uestioned or _etted before appro_al; _uality _raftmanship _an’t be _ui_kly o_erlooked with such e__ru_iating _arelessness.
The symbol № (U+2116, NUMERO SIGN) is the only addition to this layout that hails from Cyrillic keyboard layouts, where it’s generally located at Shift‑3; here, it’s been inexplicably moved to Shift‑6 [acquiescing to Twitter lobbyists can’t be the reason for having kept the (Western) number sign (#), as this layout was developed before that company got big; neither can it be Microsoft shilling C#, for in that case all the missing typographical symbols, needed for programming in that language, would still be present].
Sources and non-sources:
See also:
Last update: 29/09/2022.
Return to Keyboard-related resources.
All rights reserved by Miguel Farah.
