Currently, Jelly has a code page that maps Unicode characters to bytes to avoid unprintables found in ASCII. Many of the characters used are multiple bytes (in UTF-8), but we score it as a single byte (as it represents a single byte).
Now, lets assume I write another "code page" that takes common language features in Python (or any other language), and maps them to shorter byte values.
For example, I could map
0x00, meaning that every print statement is now 1 byte. I do make the assumption that my python program doesn't have the null character in it, but I'm OK with that.
If you feel that the above is invalid because Python doesn't support my custom code page, then what if I make a custom language that is identical to Python, except that it uses my custom code page?
TL;DR: If I write a general purpose encoding for a language, can I still answer in the original language, and score it based on the encoding?