I very strongly recommend that an English style sheet be created for language
English is an awful language for describing technical concepts - this stems from its origins as a "pidgin" (trading language) which became a "creole" (native speakers of the pidgin) and went through these two steps multiple times.
Whilst it has the concept of strict ordering, in practice that's rather....."fluid".
That in turn can lead to very creative misinterpretations - which have caused serious interoperation issues on the Internet (and had deadly results in other fields)
As one example: "Clean the floor with a mop" and "Clean the floor with Bob" - Bob might get very upset
"Clean the floor using a mop" or "You and Bob, Clean the floor" are less likely to cause trouble
Almost all amule documentation is excellent and clearly understandable, but a style sheet will help ensure it stays that way
I very strongly recommend that an English style sheet be created for language
English is an awful language for describing technical concepts - this stems from its origins as a "pidgin" (trading language) which became a "creole" (native speakers of the pidgin) and went through these two steps multiple times.
Whilst it has the concept of strict ordering, in practice that's rather....."fluid".
That in turn can lead to very creative misinterpretations - which have caused serious interoperation issues on the Internet (and had deadly results in other fields)
As one example: "Clean the floor with a mop" and "Clean the floor with Bob" - Bob might get very upset
"Clean the floor using a mop" or "You and Bob, Clean the floor" are less likely to cause trouble
Almost all amule documentation is excellent and clearly understandable, but a style sheet will help ensure it stays that way