On Jul 10, joost witteveen <[EMAIL PROTECTED]> wrote: >> It should not need duplicate data for these program but get the needed >> information from the native menu entry which comes with the package. >Please bear in mind that the menu system was designed when all >window managers available did not come with (usable) menu's. So, I see no reason it can't be modified to do the right thing.
>Another consideration should be that, although the gnome format >is reasonably OK, the format of most other (all except KDE?) window >manager's startup files realy dosn't allow using them as a basis I'm referring only to KDE and GNOME menu files. >> >Well, then I would like you to point out to just one such package. >> /usr/share/apps/Productivity/gnumeric.desktop, but it is a GNOME menu. >And how do you suppose a german using fvwm is going to make use >of that entry? The debian menu structure is there for all Like a menu can be made from the debian menu file it would be made from the GNOME menu. Or maybe from both, if needed. >debian window managers (over 10 of them), not just for GNOME. I'm not proposing we should switch menu format, only that we should use the information already present in gnome and KDE apps. >> >in the menu entry files: that way the debian menu tree will basically >> >always be mixed-language (for at least some languages), and entries like >> >"Dwww Konfiguratie" will basically indefinately live alongside >> >"Lilo Config", as some entries are translated while others are not. >> Why that would be different with your system? >That one is easy: because the translators would get a complete list >of all to-be-translated menu entries. And, unless the translators This is only a coordination problem. Just make a mailing list for translators were maintainers send the new menu needing translation. -- ciao, Marco
