private void RenderList(ListLayout layout, IContentContainer container)
{
++_numberingLevel;
s.ListStyle listStyle = (s.ListStyle)layout.Style;
// Translate the bullet text from design syntax to Word syntax. The
// design specification can include formatting of its own, unrelated
// to the list style. The easiest way to interpret such formatting
// is to create a text layout from the bullet text, which will
// separate the formatting from the text. If the bullet includes
// formatting then the new text layout will start with a paragraph
// verse, which we'll ignore. And it could contain any
// number of other verses, but a numbering definition in Word supports
// only a single run, so we just concatenate the text from all the
// verses, and apply the first verse format we find. Note that our
// report design language doesn't support including lower level numbers
// in the number, such as 3x in 1, 2, 3a, 3b, 3c, 4, 5 etc.
s.BulletStyle bulletStyle = listStyle.BulletStyle;
string bulletText = bulletStyle.BulletText
.Replace("%", "%%")
.Replace(ListItemLayout.BulletNumberProperty, $"%{_numberingLevel+1}");
TextFormat bulletFormat = new TextFormat(bulletStyle.Font, bulletStyle.Color);
TextBlock block = new TextBlock(bulletText, bulletFormat, _generator);
bulletText = block.Verses.Select(v => v.Text).Aggregate((c, n) => c + n);
bulletFormat = block.Verses.Select(v => v.Format).Where(f => f != null).FirstOrDefault();
int numberingStyleId = _document.AddNumberingStyle(bulletStyle, _numberingLevel, bulletText);
// Create a numbering instance based on the numbering style, and add it
// to the paragraph. As far as I can make out, in a sequence of numbered
// paragraphs every paragraph refers to the one numbering instance.
// Any number of such sequences can get their numbering from the one
// underlying abstract definition, but each sequence would have its own
// instance. Instances are stored in the numbering part along with the
// abstract definitions.
//
// We have to store abstract definitions in a dictionary in the document
// because we need random access to them so that different layouts in the
// design can share a single definition. But we can store instances in a
// simple stack in this class because each one is needed only for the
// current list.
int numberingInstanceId = _document.AddNumberingInstance(numberingStyleId);
_numberingInstances.Push(numberingInstanceId);
// Lists in the design can be nested - that's how we do indented list
// levels. But in Word each item must be its own paragraph, and the
// items together form the list by being contiguous paragraphs with
// a common numbering style. That is, Word doesn't have lists, but
// rather just has numbered paragraphs.
foreach (Layout sublayout in layout.SubLayouts)
{
Render(sublayout, container);
}
_numberingInstances.Pop();
--_numberingLevel;
}