flnews_post_proc 2.08 → 2.09

data/doc/man/flnews_post_proc.1

@@ -0,0 +1,648 @@
+.\" Man page generated from reStructuredText
+.\" by the Docutils 0.23 manpage writer.
+.
+.
+.nr rst2man-indent-level 0
+.
+.de1 rstReportMargin
+\\$1 \\n[an-margin]
+level \\n[rst2man-indent-level]
+level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
+-
+\\n[rst2man-indent0]
+\\n[rst2man-indent1]
+\\n[rst2man-indent2]
+..
+.de1 INDENT
+.\" .rstReportMargin pre:
+. RS \\$1
+. nr rst2man-indent\\n[rst2man-indent-level] \\n[an-margin]
+. nr rst2man-indent-level +1
+.\" .rstReportMargin post:
+..
+.de UNINDENT
+. RE
+.\" indent \\n[an-margin]
+.\" old: \\n[rst2man-indent\\n[rst2man-indent-level]]
+.nr rst2man-indent-level -1
+.\" new: \\n[rst2man-indent\\n[rst2man-indent-level]]
+.in \\n[rst2man-indent\\n[rst2man-indent-level]]u
+..
+.TH flnews_post_proc "1" "Tue 22 Sep 2026" "1" "General Commands"
+.SH Name
+flnews_post_proc \- Post-Processor for the flnews Newsreader
+.INDENT 0.0
+.IP \(bu 2
+SYNOPSIS
+.IP \(bu 2
+DESCRIPTION
+.INDENT 2.0
+.IP \(bu 2
+Limitations of Basic Newsreaders
+.IP \(bu 2
+Dialog for Overriding Settings
+.UNINDENT
+.IP \(bu 2
+CONFIGURATION
+.INDENT 2.0
+.IP \(bu 2
+Configuration Options
+.UNINDENT
+.IP \(bu 2
+Other Information
+.INDENT 2.0
+.IP \(bu 2
+Subject changes:
+.IP \(bu 2
+Editing footnotes
+.IP \(bu 2
+Signatures in Supersedes
+.IP \(bu 2
+Testing
+.IP \(bu 2
+Source Code
+.IP \(bu 2
+License
+.IP \(bu 2
+Author
+.IP \(bu 2
+This document
+.UNINDENT
+.UNINDENT
+.SH SYNOPSIS
+.INDENT 0.0
+.INDENT 3.5
+The post\-processor is invoked by piping an article into it. This typically
+occurs automatically when the \(dqpost_proc\(dq variable is set to \fBflnews_post_proc\fP
+in the flnews configuration file.
+.sp
+For testing purposes, you can also pipe locally stored articles into the
+post\-processor using a command like:
+.INDENT 0.0
+.INDENT 3.5
+\fBflnews_post_proc\fP < article
+.UNINDENT
+.UNINDENT
+.sp
+\&.or:
+.INDENT 0.0
+.INDENT 3.5
+cat article.txt | \fBflnews_post_proc\fP
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.SH DESCRIPTION
+.INDENT 0.0
+.INDENT 3.5
+The flnews newsreader fully supports Usenet access, enabling the reception and
+reading of articles from newsgroups, as well as composing and posting them.
+.sp
+When comparing various news clients, differences will often influence your
+choice of preferred client. Flnews distinguishes itself by not only offering
+control over its internal behavior, but also by allowing you to modify outgoing
+posts just before they are sent to the configured NNTP server.
+.sp
+The \fBflnews_post_proc\fP program can be used to modify and enhance a post in ways
+that flnews alone cannot. It is configurable and may meet the needs of some
+Usenet users, though it is primarily intended as a starting point for creating
+your own custom solutions.
+.UNINDENT
+.UNINDENT
+.SS Limitations of Basic Newsreaders
+.INDENT 0.0
+.INDENT 3.5
+While flnews creates posts that are generally complete and ready for
+submission, there are instances where users might find the output
+unsatisfactory for arbitrary reasons:
+.INDENT 0.0
+.IP \(bu 2
+If you\(aqre posting to different newsgroups in multiple languages, the
+introductory line referencing a prior post can only be set once in the flnews
+configuration file. As a result, posts to a French newsgroup, for example,
+may start with an introduction in English. The post\-processor can address
+this by setting specific introductory lines for each newsgroup.
+.IP \(bu 2
+Similar issues arise when you set a standard signature and want it to vary
+based on the newsgroup. The post\-processor allows different signatures to be
+used for different newsgroups, and you can even randomize the selection from
+a list of signatures stored in a file.
+.IP \(bu 2
+Custom headers, such as GnuPG key IDs or your language proficiency, can also
+be added to posts, though signatures may be a better alternative. Custom
+headers can be defined in the configuration file and will be added to
+outgoing posts.
+.IP \(bu 2
+Headers like \(dqArchive\(dq and \(dqX\-No\-Archive\(dq are sometimes set to prevent an
+article from being indexed by search engines (e.g., Google). For example,
+test posts likely don\(aqt need to be included in search results. The
+post\-processor can apply both headers to all posts sent to certain
+newsgroups.
+.UNINDENT
+.sp
+\fBNOTE\fP: As of 2024, the \(dqX\-No\-Archive\(dq header has limited effectiveness,
+and it is up to server operators whether or not to honor it.
+.INDENT 0.0
+.IP \(bu 2
+Posts that include many references to other posts or URLs can become
+cluttered. The post\-processor can convert marked text into footnotes, similar
+to the <ref/> link format used in Wikipedia, with the delimiter configurable
+in the configuration file.
+Example (using %=): \(dqThis is an object %=and this becomes the footnote,
+describing the object further=%\(dq. See also the hints under
+EDITING FOOTNOTES, below.
+.IP \(bu 2
+When you decide to postpone the publication of an article, flnews does
+currently not offer a way to keep draft messages. The post\-processor lets
+you save preliminary versions of your message in a configured directory
+instead of posting them.
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.SS Dialog for Overriding Settings
+.INDENT 0.0
+.INDENT 3.5
+\fBIMPORTANT\fP: As of version 2.01, only the text interface remains to display the dialog.
+XTerm \%<https://\:xterm\:.dev/> must be installed to use the dialog.
+.sp
+Before the post\-processor runs, a dialog can be displayed to allow users to
+\fBdisable\fP certain CONFIGURATION options and – as of version 2.01 – to
+\fBenable\fP others . If XTerm is available, you can choose to disable the
+following options. You \fBcannot\fP enable options that haven\(aqt already been
+set in the configuration. But you can choose to add an option that is not present
+in the configuration file:
+.INDENT 0.0
+.INDENT 3.5
+.INDENT 0.0
+.IP \(bu 2
+Signatures (if set in the CONFIGURATION) can be \fBignored\fP\&. A default signature will be used, or no signature at all.
+.IP \(bu 2
+Custom headers can be \fBomitted\fP\&.
+.IP \(bu 2
+The \(dqArchive\(dq and \(dqX\-No\-Archive\(dq headers can be \fBignored\fP if set for the current newsgroup.
+.IP \(bu 2
+Logging can be \fBdisabled\fP, if enabled.
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.sp
+There is 1 additional option, which is disabled by default, that you can enable only in the dialog and nowhere else:
+.INDENT 0.0
+.INDENT 3.5
+.INDENT 0.0
+.IP \(bu 2
+The current message can be saved as a draft,  \fBinstead\fP of being posted to Usenet.
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.sp
+When your configuration contains the path to a directory for these drafts (option DRAFT_DIR), it will be used to store
+these draft messages, otherwise the temporary directory from the environment variable $TEMP.
+.sp
+Pressing Esc or the Cancel button on the dialog will interrupt the process, and
+flnews will not post the article.
+.sp
+To disable the dialog entirely (and apply all configured options without
+further interaction), set the \fBOVERRIDE_CONFIG\fP option.
+.UNINDENT
+.UNINDENT
+.SH CONFIGURATION
+.INDENT 0.0
+.INDENT 3.5
+Upon first execution of the program, a copy of the original configuration file
+is created in \fI/home/[user]/.flnews_post_proc.conf\fP\&. This file is used
+thereafter. Deleting it will cause the file to be recreated, but any custom
+changes will be lost.
+.sp
+The configuration file uses YAML syntax and includes detailed explanations. The
+variables within it fall into two categories:
+.INDENT 0.0
+.IP 1. 3
+Two variables that represent values originally set by flnews, which can be
+used or replaced. These elements are typically captured using regular
+expressions.
+.IP 2. 3
+Most variables define new or modified content.
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.SS Configuration Options
+.\" empty lines in the following definition list are in reality '\ '
+.
+.sp
+\fBFUP_NAME\fP
+.INDENT 0.0
+.INDENT 3.5
+A regular expression that matches the name of the previous poster in a
+quoted post. This string is recognized in the original article and used
+with the matching element from GROUP_INTROS\&.
+.sp
+Leave this field empty to retain the default value from the FLNews
+configuration.
+.sp
+CONTENT: A string representing a regular expression.
+.sp
+DEFAULT: EMPTY
+.sp
+EXAMPLE1: \(dqOn \e\ed+.\e\ed+.\e\ed{2,4} at \e\ed+:\e\ed+ \fB(.*)\fP wrote:\(dq
+.sp
+EXAMPLE2: \(dq\fB(.*)\fP wrote:\(dq
+.UNINDENT
+.UNINDENT
+.sp
+\fBFUP_GROUP\fP
+.INDENT 0.0
+.INDENT 3.5
+A regular expression that matches the newsgroup where the quoted post was
+published.
+.sp
+Leave this field empty to ignore the exact group.
+.sp
+CONTENT: A string representing a regular expression.
+.sp
+DEFAULT: EMPTY
+.sp
+EXAMPLE: \(dqwrote in \fB(.*)\fP:\(dq
+.UNINDENT
+.UNINDENT
+.sp
+\fBGROUP_INTROS\fP
+.INDENT 0.0
+.INDENT 3.5
+Introductory strings referring to the previous poster in a quoted post.
+When the newsgroup matches FUP_GROUP, these variables are used in the
+resulting introduction.
+.sp
+CONTENT: A newsgroup or regular expression per line, followed by a colon,
+space, and string.
+.sp
+DEFAULT: As configured in FLNews.
+.sp
+EXAMPLE: alt.test: \(dqThus spoke %fup_name% on that baleful %fup_date%:\(dq
+.UNINDENT
+.UNINDENT
+.sp
+\fBGROUP_SIGS\fP
+.INDENT 0.0
+.INDENT 3.5
+Signature lines for each newsgroup or a path to a file containing
+signatures, which should be formatted and separated by one empty line. A
+random signature is picked from the file for each newsgroup. You can also
+source another file within the signature file by starting a line with
+\(dq.  /path/to/other/file\(dq.
+.sp
+CONTENT: A newsgroup or regular expression per line, followed by a colon,
+space, and string.
+.sp
+DEFAULT: As configured in flnews.
+.sp
+EXAMPLE:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.EX
+alt.test: \(dqSignature for alt.test\e\er\e\ensecond line\(dq
+comp.*: /home/[user]/.my_sigs
+.EE
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.sp
+\fBCUSTOM_HEADERS\fP
+.INDENT 0.0
+.INDENT 3.5
+Additional custom headers to be added to outgoing articles.
+.sp
+CONTENT: One line per header, starting with a dash and space, followed by
+the header name and value.
+.sp
+DEFAULT: Undefined
+.sp
+EXAMPLE:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.EX
+\- \(aqX\-My\-Header: nothing fancy\(aq
+\- \(aqX\-Another\-Header: care not!\(aq
+.EE
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.sp
+\fBNAME_POSTPROCESSOR\fP
+.INDENT 0.0
+.INDENT 3.5
+Can be used to set a custom header \(dqX\-Post\-Processor\(dq with the name of
+the program and its current version. Leave empty or set to no or false
+to avoid the creation of this header.
+This setting is independent of the presence or absence of other custom
+headers and cannot be manipulated in the Override Dialog, only in the
+configuration file.
+.sp
+CONTENT: yes, YES, True, no, NO, empty string, False and variations.
+.sp
+DEFAULT: Empty
+.sp
+EXAMPLE: Yes
+.UNINDENT
+.UNINDENT
+.sp
+\fBNO_ARCHIVE_GROUPS\fP
+.INDENT 0.0
+.INDENT 3.5
+Newsgroups where the \(dqArchive: no\(dq and \(dqX\-No\-Archive: YES\(dq headers should
+be set.
+.sp
+CONTENT: A line with a dash and space, followed by the group name or a
+regular expression.
+.sp
+DEFAULT: Empty
+.sp
+EXAMPLE:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.EX
+\- \(dqalt.test\(dq
+\- \(dq^news.*\(dq
+.EE
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.sp
+\fBDEBUG_LOG\fP
+.INDENT 0.0
+.INDENT 3.5
+The name of the file where debug messages are logged. If specified, logging
+will be enabled.  If empty, logging is disabled.
+.sp
+CONTENT: The name of a writable file, which will be created if it doesn\(aqt
+exist and overwritten if necessary.
+.sp
+DEFAULT: Empty
+.sp
+EXAMPLE: \(dq/tmp/a_log\-file.txt\(dq
+.UNINDENT
+.UNINDENT
+.sp
+\fBLOG LEVEL\fP
+.INDENT 0.0
+.INDENT 3.5
+One of: debug, fatal, error, info, warn.
+.UNINDENT
+.UNINDENT
+.sp
+\fBREFERENCES_SEPARATOR\fP
+.INDENT 0.0
+.INDENT 3.5
+A symbol or sequence marking the end of the message body and the beginning
+of a footnote list.  If not defined, footnotes are appended directly after
+the message body.
+.sp
+CONTENT: A quoted symbol or sequence.
+.sp
+DEFAULT: Empty
+.sp
+EXAMPLE: \(dq\-\-\-\-\-\-\-\-\-\(dq
+.UNINDENT
+.UNINDENT
+.sp
+\fBREFERENCES_DELIMITER\fP
+.INDENT 0.0
+.INDENT 3.5
+A sequence marking the beginning and end of text to be used as a footnote
+or reference. The reversed sequence is used to mark the end.
+.sp
+CONTENT: A quoted symbol or sequence.
+.sp
+DEFAULT: None (empty)
+.sp
+EXAMPLE: \(dq%?\(dq
+.UNINDENT
+.UNINDENT
+.sp
+\fBREFERENCE_FORMAT\fP
+.INDENT 0.0
+.INDENT 3.5
+A format string using \fI%s\fP for a number to replace the reference text in
+the body.
+.sp
+DEFAULT: \(dq %s)\(dq → becomes 1) ... 2) ... 3)
+.sp
+EXAMPLE: \(dq(%s)\(dq → becomes (1) ... (2) ... (3)
+.UNINDENT
+.UNINDENT
+.sp
+\fBVFY_URLS\fP
+.INDENT 0.0
+.INDENT 3.5
+A boolean constant determining whether URLs should be verified and
+corrected if necessary.  URL manipulations include adding angular brackets
+(\(aq<\(aq, \(aq>\(aq) and slashes after \(dqhttp(s):\(dq.
+.sp
+CONTENT: One of YES, yes, NO, no (case insensitive).
+.sp
+DEFAULT: yes
+.sp
+EXAMPLE: ... I leave this to your discretion.
+.UNINDENT
+.UNINDENT
+.sp
+\fBOVERRIDE_CONFIG\fP
+.INDENT 0.0
+.INDENT 3.5
+A boolean constant that controls whether configuration options can be
+overridden before posting.
+.sp
+Set this to \(dqno\(dq to disable the dialog.
+.sp
+DEFAULT: yes
+.sp
+EXAMPLE: No
+.UNINDENT
+.UNINDENT
+.sp
+\fBUSE_OLD\fP
+.INDENT 0.0
+.INDENT 3.5
+A boolean constant that controls whether \fBflnews_post_proc\fP handles subject changes.
+See Subject changes for the details.
+.sp
+Set to \(dqfalse\(dq or leave empty to ignore subject changes.
+.sp
+DEFAULT: false
+.sp
+EXAMPLE: yes
+.UNINDENT
+.UNINDENT
+.sp
+\fBDRAFT_DIR\fP
+.INDENT 0.0
+.INDENT 3.5
+The path to a directory for draft messages. You can activate an option
+DRAFT_ONLY in the Dialog for Overriding Settings\&. The current message will
+then be saved to this directory, \fBinstead\fP of being posted to Usenet.
+If you leave this option empty, a temporary directory ($TEMP) will be used instead.
+The draft files will be named according to this schema:
+.INDENT 0.0
+.INDENT 3.5
+[n][1st_group][++].draft
+.UNINDENT
+.UNINDENT
+.sp
+where \fIn\fP is the number of files in this directory, \fI1st_group\fP the first
+newsgroup that the message was addressed to and \fI++\fP an optional suffix,
+indicating that there are more newsgroups in the list (cross post). The
+content of a draft file is the current body of the message, preceded by the
+list of newsgroups.
+.sp
+DEFAULT: empty
+.sp
+EXAMPLE: ~/.flnews_drafts
+.UNINDENT
+.UNINDENT
+.SH Other Information
+.SS Subject changes:
+.INDENT 0.0
+.INDENT 3.5
+\fBflnews_post_proc\fP can handle subject changes, provided the configuration option \fBUSE_OLD\fP
+is set to \fBtrue\fP\&.  In this case, additional prefixes are recognized (flnews
+handles \(dqWas:\(dq on its own).  The additional prefixes are case insensitive
+variations of the German \(dq\fIWar:\fP\(dq and a french \(dq\fIÉtait:\fP\(dq, with or without
+Accent. The french prefix can also contain 1 space before the colon.
+.sp
+When you write a follow\-up to an Article with
+\fISubject: This topic (Was: old topic)\fP
+\fBflnews_post_proc\fP will remove the part in parenthesis, also (War: old topic) and
+(était : old topic).
+.sp
+This necessitates that \fByour own subject changes must not use one of those
+prefixes\fP\&.  Instead, use \fI(Old: ...)\fP like in
+\fISubject: new topic (Old: previous topic)\fP
+.sp
+\fBflnews_post_proc\fP will replace Old: by Was: in the posted article.
+.sp
+\fBImportant\fP: When \fIUSE_OLD\fP is true, none of the recognized prefixes will
+survive. If you forget to use \fIOld\fP instead, the subject change will not be
+recognizable as such, your article will only carry the new subject.
+.sp
+Leave the option USE_OLD untouched or set it to \fBfalse\fP to ignore subject
+changes.
+.sp
+\fBNOTE\fP that Flnews may continue to remove the part of the subject line that
+is prefixed with \fI(Was:\fP or \fI(was:\fP\&.
+.UNINDENT
+.UNINDENT
+.SS Editing footnotes
+.INDENT 0.0
+.INDENT 3.5
+Writing footnote text (or URL references) inline while composing an article may
+be tempting, but it will likely break your line formatting. It\(aqs difficult to
+predict line lengths after footnotes are automatically moved to the end.
+Instead, write your complete article first, then add footnotes just before
+posting.
+This lets you anticipate how the final article will look after footnote markers
+replace the inline text (see REFERENCE_FORMAT, above).
+.UNINDENT
+.UNINDENT
+.SS Signatures in Supersedes
+.sp
+Since version 2.0, signatures in supersedes are by default not handled
+differently from other articles, and their signature is assigned in the same
+way as to a new original article.
+However, if you want to maintain the signature from the post that you want to
+replace, you can:
+.INDENT 0.0
+.INDENT 3.5
+.INDENT 0.0
+.IP \(bu 2
+select the complete message body of the original article, including the
+signature
+.IP \(bu 2
+Trigger the supersedes in flnews.
+.IP \(bu 2
+Write your new version of the article while leaving the current signature
+intact.
+.IP \(bu 2
+In the Override Dialog (see Dialog for Overriding Settings), clear the
+signature option.
+.IP \(bu 2
+Hit \(aq0\(aq to confirm your options and to make flnews send the article.
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.SS Testing
+.INDENT 0.0
+.INDENT 3.5
+You can verify the post\-processor’s effect by using one of two methods:
+.INDENT 0.0
+.IP 1. 3
+Pipe a saved post into the program:
+.sp
+\fB:~$ /usr/local/bin/[post\-processor] < [test\-article]\fP
+.INDENT 3.0
+.INDENT 3.5
+This will show the modified article, and you can pipe it into another file
+for further testing.
+.UNINDENT
+.UNINDENT
+.IP 2. 3
+Post directly to a test newsgroup (e.g., alt.test). This is essential before posting to real newsgroups,
+especially when the post\-processor will alter the article.
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.SS Source Code
+.INDENT 0.0
+.INDENT 3.5
+The gem file for the program, available via the gem utility or rubygems.org \%<https://\:rubygems\:.org/\:gems/\:flnews_post_proc>,
+contains all the source code and documentation (this page included). To extract
+it, do the following:
+.INDENT 0.0
+.IP 1. 3
+Extract the gem file: \fItar \-xf flnews_post_proc\-0.1.gem\fP
+.IP 2. 3
+Uncompress the data archive: \fIgunzip data.gz\fP
+.IP 3. 3
+Extract the data archive: \fItar \-xf data.tar\fP
+.UNINDENT
+.sp
+This will create the directories \fIbin\fP, \fIdoc\fP, and \fIlib\fP\&.
+.UNINDENT
+.UNINDENT
+.SS License
+.INDENT 0.0
+.INDENT 3.5
+The \fBflnews_post_proc\fP is distributed under the WTFPL\-2.0 \%<https://\:www\:.wtfpl\:.net/\:about/> or later License.  For
+the complete license text, visit \%<http://\:www\:.wtfpl\:.net/\:txt/\:copying/> or refer to
+the license file in the documentation directory of the gem.
+.UNINDENT
+.UNINDENT
+.SS Author
+.INDENT 0.0
+.INDENT 3.5
+\fBflnews_post_proc\fP has been developed by Michael Uplawski <\%<michael\:.uplawski@\:uplawski\:.eu>>
+.UNINDENT
+.UNINDENT
+.SS This document
+.INDENT 0.0
+.INDENT 3.5
+©Michael Uplawski <\%<michael\:.uplawski@\:uplawski\:.eu>>
+.sp
+License: CC BY\-ND 4.0 \%<https://\:creativecommons\:.org/\:licenses/\:by-nd/\:4\:.0/>
+.sp
+Date: 2026\-09\-22
+.UNINDENT
+.UNINDENT
+.sp
+The man page can be accessed in the ordinary way, by executing \fIman\fP
+\fBflnews_post_proc\fP, \fBif\fP the manpages \%<https://\:rubygems\:.org/\:gems/\:manpages> gem is installed. Initially, executing \fIgem
+manpages \-\-update\-all\fP will ensure that the man pages for all packages which
+provide such documentation are copied to the default locations for man pages.
+.sp
+\fBΩ\fP
+.\" End of generated man page.

data/doc/rst/flnews_post_proc.rst

@@ -11,7 +11,7 @@ flnews_post_proc
 .. _rubygems.org: https://rubygems.org/gems/flnews_post_proc
 .. _en Français: https://www.uplawski.eu/div/flnews/gem_doc/fr
 .. _XTerm: https://xterm.dev/
-
+.. _manpages: https://rubygems.org/gems/manpages
 
 ------------------------------------------
 Post-Processor for the flnews_ Newsreader
@@ -504,6 +504,13 @@ This document
   License: `CC BY-ND 4.0`_
 
   Date: |date|
+ 
+  
+The man page can be accessed in the ordinary way, by executing *man*
+|program|, **if** the `manpages`_ gem is installed. Initially, executing *gem
+manpages --update-all* will ensure that the man pages for all packages which
+provide such documentation are copied to the default locations for man pages.
+
 
 **Ω**
 

data/lib/version.rb

@@ -14,7 +14,7 @@
 =end
 
 PROGNAME = 'flnews_post_proc'
-PROGVERSION = "2.08"
+PROGVERSION = "2.09"
 AUTHORS = "Michael Uplawski"
 EMAIL = "michael.uplawski@uplawski.eu"
 YEARS = "2023 - 2026"