My boss recently asked me to write a couple of very simple Python scripts for mobile translations. I had to convert files to replace &#123456 type sequences int

My boss recently asked me to write a couple of very simple Python scripts for mobile translations. I had to convert files to replace &#123456 type sequences into proper UTF-8 codepoints. I had to replace a bunch of unicode codepoints with a mirrored en-us side. I had to convert lines like "abc" = "def"; into a trivial .json file (a single flat dictionary). The task was very simple in Python, but would be absolutely trivial and fun in AWK if it a) had first class unicode support, including conversion b) had a support for quoted fields. I think it needs a new variable, like QC (Quote Character) of FD (Field Delimiter). I would put money on a kickstarter of another crowdfunding initiative to modernize AWK. I don't mean by slapping a Python or other programming language on it, but by fishing long-standing issues with it. I think a for loop like in Python, Rust and VimL would be a better fit to an otherwise simple language (only C-style fors are available in BEGIN/END).