helpSavannah Administration - Support: sr #110621, request better handling of...

 
 

sr #110621: request better handling of numbered-list markup in email

Submitter:  Dave <barx>
Submitted:  Wed 16 Mar 2022 09:42:24 AM UTC
 
Category:  Savannah trackers - bugs, tasks, etc. Priority:  5 - Normal
Severity:  1 - Wish Status:  In Progress
Assigned to:  ineiev Operating System:  None
Open/Closed:  Open
* Mandatory Fields

Add a New Comment (Rich Markup)
   

Comment Type & Canned Response:
       

 

( Jump to the original submission )

Sat 03 Sep 2022 09:22:19 AM UTC, comment #14: 

Hmm, maybe now it's a little too aggressive: it seems to convert lines within "verbatim" blocks.

For example, the first such block in http://savannah.gnu.org/bugs/?62983#comment1 displays correctly in the browser, but one line was erroneously made into a "list" entry in the associated email: http://lists.gnu.org/r/bug-groff/2022-09/msg00001.html

Dave <barx>
Tue 30 Aug 2022 11:37:38 PM UTC, comment #13: 

http://lists.gnu.org/r/savannah-hackers/2022-08/msg00049.html
Fantastic!  Thanks so much for tracking this down.

Dave <barx>
Tue 30 Aug 2022 11:33:00 PM UTC, comment #12: 
  1. This appears to be not working in at least some circumstances.
  2. I'm formatting this comment as a list to see whether it works here.
  3. It did not work in http://savannah.gnu.org/bugs/?62825#comment10, which can be seen from the email logged at http://lists.gnu.org/r/bug-groff/2022-07/msg00141.html
  4. When I encounter situations like this, would you rather I add a comment to a closed bug report that already logs discussion about the same problem, or open a new one?
Dave <barx>
Tue 30 Aug 2022 11:31:50 PM UTC, comment #11: 

Thank you!  Will repost comment #8 as-is to see how it fares; ignore its content.

Dave <barx>
Tue 30 Aug 2022 05:03:57 PM UTC, comment #10: 

Broke in b2a3eda14 (2022-05-31); (hopefully) fixed.

Ineiev <ineiev>
Site Administrator
Fri 29 Jul 2022 08:08:47 PM UTC, comment #9: 

Half-and-half is definitely not a result I expected!
http://lists.gnu.org/r/savannah-hackers/2022-07/msg00015.html

Dave <barx>
Fri 29 Jul 2022 07:57:44 PM UTC, comment #8: 
  1. This appears to be not working in at least some circumstances.
  2. I'm formatting this comment as a list to see whether it works here.
  3. It did not work in http://savannah.gnu.org/bugs/?62825#comment10, which can be seen from the email logged at http://lists.gnu.org/r/bug-groff/2022-07/msg00141.html
  4. When I encounter situations like this, would you rather I add a comment to a closed bug report that already logs discussion about the same problem, or open a new one?
Dave <barx>
Tue 26 Apr 2022 01:02:25 AM UTC, comment #7: 

Thank you again for your quick attention to this!

Dave <barx>
Mon 25 Apr 2022 05:57:37 PM UTC, comment #6: 

Thank you, fixed.

Ineiev <ineiev>
Site Administrator
Thu 21 Apr 2022 10:08:19 PM UTC, comment #5: 

Numbering still works in email generated from a Rich Markup post originating on savannah.nongnu.org (the condition that was previously shown to work in comment #2): http://lists.gnu.org/r/savannah-hackers/2022-04/msg00029.html

So this does not appear to be a regression, merely an incomplete implementation.

Dave <barx>
Thu 21 Apr 2022 09:42:45 PM UTC, comment #4: 

This change appears to have been undone since then; compare:

  1. http://savannah.gnu.org/bugs/?62344#comment0
  2. http://lists.gnu.org/r/bug-groff/2022-04/msg00052.html

I've made those into a numbered list in this post to see if the problem exists across the board, or perhaps only on savannah.gnu.org but not savannah.nongnu.org, or perhaps in Full Markup posts but not Rich Markup ones.

I don't have the authority to reopen this ticket, but I can open a new one if that makes more sense--that would also let me test Full Markup on savannah.nongnu.org to perhaps narrow the field further.

Dave <barx>
Thu 17 Mar 2022 07:10:21 PM UTC, comment #3: 

Looks great, thank you!  (Email form, for comparison: http://lists.gnu.org/r/savannah-hackers/2022-03/msg00014.html -- looks identical to the web version now)

Dave <barx>
Thu 17 Mar 2022 11:39:10 AM UTC, comment #2: 

Thank you, initially done:

  1. item 1
  2. item 2
    1. item 2.1
      1. item 2.1.1
    2. item 2.2
    3. item 2.3
  3. item 3
Ineiev <ineiev>
Site Administrator
Wed 16 Mar 2022 09:49:35 AM UTC, comment #1: 

http://lists.gnu.org/r/savannah-hackers/2022-03/msg00010.html shows this bug submission in email form, for comparison against how it's displayed in savannah.

Dave <barx>
Wed 16 Mar 2022 09:42:24 AM UTC, original submission:  

When comments posted to this bug tracker are sent as email, some formatting is necessarily lost because the email is plain text (so, e.g., bold and italic markup cannot be represented other than how they are entered).  But some markup is handled intelligently: for instance, the Rich Markup "verbatim" markers are recognized and handled appropriately.

Of the other items listed under Rich Markup in http://savannah.nongnu.org/markup-test.php, I would like to request that those for numbered lists be converted to numbers in email using the same algorithm as within savannah.  This list, for example:

  1. acquire straw
  2. transport straw to hideout
  3. spin straw into gold
  4. PROFIT

renders in a meaningful way when viewed in savannah but is less useful in email, especially if further text refers to the numbers to identify list items.

This seems like a straightforward transformation, so I hope it can be implemented fairly easily.  Thanks for considering this.

Dave <barx>

 

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

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

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

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

     

     

     

    Follow 13 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2022-09-05 ineiev StatusDone In Progress
        Open/ClosedClosed Open
    2022-08-30 ineiev StatusIn Progress Done
        Open/ClosedOpen Closed
    2022-08-08 ineiev StatusDone In Progress
        Open/ClosedClosed Open
    2022-04-25 ineiev StatusIn Progress Done
        Open/ClosedOpen Closed
    2022-04-22 ineiev StatusDone In Progress
        Open/ClosedClosed Open
    2022-03-17 ineiev StatusNone Done
        Assigned toNone ineiev
        Open/ClosedOpen Closed

    Back to the top


    Powered by Savane 3.9