Re: Debian Menu policy leads to confusion
On Sat, Jan 28, 2006 at 02:38:41AM +0200, Linas Zvirblis wrote:
> Bill Allombert wrote:
>
> >Try
> >
> >translate section->section
> > Apps/Database "Apps/Data management"
> >endtranslate
> >
> >substitute section->section
> > Apps/ Applications/
> >endtranslate
>
> Thank you, that worked. Things suddenly started making sense after
> couple hours of sleep. Anyway, I have one more question: are you going
> to support 4 level sections like "Apps/System/GNUstep/WildMenus", or
> should I make "translate_menus" flatten them? And what about unofficial
> 3 level sections, should I flatten them too?
Do not use translate_menus to flatten them, let them as is.
Note that menu actually allow programms to create there own 3rd level
(or 4th level) section for private purpose, to group related entries
(like xteddy and mozilla does). There is no need to document them.
> And here is hopefully last edition of my draft. It still is for "Apps"
> only. There are, however, some minor things I would like to change in
> other sections. Like renaming "WindowManagers" to "Window Managers" for
> example. Are things like this worth including in my draft?
Yes please do!
> Webmaster
> Software for web site editing, web
> programming and site administration.
> bluefish, screem, gphpedit
Well I don't really like the title "Webmaster" because it refers to the
user, not the software. How about "Web development" or "Web design" ?
> P.S. This is totally unrelated, but are there any plans expanding
> menufile format to include freedesktop.org style information for
> translations etc.? Would such feature be accepted if it was implemented
> by someone?
The question is whether there is enough interest to use them instead
of the global menu l10n. So far evidence are not compelling.
The cost of maintaining the translation inside the menu files is going
to be much higher than maintaining all the translation in a centralised
manner (like it is done currently).
Cheers,
Bill.
Reply to: