Request to add Makassarese in Translatewiki

Request to add Makassarese in Translatewiki

Hello, Good Day

I would like to ask for add Makassarese (mak) on translatewiki, especially in Latin script
I'm currently developing Makassar Wikipedia in the Incubator.

English name: Makasar, Makassarese
Native name: Basa Mangkasarak, ᨅᨔ ᨆᨀᨔᨑ, 𑻤𑻰 𑻥𑻠𑻰𑻭
ISO 639-3 code: mak
Directionality: LTR Script: Latin (Priority, common use), Bugis, Makasar

~Thank you, ᨔᨀᨆᨀᨗ ᨊᨀᨗᨄᨑ ᨔᨒᨆ :)

Han4299 (talk)06:19, 10 August 2022

Should the Latin variant be the default ([mak] insted of [mak-latn]), or should it be always suffixed ([mak-lant] and not just [mak])? Do you intend to use that default in a future wiki (or any future wikis that could exist)?

Note how Chinese for example is managed: it has no default [zh] enabled, only the two variants [zh-hans] and [zh-hant] are enabled, plus a legacy variant [zh-tw] with some distinctions from the fallback to [zh-hant])

I see that on the portal you tried to activate it, and hesitated with the "-1" suffix for script variants. The variants without "-1" is to be used for the bare language code; the variant with "-1" indicates that the language code will always be suffixed and the bare code will not be used. You can't have both at the same time. And the "no-" options must match together with the variant it disables in the portal with the same numeric suffix.

So my question here is whever you want [mak] (no "-1" in parameters of the portal) or [mak-latn] (with "-1") as the default to be enabled for translations in that language... If you consider Chinese, no default script is applied, and all translations are made in a suffixed language code for each variant. This is not the case for all languages that have some variants, such as Mongolian, or English (which has some variants e.g. in the Deseret script, but keep the default Latin script unsuffixed in the language code [en]).


Note also that the Portal:Mak is already created, but marked disabled (it will be enabled by a site admin after he creates one or more of the 3 variants; at that time the portal and its related categories can be unmarked; do not remove this mark, to avoid activating translation links in the portal that would actually not reach the intended target language, but would display the translation UI for another unrelated language).

Anyway you can already register yourself in the list of translators on the portal, and also update your own user page to use "mak" in your #babel box (these two are separate, because you could wantto indicate with #babel boxes your knowledge of a language, for example when communicating with other people, without desiring to translate to it; the registration in the portal indicates your desire to translate it and your effective activity into it; you may as well unregister from the portal if you abandon that project, while leaving the language in your user page, where you indicate the languages with which you prefer communicating with others).


(when the language has been effectively enabled, you'll see that Special:ActiveLanguages/mak (or maybe Special:ActiveLanguages/mak-latn?) no longer displays that the error message at bottom saying it is unknown or unsupported; when this is done, the portal may be updated to remove the "disabled" banner and to enable the correct translation link).

Verdy p (talk)07:56, 10 August 2022

Currently the use of Latin letters is very massive, even the majority now write them in Latin script. However, some cultural activists want to keep writing lontarak.

I'm also still in a dilemma with this. How best for this case?

On the one hand, I want to harmonize the Bugis Wikipedia which uses lontarak as its main system, but on the one hand its use is now less popular. People mostly use Latin letters.

Han4299 (talk)14:01, 16 August 2022
 

Google Gboard and Ethnologue say that the name of the language is "Mangkasara’", with an apostrophe in the end.

Are there any other sources that call it "Mangkasarak", with a "k" in the end?

Amir E. Aharoni (talk)07:36, 11 August 2022

I also agree, but the apostrophe represents a final glottal stop (which is never written when using the Bugis or old Makassar script). In the Latin script, that apostrophe is prefered, but some may still use a final 'k', which is an approximation of that glottal stop (which is not always pronounced, so the apostrophe is more acurate for spoken dialects that avoid it, as it is not really in the phonology).

Some won't like the ASCII apostrophe in some cnotexts where it is restricted, and the prefered curly apostrophe may not be easily typed no loacl keyboards. So the final k is an alternative. Things would be better with better support of that apostrophe on keyboard layouts.

We have identifical problems with Polynesian languages (depending on the region, that typical Polynesian consonants has severeal representations, different between what is use in Hawaii, French Polenesia or New Zealand, and also varying depending on dialects). The same occurs with Arabic used in Northern Africa or in Europe (but not alwyas preserving the same consonant distictions or confusing them in the orthography, even though they are clearly distinguished in the Arabic script and in the "standard" phonology of Arabic).

So all that is a matter or orthographic convention for Latin (and given that there's no Academic source to fix it, it's the user communities that decide what is best for them to support in their local community, but not necessarily by consulting all other users in other local dialects or living elsewhere).

Verdy p (talk)10:28, 11 August 2022
 

In Makassar language, the glottal sound greatly affect the meaning, for example

/pepe/ = mute
/pepeɁ/ = fire
/balla/ = layur
/ballaɁ/ = house

so, the glottal stop always be pronounced

Some Makassarese linguists agree to use "k" to represent the glottal stop because the sound only exists at the end. Most of the Makassar language learning modules at the school level use the Indonesian based system which was initiated in 1975 which was held at seminars and workshops on standardizing the writing of regional languages in Ujungpandang (now Makassar).

Writing apostrophes for glottal stops causes many errors in writing, sometimes they are not even written (even though there are glottal stops in them). Examples of baji pamai /bajiɁ paɁmaiɁ/, Jeneponto /jeɁneɁponto/, etc.

Asis Nojeng, a Makassar language expert and lecturer, believes that apostrophes are not letters but punctuation marks. source

In this speeling system, apostrophe to mark ʻmissingʼ (elided) letters in verb prefixes and encliticised demonstratives, e.g:
iami anjo = iami'njo
iami anne = iami'nne

Glottal stop in Makassare is the same compare as -k in Indonesian
batuk "cough" dan batu "stone"
Likewise in Makassar language
pepek "fire" and pepe "mute"

Most books from the Ministry of Education and Culture also use this spelling. For example:


For this reason I use the standard 1975 spelling.

This is for example Makassar grammar Structure of Makassar language Makassar Dictionary Pantun Makassar Makassar Poems Morphology and Syntax in Makassarese

Most of the learning modules in schools use this spelling Pappilajarang Basa Magkasarak Pappilajarang Basa Mangkasarak

Han4299 (talk)13:46, 16 August 2022

I wonder if with the Bugis or old Makassar Script, representing the final glottal may be possible using the sign for the letter 'ka' (with its final a/schwa normally implied), with an additional diacritic to mark its elision). This could be the sign of an evolution of the language.

For example in the Bugis script you can change a 'ka' (two slanted lines on top of each other) into a 'kə' by adding the vowel diacritic for 'ə' (schwa). Ususally that schwa is normally pronounced as a true vowel, but there could be conventions to no pronounce it at end of words so the elision is implicit. If this is not true for the modern language, a variant of the 'ə' may eventually be used to mark its elision (similar to "halant"/"virama" in Indic scripts, which usually, but not always is represented by a dot added below the cluster).

In Bugis, the dot below is already used to make the diacritic changing the implicit 'a' into a vowel 'u', but may be the two diacritics for 'ə' (looking like an accent above the letter) and for 'u' (dot below the letter) could have been combined, if clusters like 'kəu' or 'kuə' are not used (at least at end of words), and could have been appropriate to mark a final glottal.

The same remark applies to the Old Makassar script. But as it is no longer used in the modern language, we would need to find evidences: did they wrote a plain 'ka' letter or a 'kə' cluster, or nothing at all?

Now for Latin, it is a recent introduction. Initiators of the romanisation of the language may have hesitated to the sign(s) to use for the final glottal. This may be now more a concern if glottals can also occur and be distinctive in the middle, or at start of words (possibly because of phonetic evolutions of the languages, where some initial 'k' would no longer be pronounced, but not the vowel following; or for other cases where more complex vowel clusters were introduced where that 'k' was elided and replaced by a glottal sign, possibly mute).

All this is typical of Indic abugidas scripts (like Bugis and Old Makassar) even if the Latin alphabet is foreign to those conventions and now just separates most vowels and consonnants (sometimes by using digrams containing a consonnant for some vowels, like 'on', otherwise using diacritics like 'õ'). But the representation of glottal-like consonants has always been a debate between "latinists" (some even prefering to use a less common consonnants like 'q').

As long as there's no clear academic source fixing the orthographic rule for Latin, you may find variants! So the ISO 639 standard, CLDR for now use an apostrophe (a curly one, not the ASCII apostrophe-quote), but some people may have difficulty with it on their keyboards.

Some languages also have multiple glottal-like consonnants (this is the case for example of Polynesian languages, or Arabic, whose romanization also knows multiple variants). This concerns as well the transcription to other alphabetic systems (e.g. Cyrillic or Greek) or syllabic systems. And finally history will fix the usage (but sometimes several standards depending on the region of use and what is perceived as the major dialect for the phonalisation of the language... up to the point that languages then split in separate branches).

Verdy p (talk)17:38, 16 August 2022
 

I'm confused... Here, you are asking for the name "Mangkasarak". But on the Incubator, you changed the title to "Mangkasaraʼ".

Online, I can see both names. So what should be done?

Amir E. Aharoni (talk)15:37, 19 August 2022

I just conform to the ISO 639 CLDR standard

but I can return it back to the 1975 standard spelling version if that spelling is more acceptable on wikipedia, If possible

I thought, The 1975 spelling doesn't seem very accepted on wikipedia

But, Makassarese 1975 spelling system still widely used in book and taught in school

Han4299 (talk)02:27, 20 August 2022

You don't have to conform to CLDR if it's wrong. CLDR has many mistakes, and it's difficult to correct them in their system for technical reasons. Also, ISO 639 is separate from CLDR, and CLDR doesn't even have a name for Makassarese in Makassarese: https://unicode-org.github.io/cldr-staging/charts/latest/by_type/locale_display_names.languages__k-n_.html . If you refer to the name in Ethnologue, then it's also not binding—I often use it as an easily available source, but not necessarily as the final truth. I usually try to cross-check with other sources.

I don't strongly care about which of the two names to use here. Evidently, both Mangkasarak and Mangkasara’ are used in publications, so neither is wrong. If the people who are involved in writing the Wikipedia in this language prefer Mangkasarak, I will go for that, because I don't want to block this request.

I just hope that this is also comfortable for the general public of this languages' speakers. Be ready to change it some day if other writers or readers bring up strong arguments for Mangkasara’.

Amir E. Aharoni (talk)06:14, 20 August 2022
 
 
 
 

This is now enabled!

Please see your user page. I've added a list of useful projects there. Start from the top, "Most used / Most important".

Amir E. Aharoni (talk)16:37, 20 August 2022