Talk:Lontara alphabet

comments

I added the sections 'Structure' and 'Usage' as well as some minor edits throughout the article. Feedback is appreciated. Bob0513 (talk) 01:58, 6 November 2008 (UTC)

I forgot to log in, IP#128.84.73.128 is me. I added a much longer sample text, as well as did some minor edits throughout the page, such as adding info on the pallawa punctuation character. Bob0513 (talk) 06:30, 4 December 2008 (UTC)

Hi, you should never force special fonts like here <div style="font-family:Saweri,'MPH 2B Damase',Code2000,sans-serif"> – different fonts in the same text do not look good. The browser is perfectly able to render Lontara glyphs if there is one font installed in the system which knows them. If there is no such font on the visitor’s computer, even forcing a font does not help. --109.193.161.69 (talk) 17:14, 10 September 2011 (UTC)

Comments for LING 1100-108 project

Great information on structure and usage, as well as the derivation of the name of the language. I also thought it was interesting that there is no marker for gemination, which seems to make the language kind of ambiguous.
Suggestion for possible additional editing: add more about the origin and development of the writing system. Also, what other ancient languages does it relate to (others with the inherent "a" vowel)? Mmg86 (talk) 01:00, 20 November 2008 (UTC)

V syllables

Regarding undo's, independant vowels only can be used in the initial position. Refer to George Campbell's Compendium of the World's Language Bob0513 (talk) —Preceding undated comment was added at 02:09, 6 November 2008 (UTC).

Campbell discusses languages, and only gives the briefest coverage of scripts. The data here, from Daniels & Bright, contradicts that claim:   ᨙᨔᨕᨘᨓ seuwa and ᨆᨀᨘᨋᨕᨗ makunrai both have internal ᨕ. kwami (talk) 06:26, 6 November 2008 (UTC)

Lontara's origin from Kawi

Is there any reliable source regarding this? I've been wondering, is it true that the script based on Kawi or Brahmic since the Bugis religion before Islam is Animism. As far as I know, Sureq Galigo didn't mentioned anything about Hinduism (they have their own story how the world been created), and I may be wrong. Based on this site, some group of Bugis still practive believes based on lontara (not the script but the manuscript). So, I think the script being originate from Kawi script or Brahmic family is still not a fact. Kurniasan (talk) 04:34, 7 November 2008 (UTC)

I don't know about Lontara being derived from Kawi, but it is incorrect to say that Hinduism and Buddhism never touched South Sulawesi. I can see that you're a Malaysian, so it's understandable. I'd expect Indonesians (especially the ones from South Sulawesi) to know that there have been influences of Brahmic religions prior to the coming of Islam. We have important artefacts such as the bronze Buddha statue, the name of the forefather of Gowa kingdom was "Batara Guru", and even the story you mentioned borrowed a lot of Hindu concepts. But yes, animism was stronger in Celebes than it was in Java, and later on, Islam was even stronger (it still is) that it's a bit difficult to see the traces of Hindu and Buddhist civilization in the area. Matahari Pagi (talk) 03:41, 27 February 2010 (UTC)

More Ling 1100-108 comments

Greetings! I agree with Madison. I thought that the organization into "usage" and "structure" and I'm actually strongly considering doing that for my own.

I was just a little confused in the usage section, however, where you start talking about how the script is still used in Bugis ceremonies. How is the script itself used in ceremonies? Do you use the script to make the wedding invitations? What did this mean? Along the same lines, I also think that the information regarding the evolution of the script needs to be expanded. If there isn't more information on how it developed (such as to which script family it belongs or some specific intricacies regarding its structure development), then that's okay, but the article hardly delves into it. This can go in "Usage" or maybe a separate "History" section.

Another suggestion is to cite some sources in your "Usage" section. Which of the sources did that information come from?

That's all! Otherwise, good job! --Rda2512 (talk) 01:42, 20 November 2008 (UTC) Rda2512 (talk • contribs) 01:37, 20 November 2008 (UTC)

W not labial

W does not represent the bilabial approximant in the IPA. If the sound is indeed [w], it should be recategorized as velar. ᛭ LokiClock (talk) 15:37, 1 July 2010 (UTC)

It's both. People don't generally bother with creating a separate column just for [w], but will place it with [kw], [gw], [xw] if they have a column. — kwami (talk) 20:54, 1 July 2010 (UTC)

Okay. I reviewed IPA classification of coarticulated sounds, which affirms this usage. What's the connection with [kw], [gw], [xw]? Are those allophonic alternations of [w]? ᛭ LokiClock (talk) 06:27, 8 July 2010 (UTC)

No, they're all just articulated the same way, just as [p], [b], [m] are. — kwami (talk) 08:39, 8 July 2010 (UTC)

They are not articulated the same way. They have the same place of articulation, but not the same manner of articulation. ᛭ LokiClock (talk) 12:24, 8 July 2010 (UTC)

Incorrect encoding in chart for vowel /e/ (U+1A19)

The chart incorrectly encodes the vowel /e/ (U+1A19) before the base consonnant on which it applies. Unicode clearly says that the diacritic vowel must be encoded after the base consonnant, even if it visually appears on the left of the base consonnant. I corrected the chart to exhibit the expected logical encoding order (even if it displays wrong for now on most platforms, and that's why I also added a note at the bottom of the table, and then created the next sub-section about support of the script in Unicode applications).

There's no logical-order exception defined for this preposed vowel in the Lontara/Buginese script (unlike in the Thai, Lao, and Tai Viet scripts, that are encoded using the visual order).

May be you have drawn this chart using a font like "Saweri" or "MPH 2B Damase", but these fonts are incorrect (not conforming to Unicode) about the placement of this vowel, if they are used with a TrueType-only implementation for text rendering, or with an OpenType implementation that does not recognize the script and implements at least its mandatory glyph reordering (OpenType renderers on Windows, MAcOSX and Linux still don't implement it in their text shaping/layout engine, only MacOSX can support the script but only if using OpenType fonts containing AAT layout tables, which are specific to the MacOSX platform and ignored on other platforms). Note that I also don't know if the script can be supported in other platforms, using TrueType fonts containing SIL Graphite feature tables, rather than OpenType feature tables, and a Graphite-enabled application (such as OpenOffice), and I also don't know if such TrueType font with Graphite features exists for now (it does not seem to be the case).

Still, you should not encode the vowel blindly before the consonnant because it breaks the analysis of grapheme cluster boundaries, (in the chart, the vowel currently appears combined with the previous space; this should not occur, because the vowel may also occur in the middle of a word and must be correctly ordered).

A temporary workaround is possible, but it requires encoding the vowel E as a separate letter in isolation, using a non-breaking space to hold it. But this has caveats, notably because it breaks the logical ordering of words, and does not warranty that the letter shown in isolation this way will not have spacing on both sides, increasing the normal side-bearings (unless the TrueType or OpenType font contains a special kerning or positioning pair for the space glyph followed by the spacing glyph of the diacritic vowel, to properly adjust the width and placement of the combination; but for now, no TrueType or OpenType font contain such kerning pair, despite of the fact that the Unicode standard specifies that all diacritics should be properly shown in isolation by encoding it after a space (either U+0020 for the usual space or the stronlgly recommanded non-breaking space U+00A0).

This issue is in fact not specific to the Buginese script, but occurs with any Brahmic script that uses prepended diacritics (for example the Devanagari script, also for a vowel, requires reordering support in the text layout/shaping engine itself rather than within tweaked tables in TrueType/OpenType fonts; all other solutions are not portable and will break the Unicode conformance for correctly supporting the script).

verdy_p (talk) 15:15, 23 July 2011 (UTC)