svn commit: r502676 - in head/science: . opensph opensph/files

[Yuri]

On 2019-05-26 01:57, Alexey Dokuchaev wrote:
> As several people, including myself, had repeatedly asked you in the
> past: please stop doing this.  Most of users expect PORTNAME=opensph
> and there are no good reasons to confuse them.


Dear Alexey,


Visual text recognition, ease of read, and users' familiarity with terms 
in specific spellings are the main reasons here.

This particular project is called "OpenSPH" in the title of its homepage 
(https://gitlab.com/sevecekp/sph) and a few search hits that mention it 
also call it with the same spelling. "SPH" is also an abbreviation in 
this case.


Mixed-case words have more distinctive and diverse shape, and the 
research into human reading behavior suggests that "configurational and 
shape information about words appears to be retained in memory" and used 
for text recognition.[1] It is also self-evident that when casing 
corresponds to natural word or term boundaries it makes it easier to 
recognize the words.


On the other hand, you site tradition and consensus. But I only saw the 
evidence of consensus for lowercase spelling of directory names. When 
you previously complained about PORTNAMEs, some other people also said 
that it was nothing wrong with these PORTNAME strings.


pkg(8) also seems to be case-blind in its 'search' and 'install' 
sub-commands. There are currently several hundred of PORTNAMEs that have 
capital letters in them.


I can assure you that I only use mixed casing after a very serious 
consideration, only in cases which have very compelling reasons for this.


Regards,

Yuri


--References--

[1] Linnea C. Ehri, Lee S. Wilce RECOGNITION OF SPELLINGS PRINTED IN 
LOWER AND MIXEDCASE: EVIDENCE FOR ORTHOGRAPHIC IMAGES, Journal of 
Reading Behavior¡982, Volume XIV, No. 3 
(https://journals.sagepub.com/doi/pdf/10.1080/10862968209547451)