UC Berkeley: Proposals From The Script Encoding Initiative
UC Berkeley: Proposals From The Script Encoding Initiative
Title
Proposal for encoding additional Sundanese characters for Old Sundanese in the UCS
Permalink
https://escholarship.org/uc/item/6ss5j9zj
Author
Everson, Michael
Publication Date
2009-09-05
Peer reviewed
Sundanese has been written in a number of scripts. Pallawa or Pra-Nagari was first used in West Java to
write Sanskrit from the fifth to eighth centuries CE, and from Pallawa was derived Sunda Kuna or Old
Sundanese which was used in the Sunda Kingdom from the 14th to 18th centuries. Both Javanese and
Arabic script were used from the 17th to 19th centuries and the 17th to the mid-20th centuries
respectively. Latin script has had currency since the 20th century. The modern Sundanese script, called
Sunda Baku or Official Sundanese, was made official in 1996. The modern script itself was derived from
Old Sundanese, the earliest example of which is the Prasasti Kawali stone (see Figure 1).
The Sundanese script was originally more similar to other scripts of the Brahmic type, in that it made use
of conjunct characters. Consonant conjuncts are not formed productively in the modern script, which uses
the explicit SUNDANESE SIGN PAMAAEH character to show indicate the absence of the inherent vowel;
PAMAAEH does not cause Brahmic conjunct formation. (Some consonant clusters are represented in the
modern script with the encoded medial signs -ya, -ra, and -la, but these are not conjuncts.) In order to
support older orthography, the “Myanmar model” as opposed to the “Devanagari model” is used. An
explicit SUNDANESE SIGN VIRAMA is proposed here to cause true Brahmic consonant clustering. Since
PAMAAEH does not cause conjunct formation, and is always visible, and since modern users do not want
conjuncts to be formed, the Myanmar model, which has an explicit ASAT alongside a conjunct-forming
VIRAMA, is the model used here. Analogous is the modern Meetei Mayek script, which has its explicit
KILLER, alongside the older Meetei Mayek orthography, which uses a conjunct-forming VIRAMA.
1
The following conjuncts (all formed with VIRAMA) are known to occur:
Note the difference between ᮮ SUNDANESE LETTER KHA and the conjunct of ka and ha, as well
as ᮯ SUNDANESE LETTER SYA and the conjunct of sa and ya. The archaic shapes in kta
(modern style ) and mpa (modern style ) are a matter of font choice. (Such a choice would
be made only for “historical” fonts; modern readers do not know or expect the archaic shapes.)
3
Linebreaking
The letters, avagraha, and virama behave as in Devanagari. The bindu symbols can occur in initial
position in a paragraph, or in final position at the end of a clause, sentence, or paragraph. Since half of
the bindus are derived from letters, and since sequences like ꧦꧠꧦ should not be broken, linebreaking
properties for all of these should be the same as those for letters. A space should be used if a user wishes
to cause a linebreak before or after any of the bindu symbols.
Ordering
The arrangement of characters in the code table here follows the Brahmic ordering, for transparency to
implementors of ISO/IEC 10646 and Unicode. The ha-na-ca-ra-ka order found in Javanese and Balinese
does not seem to have currency in Sundanese. Two Brahmic orderings do have some currency, however.
One of these inserts modern additions to the character set into the order according to place of articulation
and lettershape. The principle followed here is the same principle that was applied in the ordering of
Balinese; it also follows the way the characters are taught (as in the children’s primer Ngalagena, 2002).
4
Bibliography
Baidillah, Idin, et al. 2008. Direktori Aksara Sunda untuk Unicode. Bandung: Pemerintah Provinsi Jawa
Barat, Dinas Pendidikan Provinsi Jawa Barat.
de Casperis, J. G. 1975. Indonesian palaeography: a history of writing in Indonesia from the beginnings
to c. A . D . 1500. (Handbuch der Orientalistik: Dritte Abteilung: Indonesian, Malaysia und die
Philippinen: unter Einschluss der Kap-Malaien in Südafrika). Leiden & Köln: E. J. Brill.
Suryani NS, Elis. 2008. Merumat warisan karuhun rang Sunda yang terpendam dalam naskah dan
prasasti. Sumedang: Alqapring & Dinas Pendidikan Kota Tasikmalaya. ISBN 979-9462-82-7
Acknowledgements.
This project was made possible in part by a grant from the U.S. National Endowment for the Humanities,
which funded the Universal Scripts Project (part of the Script Encoding Initiative at UC Berkeley) in
respect of the Sundanese encoding. Any views, findings, conclusions or recommendations expressed in
this publication do not necessarily reflect those of the National Endowment of the Humanities.
5
1B80 Sundanese 1BBF
0 $ᮀ ᮐ ᮠ ᮰
1B80 1B90 1BA0 1BB0
1 $ᮁ ᮑ $ᮡ ᮱
1B81 1B91 1BA1 1BB1
2 $ᮂ ᮒ $ᮢ ᮲
1B82 1B92 1BA2 1BB2
3 ᮃ ᮓ $ᮣ ᮳
1B83 1B93 1BA3 1BB3
4 ᮄ ᮔ $ᮤ ᮴
1B84 1B94 1BA4 1BB4
5 ᮅ ᮕ $ᮥ ᮵
1B85 1B95 1BA5 1BB5
6 ᮆ ᮖ $ᮦ ᮶
1B86 1B96 1BA6 1BB6
7 ᮇ ᮗ $ᮧ ᮷
1B87 1B97 1BA7 1BB7
8 ᮈ ᮘ $ᮨ ᮸
1B88 1B98 1BA8 1BB8
9 ᮉ ᮙ $ᮩ ᮹
1B89 1B99 1BA9 1BB9
A ᮊ ᮚ $᮪ ᮺ
1B8A 1B9A 1BAA 1BBA
B ᮋ ᮛ ᮫ ᮻ
1B8B 1B9B 1BAB 1BBB
C ᮌ ᮜ $ᮬ ᮼ
1B8C 1B9C 1BAC 1BBC
D ᮍ ᮝ $ᮭ ᮽ
1B8D 1B9D 1BAD 1BBD
E ᮎ ᮞ ᮮᮾ
1B8E 1B9E 1BAE 1BBE
F ᮏ ᮟ ᮯ ᮿ
1B8F 1B9F 1BAF 1BBF
Vowel signs
1BA4 $ᮤ SUNDANESE VOWEL SIGN PANGHULU
=i
1BA5 $ᮥ SUNDANESE VOWEL SIGN PANYUKU
=u
1BA6 $ᮦ SUNDANESE VOWEL SIGN PANAELAENG
= ae
1BA7 $ᮧ SUNDANESE VOWEL SIGN PANOLONG
=o
1CC Punctuation
1CC0 ᳀ SUNDANESE PUNCTUATION BINDU
0 ᳀ SURYA
• sun
1CC0 1CC1 ᳁ SUNDANESE PUNCTUATION BINDU
PANGLONG
1 ᳁ • half moon
1CC2 ᳂ SUNDANESE PUNCTUATION BINDU
1CC1 PURNAMA
• full moon
2 ᳂ 1CC3 ᳃ SUNDANESE PUNCTUATION BINDU
CAKRA
1CC2 • wheel
1CC4 ᳄ SUNDANESE PUNCTUATION BINDU LEU
3 ᳃ SATANGA
1CC5 ᳅ SUNDANESE PUNCTUATION BINDU KA
1CC3 SATANGA
1CC6 ᳆ SUNDANESE PUNCTUATION BINDU DA
4 ᳄ SATANGA
1CC7 ᳇ SUNDANESE PUNCTUATION BINDU BA
1CC4 SATANGA
5 ᳅
1CC5
6 ᳆
1CC6
7 ᳇
1CC7
9
Figure 3a. Black and white photo of the Prasasti Kawali 1 stone.
Figure 3b. Inverse black and white photo of the Prasasti Kawali 1 stone.
Circled are ᮽ LETTER BHA and ᮻ LETTER REU.
10
Figure 4. The Old Sundanese Prasasti Kawali 3 inscription showing ᳀ PUNCTUATION BINDU SURYA
Figure 6. The same Old Sundanese manuscript showing ᳆ PUNCTUATION BINDU DA SATANGA
and ᳀ PUNCTUATION BINDU PURNAMA
11
Figure 7. Old Sundanese manuscript showing ᳄ PUNCTUATION BINDU LEU SATANGA
Figure 9. Old Sundanese manuscript showing ᳇ PUNCTUATION BINDU BA SATANGA looking like a furry
caterpillar. ᮘ LETTER BA is seen in the top line.
Figure 10. Old Sundanese manuscript showing a number of examples of ᳃ PUNCTUATION BINDU CAKRA
12
ͷȌ ° α patén (pamaéh)
Ǥ
= ka ÆαkǤ
ǣαawakǮǯǤ
α s α
α
Figure 13. Examples of two words written with a conjunct and written with the explicit killer.
13
Figure 14. Sample text from Suryani 2008.
14
Figure 16. Discussion of font design and example of sans-serif and serif fonts in the modern style.
15
A. Administrative
1. Title
Proposal for encoding additional Sundanese characters for Old Sundanese in the UCS.
2. Requester’s name
UC Berkeley Script Encoding Initiative (Universal Scripts Project)
3. Requester type (Member body/Liaison/Individual contribution)
Liaison contribution.
4. Submission date
2009-09-05
5. Requester’s reference (if applicable)
6. Choose one of the following:
6a. This is a complete proposal
Yes.
6b. More information will be provided later
No.
B. Technical – General
1. Choose one of the following:
1a. This proposal is for a new script (set of characters)
No.
Proposed name of script
1b. The proposal is for addition of character(s) to an existing block
Yes.
1c. Name of the existing block
Sundanese, Sundanese Supplement.
2. Number of characters in proposal
17.
3. Proposed category (A-Contemporary; B.1-Specialized (small collection); B.2-Specialized (large collection); C-Major extinct; D-Attested
extinct; E-Minor extinct; F-Archaic Hieroglyphic or Ideographic; G-Obscure or questionable usage symbols)
Category A.
4a. Is a repertoire including character names provided?
Yes.
4b. If YES, are the names in accordance with the “character naming guidelines” in Annex L of P&P document?
Yes.
4c. Are the character shapes attached in a legible form suitable for review?
Yes.
5a. Who will provide the appropriate computerized font (ordered preference: True Type, or PostScript format) for publishing the standard?
Michael Everson and “Tim Unicode Aksara Sunda”.
5b. If available now, identify source(s) for the font (include address, e-mail, ftp-site, etc.) and indicate the tools used:
Michael Everson, Fontographer.
6a. Are references (to other character sets, dictionaries, descriptive texts etc.) provided?
No.
6b. Are published examples of use (such as samples from newspapers, magazines, or other sources) of proposed characters attached?
Yes.
7. Special encoding issues: Does the proposal address other aspects of character data processing (if applicable) such as input, presentation,
sorting, searching, indexing, transliteration etc. (if yes please enclose information)?
Yes.
8. Additional Information: Submitters are invited to provide any additional information about Properties of the proposed Character(s) or
Script that will assist in correct understanding of and correct linguistic processing of the proposed character(s) or script.
See above.
C. Technical – Justification
1. Has this proposal for addition of character(s) been submitted before? If YES, explain.
No.
2a. Has contact been made to members of the user community (for example: National Body, user groups of the script or characters, other
experts, etc.)?
Yes.
2b. If YES, with whom?
Sai Zin Di Di Zone, Khwaan Tai, Sai Murngzuen Hengtai.
2c. If YES, available relevant documents
3. Information on the user community for the proposed characters (for example: size, demographics, information technology use, or
publishing use) is included?
People in West Java, Indonesia.
4a. The context of use for the proposed characters (type of use; common or rare)
Rare.
4b. Reference
16
5a. Are the proposed characters in current use by the user community?
Yes.
5b. If YES, where?
In Indonesia.
6a. After giving due considerations to the principles in the P&P document must the proposed characters be entirely in the BMP?
Yes.
6b. If YES, is a rationale provided?
Yes.
6c. If YES, reference
Keep with other Sundanese characters.
7. Should the proposed characters be kept together in a contiguous range (rather than being scattered)?
No.
8a. Can any of the proposed characters be considered a presentation form of an existing character or character sequence?
No.
8b. If YES, is a rationale for its inclusion provided?
8c. If YES, reference
9a. Can any of the proposed characters be encoded using a composed character sequence of either existing characters or other proposed
characters?
No.
9b. If YES, is a rationale for its inclusion provided?
9c. If YES, reference
10a. Can any of the proposed character(s) be considered to be similar (in appearance or function) to an existing character?
No.
10b. If YES, is a rationale for its inclusion provided?
10c. If YES, reference
11a. Does the proposal include use of combining characters and/or use of composite sequences?
Yes.
11b. If YES, is a rationale for such use provided?
Yes.
11c. If YES, reference
Brahmic vowel and consonant signs.
11d. Is a list of composite sequences and their corresponding glyph images (graphic symbols) provided?
No.
11e. If YES, reference
12a. Does the proposal contain characters with any special properties such as control function or similar semantics?
No.
12b. If YES, describe in detail (include attachment if necessary)
13a. Does the proposal contain any Ideographic compatibility character(s)?
No.
13b. If YES, is the equivalent corresponding unified ideographic character(s) identified?
17