Community
Participate
Working Groups
I20110124-1800. The new option sounds a bit complicated: &Store derived resources encodings in a derived preferences file How about: &Store the encoding of derived resources separately or &Store the encoding of a derived resource in separate derived preference file (second one is a bit long)
I like this one: &Store the encoding of derived resources separately
Created attachment 187572 [details] Patch v.0.1
The patch looks good. Will either commit to M5 or M6 (needs to be coordinated with the N&N entry).
Given the feature is new in M5 it makes sense to polish it. Committed the patch to HEAD and released into I20110126-0800.
Verified in I20110126-1800.