Quote:
Originally Posted by ah-
What exactly do you mean by this? The only versioning scheme that would make sense at the moment would be to include the git revision somewhere or to use the date as a version.
|
Well, every piece of software has a version number - guess why?
Quote:
Originally Posted by ah-
I think at the moment you have to manually chose the language but that should improve in the future.
|
How can I chose the language manually?
Quote:
Originally Posted by ah-
Or do you mean that the order is different/some things are named differently?
|
Some things are named differently.
Quote:
Originally Posted by ah-
Also about the INI, I'm not sure what to do with it. Creating the ini file automatically creates versioning problems when the options change in the future and the ini gets out of sync. Also I'd prefer if it were unnecessary to edit any config files by hand.
|
That should be simple. Parse the old file. If an entry exists, used also in the new version, copy the whole line. If an entry not exists, create it with a default value. If an option exists no more, jump over. Then create the new INI and overwrite the old.