1. 30 Jul, 2019 1 commit
  2. 09 Jun, 2019 1 commit
    • Ran Benita's avatar
      Compose.man: fix escaped hexadecimal char description · 33b9148a
      Ran Benita authored
      The man page says:
          Strings may be direct text encoded in the locale for which the
          compose file is to be used, or an escaped octal or hexadecimal
          character code.   Octal codes are specified as "\123" and
          hexadecimal codes as "\0x123a".
      
      But the grammar in the parser and the implementation say:
          ESCAPED_CHAR  ::= ('\\' | '\"' | OCTAL | HEX )
          HEX           ::= '\' (x|X) HEX_CHAR [HEX_CHAR]]
          HEX_CHAR      ::= (0|1|2|3|4|5|6|7|8|9|A|B|C|D|E|F|a|b|c|d|e|f)
      
      So "\0x123a" -> "\x3a".
      Signed-off-by: default avatarRan Benita <ran234@gmail.com>
      Signed-off-by: Alan Coopersmith's avatarAlan Coopersmith <alan.coopersmith@oracle.com>
      33b9148a
  3. 05 Feb, 2015 1 commit
    • Ran Benita's avatar
      compose: fix the description of modifiers in compose sequences · ddf3b09b
      Ran Benita authored
      The Compose format has a feature which allows specifying certain
      modifiers must (or must not) be present with a given keysym in the
      sequence.
      
      The grammar in imLcPrs.c and the Compose man page both do not match what
      the code actually does (see the handling of the variables
      `modifier_mask` and `modifier` in parseline() in imLcPrs.c, which are
      eventually matched as `ev->state & modifier_mask == modifier`).
      
      Also explicitly list the accepted modifier names, since they are
      not standard (e.g. "Ctrl" instead of "Control").
      Signed-off-by: default avatarRan Benita <ran234@gmail.com>
      Signed-off-by: James Cloos's avatarJames Cloos <cloos@jhcloos.com>
      ddf3b09b
  4. 04 Sep, 2010 1 commit
  5. 24 Jul, 2010 1 commit
  6. 14 Jan, 2010 2 commits
  7. 23 Oct, 2009 1 commit