I suggest to implement the following feature:
Allow .LST and .LBL files to be saved and opened in UTF-8 encoding.
A typical use case might be:
I know this is a tough one. Currently .LST files are UTF16 encoded. This makes perfect sense to support chinese, japanese and other language projects.
But in the year 2020 everyone uses UTF-8. With UTF-8 there is no endianess problem. The endian is always right. As a downside chinese and japanese language project files could get bigger, but it depends.
Direct manipulation of .LST and .LBL files will be easier because UTF-8 has the widest support nowadays.
It will also be the better encoding if combit, someday, will deliver LL for other platforms like Mac and Linux
The main benefit will be: I could save my layouts without problems in Git to get version management. I then could diff them to get a feeling what has changed to prior versions. This is not perfect but sometimes really helpful to get a clue what’s different.
Just for reference which problems could evolve by using git with UTF-16 encoding: utf 16 - Why doesn't Git natively support UTF-16? - Stack Overflow
If you implement this feature, please be aware of BOM and BOMless UTF-8 files. Other platforms prefer BOMless UTF8-files.