Fix font picker in Editor wrongly keeping fonts of old documents
Merge pull request #644 from kossebau/fixBrokenFontsAccumulation

Fix font picker in Editor wrongly keeping fonts of old documents
Fix SessionView constructor arguments in benchmark
Re-enable direct text styling in benchmark
Merge pull request #645 from peitschie/benchmark-fix

Fix SessionView constructor arguments in benchmark
Fix hyperlink editor to no longer extract non-odf text for the display text
Remove unneeded variable filter in gui.MimeDataExporter
Merge pull request #646 from kossebau/fixBadTextInHyperlinkEditor

Fix hyperlink editor to no longer extract non-odf text for the display text
Convert long regex into a switch statement for clarity
Allow transformation tests to carry additional tags (e.g., comments)
Ensure OpSetParagraphStyle position is first step within the paragraph

The merge paragraph op depends on the impacted paragraphs being identified
by the position of the first step within the paragraph. In order to
facilitate OT'ing of paragraph-based ops, all paragraph ops need to
consistently use the first step in the paragraph to identify the paragraph
they impact.
Make SplitParagraph op specify the new paragraph style

In order to allow convergence between collaborative clients, the split
paragraph op needs to specify what the resulting style of the new
paragraph will be.
Remove createOp function to improve closure compiler's type checking

Having the createOp function prevents closure compiler from accurately
detecting if any of these ops are being constructed with incomplete or
incorrect data.
Change OT to handle new paragraphStyleName property in SplitParagraph

In particular, to allow SplitParagraph to transform with SetParagraphStyle,
the source paragraph boundaries for the split paragraph op also need to
be recorded.
Merge pull request #647 from peitschie/op-split-para

Implement OT for SetParagraphStyle vs. SplitParagraph
Group up style information changes and report at the end of an op batch

Operation batches that modify a large number of paragraphs (or repeatedly
modify the same paragraph) can cause numerous unnecessary style change
events to be triggered. Rather than reporting these instantly, track them
as they occur and emit the style change summary on batch end.

Related to #610.
Merge pull request #648 from peitschie/style-change-evt

Group up style information changes and report at the end of an op batch
Split Editor into Wodo.Texteditor and Wodo.CollabTexteditor
move fullscreen pinch-zoom into own class FullWindowZoomHelper
add product wodotexteditor