Yohan Yukiya Sese Cuneta 사요한🦣<p>Projects on my plate (in no particular order; or maybe it is in priority-order):</p><p>1. My personal <a href="https://c.im/tags/Hugo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Hugo</span></a> / <a href="https://c.im/tags/GoHugo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>GoHugo</span></a> boilerplate (with <a href="https://c.im/tags/a11y" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>a11y</span></a> (accessibility), <a href="https://c.im/tags/microformats" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>microformats</span></a>, <a href="https://c.im/tags/fediverse" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>fediverse</span></a>, <a href="https://c.im/tags/IndieWeb" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IndieWeb</span></a>, support)</p><p>2. <a href="https://c.im/tags/Filipino" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Filipino</span></a> language in <a href="https://c.im/tags/Hangeul" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Hangeul</span></a>. (Temporarily calling it <a href="https://c.im/tags/FilipinoHangeul" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>FilipinoHangeul</span></a>.)</p><p>So far, I've mapped the IPA phonemic between Korean <a href="https://c.im/tags/Hangul" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Hangul</span></a> and the Filipino language.</p><p>Inspired by:<br>a. <a href="https://c.im/tags/CiaCial" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CiaCial</span></a> Hangeul (actually in use)<br>b. <a href="https://c.im/tags/TaiwaneseHangul" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TaiwaneseHangul</span></a><br>c. <a href="https://c.im/tags/FilipinoHanzi" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>FilipinoHanzi</span></a> (Filipino language in Hanzi [Chinese script])<br>d. Taiwanese Kana</p><p>3. <a href="https://c.im/tags/AnsalonMUD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>AnsalonMUD</span></a> <a href="https://c.im/tags/MUDlet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>MUDlet</span></a> client.</p><p>I'm porting our <a href="https://c.im/tags/Lua" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Lua</span></a> / <a href="https://c.im/tags/LuaLang" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>LuaLang</span></a> scripts from <a href="https://c.im/tags/MUSHclient" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>MUSHclient</span></a> to MUDlet, as well as, create a new UI and other MUDlet widgets.</p><p>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 <a href="https://c.im/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Linux</span></a>, a native client is much preferred than using <a href="https://c.im/tags/WINE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>WINE</span></a>. </p><p>4. An update to the <a href="https://c.im/tags/Philippines" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Philippines</span></a> Unicode Keyboard Layout.</p><p>'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.</p><p>Whatever becomes the “law”, will be the next update for PUKL.</p><p>Layouts planned:<br>* A true <a href="https://c.im/tags/Baybayin" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Baybayin</span></a> layout.<br>* QWERTY (with Baybayin)<br>* <a href="https://c.im/tags/Colemak" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Colemak</span></a> (with Baybayin)<br>* <a href="https://c.im/tags/Dvorak" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Dvorak</span></a> (with Baybayin)</p><p>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.</p><p>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).</p><p>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.)</p>