Skip to content
Snippets Groups Projects
  1. Apr 14, 2015
  2. Apr 13, 2015
  3. Apr 12, 2015
  4. Apr 11, 2015
  5. Mar 22, 2015
  6. Mar 21, 2015
  7. Mar 19, 2015
  8. Mar 18, 2015
    • Arseny Kapoulkine's avatar
      Do not emit surrounding whitespace for text nodes · 5f996eba
      Arseny Kapoulkine authored
      Previously we omitted extra whitespace for single PCDATA/CDATA children, but in
      mixed content there was extra indentation before/after text nodes.
      
      One of the problems with that is that the text that you saved is not exactly
      the same as the parsing result using default flags (parse_trim_pcdata helps).
      
      Another problem is that parse-format cycles do not have a fixed point for mixed
      content - the result expands indefinitely. Some XML libraries, like Python
      minidom, have the same issue, but this is definitely a problem.
      
      Pretty-printing mixed content is hard. It seems that the only other sensible
      choice is to switch mixed content nodes to raw formatting. In a way the code in
      this change is a weaker version of that - it removes indentation around text
      nodes but still keeps it around element siblings/children.
      
      Thus we can switch to mixed-raw formatting at some point later, which will be
      a superset of the current behavior.
      
      To do this we have to either switch at the first text node (.NET XmlDocument
      does that), or scan the children of each element for a possible text node and
      switch before we output the first child.
      
      The former behavior seems non-intuitive (and a bit broken); unfortunately, the
      latter behavior can cost up to 20% of the output time for trees *without* mixed
      content.
      
      Fixes #13.
      5f996eba
  9. Mar 14, 2015
    • Arseny Kapoulkine's avatar
      tests: Fix truncation test · 51da129b
      Arseny Kapoulkine authored
      data/truncation.xml was corrupted at some point and was not actually valid.
      Fix the file and make the test fail if we can't parse truncation.xml at all.
      51da129b
  10. Mar 13, 2015
  11. Mar 10, 2015
  12. Mar 05, 2015
  13. Mar 04, 2015
  14. Mar 02, 2015
  15. Feb 12, 2015
  16. Jan 24, 2015
  17. Jan 18, 2015
  18. Jan 17, 2015
  19. Jan 10, 2015
    • Arseny Kapoulkine's avatar
      Simplify header-only mode usage · f3e42969
      Arseny Kapoulkine authored
      It's sufficient to define PUGIXML_HEADER_ONLY anywhere now, source is included
      automatically.
      
      This is a second attempt; this time it includes a workaround for QMake bug
      that caused it to generate incorrect Makefile.
      f3e42969
Loading