[SourceForge.net Logo]
Polska wersja / Polish version

KeyParaStocX -

[SourceForge] [SourceForge] [Sonar Cloud]

Contents:


Description

KeyParaStocX (Keyword-based Paragraph Styling and Table of Contents eXtension) is an extension for LibreOffice, Apache OpenOffice and the old OpenOffice.org that searches for keywords in a text, changes their style and builds a Table of Contents for them.

The keywords and their target styles can be configured by the users.

Documentation is also available on the KeyParaStocX wiki.

KeyParaStocX can also serve developers as an example of how to write a LibreOffice/Apache OpenOffice component in Python and how to call a Python component from Basic/StarBasic macro code.


Screenshots of KeyParaStocX

Screenshots are available on the SourceForge project page.


Download KeyParaStocX

Current version is 1.0.1.
[CodeQL] [Semgrep] [Bandit] [SonarCloud]

[Sonar Cloud vulnerabilities] [Sonar Cloud bugs] [Sonar Cloud security]
Download this at SourceForge.

Download KeyParaStocX

[Download KeyParaStocX] [Download KeyParaStocX from Apache OpenOffice extensions]
(free badges provided by Shields.io)

[Feed] KeyParaStocX release file feed


Installing the software

Installation steps - simple:

  1. If you have the right file associations configured, simply double-click the KeyParaStocX-1.0.1.oxt file to install the extension.
  2. Restart the application if prompted.

Installation steps - manual:

  1. Open the "Writer" application (word processor) of the office suite.
  2. Open the Tools menu and choose Extension Manager.
  3. Click the "Add" button.
  4. Navigate to and select the KeyParaStocX-1.0.1.oxt extension file.
  5. Accept the license.
  6. Click the "Close" button in the Extension Manager.
  7. Restart the application when prompted.

Uninstallation steps:

  1. Open the "Writer" application (word processor) of the office suite.
  2. Open the Tools menu and choose Extension Manager.
  3. Click the KeyParaStocX extension on the list.
  4. Click the "Remove" button.
  5. Click the "Close" button in the Extension Manager.
  6. Restart the application when prompted.

User manual

Running with the default settings:

  1. Open the Writer application of the office suite.
  2. Open a document you wish to transform.
  3. 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 Tools menu, then Add-Ons and KeyParaStocX.
  4. Wait until a message box saying "OK" is displayed.

Configuring the extension:

  1. Open the Writer application of the office suite.
  2. Choose the Tools menu and then Options...
  3. Expand Writer section on the left (e.g. "LibreOffice Writer").
  4. Click "KeyParaStocX - options".
  5. Set the keywords/regular expressions you wish KeyParaStocX to recognize and the styles you wish they should get.
  6. Click "OK".

There are 7 levels of the Table of Contents and thus 7 keyword-style pairs. The lowest level allows an additional keyword to be searched for in case the primary one isn't found. This is for historical reasons - the primary goal the extension was created for was processing legal acts of two types.


System compatibility

KeyParaStocX, in various versions, has been successfully used in the following office suites:

  1. LibreOffice:
  2. Apache OpenOffice:
  3. OpenOffice.org:

Other versions may also work.


Reporting issues

Any defects or issues can be reported by e-mail or in the SourceForge project defect manager (in English).

Any improvement suggestions can be reported by e-mail or in the SourceForge project ticket manager (in English).

To report usage or installation problems, include:

  1. the KeyParaStocX version you're using, e.g. KeyParaStocX version 1.0.1,
  2. the office suite name and version (e.g. LibreOffice version 7.5.0.3),
  3. a description of the problem that the software causes,
  4. information whether you tried other input files and whether they are processed correctly,
  5. (if the problem is with an input file) if possible, the whole input file or a minimalistic input file that causes the problem to show up,
  6. any error messages that are displayed,
  7. any other information that you think could lead to solving the problem.

-- Help in victory, play a game, send regards, or at least stop using some products


My projects on SourceForge

The always-up-to-date list of my SourceForge projects is on my profile page on SourceForge.


My other software


See my other free software:
  1. Certificate and key generators
  2. E-mail address verifiers
  3. LastMod - a script that inserts or updates a META element with the Last-Modified HTTP header
  4. Atom2Rss - a script that converts an Atom (RFC 4287) channel XML file to an RSS 2.0 XML file
  5. List2Atom - a script that generates an Atom (RFC 4287) channel XML file from a list of files
  6. InSyTrack - telemetry software to track program flow (calls) across libraries, threads, programming languages or even different systems on different machines
See also my assembly-related free software:
  1. Kate/KWrite syntax highlighting for NASM/fasm



Contact information

[mail] Contact me: bogdro AT users . sourceforge . net (English accepted, just say '[SOFT]' in the title).

Keys for the bogdro aliases

[certificate] The public certificate for the e-mail: crt format, cer format, pem format, p7b format, p7c format
Certificate's RIPEMD160 fingerprint: 99:4E:9C:0F:D9:1B:F8:D2:F2:AE:E5:18:9F:3B:5C:61:E6:6C:B4:A8
Certificate's SHA256 fingerprint: 26:22:FE:0F:D7:3A:DE:0A:60:4A:99:29:CB:66:3D:DF:10:45:8B:B6:EC:3E:04:31:DA:67:A5:6E:C4:70:30:B9

[certificate] The public certificate for bogdro-soft: crt format, cer format, pem format, p7b format, p7c format
Certificate's RIPEMD160 fingerprint: 01:A7:57:30:52:EB:F6:58:70:AC:EF:DF:C9:74:50:B1:B3:40:BD:47
Certificate's SHA256 fingerprint: D2:B3:73:22:C0:10:DB:62:3F:DB:1D:FC:EC:44:5C:48:21:0C:C5:9B:E1:7D:E3:63:26:CB:3A:B5:94:45:8C:A5

[certificate] The public certificate for bogdro-perl: crt format, cer format, pem format, p7b format, p7c format
Certificate's RIPEMD160 fingerprint: BF:66:A2:24:6C:87:55:53:90:2C:2B:A5:62:26:D8:11:93:AC:41:98
Certificate's SHA256 fingerprint: 45:C6:17:13:CD:19:FF:39:6C:8D:EC:02:86:5E:E5:90:B5:0B:B6:3F:86:68:E2:7F:60:B7:19:FF:7D:B4:0D:24

[certificate] Issuer's certificate: der format
Issuer's certificate's RIPEMD160 fingerprint: D8:F4:50:F0:8F:79:25:CC:65:20:C9:8D:70:1F:63:14:22:B0:12:24
Issuer's certificate's SHA256 fingerprint: 5E:B4:48:78:F7:58:C6:94:D9:C8:04:B2:42:63:24:9F:5F:03:D0:22:E1:C6:55:18:3E:21:D8:4B:F0:7E:7F:11

[keys] The public GnuPG / PGP keys:
Bogdro-sf e-mail, asc format, key number 476249B50EE1F2E59C4005AF67FFC0790E2D6D3C. A verified version is available at PGP® Global Directory entry for bogdro-sf
Bogdro-soft, asc format, key number 7E05C1468119E8C32B69F72E11B90C14CAE8F72A. A verified version is available at PGP® Global Directory entry for bogdro-soft
Bogdro-perl, asc format, key number A17EBF519B8D55F43472997BFCDBA236678656EA. A verified version is available at PGP® Global Directory entry for bogdro-perl

PGP® and Pretty Good Privacy® are registered trademarks of Symantec Corporation in the United States and other countries.

[certificate] The certificate of the timestamping server which confirms the signature time, can be found on freeTSA.org.


Page information

This page is hosted at SourceForge.net.
This page is written using valid HTML 4.01 [Check my HTML 4.01], [Checked by HTML Validator (based on HTML Tidy)], for all browsers: [For all browsers]

This page uses a valid CSS [Check my CSS]

This page has a content security policy.

This page doesn't use GIF images and doesn't use JPG images.

This page is pure HTML and CSS.

The project icon was created using Inkscape™.


Legal information

"LibreOffice"® is a registered trademark of "The Document Foundation"®.

Apache, OpenOffice, OpenOffice.org and the seagull logo are registered trademarks of The Apache Software Foundation.

Python and PyCon are trademarks or registered trademarks of the Python Software Foundation.

All other trademarks, logos and names on this page and all subpages are properties of their respective owners and are given here only as an example.