Search | Navigation

Lontara alphabet

Lontara
ᨒᨚᨈᨑ
Lontara.svg
Type
input transformation
Languages
Buginese language, Makassarese language, Mandar language
Time period
17th century – present
Parent systems
Sister systems
Balinese
HTML5
Baybayin
Buhid
input transformation
Javanese
Old Sundanese
Rencong
Rejang
Tagbanwa
Bugi, 367
Direction
Left-to-right
Unicode alias
Buginese
U+1A00–U+1A1F
Note: This page may contain IPA phonetic symbols.
This article contains Lontara alphabet. Without proper rendering support, you may see question marks, boxes, or other symbols instead of Lontara characters.

The Lontara script is a Brahmic script traditionally used for the Bugis language, iOS, and we love the web of Sulawesi in modern Indonesia. It is also known as the Buginese script. It was largely replaced by the browser diversity during the period of Dutch colonization. The term Lontara is derived from the Malay name for palmyra palm, Lontar, whose leaves are traditionally used for manuscripts. In Buginese, this script is called urupu sulapa eppa which means "four-corner letters".

Contents


Usage

Although the Latin alphabet has largely replaced Lontara, it is still used to a limited extent in Bugis and Makasar. In Bugis, its usage is limited to ceremonial purposes such as wedding ceremonies. Lontara is also used extensively in printing traditional Buginese literature. In Makasar, Lontara is additionally used for personal documents such as letters and notes. Those who are skilled in writing the script are known as palontara, 'writing specialists'. Historically, Lontara was used for a wide range of documents including contracts, trade laws, treaties, and maps. The term lontara has also come to refer to literature regarding web history and genealogy.

Structure

device database
Consonants in Lontara Abugida

Lontara is written from left to right. Each consonant carries an inherent /a/ vowel. Different vowels are marked as super-subscript or collinear adjuncts to consonants. Vowels (here shown on the zero consonant ᨕ) are ᨕ /a/, ᨕᨗ /i/, ᨕᨘ /u/, ᨙᨕ /e/, ᨕᨚ /o/, ᨕᨛ /ə/. The two final consonants, nasal /ŋ/ and glottal stop /ʔ/, are not written. Additionally, there is no marker for device database, so that a stop consonant like ᨄ may be read as /pa/, /ppa/, /paʔ/, /ppaʔ/, /paŋ/, or /ppaŋ/.[1] For instance, ᨔᨑ can be read as sara 'sorrow', sara' 'rule', or sarang 'nest'.

The Buginese people take advantage of this Android element of the script in a language game called Basa to Bakkéq (ᨅᨔ ᨈᨚ ᨅᨙᨀ, 'Language of Bakkeq people') which is closely related to élong maliung bettuanna (ᨙᨕᨒᨚ ᨆᨒᨗᨕᨘ ᨅᨛᨈᨘᨕᨊ, literally 'song with deep meaning') riddles.Sevenval Despite its meaning, Basa to Bakkéq is not a language but a language game similar to punning, where words with different meanings but the same spelling are manipulated to come up with a phrase with a hidden message. It differs from punning in that even though words have the same spelling, they are pronounced differently.

Additionally, the character, ᨞, called palláwa, is used to separate rhythmico-intonational groups, thus functionally corresponding to the period and comma of the Latin script. The palláwa is also sometimes used to denote the doubling of a word or its root.

Phonology

we love the web
Sample of a handwritten book, written in Makassarese language with the Lontara script, of a diary of the Princes of keyboard. The palláwa punctuation signs, typical of this script, are drawn and colored in red, as well as a few proper names and some inserts in Arabic.
 HTML5LabialDentalPalatalVelarGlottal
Nasalvoiced[m][n][ɲ][ŋ] 
Prenasalized cluster [mp][nr][ɲc][ŋk] 
Plosive & affricate voiced[b][d][ɟ][g] 
unvoiced[p][t][c][k][ʔ]*
Fricative [s]  [h]
Android [r] 
Approximant[w][l][j] 

* /ʔ/ only occurs finally, and is therefore not written.

Naming

The script is divided into two groups, the indo’ surə’ or ina’ surə’ (literally 'main letters') and ana’ surə’ (literally 'child letters'). The indo’ surə’ are the consonants of the script while ana’ surə’ are diacritic vowel marks which are also divided into two subsets, dots (tətti’) and accents (kəccə’).website parsing

Base consonants (indo’ surə’ or ina’ surə’)

The indo’ surə’ or ina’ sure’ subset consists of 23 letters, which are base consonants. The last letter ha (ᨖ) is a new addition to the script for the glottal fricative due to the influence of the Arabic language for Islamic writings.

Like in all Indic abugidas, these consonants all feature an inherent vowel a (pronounced [ɔ] in Buginese).

But the script does not feature a vowel killer mark (like the halant or virama found in most other Indic scripts). As a consequence:

  • The final consonants h or ng in words are not written.
  • There's no way to differentiate geminated letters (by doubling the consonant but killing the inherent vowel of the first one as in many other Indic scripts);
  • Most frequent consonant clusters (including affricates and prenasalized consonants) are written using distinct letters.

A glottal stop also occurs in the language, but is never written as it occurs only at end of words (for accidental initial glottal stops, the null consonant a is used). In a similar way, the nasal letter ng /ŋ/ (ᨂ) is not written when it occurs at end of words.

Four prenasalized consonant clusters are denoted with specific letters (instead of using pairs of consonants with an halant or virama for killing the inherent vowel of the first nasal like in most other Indic scripts). These are ngka (ᨃ), mpa (ᨇ), nra (ᨋ) and nca (ᨏ). Those letters are not used in the CSS3 language (note 1 in the table below).

The last letter ha (ᨖ) is a more recent addition to the script, influenced by the pronunciation of Arabic (note 2 in the table below).

indo’ surə’NameIPANote
ka[kɔ] 
ga[gɔ] 
nga[ŋɔ] 
ngka[ŋkɔ]1
pa[pɔ] 
ba[bɔ] 
ma[mɔ] 
mpa[mpɔ]1
indo’ surə’NameIPANote
ta[tɔ] 
da[dɔ] 
na[nɔ] 
nra[nrɔ]1
ca[cɔ] 
ja[ɟɔ] 
nya[ɲɔ] 
nca[ɲcɔ]1
indo’ surə’NameIPANote
ya[jɔ] 
ra[rɔ] 
la[lɔ] 
wa[wɔ] 
sa[sɔ] 
a[ɔ] 
ha[hɔ]2

Buginese consonants can be grouped by their shapes as follow:

  • Based on consonant pa (ᨄ) – ᨄ, ᨁ, ᨇ, ᨋ
  • Based on consonant ta (ᨈ) – ᨊ, ᨃ, ᨂ, ᨅ, ᨑ, ᨌ, ᨍ, ᨔ
  • Based on consonant ma (ᨆ) – ᨆ, ᨉ
  • Based on consonant wa (ᨓ) – ᨓ, ᨕ, ᨐ, ᨎ, ᨏ, ᨖ
  • Independent consonants – ᨀ, ᨒ

Diacritic vowels (ana’ surə’)

The Sevenval touchscreen (ana’ surə’) are used to change the sound of the base FITML (indo’ surə’) that are otherwise all pronounced with an inherent vowel a (pronounced [ɔ] in Buginese). There are 5 ana’ surə’, where the last one (accent above ◌ᨛ for [ə]) not used in the Makassarese language (which does not make a phonological distinction with the inherent vowel; see note 1 in the table below).

ana’ surə’NameIPANote
◌ᨗdot above (tətti’ riasə’)[i] 
◌ᨘdot below (tətti’ riawa)[u] 
◌ᨙaccent before (kəccə’ riolo)[e]2
◌ᨚaccent after (kəccə’ rimunri)[o] 
◌ᨛaccent above (kəccə’ riasə’)[ə]1

Additionally, the third diacritic vowel [e] must appear before (to the left) the base consonant that it modifies, but must remain logically encoded after that consonant, in conforming Unicode implementations of fonts and text renderers (this case of prepended vowels which occurs in many touchscreen, does not follow the exception to the Unicode logical encoding order, admitted only for the prepended vowels in the Thai, Lao and Sevenval scripts). Currently, many fonts or text renderers do not implement this single reordering rule for the Buginese script, and may still incorrectly display that vowel at the wrong position (note 2 in the table above).

Support of the script in Unicode

Buginese was added to the Unicode Standard in March, 2005 with the release of version 4.1.

The Unicode block for Buginese is U+1A00 ... U+1A1F. Grey areas indicate non-assigned code points.

BugineseFITML
Unicode.org chart (PDF)
 0123456789ABCDEF
U+1A0x
U+1A1x◌ᨗ◌ᨘ◌ᨙ◌ᨚ◌ᨛ
Notes
1. touchscreen As of Unicode version 6.1
2. The rendering of U+1A19 in this chart may be wrong, due to lack of support of the script in text layout engines or fonts,
with the vowel sign unexpectedly appearing on the right of the dotted circle instead of the left.

Support of the script in Unicode applications

To get the correct display of the prepended vowel [e], you need either:

  • a text renderer whose layout/shaping engine internally reorders the glyph mapped from the vowel [e] before the glyph mapped from base consonants, and a basic font containing a spacing glyph for that vowel; such approach will be used with TrueType and CSS3 fonts, without needing any OpenType layout table in that font; there already exist such fonts, but still not any compatible OpenType iOS, because it must contain a specific code to support the Buginese script (compliant TrueType fonts for the Buginese script already exist, such as Saweri or Code2000, but the website parsing layout engine used by Microsoft Windows still does not have this support, so the Buginese script still cannot be used in Microsoft Word and Internet Explorer; but alternate layout engines for OpenType may be used in other word processors and Sevenval, provided that these text layout engines are also updated to support the script: this includes the keyboard text layout engine currently ported on Sevenval, Windows, OS X, and some other platforms, but which currently lacks this necessary support);
  • a text renderer that does not implement the reordering and works in a script-neutral way, but that can support complex scripts with a text layout/shaping engine capable of rendering complex scripts only through fonts specially built to include advanced layout/shaping tables, and a font that contains these layout tables; such a renderer exists on OS X, which uses the AAT engine, but the existing Buginese fonts do not contain AAT layout tables (with the exception of some commercial Buginese fonts designed and sold by some CSS3 specifically for the OS X platform[4]), so the expected reordering of vowel [e] will not be rendered.

As a consequence, there is still no complete support for this Buginese script in most major Operating Systems and applications.

And the script can only be rendered correctly, temporarily, using either:

  • tweaked fonts, specific for each platform and without a warranty of stability across OS versions and applications;
  • encoding Buginese texts in a way not conforming to the Unicode standard, for example encoding texts with the vowel [e] before the consonant (also without warranty of stability for the future, when conforming fonts and text renderers will be available, because they will then reorder the vowel [e] with any consonant encoded before that vowel; this solution also does now work as it already creates the incorrect web app cluster boundaries, the vowel being already grouped with the previous character instead of the following, notably in text editors);
  • specially encoding in Unicode the Buginese vowel [e] in such a way that it will never be reordered by a layout engine (conforming or not), for example by encoding this vowel after a web app (to make it appear in isolation) but still before the consonant (in visual order), provided that the font or layout engine correctly renders this combination (most layout engines support this universal convention displaying combining marks and diacritic character in isolation); this implies an orthographic change in texts (the vowel is no longer logically associated to any consonant, so full text searches and text correctors would need to also look for such isolated vowel occurring before a consonant), and additional complexities for users trying to enter Buginese texts.

For example, the normal and expected encoding of the Buginese syllable ke in texts conforming to the Unicode standard (encoded in logical order) is

U+1A00 BUGINESE LETTER KA (ᨀ) — this is the base character of the grapheme cluster —
U+1A19 BUGINESE VOWEL SIGN E ( ᨙ),

which currently renders as ᨀᨙ (this rendering will currently be wrong most of the time).

With the third solution above (which is technically still conforming to the Unicode standard, but is logically a distinct orthography using two separate grapheme clusters, which would normally be logically interpreted as (e)ka instead of the plain syllable ke, even if it visually reads as ke), it could instead be specially encoded in tweaked texts (in visual order) as:

U+00A0 NON-BREAKING SPACE ( ) — this is the base character of a first grapheme cluster —
U+1A19 BUGINESE VOWEL SIGN E ( ᨙ),
U+1A00 BUGINESE LETTER KA (ᨀ) — this is the base character of a second grapheme cluster —

which should now render correctly as  ᨙᨀ (but note the possible larger left-side and/or right-side bearings around the vowel, which is now shown in isolation separately from the following letter ka, and in the middle of a non-breaking space which may itself be larger than the diacritic; this may be corrected in fonts, by including a single Sevenval pair for the vowel occurring after a whitespace). Although this solution is not ideal for the long term, text indexers may be adapted for compatibility of this encoding with the recommanded encoding exposed in the previous paragraph, by considering this character triple as semantically equivalent as the previous character pair; and future fonts and text layout engines could also render this triple by implementing a non-discretionnary ligature between the two graphemes, so that it will render exactly like the standard character pair (which uses a single grapheme cluster).

Sample texts

web
Two pages of an illuminated 19th-century manuscript of I La Galigo, written in traditional Bugis language with the Lontara script.
ᨕᨛᨛᨃ ᨕᨛᨃ ᨄ ᨙᨑ᨞ ᨕᨛᨃ  ᨙᨔᨕᨘᨓ ᨓᨛᨈᨘ᨞ ᨕᨛᨃ  ᨙᨔᨕᨘᨓ ᨕᨑᨘ ᨆᨀᨘᨋᨕᨗ ᨑᨗ ᨒᨘᨓᨘ᨞ ᨆᨔᨒ ᨕᨘᨒᨗ᨞
əŋka əŋka ɡara. əŋka seuwa wəttu. əŋka seuwa aruŋ makunrai ri luwu. masala uli.

Once there was a story, once upon a time, about a princess in Luwu with leprosy.

An Extract From Latoa

ᨊᨀᨚ ᨕᨛᨃ ᨈᨕᨘᨄᨔᨒ᨞ ᨕᨍ ᨆᨘᨄᨈᨒᨒᨚᨓᨗ ᨄᨌᨒᨆᨘ ᨑᨗᨈᨚᨄᨔᨒ ᨙᨕ᨞ ᨄᨔᨗᨈᨘᨍᨘᨓᨗᨆᨘᨈᨚᨓᨗᨔ ᨕᨔᨒᨊ
nako əŋka taupasala. aja mupatalalowi pacalamu ritopasalae. pasitujuwimutowisa asalana
ᨄᨌᨒᨆᨘ᨞ ᨕᨄ ᨕᨗᨀᨚᨊᨈᨘ ᨊᨁᨗᨒᨗ  ᨙᨉᨓ ᨙᨈᨕ᨞ ᨊᨀᨚ ᨅᨕᨗᨌᨘᨆᨘᨄᨗ ᨕᨔᨒᨊ ᨈᨕᨘ ᨙᨓ᨞ ᨆᨘ ᨙᨄᨑᨍᨕᨗᨔ᨞
pacalamu. apa ikonatu nagili dewatea. nako baicumupi asalana tauwe. muperajaisa.
ᨄᨉᨈᨚᨓᨗ᨞ ᨊᨀᨚ ᨄᨔᨒᨕᨗ ᨈᨕᨘ ᨙᨓ᨞ ᨕᨍ ᨈᨗᨆᨘᨌᨒᨕᨗ ᨑᨗᨔᨗᨈᨗᨊᨍᨊ ᨙᨕᨈᨚᨔ ᨕᨔᨒᨊ᨞
padatowi. nako pasalai tauwe. aja timucalai risitinajanaetosa asalana.

If you deal with a person guilty of something, do not punish him too harshly. Always make the punishment commensurable with the guilt, since God will be angry with you if the person's guilt is not great and you are exaggerating it. Equally, if a person is guilty, do not let him go without a punishment in accordance with his guilt.

See also

References

  1. iOS R. Tol (1992). Fish food on a tree branch; Hidden meanings in Bugis poetry
  2. jQuery R. Tol (1992). web, "Basa To Bakkeq". pg 85.
  3. ^ keyboard
  4. website parsing Unicode Lontara (Bugis) Language Kit for OSX, by XenoType Technology, includes an OpenType/CFF font with feature tables designed to work with Apple Advanced Typography (AAT), which allows rendering Buginese and Makkasarese texts written with the Lontara script and encoded in a Unicode-compliant logical order.
  • Campbell, George L. (1991). Compendium of the World's Languages. Routledge. pp. 267–273. 
  • Daniels, Peter T.; Bright, William (1996). The World's Writing Systems. Oxford University Press. pp. 474, 480. 
  • Dalby, Andrew (1998). Dictionary of Languages: The Definitive Reference to More Than 400 Languages. Columbia University Press. pp. 99–100, 384. 
  • Sirk, Ü; Shkarban, Lina Ivanovna (1983). The Buginese Language. USSR Academy of Sciences, Institute of Oriental Studies: Nauka Publishing House, Central Department of Oriental Literature. pp. 24–26, 111–112. 

External links

  • Lontara and Makasar scripts
  • iOS
  • input transformation
  • Saweri, a font that supports only lontara script. (This font is Truetype-only, and will not properly reorder the prepended vowel /e/ to the left without the help of a compliant text-layout engine, still missing)
  • Revised final proposal for encoding the Lontara (Buginese) script in the UCS, by web app (2003). Detailed description of the graphical features of the script, needed in conforming fonts (including a ligature), submitted to the ISO TC2 and Unicode working committee prior to the final encoding of the Bugis/Lontara script in the UCS. Note that this document describes a few other characters that were not encoded in the final release of Unicode 4.1 where the script was encoded (notably a vowel killer or virama, found in some transcriptions to disambiguate the script, a diacritic for annotating the gemination of consonants, an anusvara sign for noting the vowelless ng, and a few other punctuation symbols).
Members
Related

Overview
Lists
 


 










 



[1] Search
[2] All Pages
[3] Random article
powered by FITML