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.)
@youronlyone So, in other words, they made it so even old computers who can do #ISO-8859-1 / #Windows-1252 but not #Unicode can still type such words with diacritics via Alt+NumKey combinations. But ē only exists in Unicode (maybe it first showed up on #Windows-1257 but that was only used by Baltic languages), so it can't be typed via Alt+NumKey codes (& not everyone knows that CharMap is a thing). @pilipinas@philippines@pinoy
I am currently designing a small toy-language and was considering making all strings proper #Unicode objects and all source files utf-8. Lo and behold, Unicode has recently published some guidance: #TR55http://www.unicode.org/reports/tr55/ I am, however, rather deeply concerned about the general strong preference for #blocklists over #allowlist, e.g. as recommended for identifiers. I get wanting to allow people to use their own language and script wherever possible, and therefore recommending switching from e.g. requiring type names to start with an upper-case character to blocking an initial lower-case character, thereby allowing the use of unicameral (without upper and lower case) scripts. But I have this deep gut-feeling that while the TR certainly solves some existing #vulnerability classes, it also opens up a huge amount of new ones with this general attitude. I haven't yet gone through the TR with a fine-toothed comb to allay that fear, but I'd appreciate input from anyone that has thoughts on the matter.
Today I am reminded that the difference between lazy "a la" and correct "à la" is called a "grave accent," not the pinyin 4th tone. We are doing french-english, not chinese-latin characters! #unicode In #emacs that's "LATIN SMALL LETTER A GRAVE"
How do you figure out what font(s) Discord desktop is using? Mine currently displays Japanese and Chinese text as Unicode "oh noes, I can't find a glyph" rectangles. There aren't any font settings in the app other than size. 🤷
What the hell is the deal with the "soon" emoji 🔜 . How did that get into the standard? It's got text in English fer chrissake. Who needed this so badly that this symbol was in sufficient circulation that they had to standardize it?
TIL that any #unicode#character is a valid #Wifi#SSID as long as your keep under 32 bytes. And yes, this includes exotic control characters. And I now have ssids that is just random #emojis. I challenge everyone to build an wifi fuzzer that finds an at most 32 bytes unicode ssid that can crash a device remotly when it tries to scan afters stations.
We live in the future now. It is OK to use Unicode everywhere. It seems bizarre to me that modern Internet services sometimes "forget" that there's a world outside the Anglosphere. Some people have the temerity to speak foreign languages! And some of those languages have accents on their letters!! Even worse, some …
MusicBrainz Picard is really good, open source and cross-platform. If your music folder is a chaotic mess of unsorted, untagged files, give it a try, it works like magic.
for last.fm users dragging their feet like me, because all those 'smart' quotes blow up your last.fm stats: there's an option to dumbify them. i wish i had known this a year earlier #MusicBrainz#LastFM#picard#unicode
After #GUI, I've now pushed implementation of a #TUI output in #Libervia#CLI frontend, which shows A/V call video streams directly into your terminal! It's using #Kitty or #iTerm2 image protocols, or #Unicode half-blocks (thanks to #termimage)
I'm not aware of any other CLI tools doing something similar (#XMPP or not). It's not as useful as GUI, but it's quite fun :)
Somehow I ended up having to explain the finger heart gesture to my coworkers on our standup this morning. Yes, I'm that cool. I've got my finger on the pulse of the youth. Also, who knew that finger heart is already in #unicode ?!
Years ago I mentioned "the little-known tapeworm operator": "\x{1F4A9}\x{0327}"
There is no such thing, but the comment confused people. I was just making an obscure (and crass) joke. \x{1F4A9} is a "pile of poo" emoji and \x{0327} is a combining cedille, that little wormlike accent you'll see in some foreign words: français.
perl -C -E 'say "\x{1F4A9}\x{0327}"'
💩̧
I know others often don't "get" my humor, but these jokes are for me. It's a bonus if others get them.