I found a way to write the #Filipino leading sound /ŋ/ (Ng̃) in #Hangeul by “reviving” an obsolete Jamo.
(NOTE: the samples below are using the Pilipino Hangeul [work-in-progress] adaption/rules.)
Ex:
ᅌᅡ욘 (nga·yon) = EN: today
ᅌᅵ삔 (ngi·pin) = EN: tooth
I also separated (R) and (L), like how they did in the #Ciacia language.
Same character: ᄙ
Ex:
빠다ᄙᅡᆺ닷 (pa·ta·las·tas) = EN: commercial
ᄙᅡ밧 (la·bas) = EN: outside; go out (depending on usage)
I was thinking of using another obsolete Jamo (ᅏ) for the /t͡s/ (Ts) sound, but ㅊ /t͡ɕʰ/ (Ch) can fulfill that role as well.
Ex:
차차 (cha·cha) = short form of “charter change”; or the dance chacha.
초꼬라데 (tso·ko·la·te) = EN: chocolate
차아 (tsa·a) = EN: tea
Ññ (enye) is, for now, transliterate.
For the Kr sound, like in “krus”, maybe we can use ㅋ since we don't have a /kʰ/ (Kh) sound in Filipino.
Vowels like Filipino “Ee” which can be either /ɛ/ (ae) or /e/ (e).
This one is tricky because the Filipino “Ee” sound can change depending on, for example, a person want to deliver a word with endearment, but the meaning never changes. So an /e/ sound can become an /ɛ/ sound, while retaining its meaning.
I actually had no idea about this “Ee” /e/ (e) vs /ɛ/ (ae). The way Filipino vowels are taught in school is simply, well, /e/ (e). But the more I read online resources, the more I learn that we do make an /ɛ/ (ae) sound for the same vowel! How crazy is that?!
It's easier to use Hangeul and Kana to write pronunciations of Filipino words, than to use Filipino diacritical marks.
Last we were taught about Filipino diacritical marks was in Grade 4 or 5 (early 90s). I don't know why, but after that diacritical marks were totally forgotten.
Tracking it down, IIRC, it was late 90s / early 00s when it was officially removed by the KWF.
Sometime 2010, the KWF brought diacritical marks back, though limited.
In 2014 (or was it 2016?) the KWF introduced a new diacritical mark, the Filipino schwa. It didn't exist before. There are only like 4 Philippine languages with a schwa vowel. They added it in Filipino so words from those Philippine languages can be integrated into the Filipino language.
Here's my problem, no matter how many times I read the KWF document on Filipino diacritical marks, I can't get my head around it. 🤪 I understood it differently, or I remembered them incorrectly. 🤷🏽♂️ Or! I've been pronouncing a lot of words wrongly! 🤦🏽♂️
However, when I use Hangeul and Kana, I don't have to worry about diacritical marks. Both scripts have stable pronunciations, not like Latin characters where we have to use diacritical marks.
The only catch, the reader should be able to read Hangeul or Kana scripts, which most don't. 🤔 So, back to trying to get a grasp of Filipino diacritical marks. 🤯
Am I right that the Filipino diacritical marks represent the sound?
Examples:
e = neutral = abrupt soft stop?
è = high to low = abrupt hard stop? (paiwa?)
é = low to high = malumay? (malumanay?)
ê = low to high to low = ??
ë = the new Filipino schwa (no idea, since I don't speak the few Philippine languages where a Filipino schwa is needed).
Any experts out there?
(In the revived diacritical marks, we no longer use ē. IIRC, it used to represent a long vowel sound.)
So far, I've mapped the IPA phonemic between Korean #Hangul and the Filipino language.
Inspired by:
a. #CiaCial Hangeul (actually in use)
b. #TaiwaneseHangul
c. #FilipinoHanzi (Filipino language in Hanzi [Chinese script])
d. Taiwanese Kana
I'm porting our #Lua / #LuaLang scripts from #MUSHclient to MUDlet, as well as, create a new UI and other MUDlet widgets.
I like the current version of MUDlet, it has come far since I last tried it; and personally, is now better than MUSHclient. Not only that, MUDlet is cross-platform while MUSHclient is Windows only. Since I'm using #Linux, a native client is much preferred than using #WINE.
An update to the #Philippines Unicode Keyboard Layout.
'Was put on-hold indefinitely. There is a plan to submit a bill to the Senate and Lower House to standardised keyboards and keyboard layout for the Philippines.
Whatever becomes the “law”, will be the next update for PUKL.
Standardising this will ensure that the default keyboard layout for Windows, Mac, Linux, Android, iOS, will be the one we designed for Philippine / Filipino use.
In addition to that, physical keyboards will have the same layout, instead of keys flying here and there. If we need an extra key, then we'll include an extra key (like in the Japanese and Korean keyboards).
For this project, it's going to take a long time because my country is terrible when it comes to standardisation. Imagine this, only government agencies are required to use the SI/Metric system. Everyone else can use whatever they want, SI, Metric, Imperial, Traditional, or alien. (This is another project I'm thinking of taking on much later.)
En: radio #Filipino: radyo ᜇᜇᜒᜌᜓ (ra-di-yo) #Korean: 라디오 (ra-di-o)
What it immediately tells me is that the word was transliterated only. Not surprising because it's a "new" word and "modern" invention.
Interestingly though, both Korean and Filipino pronunciations are very similar especially with "ra". Direct transliteration would be "rey-di-yo" but in both languages it's "ra".
The #Hangul (#Korean writing script) lessons provided by #Duolingo is confusing if you're coming from English, or any Romance languages.
Different pronunciations.
Reliance on transliterations.
The focus on "lesson" achievements will throw a new student into semi-advance instead of starting with root letters.
Lack of explanations why (a) the pronunciations are different for the same letters or combination of letters (block); and (b) why the transliterations are similar in some cases.
Examples:
go 거 official transliteration is "geo"; pronunciation "go"
go 고 transliteration "go"; pronunciation "gu"
It's much better to hide the transliteration (not a feature though) and focus on pronunciation, otherwise, it'll be confusing.
Maybe in the advance levels it is clearer. But by the time the student reaches that, they probably learned the wrong pronunciations and rules; or gave up already.
The good thing I found, they teach the proper stroke.
Because they rely on transliteration to teach students how to read #Hangul (Korean writing script), it gets confusing as you learn more root letters.
For example:
ㅓ - eo
ㅗ - o
ㅜ - u
ㅡ - eu
In Duolingo, the transliteration "do" can be 두 or 도. To know the difference, you have to carefully listen to the pronunciation. The problem is, they use two female and one male voices each with different pronunciations.
However, in one such lesson you are asked to pick the correct Hangul for "do", with no pronunciation offered of what particular "do" it is. Again, emphasis on transliteration.
How can a student know the correct answer when 두 and 도 are in the options, and both were used before in earlier lessons?
Back to pronunciation, depending on the speaker (and rules that Duolingo didn't explain), ㅓ(eo) and ㅗ (o) can also sound as ㅜ (u) and ㅡ (eu).
Conclusion:
If you want to learn to recognise Hangul, then Duolingo is good. There also teach you the proper strokes.
But if you want to learn pronunciations and words and rules, get a lesson from native Koreans language teachers.
You see, Duolingo claims "scientists" were involved in creating their lessons but I don't see any sign scientists were involved. No logic in their lessons.
And I agree with the native Korean language teachers, if you rely on transliterations instead of learning it the natural way, you're setting yourself into disappointment and hardship.
You have to know the pronunciation. When you see Hangul characters, your mind should process it that way, not transliterating it first.
The official transliteration of Korean is geared towards linguists instead of pure pronunciation. A linguist understands why 가가 is pronounced "kaga" but is transliterated as "gaga". Or why 도 is pronounced "pu" but is transliterated as "do".
In other words, if you're a regular student and you rely on transliterations, you'll be confused and will think it is hard.
When you see 마마 your brain should naturally process it as such 마마. Your brain should never transliterate it first before you can understand it. 마마 means "your highness" and is transliterated and pronounced as "mama"; it doesn't mean "mother".
Learn to read Hangul, after that move to learning from native Korean language teachers, not Duolingo.