cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew C. Oliver" <>
Subject Re: file naming convention
Date Tue, 07 May 2002 12:51:11 GMT
Oh man...  This is very pedantic.  I prefer to see ACTUAL REAL 
documentation rather than rejected documentation based on some minor 
colloquiallism that irritated someone.  I'm an American, I work with 
someone from Austrailia, several folks from GB have contributed, Indian 
folks, etc.  And in text I have no difficulty reading ANY of their 
dialects.  The documentation should be written to an international 
audience and thats enough said.  Avoid slang and the such and you should 
have no trouble making the reader understand.  Of course seeing this is 
technical documentation that should NOT be hard.

This is the classic *stupid* Apache discussion, there is all kinds of 
important work to be done in the documentation and we're worrying about 
something pedantic.  The documenation should be understandable by an 
international audience.  Thats enough.  The rest is up to the contributer.


Robert Koberg wrote:

> What about standardizing on a lang and creating localization 
> sub-projects? I worked for a large British company and they did not 
> have a problem with us writing everything in American English. We then 
> set it up for their authors to localize to British (basically to not 
> offend (uggghhhh...) the British, not for usablity reasons...).
> Put the lang up for a vote on cocoon-users to see how many users would 
> prefer what language. Sure American English might be an *irritant* to 
> some, but the reality is coutries like NZ and GB are not at the 
> forefront of technology (even though you guys are)....
> feistily :) yours,
> -Rob
> Robert Koberg wrote:
>> Conal Tuohy wrote:
>>>> From: Diana Shannon []
>>>> On May 5, 2002, David Crossley wrote:
>>>>> Another issue to add to the list is standard spelling.
>>>>> Considering that we are talking English, i would prefer
>>>>> to see British English spelling rather than a dialect,
>>>>> such as Americanization. For example:
>>>>> howto-visualise-sitemap.html rather than
>>>>> howto-visualize-sitemap.html
>>> As a New Zealander, I also find American spelling an irritant: I'm 
>>> always
>>> typing "serialise" instead of "serialize", for instance, but I don't 
>>> think
>>> it's worth losing sleep over. (Or should that be "lozing sleep"? ;-)
>> This has been raised on the CSS list a few times. It is relevant 
>> there because you do alot of guessing in CSS (at least when starting 
>> out...). What is bad: color is used instead of colour, but gray is 
>> used instead of grey. I don't think it is a major issue for doc 
>> files, but if people do hack URLs (I agree that usability studies 
>> show that people do not usually hack URLs), then it could be annoying.
>> I just wanted to bring this up. I am not sure the lang 
>> standardization would be better than not for cocoon-docs...
>> best,
>> -Rob
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
>> For additional commands, email:
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, email:

To unsubscribe, e-mail:
For additional commands, email:

View raw message