1. 21 Nov, 2018 1 commit
  2. 15 Nov, 2018 1 commit
  3. 13 Nov, 2018 2 commits
  4. 11 Sep, 2018 1 commit
  5. 06 Feb, 2018 1 commit
  6. 29 May, 2017 3 commits
  7. 19 Apr, 2017 1 commit
  8. 05 Oct, 2016 1 commit
  9. 09 May, 2016 2 commits
  10. 08 May, 2016 1 commit
  11. 10 Dec, 2015 1 commit
  12. 13 Nov, 2015 1 commit
  13. 28 Oct, 2015 1 commit
  14. 13 Mar, 2015 2 commits
  15. 15 Feb, 2015 2 commits
  16. 07 Feb, 2015 3 commits
  17. 06 Feb, 2015 4 commits
    • totten's avatar
      CRM-15832 - Scan "partials" · f9412d3d
      totten authored
      f9412d3d
    • totten's avatar
      258f5eac
    • totten's avatar
      bb4eb242
    • totten's avatar
      CRM-15832 - Rewrite create-pot-files.sh · 57371fcd
      totten authored
      I found it fairly hard to trace through which source-code files mapped to
      which *.pot files; there were several interacting rules/patterns in
      create-pot-files.sh and in extractor.php which determined that policy
      question.
      
      This rewrite replaces *extractor.php with civistrings and moves all the
      policy/pattern questions into create-pot-files.sh (with a big "case"
      statement).  For example, the question of "What files go into event.pot?"
      could be answered by this clause:
      
      ```
      function build_raw_pot() {
        ...
        case "$name" in
          ...
          Event)
            _civistrings -o "$filepath" \
              CRM/Event \
              templates/CRM/Event \
              xml/templates/message_templates/event_* \
              xml/templates/message_templates/participant_*
            ;;
        esac
        ..
      }
      ```
      
      Any PHP/TPL/JS/HTML in those files/folders will be scanned for strings.
      57371fcd
  18. 04 Feb, 2015 3 commits
  19. 14 Nov, 2014 1 commit
  20. 30 May, 2014 1 commit
  21. 19 May, 2014 3 commits
  22. 16 May, 2014 3 commits
  23. 08 May, 2014 1 commit