I suggest that before you issue any abbreviation. I suggest that before you issue any abbreviation. You should make sure it is known to everyone and that is done by simply defining it (even within brackets). I didn't for example get what is an IDE for example. This is not intended for someone in particular.

IDE ----> Integrated Development Environment.

You can use the Jargon File to help you decode most of the appreviations you find in the linux and open-source community.
Jargon File (http://www.tuxedo.org/~esr/jargon/)


Regards
Mohamed Eldesoky

I really meant this from a scientific point of view. We should follow scientific rules in presenting scientific terms. That is what I was pointing to, I don't want the meaning of the abbreviation myself (I heard about it but didn't check it out).

I'm sorry but even in scientific writings you don't go around and explain each and every abrevation as long as there are good glossaries available and the abbrevations themselves are widely adopted.

if I follow your advice then the whole point of using abbrevations (saving time) is lost.

for instance do you really want me to say RAM (Random Access Memory), and USB (universal serial bus), what about PCMCIA I don't even know what this stands for??

what if I tell you that GNOME is an abrevation?? obvioulsy whatever it stands for is irrelevant, and maybe you want me to type :-) (smiling) etc.

there are established guidlines on how to communicate over the net, they include abbrivations and emoticons people should learn them not complain.

cheers,
Alaa

How about making a file or something similar for this site that has most abbreviations used and instead make a link to it for every abbreviation used? That would be a good alternative, right? (Who said I don't know what Gnome and KDE stand for? May be again someone really don't).:)