Features

Why differ the (gray) table headings in the exported files from the Confluence page?

When exporting content from Confluence, Scroll converts the contents in the so-called meta model, which is a media-neutral representation of the content and can converted into different output formats. This is how we implement single-source publishing.

Tables in the meta model may only contain header cells at the top of the table, which is why Scroll removes table headings that are not at the top of the table and why the Scroll exporters do not export those headings.

Deployment Options

Is Scroll Office supported on Atlassian OnDemand?

No.

It used to be supported on JIRA Studio, that's why we have clients using it on Hosted Installations and that's why we still have the pricing online.

Atlassian has a pretty strict Atlassian OnDemand Plugin Policy to make sure that all the components have been rigorously tested for compatibility and stability in the environment, so the only way to add extra plugins is to have them bundled by the developers.

We have started talks with Atlassian to get Scroll Office integrated into Atlassian OnDemand. Our goal is to have our products integrated somewhen later this year (2012), but we cannot guarantee this.

In the meantime please vote for https://studio.atlassian.com/browse/JST-4869 and tell everyone at Atlassian!

Templates

Why do tables sometimes use Times New Roman as font even if the Scroll Table Normal style in the template uses a different font ?

The reason for the wrong font usually is that in your template the "Scroll Table Normal" style does not define a font. Therefore it falls back to the "Normal Table" style, which neither defines a font. And then it falls back to some standard font defined somewhere in Word. On your system this probably something different from Times New Roman.

Unfortunately when you edit the style in Word then the font box will show something like "Calibri (Body)". This means it will fall back to the font specified in the "Body" style, which ultimately is / falls back to that "Word default font" unless you specified something explicitly.

Scroll Office uses Times New Roman in these cases because the Word programming library that we internally use returns that font if the style contains no explicit setting for the font. And we can't distinguish this case from a case where the user actually selected Times New Roman.

To fix it you simply need to explicitly set the font to "Calibri" (for example) in the "Scroll Table Normal" style.