Currently we're adding "Figure XYZ" or "Table XYZ" to captions when using the scroll-title macro on images or tables.
While a few localisations for those prefixes exist (Russian, German, Italian and English), they are not at all configurable by the user but hardcoded in Scroll Word Exporter. We should make those configurable on the captions tab of the export scheme configuration.
Please see our related documentation for changing the figure/table captions for hard-coded languages - please click here.
The issue description says "While a few localisations for those prefixes exist (Russian, German, Italian and English), they are not at all configurable by the user but hardcoded in Scroll Word Exporter."
The hard-coded defaults would be fine for us (we need German: "Abbildung"), but how does Scroll Word Exporter select the locale then? Does it use the instance locale of Confluence (which is set to English in our case). In my opinion, it could just use the locale setting of the template, which is also used for date formatting etc. Wouldn't this be easy and most consistent?
Scroll Word Exporter actually tries to detect the correct locale from the template docx file. Unfortunately there is no ‘document language setting’ in Word (files). Therefore the locale from the very first paragraph in the document is used. You may change that paragraph’s locale by selecting the paragraph and then using the ‘Language’ button in the ‘Review’ section of the toolbar.
Scroll Word Exporter currently supports caption translations for these languages:
The 'Language' setting in the template (on our template administration screen, not the docx file) is not used for historic versions. In previous versions of Scroll Word Exporter this screen did not exist, so there was no way to choose a language.
We might make this a bit easier by using the language setting from our screen in the future. However this would mean a change in export behaviour for existing templates if the setting and the first paragraph have different values, so it won’t happen in a bugfix release.
It’s working! I changed the language of the first paragraph to German (why was it English anyway?) and now it works like a charm 🙂
Thank you so much, this resolves the issue for us!
Hello, I’m happy for for added several translations, but there is much more languages in the world. It is really hard to pull out few hardcoded string to properties of Scroll Exporter and allow to users fill there any word (or left empty)? Thanks