January 2010 - openSUSE Features - openSUSE Mailing Lists

[openFATE 305546] Support for NTLM authentication (proxy) in YaST and libzypp
by fate_noreply＠suse.de 13 Jan '10

13 Jan '10

Feature changed by: Mark Muhlestein (mmuhlestein) Feature #305546, revision 11 Title: Support for NTLM authentication (proxy) in YaST and libzypp openSUSE-11.2: Rejected by Christoph Thiel (cthiel1) reject date: 2009-07-16 18:02:44 reject reason: out of context for openSUSE. Priority Requester: Desirable Projectmanager: Desirable openSUSE-11.3: New Priority Requester: Desirable Requested by: Katarina Machalkova (kmachalkova) Partner organization: openSUSE.org Description: YaST and libzypp should work in an environment with proxy server requiring NTLM authentication. The feature consists of two parts: 1) YaST proxy module has to provide UI to let user choose NTLM and write configuration file (/root/.curlrc) accordingly 2) libzypp media backend needs to be adapted to read and understand such configuration( that is, accept also --proxy-ntlm option instead of bare --proxy only) References: https://bugzilla.novell.com/show_bug.cgi?id=440296 https://bugzilla.novell.com/show_bug.cgi?id=412137 Business case (Partner benefit): openSUSE.org: Significant for adoption in mixed datacenters where the proxy infrastruture is on MSFT assets. Discussion: #1: Federico Lucifredi (flucifredi) (2009-01-26 20:57:23) Sadly, there is a realistic business case for this in mixed datacenters. Some odd people like to use NTLM proxies, I will never understand why. this will be a headache to do :-/ + #2: Mark Muhlestein (mmuhlestein) (2010-01-13 18:10:39) + Many of the engineers at Dell Computer in Austin want to use openSUSE + 11.2 on their desktop machines. Dell uses a NTLM proxy on their + corporate network so a lack of this functionality is keeping them from + doing so. + This group of engineers are very loyal SUSE/Novell folks who are trying + very hard to help a SUSE desktop make inroads into Dell's corporate + environment. + Current number of engineers who cannot use the product is 50 - 60 + On a side note, they see this a glaring problem. I don't know how many + corporations use NTLM proxies but the gents at Dell seem to think it is + quite a lot. -- openSUSE Feature: https://features.opensuse.org/305546

1 0

[openFATE 307548] Make openFATE software available
by fate_noreply＠suse.de 13 Jan '10

13 Jan '10

Feature added by: Pascal Wallenius (pascalw) Feature #307548, revision 1 Title: Make openFATE software available openFATE: Unconfirmed Priority Requester: Desirable Requested by: Pascal Wallenius (pascalw) Description: openFATE appear to be a great tool for helping prioritizing feature development. I would love to be able to download it and use on my own. Perhaps make it available ready to run as a virtual appliance? (VMware, XEN, etc.) Thanks, Pascal -- openSUSE Feature: https://features.opensuse.org/307548

1 3

[New: openFATE 308522] Blacklist Updates
by fate_noreply＠suse.de 13 Jan '10

13 Jan '10

Feature added by: Mark Pirnie (markcynt) Feature #308522, revision 1 Title: Blacklist Updates openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Mark Pirnie (markcynt) Description: Users should have the ability to blacklist an update and never be reminded of it again. This can be done to an extent using the terminal but that's not perfect either. Because of this I have uninstalled the Updater applet and now use strictly zypper to run updates. The Updater applet will be promptly uninstalled by me on all versions of openSUSE until this feature can be added. Keep up the good work openSUSE team! -- openSUSE Feature: https://features.opensuse.org/308522

1 2

[openFATE 308334] Distribute individual letters across cell width and height (aka 均等割符)
by fate_noreply＠suse.de 12 Jan '10

12 Jan '10

Feature changed by: Kohei Yoshida (kohei_yoshida) Feature #308334, revision 23 Title: Distribute individual letters across cell width and height (aka 均等割符) Requested by: Kohei Yoshida (kohei_yoshida) Description: Distribute letters at equal intervals across cell's width such that the first and last letters are aligned with the left and right edge of the cell, respectively. Also support similar distribution mechanism in a vertical direction. This functionality is also known as Kin-tou Wari-fu (均等割符) in Japanese, and is very common operation among Japanese Excel users. Relations: - i#107467 - Excel import issue with cells with distributed content (url: http://qa.openoffice.org/issues/show_bug.cgi?id=107467) - i#107470 - Request for this feature in the upstream IZ (url: http://qa.openoffice.org/issues/show_bug.cgi?id=107470) + - i#53373 - Jusitification issue in Draw/Impress for Japanese text. (url: + http://qa.openoffice.org/issues/show_bug.cgi?id=53373) - User-contributed doc on text justification in Japanese text. (url: http://wiki.services.openoffice.org/wiki/User:Foral/Spec/Justification) Use Case: Sentences in the Japanese language do not normally break at each word unlike most Western languages. The normal justification functionality is therefore useless for the Japanese users. Instead, they typically justify sentences by adjusting spaces between letters, which is what this requested functionality will provide. Discussion: #3: Kohei Yoshida (kohei_yoshida) (2010-01-05 14:22:02) I've started looking into this. #4: Kohei Yoshida (kohei_yoshida) (2010-01-05 17:36:46) Here is the initial hurdle: Calc uses XSL-FO for all text formatting, and fo:text-align specifies the alignment of a text (I assume for both horizontal and vertical directions). The bad news is that, this attribute does not allow a "distributed" alignment, but in order for us to implement this feature, we need that to allow a distributed alignment. Reference: http://www.w3.org/TR/xsl/#text-align #5: Kohei Yoshida (kohei_yoshida) (2010-01-05 17:45:10) (reply to #4) Well, I guess I could use the "justify" alignment and additional flag to specify how the content is justified. The spec allows user-agent- specific justification algorithm, so it's doable without breaking the standard. #6: Kohei Yoshida (kohei_yoshida) (2010-01-05 17:49:15) (reply to #5) And we could perhaps use the 'text-justify' attribute to specify the justification algorithm. See below: http://www.w3.org/TR/1999/WD-i18n-format-19990910/#a5 #7: Kohei Yoshida (kohei_yoshida) (2010-01-05 17:59:37) (reply to #6) This one is the latest spec of the fore-cited: http://www.w3.org/TR/i18n-format/#text-justify #8: Kohei Yoshida (kohei_yoshida) (2010-01-08 12:39:43) Ok. Here is how I've decided to store this in ODF. For both normal justifiation and distributed justification, the style attribute 'fo:text-align' is saved as 'justify'. Then, for the distributed justification, an additional style attribute 'csstext3:text- justify' gets stored with a value of 'distribute'. For the normal justification, either this value is 'auto', or this attribute won't get stored at all. It took me a while to get to this point since OOo's handling of style attributes and how they are exported to xml are very complex. But I eventually got it to save and load correctly. #9: Kohei Yoshida (kohei_yoshida) (2010-01-11 13:23:40) For alignment in vertical direction, the current ODF uses style: vertical-align attribute which can be either one of: automatic, bottom, middle, top. First, we need to add a new alignment type 'justify' to the style:vertical-align, and use another attribute to specify the justification method. This would be similar to how the horizontal justification is handled. The problem is that we can't reuse the same 'text-justify' attribute name since that would clash with the horizontal justification method attribute. We need a new attribute name for this to avoid such naming clash. The first name that comes to mind is style:vertical-justify , which specifies the same set of values that the csstext3:text-justify supports. Of course, this imlies that to finalize this feature we need to get blessing from the ODF TC, which may not happen in a timely manner. We need to come up with a "solution" for that as well. #10: Kohei Yoshida (kohei_yoshida) (2010-01-11 22:20:20) So, I was wrong in thinking that this would be a very simple task. Not at all... Calculating text / char spacing involves at least 3 modules: sc, svx, and vcl. So, while the text attributes themselves originate from sc, the actual drawing of the text is done by svx and vcl. On the bright side, once we implement this feature, it would be trivial to extend this support to Draw and Impress as well, since those two apps simply re-use the same text rendering code. #11: Kohei Yoshida (kohei_yoshida) (2010-01-12 15:38:08) (reply to #10) Finally found where the text justification code is. Luckily fixing this there will automatically fix it for all of Calc/Impress/Draw for the Japanese text processing. + #12: Kohei Yoshida (kohei_yoshida) (2010-01-12 16:01:07) (reply to + #11) + Just fixed i#53373 (http://qa.openoffice.org/issues/show_bug.cgi?id=53373) + by accident. -- openSUSE Feature: https://features.opensuse.org/308334

1 0

[openFATE 308334] Distribute individual letters across cell width and height (aka 均等割符)
by fate_noreply＠suse.de 12 Jan '10

12 Jan '10

Feature changed by: Kohei Yoshida (kohei_yoshida) Feature #308334, revision 22 Title: Distribute individual letters across cell width and height (aka 均等割符) Requested by: Kohei Yoshida (kohei_yoshida) Description: Distribute letters at equal intervals across cell's width such that the first and last letters are aligned with the left and right edge of the cell, respectively. Also support similar distribution mechanism in a vertical direction. This functionality is also known as Kin-tou Wari-fu (均等割符) in Japanese, and is very common operation among Japanese Excel users. Relations: - i#107467 - Excel import issue with cells with distributed content (url: http://qa.openoffice.org/issues/show_bug.cgi?id=107467) - i#107470 - Request for this feature in the upstream IZ (url: http://qa.openoffice.org/issues/show_bug.cgi?id=107470) - User-contributed doc on text justification in Japanese text. (url: http://wiki.services.openoffice.org/wiki/User:Foral/Spec/Justification) Use Case: Sentences in the Japanese language do not normally break at each word unlike most Western languages. The normal justification functionality is therefore useless for the Japanese users. Instead, they typically justify sentences by adjusting spaces between letters, which is what this requested functionality will provide. Discussion: #3: Kohei Yoshida (kohei_yoshida) (2010-01-05 14:22:02) I've started looking into this. #4: Kohei Yoshida (kohei_yoshida) (2010-01-05 17:36:46) Here is the initial hurdle: Calc uses XSL-FO for all text formatting, and fo:text-align specifies the alignment of a text (I assume for both horizontal and vertical directions). The bad news is that, this attribute does not allow a "distributed" alignment, but in order for us to implement this feature, we need that to allow a distributed alignment. Reference: http://www.w3.org/TR/xsl/#text-align #5: Kohei Yoshida (kohei_yoshida) (2010-01-05 17:45:10) (reply to #4) Well, I guess I could use the "justify" alignment and additional flag to specify how the content is justified. The spec allows user-agent- specific justification algorithm, so it's doable without breaking the standard. #6: Kohei Yoshida (kohei_yoshida) (2010-01-05 17:49:15) (reply to #5) And we could perhaps use the 'text-justify' attribute to specify the justification algorithm. See below: http://www.w3.org/TR/1999/WD-i18n-format-19990910/#a5 #7: Kohei Yoshida (kohei_yoshida) (2010-01-05 17:59:37) (reply to #6) This one is the latest spec of the fore-cited: http://www.w3.org/TR/i18n-format/#text-justify #8: Kohei Yoshida (kohei_yoshida) (2010-01-08 12:39:43) Ok. Here is how I've decided to store this in ODF. For both normal justifiation and distributed justification, the style attribute 'fo:text-align' is saved as 'justify'. Then, for the distributed justification, an additional style attribute 'csstext3:text- justify' gets stored with a value of 'distribute'. For the normal justification, either this value is 'auto', or this attribute won't get stored at all. It took me a while to get to this point since OOo's handling of style attributes and how they are exported to xml are very complex. But I eventually got it to save and load correctly. #9: Kohei Yoshida (kohei_yoshida) (2010-01-11 13:23:40) For alignment in vertical direction, the current ODF uses style: vertical-align attribute which can be either one of: automatic, bottom, middle, top. First, we need to add a new alignment type 'justify' to the style:vertical-align, and use another attribute to specify the justification method. This would be similar to how the horizontal justification is handled. The problem is that we can't reuse the same 'text-justify' attribute name since that would clash with the horizontal justification method attribute. We need a new attribute name for this to avoid such naming clash. The first name that comes to mind is style:vertical-justify , which specifies the same set of values that the csstext3:text-justify supports. Of course, this imlies that to finalize this feature we need to get blessing from the ODF TC, which may not happen in a timely manner. We need to come up with a "solution" for that as well. #10: Kohei Yoshida (kohei_yoshida) (2010-01-11 22:20:20) So, I was wrong in thinking that this would be a very simple task. Not at all... Calculating text / char spacing involves at least 3 modules: sc, svx, and vcl. So, while the text attributes themselves originate from sc, the actual drawing of the text is done by svx and vcl. On the bright side, once we implement this feature, it would be trivial to extend this support to Draw and Impress as well, since those two apps simply re-use the same text rendering code. + #11: Kohei Yoshida (kohei_yoshida) (2010-01-12 15:38:08) (reply to + #10) + Finally found where the text justification code is. Luckily fixing this there + will automatically fix it for all of Calc/Impress/Draw for the Japanese + text processing. -- openSUSE Feature: https://features.opensuse.org/308334

1 0

[New: openFATE 308346] Make notifications work even after evolution window is closed
by fate_noreply＠suse.de 12 Jan '10

12 Jan '10

Feature added by: Atri Bhattacharya (badshah400) Feature #308346, revision 1 Title: Make notifications work even after evolution window is closed openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Atri Bhattacharya (badshah400) Description: Evolution has a notification-plugin that currently is supposed to work only when the main window of evolution is running. After closing the evolution window one does not get notifications for new mail arriving, even though he/she might have selected the check for new mail every X min option. The feature request is to make the notifications in evolution work even when evolution is closed (Ctrl+W), so that the system tray icon shows up whenever evolution knows of arriving new mails despite the main application not running (evolution-data-server still running in the background). Thus, firstly evolution has to have knowledge of incoming new mails despite running only as a background service, and second, the notification-icon must show up whenever new mails are detected (as configured). This way users will get notifications for new mails without having to run the main app window all the time. This happens for alarms for events set up in evolution currently. -- openSUSE Feature: https://features.opensuse.org/308346

1 3

[New: openFATE 308471] KBasic
by fate_noreply＠suse.de 12 Jan '10

12 Jan '10

Feature added by: Lee Matheson (oldcpu) Feature #308471, revision 1 Title: KBasic Package Wishlist: Unconfirmed Priority Requester: Important Requested by: Lee Matheson (oldcpu) Description: I also added this as a desired package for openSUSE-11.3, being not certain where it belongs: https://features.opensuse.org/308466 KBasic is a programming language which is simply intuitive and easy to learn. It is a new programming language, a further BASIC dialect and is related to VB.NET™, Visual Basic®, Visual Basic for Application® and Java™. It combines many features of those tools and comes with built-in backward support for those tools and QBasic® as it is 100% syntax compatible to VB6, VBA and QBasic®. A web page with more information on KBasic to assist in any evaluation as to whether it is worth the effort to include in openSUSE package: http://kbasic.com/ (http://kbasic.com/) A big advantage is its reasonably similar look/feel will mean users migrating to openSUSE Linux from MS-Windows will be more at home with a programming language reasonably similar to what they are used to. Also, independant of what ever one may think of users migrating from a "Redmond" based operating system, in my view openSUSE needs a basic visual programming language for all openSUSE users who want a simple programming environment. It does not matter how the users arrived at openSUSE, nor where they originated from. openSUSE needs such a user friendly programming language environment. This kbasic package can provide that environment. -- openSUSE Feature: https://features.opensuse.org/308471

1 3

[New: openFATE 308527] mkinitrd should include firmware files
by fate_noreply＠suse.de 12 Jan '10

12 Jan '10

Feature added by: Marvin FourtyTwo (marvin24) Feature #308527, revision 1 Title: mkinitrd should include firmware files openSUSE-11.3: Unconfirmed Priority Requester: Neutral Requested by: Marvin FourtyTwo (marvin24) Description: mkinitrd currently (11.2) whines when a module requires firmware (detected by modinfo -F firmware), instead of just coping the required file(s). -- openSUSE Feature: https://features.opensuse.org/308527

1 2

[New: openFATE 308559] KDE Desktop Folder Bar
by fate_noreply＠suse.de 12 Jan '10

12 Jan '10

Feature added by: John Palmer (bugreprt) Feature #308559, revision 1 Title: KDE Desktop Folder Bar Buildservice: Unconfirmed Priority Requester: Desirable Requested by: John Palmer (bugreprt) Partner organization: openSUSE.org Description: Right mouse click option to turn on and off the bar on the KDE Desktop Folder Business case (Partner benefit): openSUSE.org: 99% of the time I enter the Desktop Folder is to run an application therefore having the bar appear every time is most annoying. For me it spoils a fantastic desktop environment! -- openSUSE Feature: https://features.opensuse.org/308559

1 3

[openFATE 308334] Distribute individual letters across cell width and height (aka 均等割符)
by fate_noreply＠suse.de 12 Jan '10

12 Jan '10

Feature changed by: Kohei Yoshida (kohei_yoshida) Feature #308334, revision 21 Title: Distribute individual letters across cell width and height (aka 均等割符) Requested by: Kohei Yoshida (kohei_yoshida) Description: Distribute letters at equal intervals across cell's width such that the first and last letters are aligned with the left and right edge of the cell, respectively. Also support similar distribution mechanism in a vertical direction. This functionality is also known as Kin-tou Wari-fu (均等割符) in Japanese, and is very common operation among Japanese Excel users. Relations: - i#107467 - Excel import issue with cells with distributed content (url: http://qa.openoffice.org/issues/show_bug.cgi?id=107467) - i#107470 - Request for this feature in the upstream IZ (url: http://qa.openoffice.org/issues/show_bug.cgi?id=107470) - User-contributed doc on text justification in Japanese text. (url: http://wiki.services.openoffice.org/wiki/User:Foral/Spec/Justification) Use Case: Sentences in the Japanese language do not normally break at each word unlike most Western languages. The normal justification functionality is therefore useless for the Japanese users. Instead, they typically justify sentences by adjusting spaces between letters, which is what this requested functionality will provide. Discussion: #3: Kohei Yoshida (kohei_yoshida) (2010-01-05 14:22:02) I've started looking into this. #4: Kohei Yoshida (kohei_yoshida) (2010-01-05 17:36:46) Here is the initial hurdle: Calc uses XSL-FO for all text formatting, and fo:text-align specifies the alignment of a text (I assume for both horizontal and vertical directions). The bad news is that, this attribute does not allow a "distributed" alignment, but in order for us to implement this feature, we need that to allow a distributed alignment. Reference: http://www.w3.org/TR/xsl/#text-align #5: Kohei Yoshida (kohei_yoshida) (2010-01-05 17:45:10) (reply to #4) Well, I guess I could use the "justify" alignment and additional flag to specify how the content is justified. The spec allows user-agent- specific justification algorithm, so it's doable without breaking the standard. #6: Kohei Yoshida (kohei_yoshida) (2010-01-05 17:49:15) (reply to #5) And we could perhaps use the 'text-justify' attribute to specify the justification algorithm. See below: http://www.w3.org/TR/1999/WD-i18n-format-19990910/#a5 #7: Kohei Yoshida (kohei_yoshida) (2010-01-05 17:59:37) (reply to #6) This one is the latest spec of the fore-cited: http://www.w3.org/TR/i18n-format/#text-justify #8: Kohei Yoshida (kohei_yoshida) (2010-01-08 12:39:43) Ok. Here is how I've decided to store this in ODF. For both normal justifiation and distributed justification, the style attribute 'fo:text-align' is saved as 'justify'. Then, for the distributed justification, an additional style attribute 'csstext3:text- justify' gets stored with a value of 'distribute'. For the normal justification, either this value is 'auto', or this attribute won't get stored at all. It took me a while to get to this point since OOo's handling of style attributes and how they are exported to xml are very complex. But I eventually got it to save and load correctly. #9: Kohei Yoshida (kohei_yoshida) (2010-01-11 13:23:40) For alignment in vertical direction, the current ODF uses style: vertical-align attribute which can be either one of: automatic, bottom, middle, top. First, we need to add a new alignment type 'justify' to the style:vertical-align, and use another attribute to specify the justification method. This would be similar to how the horizontal justification is handled. The problem is that we can't reuse the same 'text-justify' attribute name since that would clash with the horizontal justification method attribute. We need a new attribute name for this to avoid such naming clash. The first name that comes to mind is style:vertical-justify , which specifies the same set of values that the csstext3:text-justify supports. Of course, this imlies that to finalize this feature we need to get blessing from the ODF TC, which may not happen in a timely manner. We need to come up with a "solution" for that as well. + #10: Kohei Yoshida (kohei_yoshida) (2010-01-11 22:20:20) + So, I was wrong in thinking that this would be a very simple task. Not + at all... Calculating text / char spacing involves at least 3 modules: + sc, svx, and vcl. So, while the text attributes themselves originate + from sc, the actual drawing of the text is done by svx and vcl. + On the bright side, once we implement this feature, it would be trivial + to extend this support to Draw and Impress as well, since those two + apps simply re-use the same text rendering code. -- openSUSE Feature: https://features.opensuse.org/308334

1 0