One more note: while fixing this, I found a bug in our code: for settings of enum type, if the settings schema was created from a .ini file, the VariantMap returned by the registry metdata() method returned the enumerators in a field named "displayValues". However, when the settings schema was created from a JSON string (as is the case for remote scopes), the same thing in in the VariantMap was in a field named "values".
I'm not sure whether that affects the shell; probably best to double- check. It is "displayValues" for both now. If the shell looks for "values" as the key for enum definitions in the scope metadata, it needs to use "displayValues" instead. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1393438 Title: "Enable location data" string displays untranslated Status in “location-service” package in Ubuntu: New Status in “unity-scopes-api” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu: Confirmed Bug description: Using rtm 162 on krillin, several of the dash screens have a "enable location data" option, that strings seems to not be translatable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1393438/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
