Comment 2 for bug 144698

Hello Johannes,

On 9/25/07, Johannes Sasongko <email address hidden> wrote:
> I'm working on this, but it won't be in 0.2.11 due to the high risk of
> (1) me running out of time, or (2) the fix being buggy.

Yes, such things tend to be very destabilizing, so that might be a
good idea to wait for 0.2.11 to be released before working on it.

> It will also break existing settings unless we have a settings upgrade
> mechanism, just like we have with the db.

I'm not sure how you could do such an upgrade regarding localized
column names. First, I fail to see how such a conversion could be done
without building a "reverse mapping" indicating the English
translation of a localized term (which would not be very easy to
build).
Second, the upgrade mechanism would then have to be locale-dependent,
so that you would have to make sure that the settings upgrade is done
using the same locale as was previously used for saving the settings.

So I would say that the quickest way to do things would be to:
1- check if column names were stored in English in the settings.ini file
2- if that was not the case, drop all "col_order" and "trackcol_*"
settings altogether.

This is very easy to implement, and would guarantee that nothing
breaks, and few informations are lost.

Cheers,
   François