On 6 February 2012 13:54, Darrell Anderson <humanreadable@...> wrote:
>> > Calvin, I responded to your
>> request for suggestions toward improving KControl. Let me
>> know when you need help with testing.
>>
>> Thanks! It's rather lengthy I need to review each of those
>> ideas.
>> Overall they look like valid choices. I like the idea of
>> separating
>> peripherals and other customizations. If not it's an 100%
>> agreement,
>> maybe a few small details.
>>
>> I am going to create a Etherpad with your ideas copied into
>> it. After
>> doing my own review I will be asking Trinity users and
>> developers for
>> further ideas and modifications.
>
> Okeydokey. How about a multi-phase approach?
>
> First address those items involving basic tree list reorganization. Those items require editing and creating some XML files but no code hacking.
>
> Second phase would be those items that require code hacking, such as moving group boxes from one location to another.
>
> Third phase involves renaming various categories. Although this sounds easy, I offer this phase last because of translations. Some of these should be straightforward, such as splitting Regional & Accessibility and Sound & Multimedia. Others will be a challenge, such as renaming Peripherals to Hardware and creating a new category named System Information. Maybe we do the best we can with various translation tools and hope for the best.
>
> The KControl tree list structure is defined in tdebase/applnk/kde-settings.menu. The individual tree list categories are named in various main/tdebase/applnk/kde-settings*.directory files. I haven't looked further to see how the sub items in each category are created.
>
> Darrell
>

That seems like a good approach.

As for Translations - what is the state of translations on Trinity in
general? I only use English so I am not really aware of it. How many
languages do we provide? do we have any translators willing to do
this?

Calvin