https://bugs.freedesktop.org/show_bug.cgi?id=64176
--- Comment #11 from Patrick Ohly <[email protected]> --- (In reply to comment #9) > > Then that's where configuring the collation in the source config breaks > > down, because we don't have some entity which would rewrite the config when > > the locale changes - other than EDS itself, of course. And if EDS rewrites > > the config, the option becomes useless. > > I'm not convinced of that, from what I understand your requirements > are described by ICU as "phonebook" order, where "phonebook" order > does not exist in 'zh' locales, and the the default in 'zh' locales > is already "pinyin" (if your requirement was instead "pinyin", then > you would not expect "phonebook" order in de_DE locale at all). My expectation is that EDS does "the right thing" by default for each field, without some non-existent entity having to tell it what that is. By all means, let's add overrides for the default behavior in EDS, but let's keep these overrides optional. The overrides would be: - "phonebook" - enable phonebook - "no-phonebook" - disable phonebook - "pinyin" - enable pinyin - "no-pinyin" - disable pinyin And the defaults should be: - use "phonebook" for name fields (and only for name fields) in "de" and "fi" locales - use "pinyin" with Chinese Pinyin and Latin characters mixed (which is *not* the default in ICU) for all strings in Chinese It's quite likely that this knowledgebase will grow over time as more localization experts tell us about the preferences in their country. EDS might not be the best place to store such a knowledgebase, but where else can we put it? By not storing the default in the source config, we can fix the wrong default by upgrading EDS. If we were to put the setting into the config, it would be difficult to change later, because it would be uncertain whether it merely represents the old, incorrect default value or was chosen intentionally. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
_______________________________________________ Syncevolution-issues mailing list [email protected] https://lists.syncevolution.org/mailman/listinfo/syncevolution-issues
