Re: manual translation issues, part 2

From: Date: Sat, 30 Dec 2000 02:18:58 +0000
Subject: Re: manual translation issues, part 2
References: 1 2 3  Groups: php.doc 
Request: Send a blank email to phpdoc+get-969333423@lists.php.net to get a copy of this message
eschmid+sic@s.netic.de wrote:. > I hope you will not rewrite the "The Chicago Manual of Style" for PHP. > Hartmut told me the last days, he has also a copy and reread it. IMHO all > titles are wrong. "COM support functions for Windows" should be written as > "COM Support Functions for Windows". Most of my work history has been in US pre-press and printing fields, where the CMoS (and other MoS's) are vital. It's great for maintaining a consistant standard of writing across many print publications for a single language. Chicago Press, USA, English, print publications, to be exact. PHP documentation is *not* printed by the Chicago Press, though. To rephrase: We *are* re-writing a MoS for PHP. There's no reason to use CP's Standards, if we don't want to. CMoS happens to lack official guidelines for things like our function names, proper abbreviations for our databases, etc. There's also "Yale style", "Microsoft Style for Technical Publications", "New York Times Style", "Xerox publishing standards", Strunk and White's "Elements of Style", "Apple Publications Style Guide", "Columbia Guide to Online Style" "Canadian Style"(dundurn press), "Prentice Hall Style Manual" etc. etc. etc. My point is that choosing a standard isn't as critical as having one in the first place. If we _are_ going to standardize on a pre-written one (with some additions for our needs), it would be helpful if it was a book easily obtained on a global basis. -Ronabop -- Personal: ron@opus1.com, 520-326-6109, http://www.opus1.com/ron/ Work: rchmara@pnsinc.com, 520-546-8993, http://www.pnsinc.com/ The opinions expressed in this email are not neccesarrily those of myself, my employers, or any of the other little voices in my head.

« previous php.doc (#969333423) next »