1. 26 Jul, 2021 1 commit
  2. 08 Mar, 2021 1 commit
  3. 07 Mar, 2021 1 commit
  4. 12 Jan, 2020 2 commits
  5. 07 Jan, 2020 1 commit
  6. 12 Dec, 2019 1 commit
  7. 11 Dec, 2019 4 commits
  8. 04 Dec, 2019 2 commits
  9. 22 Sep, 2019 9 commits
  10. 13 Aug, 2019 5 commits
  11. 09 Jul, 2019 1 commit
  12. 20 Feb, 2019 1 commit
  13. 16 Feb, 2019 3 commits
  14. 11 Jul, 2018 2 commits
    • Matthieu Moy's avatar
      Fix for the previous fix: deal with multiple % in the line · 3cf650ff
      Matthieu Moy authored
      The naive s/%.*\n/ / doesn't properly deal with \%, and matching for a
      command followed by a % anywhere in the line doesn't work for e.g.
      Foo%\bar%\nboz.
      
      Fix this by using the same full-line, non-ambiguous matching style as
      we did for non-commands cases.
      3cf650ff
    • Matthieu Moy's avatar
      Add a space when removing comments right after a command · 57a1383e
      Matthieu Moy authored
      When a line ends with a command, like:
      
      \command%
      Text
      
      we don't want to just remove the comment, as it would yield
      
      \commandText
      
      One option would be to add a pair of braces ({}), but this only works
      if the command takes no argument (otherwise, the extra {} is
      considered as an extra, first, parameter). This commit fixes the issue
      by adding an extra space so that the substitution becomes:
      
      \command Text
      
      TeX ignores this space after a command hence the output is the right
      one.
      
      Fixes #10.
      57a1383e
  15. 13 Jun, 2018 1 commit
    • Matthieu Moy's avatar
      Default to 'bytes' mode for input and output · 1d6ba6c9
      Matthieu Moy authored
      All files read during the same execution of latexpand should be open
      using the same encoding. Letting perl autodetect the encoding leads to
      weird behaviors in case the guessing fails.
      
      AFAIK, LaTeX can only work with charsets that are supersets of
      us-ascii, and latexpand only deals with us-ascii charsets, so opening
      all files in 'bytes' mode will always work. In case I'm wrong, provide
      --in-encoding and --out-encoding to let the user specify another mode.
      
      Fixes #9.
      1d6ba6c9
  16. 06 Jun, 2018 2 commits
  17. 19 Apr, 2018 2 commits
  18. 18 Apr, 2018 1 commit