1. 03 Sep, 2014 1 commit
    • Alex Vandiver's avatar
      Standardize on the stricter Encode::encode("UTF-8", ...) everywhere · 1d18663b
      Alex Vandiver authored
      This is not only for code consistency, but also for consistency of
      output.  Encode::encode_utf8(...) is equivalent to
      Encode::encode("utf8",...) which is the non-"strict" form of UTF-8.
      Strict UTF-8 encoding differs in that (from `perldoc Encode`):
      
          ...its range is much narrower (0 ..  0x10_FFFF to cover only 21 bits
          instead of 32 or 64 bits) and some sequences are not allowed, like
          those used in surrogate pairs, the 31 non-character code points
          0xFDD0 .. 0xFDEF, the last two code points in any plane (0xXX_FFFE
          and 0xXX_FFFF), all non-shortest encodings, etc.
      
      RT deals with interchange with databases, email, and other systems.  In
      dealing with encodings, it should ensure that it does not produce byte
      sequences that are invalid according to official Unicode standards.
      1d18663b
  2. 01 May, 2013 1 commit
    • Thomas Sibley's avatar
      Switch the default scrip templates to HTML for new installs · 7a33b13f
      Thomas Sibley authored
      This also switches the default for testing.  As an escape hatch,
      RT::Test now sports a text_templates flag.
      
      Tests which failed non-obviously with HTML templates enabled were copied
      to a t/mail/*-plaintext.t filenames and flipped back to testing
      plaintext.  The original files were fixed to expect the New World Order
      of HTML.  This way both the new HTML templates and the old plaintext
      templates are tested.
      7a33b13f
  3. 01 Nov, 2012 1 commit
  4. 18 Mar, 2011 2 commits
  5. 22 Nov, 2010 1 commit
  6. 21 Oct, 2010 1 commit
  7. 26 Sep, 2010 1 commit
  8. 24 Aug, 2010 1 commit
  9. 17 Aug, 2010 1 commit
  10. 18 Dec, 2009 1 commit
  11. 24 Jun, 2009 1 commit
  12. 23 Jun, 2008 1 commit
  13. 20 Jun, 2008 2 commits