On Thu, Mar 20, 2014 at 10:08:56AM +0200, Antonis Tsolomitis wrote: > Στις 19/03/2014 06:29 μμ, ο/η ibid...@gmail.com έγραψε: > > Here's a fourth revison of desktop2dt. > > Changes: > > * export and test were changed for compatability with old shells like > > Solaris has > > * ~ was changed to $HOME because it didn't always get expanded. > > Does your script support the reverse process. I.e., remove an > integrated (by the script) app?
No, and I don't intend to: desktop2dt is about converting a desktop file to a dt action database, not about every aspect of integrating applications. > I did not tried this version yet, I will. But for an addition for next > version > think about adding a parameter that will add the application (in its group) > in the root menu. Like this: > > http://myria.math.aegean.gr/~atsol/newpage-en/software/cde/screenshots/cde-rootmenu.jpg > <http://myria.math.aegean.gr/%7Eatsol/newpage-en/software/cde/screenshots/cde-rootmenu.jpg> The root menu should be something you can handle with Debian "menu"; Debian mwm has rules to autoconfigure the menus like you're wanting. The only change you are likely to need is something like s/mwm/dtwm/g. I don't intend to duplicate the functionality of menu, for the reason I mentioned before. > > Still no multi-locale stuff. If someone has a way to figure out which > > locales to grab (two-letter) and where they go (CDE locale), I'm open to > > including it. > > > I do not know about other locales but since I am finishing with the > translation of CDE to > Greek I would like to support this. The two letter code is el. The CDE > locale will be > el_GR.UTF-8 > Of course if no "GenericName[el]=..." exists in the desktop file it > should fall back to US English. > The bigger questions that I have are: 1) How do we decide which locales to generate? Do we do "all" of them all the time, autodetect from $LANG, let the user specify some extra ones, or something else? If we do "all" all the time, do we hard-code a list or figure it out from /usr/dt/(some config directory)? (Shell script preferred.) The *easiest* way is to do one language at a time, and specify it something like this: -l el el_GR.UTF8 I'm getting the impression that it would be possible to grab the first two letters of the full locale, though. 2) In terms of shell script, what do I need to change to make to process_desktop() and the line that invokes it? What about the changes to -i and -a? I'm guessing that it would work to expect the two-letter name in $2 for process_desktop when we're producing something that's not in the C locale. 3) If I can't generate a localized action database, what do I do? This depends partly on how CDE handles dt databases that are present in the C locale but not others: if CDE falls back to the C locale (which I have gotten the impression is what it does), desktop2dt should skip desktop files that cannot be localized (in the case of Greek, if neither GenericName[el] nor Comment[el] are present). Thanks, Isaac Dunham ------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/13534_NeoTech _______________________________________________ cdesktopenv-devel mailing list cdesktopenv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cdesktopenv-devel
