One question: changing from defaultFont to defaultFontV2 means that if I had a default font (which actually behaved as an override font) in v2.0.3 upon upgrading to v2.1 this setting will be completely lost (it will neither be a default font or an override font).

I think it would be okay for keep "defaultFont" and not use the V2 and consider this a "fix" of the behavior as well as the introduction of an override font which offers a similar behavior to what was offered before. We could include this in the FAQ and release notes so that people that were using these will have a way to update their settings.

An alternative would be to "upgrade" the defaultFont value to become the overrideFont. We could put that check in the same place where we have the check for whether to check the database: if defaultFont is set, clear defaultFont and set overrideFont (and user defaultFontV2 for the new setting). Not sure if it worth it. If we have clear instructions, it might be sufficient to "fix" the defaultFont behavior (and not introduce a defaultFontV2).

@hssm (since you looked at default font behavior before)