Skip to content

API dox: state explicitly expected encoding for KConfig key & group names

Friedrich W. H. Kossebau requested to merge work/kossebau/documentgroupnameencoding into master

While the API might have been once designed to allow random byte strings to be used as ids and only converted QString to UTF-8, the current implementation in many places assumes the byte strings passed via const char* or QByteArray are also in of UTF-8 encoding (or at least ASCII7-only). See e.g. KConfigGroup::entryMap() or KConfigGroup::name().

Stating the supported encoding explicitly should avoid any misassumptions.

@dfaure @davidedmundson @meven @davidre @ervin

Merge request reports