So after tracking down a bug that impacts Unicode versions of Windows, I've been giving some thought to Unicode support in general- clearly geek.menu _should_ support Unicode in general, so that customized labels, etc can use extended characters. However, this support is likely to break previously configured versions of geek.menu. There are a couple of options - building a conversion utility, changing the configuration file name so that there is at least a backup to refer to, etc.
I'd like some feedback on your thoughts regarding this before I build the solution. The _best_ solution is probably to come up with a new name for the geekmenu.ini file, autodetect the old file and suggest a conversion, but that's quite a bit of work that I may not get around to for a long time. How do people feel about having to re-configure from scratch?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
So after tracking down a bug that impacts Unicode versions of Windows, I've been giving some thought to Unicode support in general- clearly geek.menu _should_ support Unicode in general, so that customized labels, etc can use extended characters. However, this support is likely to break previously configured versions of geek.menu. There are a couple of options - building a conversion utility, changing the configuration file name so that there is at least a backup to refer to, etc.
I'd like some feedback on your thoughts regarding this before I build the solution. The _best_ solution is probably to come up with a new name for the geekmenu.ini file, autodetect the old file and suggest a conversion, but that's quite a bit of work that I may not get around to for a long time. How do people feel about having to re-configure from scratch?