taskSavannah Administration - Tasks: task #12961, Commas in login page


task #12961: Commas in login page

Submitted by:  Wes Turner <westurner>
Submitted on:  Sun 01 Dec 2013 01:02:18 PM UTC  
Should Start On:  Sun 01 Dec 2013 12:00:00 AM UTC Should be Finished on:  Sun 01 Dec 2013 12:00:00 AM UTC
Category:  System Priority:  5 - Normal
Status:  Done Privacy:  Public
Percent Complete:  0% Assigned to:  Bob Proulx <rwp>
Open/Closed:  Closed Effort:  0.00

Add a New Comment (Rich Markup)

You are not logged in

Please log in, so followups can be emailed to you.


( Jump to the original submission)

Thu 02 Jan 2014 09:40:31 PM UTC, comment #6: 

This has been done.

Bob Proulx <rwp>
Site AdministratorIn charge of this item.
Thu 02 Jan 2014 09:33:06 PM UTC, comment #5: 

I got back to looking at this problem again.  No one else jumped in so I will take the task.  I think the entire statement is obsolete.  The problem it is referring to isn't relevant today.

  "Lynx, Emacs w3 and Microsoft Internet Explorer users will have intermittent https problems, so they should leave https after login. Gecko-based browser (Mozilla, Galeon, Netscape...) and Konqueror users should stay in https mode permanently for maximum security."

I am going to remove the entire statement.

Bob Proulx <rwp>
Site AdministratorIn charge of this item.
Mon 02 Dec 2013 05:04:01 AM UTC, comment #4: 

You may be more qualified for such an operational transformation.

A bit OT, maybe, but these links may be helpful instead:



I don't know if they are still accepting reservations for this list:


This is a great resource:


Wes Turner <westurner>
Mon 02 Dec 2013 03:33:34 AM UTC, comment #3: 

I think you are definitely onto a problem.  But I think the question should be does that section still apply anymore?  That text dates back to 2006.  That is quite a long time in web browser development.  Back then MS-IE-6 was the main problem.  (Sad thing is that it still isn't gone yet.  But perhaps it can be paid less attention now.)  Also it mentions the then very wonderful Galeon which is moribund now.  Also Netscape.

I really doubt that the issues it is hinting at even apply now.  I am inclined to say that the entire section should be dropped.

Bob Proulx <rwp>
Site AdministratorIn charge of this item.
Mon 02 Dec 2013 01:27:25 AM UTC, comment #2: 

1. My mistake. Is the admonition regarding HTTPS incapability applicable to just Emacs/W3 or also to w3m.el? Should the browser name in question be specified more clearly as 'Emacs/W3'?




2. It may be appropriate to also reference WebKit browsers' HTTPS capabilities.


Wes Turner <westurner>
Sun 01 Dec 2013 10:01:17 PM UTC, comment #1: 

First let me thank you for taking the time to look carefully at the site and to make a suggestion for its improvement.  That is great!  So few people do this.

This is the style question known as the Oxford Comma.  You appear to be aware of this because you cited the wikipedia page on it.  But you failed to acknowledge that the usage of it on the login page was also acceptable usage.

In school I was taught that the Oxford Comma was obsolete usage and it should always be avoided in modern writing.   But in later years I have come to prefer the comma regardless and have learned that it is now a debated item.  In the end in my opinion it really depends upon context and judgement.

Here I think it could be stated with the Oxford comma and be okay.  But it is correct as it stands.  These two differing usages are both correct.  Frankly either way would be acceptable to me.  I am going to refuse to get trapped between the two camps on this one.

However you have misunderstood something and have placed extra commas that are incorrect.  It is definitely incorrect to seperate "Emacs, w3," with a comma since that is a single item.  You didn't separate the "Microsoft, Internet, Explorer," with commas and Emacs w3 is just the same.  Therefore your patch should not be included as it stands.

If you are unfamiliar let me point you to:

Bob Proulx <rwp>
Site AdministratorIn charge of this item.
Sun 01 Dec 2013 01:02:18 PM UTC, original submission:  



> Lynx, Emacs w3 and Microsoft Internet Explorer users will have intermittent https problems

I believe it should read:

"Lynx, Emacs, w3, and Microsoft Internet Explorer users will have intermittent https problems"

The attached patch makes these modifications in login.php and sed'able localization files.

Note that this patch says nothing of WebKit based browsers or capitalization of HTTPS.


Wes Turner <westurner>


(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:

Attached Files


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -email is unavailable- added by rwp (Posted a comment)
  • -email is unavailable- added by westurner (Submitted the item)

    Do you think this task is very important?
    If so, you can add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.




    Follow 7 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2014-01-02 rwp StatusIn Progress => Done
        Open/ClosedOpen => Closed
    2014-01-02 rwp StatusNone => In Progress
        Assigned toNone => rwp
    2013-12-01 rwp CategoryApproved Projects to be Reviewed => System
    2013-12-01 rwp CategoryNone => Approved Projects to be Reviewed
    2013-12-01 westurner Attached File- => Added login_page_serial_comma.patch, #29746

    Back to the top

    Powered by Savane 3.5