Fixed many bugs in the code for latinify, added the option to the html, and published latest to npm as 15919ify@2.0.2. Also, known error, dont put latin text in the latinify input, it will give out undefined. punctuation have been allowed to passthrough. also, playfair display updated, so i had to switch the branding back to playfair.

For the final few devlogs, i have decided to add another giant feature, the latinifier, which takes text in normal scripts and converts it into our format. its already too late at night bruh

Published to NPM!!!!!

The reason I wasnt able to publish earlier is because firefox kept throwing errors, and the fact that fido:// key thingies didnt work.
Today i had the exttremely smart idea to try and use Chrome, and then was forced to use the Passwd mgr, but i finally published it!

Just added more of the lanaguage typing instructions MDs, linked them up to the main MD. Also, I found many bugs in the mappings, which i fixed. (Gujarati had chandrabindu mapped as tN and not tM, Bengali-Asamiya had more bugs like the uhh Letter II was used inplace of symbol II accidentally, and some devanagari mappings were not removed.).

• Fixed copy, now can copy without adding “c” to the input.

FAQs yall been asking on the rating

Do you know all these scripts?

Uh, no, not most of them. I know Malayalam (native), Devaagari, English (learnt in school), Tamil and Kannada because I like to learn stuff when i go on tours (im a nerd lol), and i learnt many scripts along this project. I didnt have to “conform” most of the stuf, because most Indic languages are pretty similar, and also because UNICODE and other organisations have already done the work on mappings, so i just had to implement that only. Occcasionally, I did ask forum posts on these langauge speakers, to fix any bugs and add features.

Is it a translator?

No, it is not a translator. It is a transliterator, it does not convert meanings, it converts sounds. Do not expect everything you type in to be a meaningful output. Often times, it is butchered, because the standard is pretty dumb, and no one ever uses it.

Why does it convert everything

Vide previous Question. So, most of everything gets transliterated, except when the sound DOESNT exist in the script, when it just ommits it entirely. Since sounds are converted, almost everything is processed.

What is this even used for.

Interational transliteration based on an International standard. Albeit it is quite stupid, and as a mallu, i feel it is very undeveloped. Only reason i devoloped this is because nobody made anything, and it was a fun project.

Why not add more scripts / langauges

Well, this project is based on the standard ISO 15919, which is limited to around 10 scripts, and i might have added more, because i trusted the wikipedia table too much. Not only do i not have any time, i also dont need to do something that isnt actually useful.

Why does this tool add a virama at the end?

Im sorry yall had to add the “a” at the end manually, but this is a slight limitation. Adding inherent virama might break someother langauges, and also other vowel signs. But i will try to see what I can do.

What is the arrow thingy in the corner

Manual refersh button so that you can manually click it to force a rerender. This is now pretty obsolete, but has existed, so idc.

Rewrote the README so that its actually usable for anybody implementing it. And I think all the features are done on this project, the only thing remaining is to iron out bugs, if any, and to maintain this repo based on issues from speakers

Added tibetan and sinhala and fixed many syntax errors i made while eepy. I also took the Descision to not do Thai and Nashtaliq for reasons of * thai has funny vowels not compatible perfectly with the current parser and would require a rewrite, *Nashtaliq already has many implementations and standards >I was busy with School so slight delay.

Today was quite unenventful and i was busy with school works, So, i just added Gujarati and Gurumukhi. The Next few are actually a bit tricky being Sinhala, Thai and Tibetan. Thai is very very complicated for me to get my head around (trust me, i tried), Sinhala just has too many letters (and therefore tokens, whcih i will add). Tibetan is also on the same level as thai, due to the phonetic change or sum shi that happened long ago, causing a difference in the written vs the spoken langauge.

So, I finally got to fixing a ton of bugs and also added Kaithi (almost dead script) and Saurashatra (not commonly used), and also a QOL onto the example html where you can now refresh without causing text to be entered. Very Much advise to check up, because last version, I had Malayalam’s virama swapped with the anuswara. Should be fixed now. Also updated the Odia’s autoAnu to be true, based on the research i did from natives.

Split Asamiya and Bangla into two seperate scripts, because I dont wanna cause another riot that Unicode had to face. (ie, Letter “ra” is different in the two langauges, but share the same script (the asamiya Ra was added to Unicode as an extension, which the natives didnt like. In my token based system, one would’ve been forced to be the main, so i split them up.)

Added Bangla-Asamiya script. The main challenge was that the 15919 standard was actually wrong on some parts. So I had to use CharMap on a native font, and I also had to cross reference the unicode block. But I did get it done. TIL: the anuswara maps to Ng in this script and not the sanksrit “-m” or “-n”, so there was that confusion.

So, I did Yet Another Refactor, now net -201 (+46, -251) lines in the 15919.js file after adding Odia. Odia is not a language I know too well, so I put up a post on an Odia subreddit to get info. So, will update as soon as get info. also updated the MD’s. From Now on, all the remaining lanaguges i do not have much knowledge in, and thus will take longer for an actual version, cuz i will have to do polls.

Added Devanagari support to the thing. Also, I had forgotten to add the MD for Telugu, so that is here as well, along with Devanagari MD. I also made imports by pkgmans easier.. Side note: I wish I could add the time required to add these induvidual files to main, but ill prolly get a reply of just use CLI git. And most of this stuff is just maintainer chores. Like I have to add and update the hosted ‘try it out’ page, otherwise it would’nt be good

So, I think I want to publish this npm or other JS pkgman’s, so that others can use it Easier. So I decided to make the whole project less dependant on the HTML and also took the repeated if’s out. Now it should be much better accessable in a console.

Due to popular demand during last ship, i decided that I would split the whole js file into the main logic file 15919.js and the dictonaries file dicts.js

Added an experimental QoL feature, that adds an Anuswara and replaces the regular ‘m’ char when a word is ended with a space, punctuation or a newline (/n)

I haven’t used Ai for the Css or the Html.

I have only used AI for js, especially only in the Dicts. The reason i got Kannada and Tamil done so quickly is because Tamil is just Malayalam but debloated (no chillu, so many less letters) and Kannada is just Malalayalam but only a slight bit of debloating (no chillu).
The reason that the github html doesnt match the css in repo, is because the Html in the repo is made deliberately empty due it only being an EXAMPLE!! It is not a finalised product. Also, the CSS is only in the repo because good practice. And, you can check the whole repo for the HISTORY of the CSS file. I did use the w3schools demos a lot to understand exactly how I can use flexboxes, and prevent broken errors. If you wanted to, you could download the HTML file I used in the Hosting, and that matches the CSS, because I made it literally in my home directory.