bugGNU Octave - Bugs: bug #59564, @result{} in HTML documentation is...

 
 

bug #59564: @result{} in HTML documentation is mis-aligned

Submitter:  Rik <rik5>
Submitted:  Sat 28 Nov 2020 03:19:29 AM UTC
 
Category:  Documentation Severity:  3 - Normal
Priority:  3 - Low Item Group:  Inaccurate Result
Status:  Confirmed Assigned to:  None
Originator Name:  Open/Closed:  * Open
Release:  * dev Operating System:  * Any
Fixed Release:  None Planned Release:  None
* Mandatory Fields

Add a New Comment (Rich Markup)
   

Comment Type & Canned Response:
       

 

Sat 28 Nov 2020 03:23:31 AM UTC, comment #2: 

In terms of resolving this issue, is this something that we can adjust in the Texinfo output settings?  If not, can we change the octave.css file to get the right result?  Last shot might be to define a new macro @xresult which is decoded to " @result{}" for HTML formats and "@result{}" for all others.

Rik <rik5>
Project Administrator
Sat 28 Nov 2020 03:20:41 AM UTC, comment #1: 

Here is the HTML version of the documentation, .

Rik <rik5>
Project Administrator
Sat 28 Nov 2020 03:19:29 AM UTC, original submission:  

The Texinfo character that results from @result{} is "=>" in a plaintext environment (2 characters) but just 1 character (&Rarr) in HTML.  This throws the alignment of columns off.  Here is one example from the documentation from cstrcat: file:Rarr_example.png.

And here is how the documentation appears in a plaintext environment:

          s = [ "ab"; "cde" ];
          cstrcat (s, s, s)
                => "ab ab ab "
                   "cdecdecde"

Rik <rik5>
Project Administrator

 

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

Attach Files:
   
   
Comment:
   

Attached Files
file #50355:  Rarr_example.png added by rik5 (3KiB - image/png)

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by rik5 (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 project members can vote.

     

     

     

     

    Follow 3 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2020-11-28 rik5 Priority5 - Normal 3 - Low
        StatusNone Confirmed
    2020-11-28 rik5 Attached File- Added Rarr_example.png, #50355

    Back to the top

    Powered by Savane 3.10