#21 Short Help screen

open-fixed
nobody
None
5
2011-02-26
2011-02-11
JvH
No

Not big deal, but this is what I noticed:
- The text is editable (I'd expect it to be read-only)
- The arrow characters aren't substituted, and so they show up as {^} etc)

Discussion

  • Averell
    Averell
    2011-02-25

    > - The text is editable (I'd expect it to be read-only)
    Fixed in 1.3.3
    > The arrow characters aren't substituted, and so they show up as {^} etc)
    Nothing is translated, and I think nothing should be translated. Just type as you want things to appear.

     
  • Averell
    Averell
    2011-02-25

    • status: open --> closed-fixed
     
  • JvH
    JvH
    2011-02-26

    • status: closed-fixed --> open-fixed
     
  • JvH
    JvH
    2011-02-26

    > Nothing is translated, and I think nothing should be translated. Just type as you want things to appear
    Oh yeah, didn't think of that :)

     
  • JvH
    JvH
    2011-02-26

    On the other hand, there is a consideration that might be a good argument in favour of also using translation for the Short Help screen.

    You implemented the [#accents] section to easily accommodate for different keyboard layouts. Now suppose a user decides to switch keyboard layout, or to choose a different key for a certain accent. In that case, the [#help] sections don't have to be manually updated.

     
  • Averell
    Averell
    2011-02-26

    I understand, but there is always an annoying point with translation : suppose I translate {<} in an arrow. What if the user wants to display {<} for any reason ?
    I think better to let things like that.

     
  • JvH
    JvH
    2011-02-26

    >What if the user wants to display {<} for any reason ?
    The 2 solutions I could think of, which are technically the same:
    - C# style escape characters; to get { and } the user has to type (for example) \{ and \}
    - HTML style entities: to get { and } the user has to type (for exapmle) &brleft; and &brright;

    This is certainly no critical issue, but I really think translation would be a nice addition to take full advantage of the [#accents] feature.