Yohan Yukiya Seseㆍ사요한・謝雪矢

Yohan Yukiya Sese-Cunetaㆍ사요한・謝雪矢(ゆきや)・謝約翰ㆍיהוחנן

♾️ #ActuallyAutistic #INFP 🐬
✨ Appeared: Sports Seoul; The Daily Report Arirang

©️ License: #CCBySA4
❗ only represent myself

🇵🇭 #Philippines
#Bibliophile #Writer #WebDev

Interests
* #FreeCulture #OpenKnowledge
* #Kosher #Torah
* #Hiking #Archery #Running
* #Violin #Flute #Ppop #Kpop #Jpop #Cpop
* #Games #Anime #Pdrama #Kdrama #Jdrama

🔏 https://youronly.one/p/verified/

#ATmosphere: @youronly.one

#YourOnlyOne #T2pub #fedi22

  • 26 Posts
  • 38 Comments
Joined 3 years ago
cake
Cake day: April 29th, 2022

help-circle







    • Taglish is code-mixing.
    • Singlish is, I can’t even remember the proper terminology.
    • Kinglish/Konglish is actually a subset of Korean. It’s different from Singlish and Taglish.

    So many foreigners, and it’s understandable, mistake Philippine English as Taglish" Or, how it is supposedly similar to Singlish and/or Kinglish/Konglish.

    It is not. Philippine English is pure English. It is a combination of Australian, British, and American English, with Philippine languages and dialects (200+) influences. It also focuses on pronouncing the letters clearly, as it is written, and as “neutral” as possible.

    Example: We clearly pronounce “than” and “then”. You won’t hear us say “other then”, you’ll hear us pronounce it correctly as “other than”.

    We also follow what is commonly known as the “Oxford comma”.

    And when it comes to spelling variations, all are valid, you can freely mix them. Although there are cases wherein a specific use became common. Like, “center vs centre”. We don’t write, “Can you centre this?” We use “center” for that. But we write, “Can you go to that centre you went to and ask for this?” Which refers to an institution. But we generally pronounce both the same as “sen-ter” (some say “sen-tre” 🤪).

    Confused already? That’s only the tip of Philippine English. We form our sentences differently too. 🤣

    There is also the politeness/respect and formality levels from various Philippine languages and dialects also influenced the way we choose which English words to use and how we construct our sentences. It’s not much because English itself is limited and simple, but the influence is there.

    Oh, and the overused “po” gets mixed in Philippine English as well. It’s the only non-English word that gets mixed in a pure Philippine English sentence (well, sometimes “na” and “ka” too).

    • “Good morning po.”
    • “How are you po?”
    • “Yes, po. We’re on the way na po.” (overused)
    • “F*ck you po!” 🤣🤣🤣 (Seriously)
    • “How do you like your egg po?”














  • @lil5@fosstodon.org

    It’s not “Firefox-only” per se, it’s CSS. Firefox is fast when it comes to implementing updates that benefits multilingual and Asian support, and Chromium is either slow, implements a small part only, or just ignores it completely.

    (aside: Another good example is Ruby annotation. Firefox’s implementation of Ruby is up-to-date while Chromium’s stuck in 2010.

    And this is very very annoying, you have to design for Chromium when it comes to Ruby annotations; or use JavaScript to serve different Ruby codes per browser. Chromium is practically the “modern IE6”.)

    It’s the same with :lang().

    In Chromium, you still have to do it like this:

    :lang(en-GB), :lang(en-US), :lang(en-AU), :lang(en-NZ), :lang(en-PH) { }  
    

    In Firefox you can do it this way:

    :lang(en-GB, en-US, en-AU, en-NZ, en-PH) { }  
    

    or

    :lang("en-GB", "en-US", "en-AU", "en-NZ", "en-PH") { }  
    

    Another example, in Chromium:

    :lang(ceb-Tglg), :lang(pam-Tglg), :lang(fil-Tglg) { }
    
    :lang(ceb-Hano), :lang(pam-Hano), :lang(fil-Hano) { }  
    

    In Firefox:

    :lang(\*-Tglg) { }  
    :lang(\*-Hano) { }  
    

    or

    :lang("*-Tglg) { }  
    :lang("*-Hano) { }  
    

    ^_~






  • @BrikoX

    > The ability to opt-out of quote posts is also currently planned, which makes it that Mastodon’s implementation will not be compatible with other fediverse implementations of quote posting.

    Not surprising. Even before ActivityPub was announced, when the #fediverse was still powered by #OStatus, Mastodon was already breaking compatibility. There were countless of heated debates about almost every Mastodon-only “feature” they implemented that all other Fediverse devs were _forced_ to implement.

    And here we are with yet another.

    I wonder what will supporters of opt-out or anti-quotepost camp will do if the other Fediverse devs ignore this Mastodon-only “feature”, and just continue with the common implementation of quote posts? Are we going to see a new reason for “fediblock”, and finally fragment the Fediverse network?