[Bug 70118] README claims homepage cont ains “details of the latest version”

https://bz.apache.org/bugzilla/show_bug.cgi?id=3D70118

--- Comment #3 from Philippe Cloutier <[email protected]> ---
Greetings Rich,

(In reply to Rich Bowen from comment #1)
> "Details of " and "information on" are synonymous.
Thank you, you seem to be right that these are parasynonymous. That is not =
how
I understood "Details of" though. I took "Details" merely as the plural of
"detail", which for example Wiktionary first defines as =E2=80=9CA part sma=
ll enough to
escape casual notice=E2=80=9D: https://en.wiktionary.org/wiki/detail#Noun
A quote from Wiktionary demonstrates the sense I expected:
> I don't concern myself with the details of accounting.
Anyway, apologies if I misinterpreted and feel free to mark this report as
invalid.

> And a product's website exists *solely* to provide information on the lat=
est
> version,
Many projects support several versions of their product, not just the lates=
t.
Even httpd=E2=80=99s website documents several versions (at least 2.0, 2.2,=
 2.4 and
2.5). A product=E2=80=99s website can also play multiple roles, such as adv=
ertising,
selling/distributing, recruiting developers and collecting feedback.

> so I have no idea how that can be "banal" or "dated".
Providing information on current versions is one of the most basic function=
s of
a product=E2=80=99s website. That has been expected for decades. Perhaps, i=
n pre-HTTP
times, when software was distributed on floppy disks, it made sense to tell
readers to go to the W-e-b s-i-t-e rather than Usenet to verify that what
reached them was fresh enough. But nowadays, featuring the =E2=80=9CThe Lat=
est Version=E2=80=9D
section before the =E2=80=9CInstallation=E2=80=9D section feels like an ana=
chronism.

(In reply to Rich Bowen from comment #2)
> FWIW the README was rewritten into markdown style formatting so that it
> would render correctly on the Github page. This happened in r1915387
Thanks
Hum, I see there is a README.md symbolic link to README, which contains
Markdown. I assume that is what lets GitHub interpret README=E2=80=99s cont=
ents as
Markdown.

I agree that the contents of README in trunk use Markdown syntax. What I me=
ant
is that a README is normally plain text, and httpd=E2=80=99s has no declara=
tion that it
contains Markdown. If one opens it directly, the OS has no clue it is Markd=
own,
since the file has no extension, and Markdown has no file type signature.

--=20
You are receiving this mail because:
You are the assignee for the bug.=