On 2010-02-28 at 14:42:16 [+0100], Michael Pfeiffer <michael.w.pfeiffer@xxxxxxxxx> wrote: > Am 28.02.2010 um 14:16 schrieb Stephan Assmus: > > On 2010-02-28 at 14:07:59 [+0100], Michael Pfeiffer > > <michael.w.pfeiffer@xxxxxxxxx> wrote: > >> > >> Am 28.02.2010 um 13:45 schrieb Stephan Assmus: > >> > >>>> For printer driver and transport add-ons they could also provide an > >>>> interface to query their display name. IMO though this is a common > >>>> problem > >>>> and should be solved on the OS level. > >>> > >>> Maybe I am missing something, but what would "HP DeskJet" be called in > >>> German? and what about "Postscript" or "USB"? These are all names that > >>> don't > >>> get translated. Can you clarify what exactly you want to be translated? > >> > >> Just try to add a new printer with the Printers preflet and you will see > >> there are some drivers / transport add-ons where a translation is needed. > >> Like: "Preview" printer driver, "Save to File" transport add-on. > > > > Ok. But isn't the name already exported by the add-on? > > No, IIRC. That's more of an API/design problem, though. It's even worse with Tracker add-ons, where the shortcut key is encoded into the file name. Providing the UI name via an API function that can use a translated string seems to be the right solution. CU, Ingo