231222 – [sec] Password recovery Q/A dialog has incorrect use of semicolon

Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 231222 - [sec] Password recovery Q/A dialog has incorrect use of semicolon

Summary: [sec] Password recovery Q/A dialog has incorrect use of semicolon

Status:	RESOLVED DUPLICATE of bug 231227

Alias:	None

Product:	Equinox
Classification:	Eclipse Project
Component:	Security (show other bugs)
Version:	3.4
Hardware:	PC Windows XP

Importance:	P3 minor (vote)
Target Milestone:	---
Assignee:	Security Inbox
QA Contact:

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2008-05-08 20:00 EDT by Kevin McGuire
Modified:	2008-05-09 15:49 EDT (History)
CC List:	1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Kevin McGuire

2008-05-08 20:00:16 EDT

The password recovery question/answer dialog says:

passwordRecoveryLabel = To be able to recover lost password in future, enter questions and answers above.\nAnswers are case-sensitive; treat answers as secondary passwords.\n

I *think* it should read:

passwordRecoveryLabel = To be able to recover a lost password in the future, enter questions and answers above.\nAnswers are case-sensitive. Treat answers as secondary passwords.\n

The reason is that you should only join sentences together by semicolon when the two are related. In this case, the fact they are case-sensitive and the fact you should treat them as passwords are unrelated to each other.

(Note I also added a missing "a" and "the" in "recover a lost password the future")

From Strunk and White:

"Indeed this simple method of indicating relationship between statements is one of the most useful devices of composition. The relationship, as above, is commonly one of cause and consequence."

Comment 1 Oleg Besedin

2008-05-09 15:49:44 EDT

Thank you for the explanation, it is nice to know. 

The fix is released as a part of the bug 231227.


*** This bug has been marked as a duplicate of bug 231227 ***