I am having a stressful time whenever a new QC version comes when checking all config and translation settings in files config.php and lang_en.php if there was some small change somewhere, to migrate old settings to the new files.
It recently occured to me that this problem could be alleviated a bit by changing these two files to INI format that is de facto a standard among projects as QC. There are many editors for INI files, for example http://initranslator.sourceforge.net/
All the transition would require would be to write a small library support for this - a snippet of code that would read/write from and to these files.
by the way, the INI Translator works quite well even if the the files you work with are *.php files. http://initranslator.sourceforge.net/
With it you can visually detect untranslated / non-existent entries in the lang files, mainly when looking for differences between files for various version of QC (for example the lang file for 3.0 and the lang file for 3.1).
Still I'd prefer transition to using INI files instead of PHP. That way you wouldn't have to care about ; and ' while working with those files.
This is cool parsing seems to be done for PHP, ready for implementation, here: http://www.php.net/manual/en/function.parse-ini-file.php
I especially like read/write support implemented here: http://www.php.net/manual/en/function.parse-ini-file.php#78221
Also, make sure you check this: http://sk.php.net/manual/en/function.parse-ini-file.php#69728 http://sk.php.net/manual/en/function.parse-ini-file.php#61875
I hope that with this much work done, Treewood will be able to implement INI config files support with a few keystrokes.
