CorvusE wrote:

Am I crazy to think that this isn't the best forum for this sort of inquiry? I joined this list to keep track of the issues with the openSUSE beta and, to date, I've read far more about the spelling, punctuation, and pronunciation of software, than it's installation and use. Don't get me wrong, it's mildly interesting, but is it to the purpose of the list?

CorvusE, I understand your point, but there are really only two openSUSE mailing lists, the last time I saw. One was announce-only, and the other was general. See: http://www.opensuse.org/index.php/Communicate. If it were like the other SuSE mailing lists, where there exist too many for me to count now (see http://www.suse.com/en/private/support/online_help/mailinglists/) different mailing lists, I would post these discussions on the appropriate list. I thought [opensuse] is a better list for discussing how openSUSE is perceived in the world, rather than suse-linux-e. Wouldn't you agree? -- Shriramana Sharma http://samvit.org

robbinsc@email.arizona.edu wrote:

Quoting CorvusE <lists@pjsattic.com>:

...

On Sunday 14 August 2005 7:17 am, Shriramana Sharma wrote:

...

Slightly different from the capitalization issues thread. Also see the recent thread I started on the SuSE Wikipedia article.

Am I crazy to think that this isn't the best forum for this sort of inquiry? I joined this list to keep track of the issues with the openSUSE beta and, to date, I've read far more about the spelling, punctuation, and pronunciation of software, than it's installation and use. Don't get me wrong, it's mildly interesting, but is it to the purpose of the list? --

This IS the opensuse mailing list, so I suppose this would be as good a place as any for this sort of inquiry. It seems to be an ongoing debate - as you said, something about "spelling, punctuation, and pronunciation of software." It's starting to get rather old, but where else would this debate go? Perhaps after the beta phase, these initial issues with pronunciation and the name of the software, etc. will slow down/stop.

-Chris admittly I have not followed this thread too closely, however, I feel I need to ask..

Whats the issue? People seems to argue over SUSE, SuSE, SuSe, suse.... Lets look: michael@nemausa:~> rpm -qa | grep SUSE cups-SUSE-ppds-dat-1.1.20-105 michael@nemausa:~> rpm -qa | grep SuSE desktop-data-SuSE-9.2.42-20 yast2-theme-SuSELinux-2.11.2-3 bootsplash-theme-SuSE-3.1-41 gnome2-SuSE-0.1-454 SuSEfirewall2-3.3-18.2 michael@nemausa:~> rpm -qa | grep SuSe michael@nemausa:~> rpm -qa | grep suse skype-1.1.0.20-suse suse-build-key-1.0-665 susehelp-2005.02.14-5 suse-release-9.3-4 suselinux-userguide_en-9.3-6 susehelp_en-2005.02.14-5 suselinux-adminguide_en-9.3-4.2 michael@nemausa:~> So it would seem even devs at Novell don't know. Ok, so what do the websites say: http://www.novell.com/linux/suse/ All caps... http://www.opensuse.org/index.php/Welcome_to_openSUSE.org again.. all caps. What confuses me I guess, is that this seems to be a massive issue, yet Novell/SUSE can not agree themselves on a standard naming convention. Might be the best policy to use what is on the websites *shrug* but to continue to argue this point would be useless. As shown, SUSE is spelt atleast 3 different ways on SUSE 9.3 Mike

On Sunday 14 August 2005 22:14, Evert Hagen wrote:

SuSE =System und Software Entwickelung must be the right spelling.

SUSE (all caps) is the official way, since some time

On Mon, Aug 15, 2005 at 08:29:55AM +1200, Michael Honeyfield wrote:

Like I pointed out, Novell's latest SUSE offering doesn't honor that, so I guess that should be fixed ASAP to avoid pointless time consuming mail threads ;)

What you pointed out what that Linux is case sensitive and that there are different programs that have different kinds of spelling. The most this signifies is that at certain moments the spelling might have been different. If you look at the Novell website, it is clear that it is SUSE and the product is "SUSE LINUX Professional" Not SUSE Professional, not just SUSE, "SUSE LINUX Professional". I am sure they have better things to do then rename all programs from SuSE* to SUSE* or suse* or whatever and then have the problems of scripts that won't run anymore. houghi -- No matter what other nations may say about the United States, immigration is still the sincerest form of flattery.

Michael Honeyfield wrote:

the addition of a Provides: suse-release and a Obsoletes: suse-release will fix issues around a naming convention with packages.. its a non-event and a pointless arguement still...

Well okay, look at it this way: I'm a newbie to Linux so don't know how the different packages are capitalized. Linux is sensitive to capitalization, so won't it give an error when I try to execute the package SuSEfirewall2-3.3-18.2 by typing susefirewall2-3.3-18.2? At least if one standard convention were enforced, then one wouldn't have to worry about such things, and the broken scripts that houghi spoke of:

I am sure they have better things to do then rename all programs from SuSE* to SUSE* or suse* or whatever and then have the problems of scripts that won't run anymore.

Sure they have better (and more important) things to do than rename, which means I agree it's not as big a priority as many other things, but I'd like to point out that the priority should not exactly be low, either. [Besides how much difficulty is it going to be to tell the computer to search for all occurrences of filereferences with one capitalization and replace it with another capitalization?] Would you like it if one Linux maker had Gcc and another had gCC and another had gcc and another GCC? Because it's universally gcc, you and I have no problem running different flavours of Linux, and yet getting the same results. And documentation on the net or anywhere which tells the user to enter the word gcc becomes universal. Else they would have to add something like: "please check with your distro provider for the exact capitalization of gcc because Linux is case-sensitive and using a wrong capitalization will probably just give you an error 'no such file or directory'". Would you like that? I say that this problem of different capitalizations should have been cut out at the start, but now that it has been allowed to grow to a certain extent, it should not be allowed to proliferate anymore, a single capitalization being officially determined by Novell, and used thence *everywhere*. Or at least some official guideline that says: "The product name is SUSE, but in all packages, all small letters must be used as in susefirewall." Of course, such an official announcement will not prevent users from casually referring to their system as a Suse box or (from the olden days) a SuSE box. But when it comes to official stuff, which affects what kind of commands we enter, I think some guideline must be announced/recommended. After that, I stop starting/continuing threads like this which would *then* (but not now) be pointless. -- Shriramana Sharma http://samvit.org

Michael Honeyfield wrote:

So, arguing over it saying it has to be SUSE or SuSE or suse is pointless until SUSE/Novell fix it.

Precisely. Which is why I hope to get SuSE/Novell to fix it, by opening this topic in this forum, which is the only way I *can* get SuSE/Novell to fix it. This is how the thing about community-contribution works, right? I mean, I'm just an ordinary end-user, with a very small amount of programming knowledge, but I *can* contribute this way. -- Shriramana Sharma http://samvit.org

Michael Honeyfield wrote:

So, moaning about in on the mailing is not "fixing" it, however creating a bug report, taking ownership of this "issue" and following it through to completion is certianly much more proactive. So maybe that should be your course of action.

Thanks for the advice, and I'll consider it, while requesting you for a better choice of words than "moaning". Thanks. -- Shriramana Sharma http://samvit.org