<feed xmlns='http://www.w3.org/2005/Atom'>
<title>pandoc/test/pptx, branch master</title>
<subtitle>Conversion between markup formats</subtitle>
<id>https://git.pashev.ru/pandoc/atom?h=master</id>
<link rel='self' href='https://git.pashev.ru/pandoc/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.pashev.ru/pandoc/'/>
<updated>2021-10-18T00:24:30Z</updated>
<entry>
<title>pptx: Line up continuation paragraphs</title>
<updated>2021-10-18T00:24:30Z</updated>
<author>
<name>Emily Bourke</name>
<email>undergroundquizscene@protonmail.com</email>
</author>
<published>2021-09-23T15:01:38Z</published>
<link rel='alternate' type='text/html' href='https://git.pashev.ru/pandoc/commit/?id=8de261ba4e1e03f9dd5f78297d7299e9d78bbcfd'/>
<id>urn:sha1:8de261ba4e1e03f9dd5f78297d7299e9d78bbcfd</id>
<content type='text'>
This commit changes the `marL` and `indent` values used for plain
paragraphs and numbered lists, and changes the spacing defined in the
reference doc master for bulleted lists.

For paragraphs, there is now a left-indent taken from the `otherStyle`
in the master. For numbered lists, the number is positioned where the
text would be if this were a plain paragraph, and the text is indented
to the next level. This means that continuation paragraphs line up
nicely with numbered lists.

It also /mostly/ matches the observed PowerPoint behaviour when
inserting paragraphs and numbered lists: the only difference is that
PowerPoint was using a different margin value for the first level
numbered lists – I’ve changed this to match the other levels, as I don’t
think it makes the spacing unappealing and it allows continuation
paragraphs at any level to line up.

With bulleted lists, I’m keeping the observed PowerPoint behaviour of
specifying only a level, letting `marL` and `indent` be automatically
taken from `bodyStyle`. To that end, this commit changes the `bodyStyle`
spacing in the master of the default reference doc, to:

- line up the text of the first paragraph in each bullet with any
  continuation paragraphs
- line up nested bullet markers in any continuation paragraphs with the
  first paragraph, matching lists and plain paragraphs

This does mean the continuation paragraphs still won’t line up for
anyone using their own reference doc where they haven’t matched the
`otherStyle` and `bodyStyle` indent levels, but I think people in that
situation will be able to troubleshoot.
</content>
</entry>
<entry>
<title>pptx: Fix list level numbering</title>
<updated>2021-10-18T00:24:30Z</updated>
<author>
<name>Emily Bourke</name>
<email>undergroundquizscene@protonmail.com</email>
</author>
<published>2021-09-17T15:05:06Z</published>
<link rel='alternate' type='text/html' href='https://git.pashev.ru/pandoc/commit/?id=8af15ab345bb0790cc3442722673d9da9f23a79c'/>
<id>urn:sha1:8af15ab345bb0790cc3442722673d9da9f23a79c</id>
<content type='text'>
In PowerPoint, the content of a top-level list is at the same level as
the content of a top-level paragraph – the only difference is that a
list style has been applied.

At the moment, the pptx writer increments the paragraph level on each
list, turning what should be top-level lists into second-level lists.

This commit changes that logic, only incrementing the paragraph level on
continuation paragraphs of lists.

- Fixes https://github.com/jgm/pandoc/issues/4828
- Fixes https://github.com/jgm/pandoc/issues/4663
</content>
</entry>
<entry>
<title>pptx: Remove excessive layout tests</title>
<updated>2021-10-07T15:45:43Z</updated>
<author>
<name>Emily Bourke</name>
<email>undergroundquizscene@protonmail.com</email>
</author>
<published>2021-10-07T14:25:15Z</published>
<link rel='alternate' type='text/html' href='https://git.pashev.ru/pandoc/commit/?id=aa78765bf9d21b3a617a9eafba59dd59e362aa6b'/>
<id>urn:sha1:aa78765bf9d21b3a617a9eafba59dd59e362aa6b</id>
<content type='text'>
When I added the tests for moved layouts and deleted layouts, I added
them to all tests. However, this doesn’t really give a lot more info
than having single tests, and the extra tests take up time and disk
space.

This commit removes the moved-layouts and deleted-layouts tests, in
favour of a single test for each of those scenarios.
</content>
</entry>
<entry>
<title>Powerpoint writer: consolidate text runs when possible.</title>
<updated>2021-10-04T19:24:12Z</updated>
<author>
<name>John MacFarlane</name>
<email>jgm@berkeley.edu</email>
</author>
<published>2021-10-04T19:18:18Z</published>
<link rel='alternate' type='text/html' href='https://git.pashev.ru/pandoc/commit/?id=b8d460eeabe97756d49e4bc5f00c6bb084b69aa5'/>
<id>urn:sha1:b8d460eeabe97756d49e4bc5f00c6bb084b69aa5</id>
<content type='text'>
This slims down the output files by avoiding unnecessary
text run elements.

Updated golden tests.
</content>
</entry>
<entry>
<title>Revert "Powerpoint writer: consolidate text run nodes."</title>
<updated>2021-10-04T18:50:32Z</updated>
<author>
<name>John MacFarlane</name>
<email>jgm@berkeley.edu</email>
</author>
<published>2021-10-04T18:50:32Z</published>
<link rel='alternate' type='text/html' href='https://git.pashev.ru/pandoc/commit/?id=82d587493d97536a64110902f647d953b5f28dd4'/>
<id>urn:sha1:82d587493d97536a64110902f647d953b5f28dd4</id>
<content type='text'>
This reverts commit 62f83aa48633af477913bde6f615fe9f8793901a.

This was already being done, it seems.
I misidentified the problem; it is really with `Str ""` nodes.
</content>
</entry>
<entry>
<title>Powerpoint writer: consolidate text run nodes.</title>
<updated>2021-10-04T18:45:01Z</updated>
<author>
<name>John MacFarlane</name>
<email>jgm@berkeley.edu</email>
</author>
<published>2021-10-04T18:45:01Z</published>
<link rel='alternate' type='text/html' href='https://git.pashev.ru/pandoc/commit/?id=62f83aa48633af477913bde6f615fe9f8793901a'/>
<id>urn:sha1:62f83aa48633af477913bde6f615fe9f8793901a</id>
<content type='text'>
This should reduce the size of the generated files.
</content>
</entry>
<entry>
<title>pptx: Support footers in the reference doc</title>
<updated>2021-09-18T16:55:45Z</updated>
<author>
<name>Emily Bourke</name>
<email>undergroundquizscene@protonmail.com</email>
</author>
<published>2021-09-14T16:07:46Z</published>
<link rel='alternate' type='text/html' href='https://git.pashev.ru/pandoc/commit/?id=50adea220d09e445572e94e225fa7a81b3b2bf89'/>
<id>urn:sha1:50adea220d09e445572e94e225fa7a81b3b2bf89</id>
<content type='text'>
In PowerPoint, it’s possible to specify footers across all slides,
containing a date (optionally automatically updated to today’s date),
the slide number (optionally starting from a higher number than 1), and
static text. There’s also an option to hide the footer on the title
slide.

Before this commit, none of that footer content was pulled through from
the reference doc: this commit supports all the functionality listed
above.

There is one behaviour which may not be immediately obvious: if the
reference doc specifies a fixed date (i.e. not automatically updating),
and there’s a date specified in the metadata for the document, the
footer date is replaced by the metadata date.

- Include date, slide number, and static footer content from reference
  doc
- Respect “slide number starts from” option
- Respect “Don’t show on title slide” option
- Add tests
</content>
</entry>
<entry>
<title>pptx: Support specifying slide background images</title>
<updated>2021-09-17T02:45:53Z</updated>
<author>
<name>Emily Bourke</name>
<email>undergroundquizscene@protonmail.com</email>
</author>
<published>2021-09-13T17:16:19Z</published>
<link rel='alternate' type='text/html' href='https://git.pashev.ru/pandoc/commit/?id=7c22c0202e8ed706d33f301e65f0aa1a847b4ec4'/>
<id>urn:sha1:7c22c0202e8ed706d33f301e65f0aa1a847b4ec4</id>
<content type='text'>
In the reveal-js output, it’s possible to use reveal’s
`data-background-image` class on a slide’s title to specify a background
image for the slide.

With this commit, it’s possible to use `background-image` in the same
way for pptx output. Only the “stretch” mode is supported, and the
background image is centred around the slide in the image’s larger axis,
matching the observed default behaviour of PowerPoint.

- Support `background-image` per slide.
- Add tests.
- Update manual.
</content>
</entry>
<entry>
<title>pptx: Add support for incremental lists</title>
<updated>2021-09-15T16:13:05Z</updated>
<author>
<name>Emily Bourke</name>
<email>undergroundquizscene@protonmail.com</email>
</author>
<published>2021-09-07T12:38:47Z</published>
<link rel='alternate' type='text/html' href='https://git.pashev.ru/pandoc/commit/?id=0fb6474a55427b52bf9aebd179f7b26f30c7dbaf'/>
<id>urn:sha1:0fb6474a55427b52bf9aebd179f7b26f30c7dbaf</id>
<content type='text'>
- Support -i option
- Support incremental/noincremental divs
- Support older block quote syntax
- Add tests

One thing not clear from the manual is what should happen when the input
uses a combination of these things. For example, what should the
following produce?

```md
::: {.incremental .nonincremental}
- are
- these
- incremental?
:::

::: incremental
::::: nonincremental
- or
- these?
:::::
:::

::: nonincremental
&gt; - how
&gt; - about
&gt; - these?
:::
```

In this commit I’ve taken the following approach, matching the observed
behaviour for beamer and reveal.js output:

- if a div with both classes, incremental wins
- the innermost incremental/nonincremental div is the one which takes
  effect
- a block quote containing a list as its first element inverts whether
  the list is incremental, whether or not the quote is inside an
  incremental/non-incremental div

I’ve added some tests to verify this behaviour.

This commit closes issue #5689
(https://github.com/jgm/pandoc/issues/5689).
</content>
</entry>
<entry>
<title>pptx: Fix logic for choosing Comparison layout</title>
<updated>2021-09-13T15:30:36Z</updated>
<author>
<name>Emily Bourke</name>
<email>undergroundquizscene@protonmail.com</email>
</author>
<published>2021-09-08T13:05:22Z</published>
<link rel='alternate' type='text/html' href='https://git.pashev.ru/pandoc/commit/?id=0ebe65e651766a2b3d006d3dee4afdfd43a386d5'/>
<id>urn:sha1:0ebe65e651766a2b3d006d3dee4afdfd43a386d5</id>
<content type='text'>
There was a mistake in the logic used to choose between the Comparison
and Two Content layouts: if one column contained only non-text (an image
or a table) and the other contained only text, the Comparison layout was
chosen instead of the desired Two Content layout.

This commit fixes that logic:

&gt; If either column contains text followed by non-text, use Comparison.
  Otherwise, use Two Content.

It also adds a test asserting this behaviour.
</content>
</entry>
</feed>
