Am Samstag, 22. Oktober 2005 03:03 schrieb Osamu Aoki: > Did you decided by yourself that the correct English spelling words with > colon should be used instead of developer-reference defined pseudo > header "Homepage:" on your package?
I know of no policy document or other convincing technical reason that this needs to be spelled one way or the other. The policy says that the description should describe the package to the user, so natural language spelling rules apply. I also use "Web site: http://foo"; or "Home pages: http:// and http://bar"; in other packages, and no one ever saw problems with that. I am of course aware of the section in the Developer's Reference (although I never fully realized that the docbook-dsssl package was linked as the example) but I figured that the point of the section was to show that noting the web site would make it clickable in the package pages, not to advocate some sort of pseudoheader. Right now I can't even think of a real application for programmatically knowing a package's upstream web sites. Reading this closely now I also notice that only a minority of packages seems to follow the advice of putting two spaces before "Homepage", the rationale behind which is also unclear to me. To summarize, it's doubtful that this matters one way or the other. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
