KeyParaStocX (Keyword-based Paragraph Styling and Table of Contents eXtension) is a LibreOffice/Apache OpenOffice/OpenOffice.org extension that searches for the configured keywords in a text, changes their style and builds a Table of Contents for them.
The extension was formerly called "Pożeracz ustaw" or "PozeraczUstaw".
Requirements: a compatible office suite:
- LibreOffice (https://www.libreoffice.org/)
- Apache OpenOffice (https://www.openoffice.org/)
- the old OpenOffice.org
Author: Bogdan Drozdowski, bogdro (at) users . sourceforge . net
License: GNU GPL version 3 or newer.
See the INSTALL file for installation instructions.
Project homepage: https://keyparastocx.sourceforge.io/
Running with the default settings:
- Open the Writer application of the office suite.
- Open a document you wish to transform.
- Click the KeyParaStocX icon (the same as the project icon) on the toolbar,
right after the "Toggle Formatting Marks" icon in the spellchecking
toolbar (see the project screenshots), or choose the
Toolsmenu, thenAdd-OnsandKeyParaStocX. - Wait until a message box saying "OK" is displayed.
Configuring the extension:
- Open the Writer application of the office suite.
- Choose the
Toolsmenu and thenOptions.... - Expand
Writersection on the left (e.g. "LibreOffice Writer"). - Click "KeyParaStocX - options".
- Set the keywords/regular expressions you wish KeyParaStocX to recognize and the styles you wish they should get.
- Click "OK".
If you get an error message when running the extension, check the spelling of your styles.
In some office suites, you may need to use the English names for the styles, i.e. "Heading 1" to "Heading 7".
Various versions of KeyParaStocX have been successfully used with the following applications in the following versions:
- LibreOffice:
- 7.x (checked: 7.5.0.3, 7.6.1.2)
- 24.x (checked: 24.2.3.2, 24.8.2.1)
- 25.x (checked: 25.2.0.3)
- Apache OpenOffice:
- 4.x (checked: 4.1.13, 4.1.14)
- OpenOffice.org:
- 3.x (checked: 3.3 probably)
Other versions may also work.
For a list of changes, refer to the ChangeLog file in the package.
The dev branch may contain code which is a work in progress and committed just for tests. The code here may not work properly or even compile.
The master branch may contain code which is committed just for quality tests.
The tags, matching the official packages on SourceForge, should be the most reliable points.