Mhhh... I was asking pointers to services-admin developers without realizing I was already speaking to one of them! How insigthful am I
Speaking about descriptions translations, aren't they a way to heavy burden to be carried on by the administration tool?
IMHO the descriptions (and their translations) should be contained within the upstart job definitions, like:
This is exactly what happens with .desktop files and insures that also custom programs installed by the user (also if out of official repositories, like skype and acrobat reader) get correcly listed in the menu with their translation (where available).
# mountall - Mount filesystems on boot
# This helper mounts filesystems in the correct order as the devices
# and mountpoints become available.
description "Mount filesystems on boot"
description[it] "Monta i filesystem all'avvio del sistema"
Since the service administration tool can't possibly be aware of every single service existing in the world and contain within itself all translations probably shouldn't try to handle the problem all on its own.
This is especially true if the development resources are limited: better focus on problems that can be solved easily than on ones which are unsolvable.
Anyway if some help is needed in the development of services-admin for Lucid I'd be glad to contribute (obviously if I'm able), if that's welcome, how can I?