bugGNU nano - Bugs: bug #57987, keystroke description can be...

 
 

You are not allowed to post comments on this tracker with your current authentication level.

bug #57987: keystroke description can be pushed to next line in help viewer

Submitter:  Benno Schulenberg <bens>
Submitted:  Thu 12 Mar 2020 11:05:40 AM UTC
   
 
Severity:  2 - Minor Status:  Fixed
Assigned to:  bens Open/Closed:  Closed

Sun 15 Mar 2020 01:01:32 PM UTC, comment #2: 

Fixed in git, commit 16f17f3f.

Benno Schulenberg <bens>
Group administrator
Fri 13 Mar 2020 06:09:55 PM UTC, comment #1: 

A different recipe: make your terminal 40 columns wide and run:
'LANGUAGE=zh_CN src/nano'.  See how the descriptions after ^O and ^R (and several other keystrokes) are pushed to the next row, and with seemingly inverted indentations: the continuation line has less indentation than the first one.

(Also note that in the introductory text, six lines start at the left edge.  Apparently these lines of Chineses characters do not contain any whitespace, and nano is forced to break a line between characters, meaning that there no inherent space will appear and the beginning of the next row.)

The problem with German I am going to avoid by increasing the minimum supported terminal width (for help texts) to 40 columns.  But that still leaves Chineses and Japanese with messy help texts on narrow terminals.  (Korean seems to behave fine.)

(The choice for 40 columns minimum is also motivated by wanting to make the translation of "enable/disable" fit on a single continuation row for most languages.)

Benno Schulenberg <bens>
Group administrator
Thu 12 Mar 2020 11:05:40 AM UTC, original submission:  

When a translation has a long word (more than thirteen characters) as the first word in a keystroke description, this word can be pushed to the subsequent line in the help viewer when the screen is very narrow.

To reproduce, make your terminal 34 columns wide, then run: 'LANGUAGE=de src/nano'.  Type: ^G ^W recht <Enter>.  See that the word "Rechtschreibprüfung" is broken into two pieces.  This is okay, it is unavoidable: there not enough room for the whole word.

However, things look like this:

^J               Absatz ausrichten
^T
                   Rechtschreibprü
                  fung aufrufen
                   (wenn
                   verfügbar)

Note that the "Rechtschreib..." fragment should have been drawn one row up, and two columns to the left.  It should have looked like this:

^J               Absatz ausrichten
^T               Rechtschreibprüfu
                  ng aufrufen
                   (wenn
                   verfügbar)


(Note that the "fung" or the "ng" is one position too far left, but... that is a different issue.  And maybe it is in fact nice, an indication that a word has been brutally broken.)

Benno Schulenberg <bens>
Group administrator

 

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

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 bens (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.

     

    Follow 5 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2020-03-25 bens Open/ClosedOpen Closed
    2020-03-15 bens StatusIn Progress Fixed
    2020-03-13 bens Summaryin the help viewer, a keystroke description can be pushed to next line keystroke description can be pushed to next line in help viewer
    2020-03-13 bens StatusNone In Progress
        Assigned toNone bens

    Back to the top

    Powered by Savane 3.13-d3ae.
    Corresponding source code