more site variables for the localizersiteinfo module

I don't like to add these variables to the settings.php file.
It is too technical for some users. It is too technical also the concept
of 'variable' from my point of view.

The variables you have listed are contained in different interfaces.
I am thinking what is the best way to follow to implement it.
Adding a separate module for every interface is too complicated.

Another problem to solve is the translation interface.
At now we have some mixed approaches, and I really
don't like these. We must provide a coherent translation
interface.
We must have the same translation interface logic everywhere.

Lessons learned until now :
- adding fieldsets on the forms is not more possible
Some interfaces would become too much complex and too big
- translating switching the language seems to be the simplest option at now,
until we'll provide the Ajax translation interface

So, probably I'll suppress fieldsets and the translation will be available
switching the language, adding a switching block also in the form.

Then I'll rename localizersiteinfo to localizervariables
and then I'll concentrate all the translation features of the variables.

I think that the translation mechanism with Ajax needs more time to be implemented
and until then we need a clean and easy way to provide translation of
the variables.
The same technique will be implemented also for profile.

Slightly offtopic, but please ...

if you rename, could you call it localizer_variables, since it seems we can't agree on a shorter prefix?
The word separation helps readability a lot ...

> if you rename, could you call it localizer_variables, since it seems we can't agree on a shorter prefix?
I have to read the Drupal guidelines better then I'll take a final decision.
If using a shorter prefix doesn't collide with Drupal guidelines we'll go
with lc_ prefix.