Minuri/sinhala-corpus-wikipedia huggingface dataset:
Adding digits in all caps styled texts may multiply these confusions, which is one aim of Leet (intentional pseudo duplicates) and can provide simple means of concealing messages (often numbers)
See also 

Caps lock
CamelCase
Letter case
Roman square capitals
Shift key
Small caps
Unicase
Uncial script

Notes
Thompson developed in 1958 a font called Alphabet 26 or a "monoalphabet," an alphabet whose uppercase and lowercase forms of each letter were identical, and case was expressed through letter size only
(In the conventional Latin alphabet, it is already the case for letters like "o" and "O" or "s" and "S" but not for a/A, r/R, etc
) His monoalphabet was a transitional serif (modelled after Baskerville) with lowercase a, e, m, and n mixed with uppercase B, D, F, G, H, I, J, K, L, P, Q, R, T, U, and Y
(The forms of C/c, O/o, S/s, V/v, W/w, X/x and Z/z are essentially the same in uppercase and lowercase letters to begin with)
The simplification was intended to make the letters of the alphabet more logical and intuitive, making the alphabet easier to learn and use
Thompson first published the alphabet in a Westvaco Inspirations for Printers
The set of letters for Alphabet 26 thus appears
a B c D e F G H I J K L m n o P Q R s T U v w x Y z

The above example uses the CSS rule font-variant-caps
unicase, which is not supported by many browsers as of July 2017.  A closer approximation that works in most current browsers (but suffers from slight variations in weight & height) is the following
a b c d e f g h i j k l m n o p q r s t u v w x y z

Example
BRaDBURY THomPson DesIGneD aLPHaBeT 26.  (Alternate approximation
Bradbury Thompson designed alphabet 26.)
Camel case (stylized as camelCase or CamelCase
also known as camel caps or more formally as medial capitals) is the practice of writing compound words or phrases such that each word or abbreviation in the middle of the phrase begins with a capital letter, with no intervening spaces or punctuation
Common examples include "iPhone ", "eBay", "FedEx", "DreamWorks", "HarperCollins", "iCarly", "WordWorld", and "WordGirl"
It is also sometimes used in online usernames such as "JohnSmith", and to make multi-word domain names more legible, for example in advertisements
Some systems prefer camelcase with the first letter capitalised, others not
For clarity, this article calls the two alternatives upper camel case (initial upper case letter, also known as Pascal case) and lower camel case (initial lower case letter)
Some people and organizations, notably Microsoft, use the term camel case only for lower camel case
Pascal case means only upper camel case
Camel case is distinct from Title Case, which capitalises all words but retains the spaces between them, and from Tall Man lettering, which uses capitals to emphasize the differences between similar-looking words such as "predniSONE" and "predniSOLONE
The name "CamelCase" is not related to the "Camel Book", the popular nickname of the book Programming Perl due to the picture of a camel on its cover, which uses all-lowercase identifiers with underscores (sometimes called snake case) in its sample code
Variations and synonyms 

The original name of the practice, used in media studies, grammars and the Oxford English Dictionary, was "medial capitals"
Other names such as "InterCaps" or "CamelCase" are relatively recent and more common in computer-related communities
Other synonyms include
BumpyCaps
 NerdCaps 
 camelBack (or camel-back) notation or CamelCaps
 CapitalizedWords or CapWords for upper camel case in Python 
 compoundNames
 Embedded Caps (or Embedded Capitals)
 HumpBack (or hump-back) notation

 InterCaps or intercapping (abbreviation of Internal Capitalization)
 mixedCase for lower camel case in Python
 PascalCase for upper camel case (after the Pascal programming language)
 Smalltalk case
 Turtle case
 WikiWord or WikiCase (especially in older wikis)
 StudlyCaps includes even randomly mixed capitalization, as in MiXeD CaPitALiZaTioN (typically a stereotyped allusion to online culture), and thus encompasses both styles of camel case
The earliest known occurrence of the term "InterCaps" on Usenet is in an April 1990 post to the group alt
computers by Avi Rappoport
The earliest use of the name "CamelCase" occurs in 1995, in a post by Newton Love
Love has since said, "With the advent of programming languages having these sorts of constructs, the humpiness of the style made me call it HumpyCase at first, before I settled on CamelCase
I had been calling it CamelCase for years
The citation above was just the first time I had used the name on USENET
"

Traditional use in natural language

In word combinations
The use of medial capitals as a convention in the regular spelling of everyday texts is rare, but is used in some languages as a solution to particular problems which arise when two words or segments are combined
In Italian, pronouns can be suffixed to verbs, and because the honorific form of second-person pronouns is capitalized, this can produce a sentence like non ho trovato il tempo di risponderLe ("I haven't found time to answer you" - where Le means "you")
In German, the medial capital letter I, called Binnen-I, is sometimes used in a word like StudentInnen ("students") to indicate that both Studenten ("male students") and Studentinnen ("female students") are intended simultaneously
However, mid-word capitalisation does not conform to German orthography
the previous example could be correctly written using parentheses as Student(inn)en, analogous to "congress(wo)man" in English
In Irish, camelcase is used when an inflectional prefix is attached to a proper noun, for example  ("in Galway"), from  ("Galway")
("the Scottish person"), from  ("Scottish person")
and  ("to Ireland"), from  ("Ireland")
In recent Scots Gaelic orthography, a hyphen has been inserted
This convention is also used by several written Bantu languages (e
, kiSwahili, "Swahili language"
isiZulu, "Zulu language") and several indigenous languages of Mexico (e
Nahuatl, Totonacan, Mixe–Zoque, and some Oto-Manguean languages)
In Dutch the letter J is capitalized if it is immediately preceded by a capital I, for example in the countryname IJsland
In English, medial capitals are usually only found in Scottish or Irish "Mac-" or "Mc-" names, where for example MacDonald, McDonald, and Macdonald are common spelling variants of the same name, and in Anglo-Norman "Fitz-" names, where for example both FitzGerald and Fitzgerald are found
In their English style guide The King's English, first published in 1906, H
and F
Fowler suggested that medial capitals could be used in triple compound words where hyphens would cause ambiguity—the examples they give are KingMark-like (as against King Mark-like) and Anglo-SouthAmerican (as against Anglo-South American)
However, they described the system as "too hopelessly contrary to use at present
"

In transliterations

In the scholarly transliteration of languages written in other scripts, medial capitals are used in similar situations
For example, in transliterated Hebrew, haIvri means "the Hebrew person" and biYerushalayim means "in Jerusalem"
In Tibetan proper names like rLobsang, the "r" stands for a prefix glyph in the original script that functions as tone marker rather than a normal letter
Another example is tsIurku, a Latin transcription of the Chechen term for the capping stone of the characteristic Medieval defensive towers of Chechenia and Ingushetia
the capital letter "I" here denoting a phoneme distinct from the one transcribed as "i"
In abbreviations 
Medial capitals are traditionally used in abbreviations to reflect the capitalization that the words would have when written out in full, for example in the academic titles PhD or BSc
In German, the names to statutes are abbreviated using embedded capitals, e
StGB (Strafgesetzbuch) for Criminal Code, PatG (Patentgesetz) for Patent Act, BVerfG (Bundesverfassungsgericht) for Federal Constitutional Court, or the very common GmbH (Gesellschaft mit beschrnkter Haftung) for Company with Limited Liability
In this context, there can even be three or more "CamelCase" capitals, e
in TzBfG for Teilzeit- und Befristungsgesetz (Act on Part-Time and Limited Term Occupations)
In French, camel case acronyms such as OuLiPo (1960) were favored for a time as alternatives to initialisms
Camel case is often used to transliterate initialisms into alphabets where two letters may be required to represent a single character of the original alphabet, e
, DShK from Cyrillic ДШК
History of modern technical use

Chemical formulae 
The first systematic and widespread use of medial capitals for technical purposes was the notation for chemical formulae invented by the Swedish chemist Jacob Berzelius in 1813. To replace the multitude of naming and symbol conventions used by chemists until that time, he proposed to indicate each chemical element by a symbol of one or two letters, the first one being capitalized
The capitalization allowed formulae like "NaCl" to be written without spaces and still be parsed without ambiguity
Berzelius' system continues to be used, augmented with three-letter symbols such as "Uue" for unconfirmed or unknown elements and abbreviations for some common substituents (especially in the field of organic chemistry, for instance "Et" for "ethyl-")
This has been further extended to describe the amino acid sequences of proteins and other similar domains
Early use in trademarks 
Since the early 20th century, medial capitals have occasionally been used for corporate names and product trademarks, such as
 DryIce Corporation (1925) marketed the solid form of carbon dioxide (CO2) as "Dry Ice", thus leading to its common name
CinemaScope and VistaVision, rival widescreen movie formats (1953)
 ShopKo (1962)
 MisteRogers, the Canadian version of Mister Rogers' Neighborhood (1962)
 AstroTurf (1967)
 ConAgra, formerly Consolidated Mills (1971)
Computer programming 

In the 1970s and 1980s, medial capitals were adopted as a standard or alternative naming convention for multi-word identifiers in several programming languages
The precise origin of the convention in computer programming has not yet been settled
A 1954 conference proceedings occasionally informally referred to IBM's Speedcoding system as "SpeedCo"
Christopher Strachey's paper on GPM (1965), shows a program that includes some medial capital identifiers, including "NextCh" and "WriteSymbol"
Multiple-word descriptive identifiers with embedded spaces such as end of file or char table cannot be used in most programming languages because the spaces between the words would be parsed as delimiters between tokens
The alternative of running the words together as in endoffile or chartable is difficult to understand and possibly misleading
for example, chartable is an English word (able to be charted)
Some early programming languages, notably Lisp (1958) and COBOL (1959), addressed this problem by allowing a hyphen ("-") to be used between words of compound identifiers, as in "END-OF-FILE"
Lisp because it worked well with prefix notation (a Lisp parser would not treat a hyphen in the middle of a symbol as a subtraction operator) and COBOL because its operators were individual English words
This convention remains in use in these languages, and is also common in program names entered on a command line, as in Unix
However, this solution was not adequate for mathematically-oriented languages such as FORTRAN (1955) and ALGOL (1958), which used the hyphen as an infix subtraction operator
These early languages instead allowed identifiers to contain unrestricted embedded spaces, determining the end of the identifier by context
This approach was abandoned in later languages due to the complexity it adds to tokenization
(FORTRAN initially restricted identifiers to no more than six characters, effectively preventing multi-word identifiers except those made of very short words, such as "GO TO"="GOTO"
)

Exacerbating the problem, common punched card character sets of the time were uppercase only and lacked other special characters
It was only in the late 1960s that the widespread adoption of the ASCII character set made both lower case and the underscore character _ universally available
Some languages, notably C, promptly adopted underscores as word separators, and identifiers such as end_of_file are still prevalent in C programs and libraries (as well as in later languages influenced by C, such as Perl and Python)
However, some languages and programmers chose to avoid underscores—among other reasons to prevent confusing them with whitespace—and adopted camel case instead
Charles Simonyi, who worked at Xerox PARC in the 1970s and later oversaw the creation of Microsoft's Office suite of applications, invented and taught the use of Hungarian Notation, one version of which uses the lower case letter(s) at the start of a (capitalized) variable name to denote its type
One account claims that the camel case style first became popular at Xerox PARC around 1978, with the Mesa programming language developed for the Xerox Alto computer
This machine lacked an underscore key, and the hyphen and space characters were not permitted in identifiers, leaving camel case as the only viable scheme for readable multiword names
The PARC Mesa Language Manual (1979) included a coding standard with specific rules for upper and lower camel case that was strictly followed by the Mesa libraries and the Alto operating system
The Smalltalk language, which was developed originally on the Alto and became quite popular in the early 1980s, may have been instrumental in spreading the style outside PARC
Camel case was also used by convention for many names in the PostScript page description language (invented by Adobe Systems founder and ex-PARC scientist John Warnock), as well as for the language itself
In addition, Niklaus Wirth, the inventor of Pascal, came to appreciate camel case during a sabbatical at PARC and used it in Modula, his next programming language
Spread to mainstream usage 
Whatever its origins within the computing world, the practice spread in the 1980s and 1990s, when the advent of the personal computer exposed hacker culture to the world
Camel case then became fashionable for corporate trade names, initially in technical fields
mainstream usage was well established by 1990
(1962) PolyGram, formerly one of the major labels of the music industry
(1971) AeroVironment
 (1976) InterCity 125
 (1977) CompuServe, UnitedHealthCare (now UnitedHealthcare)
(1978) WordStar
 (1979) MasterCard, SportsCenter, VisiCalc
 (1980) EchoStar
 (1982) MicroProse, WordPerfect
 (1983) NetWare
 (1984) BellSouth, LaserJet, MacWorks, iDEN
 (1985) PageMaker, EastEnders
 (1986) SpaceCamp
 (1987) ClarisWorks, HyperCard, PowerPoint
 (1990) HarperCollins, SeaTac, iconic WorldWideWeb

During the dot-com bubble of the late 1990s, the lowercase prefixes "e" (for "electronic") and "i" (for "Internet", "information", "intelligent", etc
) became quite common, giving rise to names like Apple's iMac and the eBox software platform
In 1998, Dave Yost suggested that chemists use medial capitals to aid readability of long chemical names, e
write AmidoPhosphoRibosylTransferase instead of amidophosphoribosyltransferase
This usage was not widely adopted
Camelcase is sometimes used for abbreviated names of certain neighborhoods, e
New York City neighborhoods SoHo (South of Houston Street) and TriBeCa (Triangle Below Canal Street) and San Francisco's SoMa (South of Market)
Such usages erode quickly, so the neighborhoods are now typically rendered as Soho, Tribeca, and Soma
Internal capitalization has also been used for other technical codes like HeLa (1983)
Current usage in computing

Programming and coding 

The use of medial caps for compound identifiers is recommended by the coding style guidelines of many organizations or software projects
For some languages (such as Mesa, Pascal, Modula, Java and Microsoft's
NET) this practice is recommended by the language developers or by authoritative manuals and has therefore become part of the language's "culture"
Style guidelines often distinguish between upper and lower camel case, typically specifying which variety should be used for specific kinds of entities
variables, record fields, methods, procedures, types, etc
These rules are sometimes supported by static analysis tools that check source code for adherence
The original Hungarian notation for programming, for example, specifies that a lowercase abbreviation for the "usage type" (not data type) should prefix all variable names, with the remainder of the name in upper camel case
as such it is a form of lower camel case
Programming identifiers often need to contain acronyms and initialisms that are already in upper case, such as "old HTML file"
By analogy with the title case rules, the natural camel case rendering would have the abbreviation all in upper case, namely "oldHTMLFile"
However, this approach is problematic when two acronyms occur together (e
, "parse DBM XML" would become "parseDBMXML") or when the standard mandates lower camel case but the name begins with an abbreviation (e
"SQL server" would become "sQLServer")
For this reason, some programmers prefer to treat abbreviations as if they were lower case words and write "oldHtmlFile", "parseDbmXml" or "sqlServer"
However, this can make it harder to recognise that a given word is intended as an acronym
Wiki link markup 
Camel case is used in some wiki markup languages for terms that should be automatically linked to other wiki pages
This convention was originally used in Ward Cunningham's original wiki software, WikiWikiWeb, and can be activated in most other wikis
Some wiki engines such as TiddlyWiki, Trac and PmWiki make use of it in the default settings, but usually also provide a configuration mechanism or plugin to disable it
Wikipedia formerly used camel case linking as well, but switched to explicit link markup using square brackets and many other wiki sites have done the same
Some wikis that do not use camel case linking may still use the camel case as a naming convention, such as AboutUs
Other uses 
The NIEM registry requires that XML data elements use upper camel case and XML attributes use lower camel case
Most popular command-line interfaces and scripting languages cannot easily handle file names that contain embedded spaces (usually requiring the name to be put in quotes)
Therefore, users of those systems often resort to camel case (or underscores, hyphens and other "safe" characters) for compound file names like MyJobResume
Microblogging and social networking sites that limit the number of characters in a message (most famously Twitter, where the 140-character limit can be quite restrictive in languages that rely on alphabets, including English) are potential outlets for medial capitals
Using camel case between words reduces the number of spaces, and thus the number of characters, in a given message, allowing more content to fit into the limited space
Hashtags, especially long ones, often use camel case to maintain readability (e
#CollegeStudentProblems is easier to read than #collegestudentproblems)
In website URLs, spaces are percent-encoded as "%20", making the address longer and less human readable
By omitting spaces, camel case does not have this problem
Readability studies 
Camel case has been criticised as negatively impacting readability due to the removal of spaces and uppercasing of every word
A 2009 study comparing snake case to camel case found that camel case identifiers could be recognised with higher accuracy among both programmers and non-programmers, and that programmers already trained in camel case were able to recognise those identifiers faster than underscored snake-case identifiers
A 2010 follow-up study, under the same conditions but using an improved measurement method with use of eye-tracking equipment, indicates
"While results indicate no difference in accuracy between the two styles, subjects recognize identifiers in the underscore style more quickly
"

See also 
All caps
Capitalization
Caps lock
Shift key
Small caps
Unicase

References

External links 

 Examples and history of CamelCase, also WordsSmashedTogetherLikeSo
NET Framework General Reference Capitalization Styles
 What's in a nAME(cq)
, by Bill Walsh, at The Slot
 The Science of Word Recognition, by Kevin Larson, Advanced Reading Technology, Microsoft Corporation
 Convert text to CamelCase
 OASIS Cover Pages
CamelCase for Naming XML-Related Components
 Convert text to CamelCase, Title Case, Uppercase and lowercase
ContextObjects in Spans, commonly abbreviated COinS, is a method of embedding latent OpenURL ContextObjects in web pages
This allows client software to retrieve bibliographic metadata and to use an OpenURL resolver to find a mediated link
A principal advantage of using COinS, rather than giving a static OpenURL, is that the client can determine which resolver to use
This allows, for instance, searching for a copy of a book in one's own library
COinS have been added to various parts of Wikipedia
They are basically just a chunk of bibliographic information stored in a way that machines can read
This has two applications
The information can be converted into a full OpenURL and resolved by a local OpenURL resolver
For instance, with LibX, OpenURL referrer, or a similar extension or bookmarklet installed in Firefox, a link will appear after many of the books and journal articles in a Wikipedia article's References section
If the extension is configured correctly, the user can click a link after a book to check if his organization's library has a copy
If the organization has the appropriate access, clicking the link after a journal article may bring up a copy of the article
The information can be stored by bibliographic tools like Zotero
The tool can download the bibliographic information from an article into a personal library for future research and retrieval
Zotero also has Wikipedia export, which allows references to be dragged into a Wikipedia edit box, where they will appear formatted as Wikipedia citation templates
So far, COinS have been added to
Book sources – just contains the ISBN
 Many citation templates and infoboxes – see
Templates generating COinS
 MediaWiki
Citethispage-content – generated when you click Cite this article
contains information for citing Wikipedia itself in other documents

Template
For use on templates generating COinS
It adds pages to the above category
Templates needing COinS
COinS could, and should, be added to these templates
COinS in citation templates
The COinS keys used in most  templates are listed at Module talk
Citation/CS1/COinS
Which renders the following HTML
Picking out the COinS keys
Pollution
Incorrect data in fields can pollute the metadata
For example, adding all of the authors into the  field
See also
 The planned citation microformat

References
In Unicode, a block is defined as one contiguous range of code points
Blocks are named uniquely and have no overlap
They have a starting code point of the form hhh0 and an ending code point of the form hhhF
A block explicitly can include code points that are unassigned and non-characters
Code points not belonging to any of the named blocks, e
in the unassigned planes 3–13, have the value block="No_block"
Conversely, every assigned code point has a property "Block name", which names in which block the character is
This is determined by the code point only, although a block name will have a descriptive nature
"Tibetan" or "Supplemental Arrows-A"
All assigned code points have a single block name
Subdivisions, such as "Chess symbols" in the block Miscellaneous symbols, are not a "block"
The subgroup name is an informative editorial addition only
The number of code points in a Unicode block is a multiple of 16. Unicode blocks range in size from the minimum of 16 to a maximum of 65,536 code points
Unicode 10.0 defines 280 blocks
162 in plane 0, the Basic Multilingual Plane (BMP)
 108 in plane 1, the Supplementary Multilingual Plane (SMP)
 6 in plane 2, the Supplementary Ideographic Plane (SIP)
 2 in plane 14 (E in hexadecimal), the Supplementary Special-purpose Plane (SSP)
 One each in planes 15 (Fhex) and 16 (10hex), called Supplementary Private Use Area-A and -B

See also
 Scripts in Unicode

References

External links
Official web site of the Unicode Consortium (English)
Sinhala is a Unicode block containing characters for the Sinhala and Pali languages of Sri Lanka, and is also used for writing Sanskrit in Sri Lanka
The Sinhala allocation is loosely based on the ISCII standard, except that Sinhala contains extra prenasalized consonant letters, leading to inconsistencies with other ISCII-Unicode script allocations
Block

History
The following Unicode-related documents record the purpose and process of defining specific characters in the Sinhala block
See also 
 Sinhala Archaic Numbers (Unicode block)

References
පරමාණුව වටා ඉලෙක්ට්‍රෝන වල පිහිටීම අවබෝධ කර ගැනීමට එකල සිටි විද්‍යාඥයන් වන ” j
තොම්සන් ,අර්නස්ට් රදර්ෆර්ඩ් ,නීල්ස් බෝර්” යන විද්‍යාඥයන් විසින් විවිධ මත ඉදිරිපත් කළ අතර  ඒවා පහත පරිදි වේ
1.    තොම්සන් ගේ ප්ලම් පුඩිම් ආකෘතිය

2.    රදර්ෆර්ඩ් ගේ ග්‍රහ ආකෘතිය 

3.    නීල්ස් බෝර් ගේආකෘතිය

v ප්ලම් පුඩිම් ආකෘතිය
“පුඩිමක් තුල තැන තැන මිදි ගෙඩි විසිරී ඇත්තා සේ (+) ආරෝපිත ඝන ගෝලයක් (එනම් න්‍යෂ්ටිය) තුළ (-) ආරෝපිත ඉලෙක්ට්‍රෝන ගිලී පවතී
” මෙය තොම්සන් විසින් ඉදිරිපත් කළ පරමාණුක ආකෘතියයි
මෙහිදී තොම්සන් විසින් අවදාරණය කර ඇති කරුණු කීපයකි
එනම්,

       පරමාණුව ඝන මාංසල ගෝලයක් බව.

       එය (+) ආරෝපිත බව.

       (-) ආරෝපිත ඉලෙක්ට්‍රෝන ගිලී පවතින බව.

නමුත්, රදර්ෆර්ඩ් කළ රන්පත් පරීක්ෂාව මගින් පරමාණුවේ බොහෝ ප්‍රදේශ හිස් අවකාශ බව හදුනා ගත් අතර (+) ප්‍රෝටෝන හා (-) ඉලෙක්ට්‍රෝන එකට පැවතිය නොහැකි නිසා තොම්සන්ගේ මෙම අදහස බැහැර විය
v ග්‍රහ ආකෘතිය
“සූර්‍යයා වටා ග්‍රහවස්තු ගමන් කරන්නා සේ (+) ආරෝපිත න්‍යෂ්ටිය වටා(-) ආරෝපිත ඉලෙක්ට්‍රෝන ගමන් කරයි
” මෙය රදර්ෆර්ඩ් විසින් ඉදිරිපත් කළ පරමාණුක ආකෘතියයි
මෙය න්‍යශ්ටිය පදනම් කරගත් පළමු ආකෘතිය වන නිසා මෙය “පළමු න්‍යශ්ටික ආකෘතිය” ලෙස හදුන්වයි.

න්‍යෂ්ටිය (+) ආරෝපිත නිසා එය වටා ගමන් කරන (-) ආරෝපිත ඉලෙක්ට්‍රෝනය, න්‍යෂ්ටිය වෙතට ශක්තිය අඩු වන මාර්ගයක් ඔස්සේ න්‍යශ්ටිය මතට පතිත විය යුතුය
නමුත් එසේ නොවීමට හේතුව රදර්ෆර්ඩ් හට තම ආකෘතිය ඔස්සේ පහදා දීමට නොහැකි විය
එමනිසා ඔහුගේ එම ආකෘතියද ඉවත දැමීමට සිදු විය
v බෝර් ආකෘතිය
පරමාණුව පිලිබඳ ආකෘතියක් නීල්ස් බෝර් විසින් ද ඉදිරිපත් කල අතර එය H පරමාණුව පදනම් කරගෙන නිර්මාණය වී ඇත
එහි පහත කරුණු ඇතුලත් වේ
H පරමාණුවේ ඉලෙක්ට්‍රෝනය න්‍යෂ්ටිය වටා යම් නිශ්චිත දුරකින් එනම් කවච වල (කක්ශ වල) පවතින බව. 

       මෙම කක්ශ වල පවතින ඉලෙක්ට්‍රෝන වල නිශ්චිත ශක්තියක් පවතින බව(ශක්ති ස්තාවර අවස්තාව)
ඉලෙක්ට්‍රෝන සිදු කරන වලයාකාර චලිතය සඳහා ඉලෙක්ට්‍රෝන ශක්තිය වැය නොකරන අතර ඉලෙක්ට්‍රෝන න්‍යශ්ටිය මතට පතිත වීමක්ද සිදු නොවේ
එක් ශක්ති මට්ටමක සිට වඩා ඈත වූ ශක්ති මට්ටමකට ඉලෙක්ට්‍රෝන සංක්‍රමනය වීමේදී ඉලෙක්ට්‍රෝන විසින් ශක්තිය අවශෝශනය කර ගනියි
එලෙසම පෙර ශක්තිමට්ටමට පැමිනීමේදී ඉලෙක්ට්‍රෝන විසින් අවශෝශනය කරගත් ශක්තිය විමෝචනය කරයි
මෙලෙස ශක්ති අවශෝශනය හා විමෝචනය “ෆෝටෝන” ලෙස සිදු කරයි
Usage 
This template returns a Wikipedia article name for an alpha-4 script code
→  so the link is
when resolving red links or wrong links, please edit this  or
This is where the connection between ISO code and a Wikipedia article is made
You might also consider using a redirect
(We cannot change ISO 15924 itself
)

See also
  to add a label in a wikilink
[[Fraktur (script)|Fraktur]]

Test 

Special input

 (no input)

All 197 ISO codes input
wp-name
ISO 15924, Codes for the representation of names of scripts, defines two sets of codes for a number of writing systems (scripts)
Each script is given both a four-letter code and a numeric one
Script is defined as "set of graphic characters used for the written form of one or more languages"
Where possible the codes are derived from ISO 639-2 where the name of a script and the name of a language using the script are identical (example
Gujarātī ISO 639 guj, ISO 15924 Gujr)
Preference is given to the 639-2 Bibliographical codes, which is different from the otherwise often preferred use of the Terminological codes
4-letter ISO 15924 codes are incorporated into the Language Subtag Registry for IETF language tags and so can be used in file formats that make use of such language tags
For example, they can be used in HTML and XML to help Web browsers determine which typeface to use for foreign text
This way one could differentiate, for example, between Serbian written in the Cyrillic (sr-Cyrl) or Latin (sr-Latn) script, or mark romanized text as such
Maintenance
ISO has appointed the Unicode Consortium as the Registration Authority (RA) for the standard
In 2004, the RA appointed Michael Everson to act as Registrar
The Registrar works with a Joint Advisory Committee (JAC) in developing and implementing the standard
The JAC contains six members
the Registrar, one member from the Library of Congress, one from Standards Norway, one from the French Encyclopaedia Universalis, an officer of Unicode, and a member of Unicode
These individuals represent the interests of the ISO 15924 RA, the ISO 639-2 RA, ISO Technical Committee 37, ISO Technical Committee 46, and the ISO Coded Character Set Sub-Committee, ISO/IEC JTC1/SC2.

Script codes

Numeric ranges
000–099 Hieroglyphic and cuneiform scripts
100–199 Right-to-left alphabetic scripts
200–299 Left-to-right alphabetic scripts
300–399 Alphasyllabic scripts
400–499 Syllabic scripts
500–599 Ideographic scripts
600–699 Undeciphered scripts
700–799 Shorthands and other notations
800–899 (unassigned)
900–999 Private use, alias, special codes

Special codes
Qaaa–Qabx (900–949)
50 Codes reserved for private use
Zsye 993
Emoji
Zinh 994
Code for inherited script
Zmth 995
Mathematical notation
Zsym 996
Symbols
Zxxx 997
Code for unwritten languages
Zyyy 998
Code for undetermined script
Zzzz 999
Code for uncoded script

Exceptionally reserved codes

Two four letter codes are reserved at the request of the Common Locale Data Repository Project (CLDR)
Reserved for the language-neutral base of the CLDR locale tree
True
Reserved for the boolean value "true"

List of codes

This list of codes is from the ISO 15924 standard
Relations to other standards
The following standards are referred to as indispensable by ISO 15924.
 ISO 639-2
1998 Codes for the representation of names of languages — Part 2
Alpha-3 code
 ISO/IEC 9541-1
1991 Information technology — Font information interchange — Part 1
Architecture
 ISO/IEC 10646-1
2000 Information technology — Universal Multiple-Octet Coded Character Set (UCS)

For definition of font and glyph the standard refers to
 ISO/IEC 9541-1
1991

Around 140 scripts are defined in Unicode
Through a linkpin called "Property Value Alias", Unicode has made a 1
1 connection between a script defined, and its ISO 15924 standard
See Script (Unicode)
References

External links
 ISO 15924
2004
 ISO 15924 Registration Authority (Unicode)
 Official ISO 15924 code lists
 Overview of changes in time

15924
Writing systems
 
2004 introductions
sinhala akshara malawa

 සිංහල අක්ෂර මාලාව යනු සිංහල භාෂාව සහ සමහරවිට පාලි හෝ සංස්කෘත භාෂාවන් ලියනු ලබන අක්ෂර මාලාවයි. සිංහල අක්ෂර මාලාව පිළිබඳ විද්වත් මත වලට අනුව සිංහල අකාරය ආකාර දෙකකි
එනම් සංවෘත හා විවෘත භේදයයි
Sinhalese is often considered two alphabets, or an alphabet within an alphabet, due to the presence of two sets of letters
The core set, known as the  (pure Sinhalese,  ශුද්ධ සිංහල) or  ( alphabet  එළු හෝඩිය ), can represent all native phonemes
In order to render Sanskrit and Pali words, an extended set, the  (mixed Sinhalese, මිශ්‍ර සිංහල), is available
Characteristics

The alphabet is written from left to right
The Sinhalese script is an abugida, as each consonant has an inherent vowel (), which can be changed with the different vowel signs or removed (see image on left for examples)
Most of the Sinhalese letters are curlicues
straight lines are almost completely absent from the alphabet
This is because Sinhala used to be written on dried palm leaves, which would split along the veins on writing straight lines
This was undesirable, and therefore, the round shapes were preferred
The core set of letters forms the  alphabet (pure Sinhalese, ශුද්ධ සිංහල), which is a subset of the  alphabet (mixed Sinhalese, මිශ්‍ර සිංහල)
This "pure" alphabet contains all the graphemes necessary to write Eḷu  (classical Sinhalese) as described in the classical grammar Sidatsan̆garā (1300 AD)
This is the reason why this set is also called Eḷu hōdiya ("Eḷu alphabet" එළු හෝඩිය)
The definition of the two sets is thus a historic one
Out of pure coincidence, the phoneme inventory of present-day colloquial Sinhala is such that yet again the śuddha alphabet suffices as a good representation of the sounds
All native phonemes of the Sinhala spoken today can be represented in , while in order to render special Sanskrit and Pali sounds, one can fall back on
This is most notably necessary for the graphemes for the Middle Indic phonemes that the Sinhalese language lost during its history, such as aspirates
Sinhalese had special symbols to represent numerals, which were in use until the beginning of the [19th] century
This system is now superseded by Arabic numerals
Neither the Sinhala numerals nor U+0DF4  ෴  Sinhalese punctuation kunddaliya is in general use today
The kunddaliya was formerly used as a full stop
History and usage
The Sinhalese script is a Brahmi derivate, and was imported from Northern India, around the 3rd century BCE, but was influenced at various stages by South Indian scripts, manifestly influenced by the early Grantha script
There have been found potteries in Anuradhapura from the 6th century BCE, with lithic inscription dating from 2nd century BCE written in Prakrit
By the 9th century CE, literature written in Sinhalese script had emerged and the script began to be used in other contexts
For instance, the Buddhist literature of the Theravada-Buddhists of Sri Lanka, written in Pali, used the Sinhalese alphabet
Today, the alphabet is used by approximately 16,000,000 people to write the Sinhalese language in very diverse contexts, such as newspapers, TV commercials, government announcements, graffiti, and schoolbooks
Sinhala is the main language written in this script, but rare instances of Sri Lanka Malay are recorded
Relations between orthography and phonology

Most phonemes of the Sinhalese language can be represented by a śuddha letter or by a miśra letter, but normally only one of them is considered correct
This one-to-many mapping of phonemes onto graphemes is a frequent source of misspellings
While a phoneme can be represented by more than one grapheme, each grapheme can be pronounced in only one way
This means that the actual pronunciation of a word is always clear from its orthographic form
Śuddha graphemes
The śuddha graphemes are the mainstay of the Sinhalese alphabet and are used on an everyday-basis
Every sequence of sounds of the Sinhalese language of today can be represented by these graphemes
Additionally, the śuddha set comprises graphemes for retroflex  and , which are no longer phonemic in modern Sinhala
These two letters were needed for the representation of Eḷu, but are now obsolete from a purely phonemic view
However, words which historically contain these two phonemes are still often written with the graphemes representing the retroflex sounds
Consonants

The śuddha alphabet comprises 8 plosives, 2 fricatives, 2 affricates, 2 nasals, 2 liquids and 2 glides
Additionally, there are the two graphemes for the retroflex sounds  and , which are not phonemic in modern Sinhala, but which still form part of the set
These are shaded in the table
The voiceless affricate (ච ) is not included in the śuddha set by purists since it does not occur in the main text of the Sidatsan̆garā
The Sidatsan̆garā does use it in examples though, so this sound did exist in Eḷu
In any case, it is needed for the representation of modern Sinhala
The basic shapes of these consonants carry an inherent  unless this is replaced by another vowel or removed by the hal kirīma
Vowels
Vowels come in two shapes
independent and diacritic
The independent shape is used when a vowel does not follow a consonant, e
at the beginning of a word
The diacritic shape is used when a vowel follows a consonant
Depending on the vowel, the diacritic can attach at several places
The diacritic for  attaches above the consonant, the diacritic for  attaches below, the diacritic for  follows, while the diacritic for  precedes
finally is marked by the combination of preceding  and following
While <a,e,i,o> are regular, the diacritic for  takes a different shape according to the consonant it attaches to
The most common one is represented on the image on the right for the consonant ප (p)
The k-shape is used for some consonants ending at the lower right corner (ක (k),ග (g), ත(t), but not න(n) or හ(h))
Combinations of ර(r) or  ළ(ḷ) with  have idiosyncratic shapes
In Sinhala the diacritics are called පිලි pili (vowel strokes)
දිග diga means "long" because the vowel is sounded for longer and දෙක deka means "two" because the stroke is doubled when written
Prenasalized consonants

The prenasalized consonants resemble their plain counterparts
is made up  by the left half of  and the right half of , while the other three are just like the grapheme for the plosive with a little stroke attached to their left
Vowel diacritics attach in the same way as they would to the corresponding plain plosive
Non-vocalic diacritics

The anusvara (often called binduva 'zero' ) is represented by one small circle ං (Unicode 0D82), and the visarga (technically part of the miśra alphabet) by two ඃ (Unicode 0D83)
The inherent vowel can be removed by a special virama diacritic, the hal kirīma ( ්), which has two shapes depending on which consonant it attaches to
Both are represented in the image on the right side
The first one is the most common one, while the second one is used for letters ending at the top left corner
Miśra set

The miśra alphabet is a superset of śuddha
It adds letters for aspirates, retroflexes and sibilants, which are not phonemic in today's Sinhala, but which are necessary to represent non-native words, like loanwords from Sanskrit, Pali or English
The use of the extra letters is mainly a question of prestige
From a purely phonemic point of view, there is no benefit in using them, and they can be replaced by a (sequence of) śuddha letters as follows
For the miśra aspirates, the replacement is the plain śuddha counterpart, for the miśra retroflex liquids the corresponding śuddha coronal liquid, for the sibilants,
ඤ () and  ඥ (gn) cannot be represented by śuddha graphemes but are found only in fewer than 10 words each
ෆ fa can be represented by ප pa with a Latin  inscribed in the cup
There are six additional vocalic diacritics in the miśra alphabet
The two diphthongs are quite common, while the "syllabic" ṛ is much rarer, and the "syllabic" ḷ is all but obsolete
The latter are almost exclusively found in loanwords from Sanskrit
The miśra  can also be written with śuddha + or +, which corresponds to the actual pronunciation
The miśra syllabic  is obsolete, but can be rendered by śuddha +
Miśra  is rendered as  śuddha , miśra   as śuddha
Note that the transliteration of both ළ් and ෟ is
This is not very problematic as the second one is extremely scarce
Names of the graphemes
The letters of the English alphabet have more or less arbitrary names, e
em for the letter  or bee for the letter
The Sinhala śuddha graphemes are named in a uniform way adding -yanna to the sound produced by the letter, including vocalic diacritics
The name for the letter අ is thus ayanna, for the letter ආ āyanna, for the letter ක kayanna, for the letter කා kāyanna, for the letter කෙ keyanna and so forth
For letters with hal kirīma, an epenthetic a is added for easier pronunciation
the name for the letter  ක් is akyanna
Another naming convention is to use al- before a letter with suppressed vowel, thus alkayanna
Since the extra miśra letters are phonetically not distinguishable from the śuddha letters, proceeding in the same way would lead to confusion
Names of miśra letters are normally made up of the names of two śuddha letters pronounced as one word
The first one indicates the sound, the second one the shape
For example, the aspirated  ඛ  (kh) is called bayanu kayanna
kayanna indicates the sound, while bayanu indicates the shape
ඛ  (kh) is similar in shape to  බ (b) (bayunu = like bayanna)
Another method is to qualify the miśra aspirates by mahāprāna (ඛ
mahāprāna kayanna) and the miśra retroflexes by mūrdhaja (ළ
mūrdhaja layanna)
Consonant conjuncts

Certain combinations of graphemes trigger special ligatures
Special signs exist for an ර (r) following a consonant (inverted arch underneath), a ර (r) preceding a consonant (loop above) and a  ය (y) following a consonant (half a ය on the right)
Furthermore, very frequent combinations are often written in one stroke, like ddh, kv or kś
If this is the case, the first consonant is not marked with a hal kirīma
The image on the left shows the glyph for śrī, which is composed of the letter ś with a ligature indicating the r below and the vowel  ī marked above
Most other conjunct consonants are made with an explicit virama, called al-lakuna or hal kirīma, and the zero-width joiner as shown in the following table, some of which may not display correctly due to limitations of your system
Some of the more common are displayed in the following table
Note that although modern Sinhala sounds are not aspirated, aspiration is marked in the sound where it was historically present to highlight the differences in modern spelling
Also note that all of the combinations are encoded with the al-lakuna (Unicode U+0DCA) first, followed by the zero-width joiner (Unicode U+200D) except for touching letters which have the zero-width joiner (Unicode U+200D) first followed by the al-lakuna (Unicode U+0DCA)
Touching letters were used in ancient scriptures but are not used in modern Sinhala
Vowels may be attached to any of the ligatures formed, attaching to the rightmost part of the glyph except for vowels that use the kombuva, where the kombuva is written before the ligature or cluster and the remainder of the vowel, if any, is attached to the rightmost part
In the table below, appending "o" (kombuva saha lepilla – kombuva with lepilla) to the cluster "ky"  only adds a single code point, but adds two vowel strokes, one each to the left and right of the consonant cluster
Similarities to other scripts
Sinhala is one of the Brahmic scripts, and thus shares many similarities with other members of the family, such as the Kannada, Malayalam, Telugu, Tamil script and Devanāgarī
As a general example,  is the inherent vowel in all these scripts
Other similarities include the diacritic for , which resembles a doubled  in all scripts and the diacritic for  which is composed of preceding  and following
Likewise, the combination of the diacritics for  and  yields  in all these scripts
Differences from other scripts
Sinhala alphabet differs from other Indo-Aryan alphabets in that it contains a pair of vowel sounds (U+0DD0 and U+0DD1 in the proposed Unicode Standard) that are unique to it
These are the two vowel sounds that are similar to the two vowel sounds that occur at the beginning of the English words at (ඇ) and ant (ඈ)
Another feature that distinguishes Sinhala from its sister Indo-Aryan languages is the presence of a set of five nasal sounds known as half-nasal or prenasalized stops
Sinhala transliteration

Sinhala transliteration (Sinhala
රෝම අකුරින් ලිවීම rōma akurin livīma, literally "Roman letter writing") can be done in analogy to Devanāgarī transliteration
Layman's transliterations in Sri Lanka normally follow neither of these
Vowels are transliterated according to English spelling equivalences, which can yield a variety of spellings for a number of phonemes
for instance can be , , , , etc
A transliteration pattern peculiar to Sinhala, and facilitated by the absence of phonemic aspirates, is the use of  for the voiceless dental plosive, and the use of  for the voiceless retroflex plosive
This is presumably because the retroflex plosive  is perceived the same as the English alveolar plosive , and the Sinhala dental plosive  is equated with the English  voiceless dental fricative
Dental and retroflex voiced plosives are always rendered as , though, presumably because  is not found as a representation of  in English orthography
Unicode

Sinhalese script was added to the Unicode Standard in September 1999 with the release of version 3.0.
This character allocation has been adopted in Sri Lanka as the Standard SLS1134.

The main Unicode block for Sinhala is U+0D80–U+0DFF
Another block, Sinhala Archaic Numbers, was added to Unicode in version 7.0.0 in June 2014. Its range is U+111E0–U+111FF
Computer support

Generally speaking, Sinhala support is less developed than support for Devanāgarī for instance
A recurring problem is the rendering of diacritics which precede the consonant and diacritic signs which come in different shapes, like the one for
Sinhala does not come built in with Windows XP, unlike Tamil and Hindi
However, all versions of Windows Vista and Windows 10 come with Sinhala support by default, and do not require external fonts to be installed to read Sinhalese script
Nirmala UI is the default Sinhala font in windows 10.

For Mac OS X, Sinhala font and keyboard support can be found at web
nickshanks
com/typography/ and at www
xenotypetech
com/osxSinhala
For Linux, the IBus, and SCIM input methods allow the use Sinhalese script in applications with support for a number of key maps and techniques such as traditional, phonetic and assisted techniques
In addition, newer versions of Android mobile operating system also support both rendering and input of the Sinhala script
Online resources
 Sinhala guide of the Sinhalese Wikipedia (in English)
 Online Sinhala Unicode Writer
 Sinhala English Dictionary and Sinhala To Hindi Language Translator
 Sinhala Unicode Support Group
 Online Unicode Converter

Image list for readers with font problems

See also
 Sinhalese Braille
 Dutch loanwords in Sinhala
 English loanwords in Sinhala
 Portuguese loanwords in Sinhala
 Tamil loanwords in Sinhala
 History of Sinhala software
 Singlish Typewriter

Notes

References

External links

Sinhala Unicode Character Code Chart
Sinhala Archaic Numbers Unicode Character Code Chart
Complete table of consonant-diacritic-combinations 
Complete table of consonant-diacritic-combinations as text 
Sinhala page at Omniglot
Sinhala basic course, module 1, "Beginning signs and letters"  (Bonny Graham MacDougall and Kamini de Abrew, Foreign service institute)

Transliteration Add-on for Firefox (Tamil script to Sinhalese script) 
Sinhala Accepted As One Of The World’s Most Creative Alphabets
Sinhala Unicode Converter 

Brahmic scripts
Sinhalese script
Scripts encoded in Unicode 3.0
A spoken language is a language produced  by articulate sounds, as opposed to a written language
Many languages have no written form and so are only spoken
An oral language or vocal language is a language produced with the vocal tract, as opposed to a sign language, which is produced with the hands and face
The term "spoken language" is sometimes used to mean only vocal languages, especially by linguists, making all three terms synonyms by excluding sign languages
Others refer to sign language as "spoken", especially in contrast to written transcriptions of signs
In spoken language, much of the meaning is determined by the context
That contrasts with written language in which more of the meaning is provided directly by the text
In spoken language, the truth of a proposition is determined by common-sense reference to experience, but in written language, a greater emphasis is placed on logical and coherent argument
Similarly, spoken language tends to convey subjective information, including the relationship between the speaker and the audience, whereas written language tends to convey objective information
The relationship between spoken language and written language is complex
Within the field of linguistics the current consensus is that speech is an innate human capability, and written language is a cultural invention
However some linguists, such as those of the Prague school, argue that written and spoken language possess distinct qualities which would argue against written language being dependent on spoken language for its existence
Both vocal and sign languages are composed of words
In vocal languages, words are made up from a limited set of vowels and consonants, and often tone
In sign languages, words are made up from a limited set of shapes, orientations, locations movements of the hands, and often facial expressions
in both cases, the building blocks are called phonemes