1. 17 Jan, 2020 1 commit
  2. 16 Jan, 2020 2 commits
  3. 13 Jan, 2020 5 commits
  4. 10 Jan, 2020 2 commits
  5. 09 Jan, 2020 1 commit
  6. 07 Jan, 2020 1 commit
  7. 06 Jan, 2020 1 commit
  8. 05 Jan, 2020 1 commit
  9. 03 Jan, 2020 2 commits
  10. 02 Jan, 2020 1 commit
  11. 21 Dec, 2019 1 commit
    • Evan W. Patton's avatar
      Treat 'global' keyword as untranslatable internally · a29c047e
      Evan W. Patton authored
      In the block name we store globals as 'global foo' where foo is the
      variable name. In Korean and Polish, the 'global' keyword has been
      translated for the blocks, but interally we still call the variable
      'global foo' even though the keyword shown to the user is
      translated. However, because the functionality to unprefix names
      references the translated name it causes bad code generation for
      languages where the global keyword isn't the string 'global'. This
      change introduces a GLOBAL_KEYWORD constant that is checked to
      identify globals where the user locale may provide a translation.
      
      Change-Id: Id18331206c28592c145bc2a1d915bcecc0799f13
      a29c047e
  12. 20 Dec, 2019 3 commits
  13. 19 Dec, 2019 1 commit
  14. 17 Dec, 2019 15 commits
  15. 16 Dec, 2019 1 commit
  16. 12 Dec, 2019 1 commit
  17. 11 Dec, 2019 1 commit