August 2012 - openSUSE Features - openSUSE Mailing Lists

[New: openFATE 314349] Migrate files, and settings & bookmarks from windows
by fate_noreply＠suse.de 24 Aug '12

24 Aug '12

Feature added by: Michael Doris (dorism) Feature #314349, revision 1 Title: Migrate files, and settings & bookmarks from windows openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Michael Doris (dorism) Partner organization: openSUSE.org Description: It would help users if, on first installation there was an option to migrate your files, email and firefox bookmarks. -- openSUSE Feature: https://features.opensuse.org/314349

1 1

[New: openFATE 311066] Autoconfiguration of Eucalyptus Cloud
by fate_noreply＠suse.de 24 Aug '12

24 Aug '12

Feature added by: J. Daniel Schmidt (jdsn) Feature #311066, revision 1 Title: Autoconfiguration of Eucalyptus Cloud Hackweek VI: Unconfirmed Priority Requester: Neutral Requested by: J. Daniel Schmidt (jdsn) Partner organization: openSUSE.org Description: Since end of 2010 the packages for Eucalyptus Cloud have been improved in order to work out of the box on SUSE systems. Nevertheless it requires a lot of manual configuration work to setup an entire cloud. The goal of this hackweek project is to autoconfigure as much as possible (avahi/zeroconf) and maybe provide a simple configuration tool to prompt for the remaining information and set it up. If time permits we try to provide SUSE Studio images for all Eucalyptus controllers. -- openSUSE Feature: https://features.opensuse.org/311066

1 15

[openFATE 307461] SFLphone SIP Client
by fate_noreply＠suse.de 23 Aug '12

23 Aug '12

Feature added by: René Krell (renekrell) Feature #307461, revision 1 Title: SFLphone SIP Client Package Wishlist: Unconfirmed Priority Requester: Important Requested by: René Krell (renekrell) Description: it is a 'must' for a good distribution to include a few really working SIP clients for internet telephony. I suggest to introduce SFLphone (http://www.sflphone.org) into the distribution. It works well with the latest stable version 0.9.6 and provides a GNOME and a KDE/Qt4 client. What do you want more. Futhermore this fills the space in timeline for a missing KDE4 SIP client (kcall isn't really usable and Twinkle stucks on Qt3). -- openSUSE Feature: https://features.opensuse.org/307461

1 4

[New: openFATE 314354] More integration with cloud based services
by fate_noreply＠suse.de 22 Aug '12

22 Aug '12

Feature added by: Michael Doris (dorism) Feature #314354, revision 1 Title: More integration with cloud based services openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Michael Doris (dorism) Partner organization: openSUSE.org Description: I'd like to see more cloud based synchronization & backup - Install dropbox by default - integration with Grooveshark from Amarok or Banshee allowing users to backup their music to Grooveshark servers - provide access via nuvola -- openSUSE Feature: https://features.opensuse.org/314354

1 0

[openFATE 300758] Show unneeded packages
by fate_noreply＠suse.de 21 Aug '12

21 Aug '12

Feature changed by: Jiri Srain (jsrain) Feature #300758, revision 143 Title: Show unneeded packages openSUSE-10.2: Rejected by Thorsten Kukuk (kukuk) reject date: 2006-08-02 11:31:19 reject reason: For SL10.2 we have to get libzypp really stable and fast before we add new features. Priority Requester: Important openSUSE-11.3: Done Priority Requester: Desirable Projectmanager: Important Requested by: JP Rosevear (jproseve) Product Manager: Federico Lucifredi (flucifredi) Partner organization: openSUSE.org Description: The package manager should learn to show unneeded packages (packages which are not required by other packages and are not in wanted selections) and allow to deinstall them like the popular debfoster/deborphan tools. A typical use case: user installs an application which pulls in some dependencies to test it, uninstalls the application shortly after or way later but the dependencies stay unused installed on the system. Commandline UI (zypper) only. References: https://bugzilla.novell.com/show_bug.cgi?id=166132 Discussion: #1: Jiri Srain (jsrain) (2007-06-05 13:46:00) Schubi, is there any possibility to make solver tell which packages are orphanized? It would be interesting especially if the packages which are marked for deletion were considered as non-installed (eg. if foo- devel is installed but marked for deletion and nothing else requires foo, then foo is orphanized). #2: Stefan Schubert (schubi2) (2007-06-06 11:04:04) (reply to #1) Currently not cause the solver has no information about who (user, package,...) has triggered the installation of a package. If we are storing this information it would be possible for solver to remove these kind of packages too. It is not simple but doable. By the way, we will have to store this kind of information in the future. E.g. we need to save the "keep state by user" in a database in order to regard this state in future solver runs. #3: Jiri Srain (jsrain) (2007-06-06 14:25:07) (reply to #2) Looks like a missunderstanding. Basically every package wihch is not required/recommended/suggested or doesn't enhance anything that is installed and not marked for deletion is IMO considered to be orphanized. If user eg. wants to remove a pattern including all its packages (which are not required by something else), solver providing this kind of information would help a lot (and I don't think that we would need any other information to be stored. #4: Stefan Schubert (schubi2) (2007-06-06 15:33:44) (reply to #3) I do not think so. What does "orphanized" mean ? Let me take your example from comment #1. foo should be deleted too if the user delete foo-devel and foo has been installed due the requirement of foo-devel. BUT the user will kill us if we are deleting foo although the user has installed foo explicit sometime ago in a seperate installation workflow. So this information ( The USER has installed foo) will be currently not saved and is needed here to decide if foo has to be deleted or not. #5: Stefan Schubert (schubi2) (2007-06-06 15:39:47) (reply to #3) Lets take your example concerning the erasing of patterns. That is much more complex. I have already described the problem here: http://en.opensuse.org/Libzypp/Solver#Known_Problems " Proper behaviour of erasing patterns" There are already some bugzilla entries: Bug 274283 - Delete iFolder from YaST makes eDirectory Delete mandatory Bug 238250 - YaST does not upgrade an Add-on Product #6: Jiri Srain (jsrain) (2007-06-08 16:46:32) See also https://bugzilla.novell.com/show_bug.cgi?id=166132 This is another use case for the same solver functionality #8: Federico Lucifredi (flucifredi) (2008-06-12 20:46:17) this should be commandline-only, definitely an advanced-user option. #9: Federico Lucifredi (flucifredi) (2008-06-12 20:47:28) cut from description: See Bug 140346 #10: Duncan Mac-Vicar (dmacvicar) (2008-11-03 11:24:53) As discussed in Prague, this could be done using the package history once we have a reader. #11: Karsten König (remur) (2009-01-19 10:09:49) How about using rpmorphan, I agree with flucifredi about the command line idea... http://rpmorphan.sourceforge.net/ And otherwise you could use their system to find orphanized packages and display them in yast but make clear that deleting -all orphanized packages will also delete the ones explicitly installed... (it only detects wether the package fullfiles any requirement...) #12: Ján Kupec (jkupec) (2009-01-19 14:48:38) (reply to #11) I'm not the solver developer, but i'm pretty sure it's easy (and probably more effective) to find the 'leaf' packages (that's what rpmorphan seems to do) using existing solver (see satsolver package). But we don't want to just highlight leaf packages, we want to remove unused packages, that is all leaves minus those explicitly installed. So we will feed the solver with this 'explicitly-installed' information. The package history will be the source of this info for now. Maybe later we find some way to store this info that could be used across tools (e.g. directly in the rpm db). So rpmorphan will be able to use this info as well. #13: Pavol Rusnak (prusnak) (2009-01-19 15:44:26) (reply to #12) Yes, that's good idea. Detecting leaf packages is the first step. Detecting which ones to remove (i.e. not explicitly installed) is the second. I think that rpmorphan shows all leaf packages, but it selects only the ones that start with "lib". If we strictly followed library packaging policy that would do the trick. btw. rpmorphan is packaged in Contrib (http://en.opensuse.org/Contrib) #14: Michal Smrž (ilfirin) (2009-03-07 20:05:22) (reply to #11) I am afraid of using rpmorphan to do this. Cause last time, I tested it, it wants to remove libdvdnav and libdvdcss libraries. This is very bad. It leads to many not advanced users to ask in phorums "Why OpenSUSE is not playing DVDs anymore?" I see many problems this could make. #15: Christoph Thiel (cthiel1) (2009-04-21 15:23:06) We don't have the resources to implementing this. Seems to be a prefect fit for a community project. #17: Piotrek Juzwiak (benderbendingrodriguez) (2009-04-22 07:58:47) Maybe the idea to accomplish this would be simply by using the packages. xml file and diff it. We can already export what packages we got right? So if it would compare the packages.xml before installation and after it would then delete it. There is a problem when installing many packages, they would all have to be "grouped" which pulled which dependencies. #20: Vladimirs Kuzmins (vovachaka) (2009-10-26 16:27:51) This feature is a specially important, now when we have distro upgrade, which changes a lot of dependencies and a lot of obsolete packages remain installed. Please, someone implement it! #21: Thomas Göttlicher (tgoettlicher) (2009-10-26 16:41:29) I've added a view for orphaned packages in yast2-qt-pkg. There is a package group "orphaned packages" similar to "suggested packages" and "recommended packages" in yast2-qt-pkg version 2.18.17. #22: Atri Bhattacharya (badshah400) (2009-10-31 14:55:26) (reply to #21) Thanks for implementing this much needed feature. But this feature does not work with the gtk interface in 11.2 RC2; please have this added for the final release of 11.2. #23: Kornél Jahn (cornail) (2009-11-02 07:48:05) (reply to #21) Tried to test this but didn't seem to work on RC2: Orphaned packages view is empty. E.g. installed blender, which pulled yafray. After uninstalling blender, yafray remained installed but didn't show up as an orphaned package. Also installing audacity or inkscape pulled a lot of dependencies which were not showed as orphaned after uninstalling them. #24: Kornél Jahn (cornail) (2009-11-02 08:06:38) (reply to #23) Since it is marked as done, I filed a bug for it: https://bugzilla.novell.com/show_bug.cgi?id=551771 (https://bugzilla.novell.com/show_bug.cgi?id=551771) #25: Ján Kupec (jkupec) (2009-11-30 14:18:55) (reply to #21) There has been a misunderstanding here. What Thomas implemented is a view of packages that no longer have update candidates (those which are probably no longer maintained, thus 'orphaned'). This very fate request (IMO) incorrectly uses the word 'orphaned' for what is better described as "unused packages" or "no longer needed packages", or "unnecessary packages". Definitely not orphans (deborphan/rpmorphan is also a misfortunate name IMO). Anyway, whether orphan or unused, this feature is not implemented yet, thus i'm reopening it for 11.3. #26: Ján Kupec (jkupec) (2009-11-30 14:21:27) reopening for 11.3 (see comment #25) #27: Ján Kupec (jkupec) (2009-11-30 14:30:44) I suggest to call these packages unused instead of orphaned . I don't want to decide this by myself, so please speak up. Here are my arguments: 1) the word 'orphan' describes something that has lost its parent(s). In this case, it is actually the child that was lost - a package that depended on other package has been removed. The parent package is still installed, but there's no more use for it - it's unused . 2) we (and a few other distros and communities as well) already use orphaned to describe packages that are no longer cared for - unmaintained packages, packages dropped from distros. #28: Ján Kupec (jkupec) (2009-11-30 15:05:21) (reply to #27) Thomas suggests that perhaps not needed (or no longer needed ) would be better than unused since 'unused' can be confused with 'not used by user' rather than 'not used by other packages'. #29: Roberto Mannai (robermann79) (2009-11-30 15:40:37) Undependent packages : packages which don't have any(more) dependency. #30: Kornél Jahn (cornail) (2009-11-30 16:15:08) I also support the not needed / no longer needed version. Orphaned is bad since it can be misunderstood, just like "undependent package", if Roberto meant to suggest it as a description for this phenomenon. Case A: If I install manually package X, which doesn't have any dependencies nor is it referred to by any other package, it is not a "not needed" one. 'Cause it was manually installed by the user. Case B: Package X is installed automatically as a dependency while installing package Y. Package Y is then removed, but X stays, with no other package referring to it as a dependency. X is then a "not needed" package. #31: Roberto Mannai (robermann79) (2009-11-30 17:00:02) (reply to #30) +1 Kornél Regarding Case A: of course "not needed package" is a subset "undependent package" - "not needed" catches the user's point of view and it is more precise. Nevertheless, determining that "not needed" packages is a hard job, so it could be a good starting point just knowing which are the "undependent" ones (at least as a first step). #32: Roberto Mannai (robermann79) (2009-11-30 17:47:05) (reply to #31) The user could have a graphical list of "undependent packages", which then he could mark each of them as "used/not used". The GUI then could suggest the "unused packages" for removal (this being a temporary but useful use case). #33: Ken Schneider (kensch) (2009-12-15 18:15:55) When you install a package using package management it checks to make sure all dependencies are also installed or adds them to the install list via the "Requires" feature. When de-installing the package check the list of "Requires" packages and see which ones can also be de- installed. That way there are no left over packages. If one of the "Requires" packages are also needed by other packages they are left installed. I am no where near being a programmer but that would seem to be simple to do. #34: Ján Kupec (jkupec) (2009-12-15 18:47:57) (reply to #33) Such procedure would also wipe out packages that you still want to use. E.g. you have nagios-plugins-zypper, which requires zypper. Now, 'zypper remove nagios-plugins-zypper' would realize that after removing nagios-plugins-zypper nothing requires zypper, and would want to remove zypper as well. So what your idea lacks is a list of packages that were installed in the past based on explicit request by user. The procedure must avoid removing these. See also c#12 #36: Ján Kupec (jkupec) (2009-12-15 18:47:02) So i'm renaming this fate request to 'Show unneeded packages' (to make it shorter) to avoid further confustion. #37: Don Hughes (dehughes) (2009-12-15 19:10:53) I also would like to see this feature. I currently use rpmorphan with a list of things that it will mark that I know that I need. I also occationally go through yast2 and try to uninstall things that I do not recognize and see if they are flagged as being needed by something else. Both time consuming and error prone. And, a lot of packages seem to be some what careless in what the require for prereqs - pulling in KDE,gnome, and X11 packages on text- only machines for example; which then triggers a flood of KDE, gnome, and X11 library installations which I then have to mannually uninstall and mark as taboo. On my external facing servers I do not like to have any extra/unneeded/unwanted packages to provide possible attack vectors. #39: Rafael Belmonte (eaglescreen) (2010-01-10 22:43:40) Hello, this is one of the main causes of I use more Debian/Ubuntu than OpenSuse. Debian & Ubuntu already have this implemented. I think this is a fundamental aspect to work in OpenSuse. Debian & Ubuntu can distinguish packages that were manually installed and packages that were installed just to satisfy dependencies. OpenSuse needs to do this too. #40: Tim Edwards (tk83) (2010-01-27 15:46:00) I'd also like to see this, Mandriva added it in a couple of releases ago and it's great. It's really missing in Opensuse #41: Eduard Huguet (eduardhc) (2010-03-02 15:55:43) (reply to #40) Agreed. Being a long time user of both Gentoo and Ubuntu, I was really shocked to discover that zypper was lacking this feature. Even more: when talking about Linux with friends I always make mention of this kind of "autoremove unneeded" option as one of the strong points of Linux package managing systems, as I was really taking for granted that any package manager out there had this feature included... Regards. #42: Rémy Marquis (spyhawk) (2010-05-02 17:13:32) Michael Andres started to implement this feature in Libzypp 7.4, see http://lists.opensuse.org/zypp-devel/2010-04/msg00033.html #45: Robin Knapp (rknapp) (2010-07-14 13:00:55) (reply to #42) --clean-deps works indeed, but what about just showing unneeded packages? It's mentioned in http://en.opensuse.org/Product_highlights#Package_management_with_zypper but I haven't found any information about this feature. #46: Moqi Ba (bamoqi) (2011-07-24 01:37:08) This FATE is marked as done but as of 11.4 "zypper rm -u" doesn't work without a package name. It cannot actively find and remove orphaned package which are auto-installed, like "apt-get autoremove" does. #47: Michael Schröder (mlschroe) (2012-02-13 12:34:53) (reply to #46) True. We can add that for 12.2, but the quality of the result really depends on knowing which packages were selected by the user and which packages were dragged in via dependencies. #49: Cristian Morales Vega (reddwarf) (2012-04-11 16:06:31) (reply to #47) That info is available already through the history, isn't? The only problem I know of is bnc#679213... that I have no idea if was fixed since the info is not public :-( + #50: Jiri Srain (jsrain) (2012-08-21 11:52:03) (reply to #49) + I have this information in the log of my 12.1. #48: Joachim Plack (jplack) (2012-02-13 13:58:53) For images generated in a SLEPOS environment, we would like the to reduce the footprint. So we'd like to find out all packages where last use (per read access time stamp) <= install time. This list we would the transfer back to the image creation server so that the next image gets reduce to what we really need. Btw. removedthe big list of rejected openSUSEs besides the first and last to get a better overview again while keeping the history + #51: Jiri Srain (jsrain) (2012-08-21 11:54:04) (reply to #48) + Jack, does this necessarily involve libzypp/zypper? I think that this + is a rather specific use-case, which can be scripted easily. + Besides, I suggest to handle this as a separate request - this one is + about unneeded, not about unused. -- openSUSE Feature: https://features.opensuse.org/300758

1 0

[openFATE 313536] Get rid of SuSEconfig.fonts
by fate_noreply＠suse.de 21 Aug '12

21 Aug '12

Feature changed by: Petr Gajdos (pgajdos) Feature #313536, revision 21 Title: Get rid of SuSEconfig.fonts openSUSE Distribution: Implementation Priority Requester: Mandatory Projectmanager: Mandatory Requested by: Andreas Jaeger (a_jaeger) Partner organization: openSUSE.org Description: There is no point to run that code after installation of every package (and it's not run when you use zypper or 3rd party tools anyways). That code should be only run as a part of post-install of the fonts packages as only those are affected. Relations: - Remove SuSEconfig (feature/id: 100011) Discussion: #1: Petr Gajdos (pgajdos) (2012-07-03 17:13:23) Added "fontpackage" package to the M17N:fonts. fontpackage is intended to common runtime deps of every font package (e. g. /usr/share/fonts/truetype) and fontpackage-devel for buildtime dependency of every font package. fontpackage-devel contains only one file for now, which installs on /etc/rpm/macros.fonts-config. For details see osc cat M17N:fonts fontpackage rpm-macros.fonts-config Example of modified font package is M17N:fonts/xano-mincho-fonts. Could you please express your opinion on this plan? #2: Petr Gajdos (pgajdos) (2012-07-04 09:39:25) (reply to #1) After rethinking I've choosen fontpackages-runtime and fontpackages- devel. #3: Thorsten Kukuk (kukuk) (2012-07-06 14:37:38) I'm not a fonts expert, but looks good to me, beside one thing I don't really like: fontpackages-runtime contains only one directory. I think we should drop that package and package the directory inside of the RPMs which contains fonts. This has the big advantage, that RPM will take care of the directory itself, if the last package using it is removed. Or the directory should be added to filesystem directory, which includes already the parent directory. #4: Petr Gajdos (pgajdos) (2012-07-10 21:32:54) Ok, submitted fontpackages package into factory. sr#127540. #5: Petr Gajdos (pgajdos) (2012-07-11 13:47:20) As far as I can tell, M17N:fonts are ready for removing SUSEconfig. fonts. There are few packages using %run_suseconfig_fonts macro: 844- ksc-pcf (forgotten font package to be moved to M17N:fonts) daps fonts- config plotutils susedoc texlive-bin tv-fonts (package maybe to be moved to M17N:fonts) x3270 xmahjong xorg-x11-fonts xterm Also ghostcript-fonts package is subject to change in this regard (% run_suseconfig -m fonts). Unfortunately I can do anything until fontpackages package is in factory, so this process is blocked by license issue of our own code :- / (see declined sr#127540). Maybe we could consider to accept package as is for now and change license later (of course Novell replaced by SUSE LINUX Products GmbH, Nuernberg, Germany or something like that). #9: Petr Gajdos (pgajdos) (2012-08-07 08:53:26) (reply to #5) I have issued appropriate submitrequests for packages above. I didn't care about building for older distributions because I always try to not add if-suse_version-bloat when not needed. Failing build of packages can be easily fixed by adding new fontpackages (link to M17N: fonts/fontpackages) dependency into project where affected package is located. #6: Petr Gajdos (pgajdos) (2012-07-30 09:22:45) https://bugzilla.novell.com/show_bug.cgi?id=772595 #7: Thorsten Kukuk (kukuk) (2012-08-02 12:09:22) (reply to #6) "You are not authorized to access bug #772595." About what is the bug and why is access limited? #8: Petr Gajdos (pgajdos) (2012-08-02 12:17:48) (reply to #7) This is default policy for legal issues I think. I have added you to cc of this bug. #10: Petr Gajdos (pgajdos) (2012-08-08 15:17:38) Request: #130395 submit: home:pgajdos/rpm -> Base:System Message: - remove %run_suseconfig_fonts macro (openFATE#313536); new macros using fonts-config directly exist in M17N:fonts/fontpackages State: new 2012-08-08T13:33:44 pgajdos Comment: <no comment> + #11: Petr Gajdos (pgajdos) (2012-08-21 12:05:19) + https://bugzilla.novell.com/show_bug.cgi?id=773575 -- openSUSE Feature: https://features.opensuse.org/313536

1 0

[New: openFATE 309558] ProFont
by fate_noreply＠suse.de 20 Aug '12

20 Aug '12

Feature added by: Thomas Dziedzic (gostrc) Feature #309558, revision 1 Title: ProFont Package Wishlist: Unconfirmed Priority Requester: Desirable Requested by: Thomas Dziedzic (gostrc) Description: This is one of the best programming fonts I have used. http://www.tobias-jung.de/seekingprofont/ Direct Download: http://www.tobiasjung.net/download.php?file=profont-x11.tar.gz -- openSUSE Feature: https://features.opensuse.org/309558

1 3

[New: openFATE 312859] Publicize Archives of Historical SuSE Releases
by fate_noreply＠suse.de 15 Aug '12

15 Aug '12

Feature added by: Anomyous Anomyous (jcat123) Feature #312859, revision 1 Title: Publicize Archives of Historical SuSE Releases openSUSE Infrastructure: Unconfirmed Priority Requester: Desirable Requested by: Anomyous Anomyous (jcat123) Partner organization: openSUSE.org Description: One can use file watcher and find Live Evauation ISOs for versions of SuSE/SUSE back to 8.0. All releases before 8.0 were deleted from the FTP servers in 2005 and 2007. There should be a special directory on the openSUSE file server where these ISO images of these historical releases' Live Filesystems can be downloaded. Of course, ensure these are marked "For Historical Purposes Only" and recommend downloading a recent release. Business case (Partner benefit): openSUSE.org: S.u.S.E., then SuSE, then SUSE, then SLE\openSUSE have a rich and far reaching history compared to other distributions. SuSE is one of the few surviving distros that go back into the 1990's. Each release of SUSE is a snapshot of what it was like to use Linux at one time. Knowing what the software looked like in the early days helps us better appreciate the distribution and is quite interesting to tinker with. A historical artifact of all our lives before the 1990's was something physically tangible. Now it is digital data. Putting out an archive of the oldest days of SuSE Linux would allow us to peer into the history of openSUSE, SLE, the Linux community and its various projects, free software and the development of computer technology in general. -- openSUSE Feature: https://features.opensuse.org/312859

1 3

[New: openFATE 312580] Add the packages: linux-atm-lib, smpppd and WvDial in: Live CD, USB Live...
by fate_noreply＠suse.de 15 Aug '12

15 Aug '12

Feature added by: Genix Info (genixinfo) Feature #312580, revision 1 Title: Add the packages: linux-atm-lib, smpppd and WvDial in: Live CD, USB Live... openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Genix Info (genixinfo) Partner organization: openSUSE.org Description: Add the packages: linux-atm-lib (http://sourceforge.net/projects/linux-atm/) , smpppd (http://en.opensuse.org/Smpppd) and WvDial (http://alumnit.ca/wiki/index.php?page=WvDial) in: Live CD, Live USB or installation DVD of openSUSE Linux 12.1 (http://en.opensuse.org/Main_Page) , can thus be made ââDSL Internet setup, the installation automatically, through automated configuration tool on CD Live, Live or USB installation DVD, I had to manually download and install packages, see the Mandriva Linux does it automatically, openSUSE Linux would have to install the needed packages automatically, as is done in Mandriva Linux (http://www.mandriva.com/) , facilitating the configuration of a DSL connection. -- openSUSE Feature: https://features.opensuse.org/312580

1 6

[New: openFATE 310161] Make Bento and www.opensuse.org translatable via PO files
by fate_noreply＠suse.de 15 Aug '12

15 Aug '12

Feature added by: Vojtech Zeisek (vojtaeus) Feature #310161, revision 1 Title: Make Bento and www.opensuse.org translatable via PO files openFATE: Unconfirmed Priority Requester: Important Requested by: Vojtech Zeisek (vojtaeus) Partner organization: openSUSE.org Description: It is possible to translate software.opensuse.org via PO file software-opensuse-org.XX.po i LCN i SVN. But more sites are using Bento theme. I did not find any way how to translate navigation bar, content of boxes in panels and so on of Bento theme. I'm not sure if content of the navigation line is same on all webs, but it is important to have translated ALL occurrences of Bento theme and translation has to be consistent - same for every site. Second similar problem is translation of content of www.opensuse.org/XX/ For example for Czech version I see mix of Czech and English version. Sometimes someone send HTML file and say "Please, translate it and we will include it to www.o.o", but it is not good way how to manage it. There is, for example, no way how to translate news or add language specific news. I'm not sure if PO files are best for translations of the web and Bento, but it is common and IMHO good way how to manage it. So, please, make ASAP Bento and content of www.o.o translatable and accessible for language specific edits. And keep translations of Bento easily consistent on all sites. Business case (Partner benefit): openSUSE.org: For localized, consistent and easily translatable openSUSE sites. -- openSUSE Feature: https://features.opensuse.org/310161

1 5