flnews_post_proc 2.04 → 2.05

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: f0e31bc94142a2ec47e03c78802b468055b2728fa4d74fa320fcfb5d007ce98a
-  data.tar.gz: 8a877289ebfe3c40cc3cf1f02046c667ceec6ba722a7181493d8be819f75af31
+  metadata.gz: 87bf0a3e9a8c5ab513c440c94fd798aba136a4fd72fb351cfbf133f1270e2758
+  data.tar.gz: 32f644c07859db2b6569621b471a786e4409e0cdaffb5e67a193e54d7f7e99a7
 SHA512:
-  metadata.gz: 224cb017bcd798025b4d159536fce5753a58442d27fde12caad6c7d710330bac1a58fd17c2128310144795143b3ad238582cecdc451baa0c94aa242ff9a067e1
-  data.tar.gz: 2d3d88a9bec625acaea47d547d28fc7084a7c56259255e50d312d44808d28d3306e111eed8b9bbea97721cccbe85612de56d970f96f9e6177c650f36a3df8c4b
+  metadata.gz: ae7465a7d6e9ec4dee294344bbdb1d6c10950351f6d5eeddb84c324d3700e653d4bb305170415071632208b3f5ec0e2f4ec05ada59dee07d9426cde2f7e87a1d
+  data.tar.gz: e0180d504592a9ab223d46c994b5a79ae81bb5a2b62970915b0b683d546c79ef2affdd12c6b17932f71a63639d9fc8c25ad41289ec69ce03a429ae71db6c92b0

data/changes.txt

@@ -1,3 +1,5 @@
+v.2.05
+    *) Gemspec: Dependency for io-console added.
 v.2.04
     *) Gemspec: Dependencies added
        -) gem New_rfc_2047 was missing from the specs.

data/doc/fr/html/flnews_post_proc.html

@@ -57,7 +57,7 @@
 
             <li>
               <p><a class="reference internal" href=
-              "#dialogue-pour-desactiver-des-options" id=
+              "#dialogue-pour-desactiver-des-options-1" id=
               "toc-entry-4">Dialogue pour désactiver des
               options</a>
               </p>
@@ -289,10 +289,19 @@
             "#creation-des-notes-de-bas-de-page">Création des notes
             de bas de page</a>)</p>
           </li>
+
+          <li>
+            <p>flnews ne propose actuellement pas la sauvegarde
+            d'un article dont vous voulez retarder la publication.
+            <strong>flnews_post_proc</strong> vous laisse cette
+            option, si un répertoire pour les brouillons a été
+            configuré.</p>
+          </li>
         </ul>
       </section>
 
-      <section id="dialogue-pour-desactiver-des-options">
+      <section id="dialogue-pour-desactiver-des-options-1">
+        <span id="dialogue-pour-desactiver-des-options"></span>
         <h3>Dialogue pour désactiver des options</h3>
 
         <p>ATTN! Depuis la version 1.72, YAD et Zenity ne sont plus
@@ -767,16 +776,15 @@ alt.fr.test: /home/[utilisateur]/.signatures</pre>
       <section id="remplacement-avec-signature">
         <h3>Remplacement avec signature</h3>
 
-        <p>Lors du remplacement d'un article existant, aucune
-        signature n'est appliquée automatiquement. Ceci permet de
-        conserver autant de contenu original que possible.</p>
-
-        <p>Pour conserver la signature originale dans la nouvelle
-        version de l'article :</p>
+        <p>Depuis version 2.0, lors du remplacement d'un article
+        existant, la signature est appliquée de la même manière que
+        pour d'autres nouvelles articles. Quand même, si vous
+        souhaitez garder la signature de l'article que vous
+        remplacez, vous pouvez:</p>
 
         <ol class="arabic simple">
           <li>
-            <p>Dans flnews, sélectionnez l'intégralité de l'article
+            <p>dans flnews, sélectionnez l'intégralité de l'article
             avec la souris – de la première ligne (y compris toute
             introduction) jusqu'à la dernière ligne de la
             signature.</p>
@@ -795,14 +803,17 @@ alt.fr.test: /home/[utilisateur]/.signatures</pre>
           </li>
 
           <li>
-            <p>Envoyez l'article.</p>
+            <p>Dans le <a class="reference internal" href=
+            "#dialogue-pour-desactiver-des-options">Dialogue pour
+            désactiver des options</a> désactiver l'option pour les
+            signatures.</p>
           </li>
-        </ol>
 
-        <p><strong>Note :</strong> Le dialogue de configuration
-        (voir ci-dessous : <a class="reference internal" href=
-        "#override-config">OVERRIDE_CONFIG</a>) n'affecte pas les
-        signatures lors d'un remplacement.</p>
+          <li>
+            <p>Appuyez sur '0' pour valider vos choix et faire
+            flnews envoyer l'article.</p>
+          </li>
+        </ol>
       </section>
 
       <section id="tester">
@@ -897,7 +908,7 @@ alt.fr.test: /home/[utilisateur]/.signatures</pre>
         "https://creativecommons.org/licenses/by-nd/4.0/deed.fr">CC
         BY-ND 4.0</a></p>
 
-        <p>Date: 2026-06-30</p>
+        <p>Date: 2026-08-11</p>
 
         <p><strong>Ω</strong>
         </p>
@@ -906,7 +917,7 @@ alt.fr.test: /home/[utilisateur]/.signatures</pre>
   </main>
 
   <div id='page_dt'>
-    2026-06-30
+    2026-08-11
   </div>
 </body>
 </html>

data/doc/fr/rst/flnews_post_proc.rst

@@ -111,6 +111,12 @@ des raisons parfois arbitraires :
   l'objet plus précisément=% » (voir plus bas : `Création des notes de bas
   de page`_)
 
+* flnews ne propose actuellement pas la sauvegarde d'un article dont vous voulez
+  retarder la publication. |program| vous laisse cette option, si un répertoire
+  pour les brouillons a été configuré.
+
+.. _Dialogue pour désactiver des options:
+
 Dialogue pour désactiver des options
 ---------------------------------------
 ATTN! Depuis la version 1.72, YAD et Zenity ne sont plus utilisés pour le
@@ -458,13 +464,11 @@ fois que les marqueurs de notes de bas de page auront remplacé le texte intégr
 Remplacement avec signature
 ---------------------------
 
-Lors du remplacement d'un article existant, aucune signature n'est appliquée
-automatiquement. Ceci permet de conserver autant de contenu original que
-possible.
-
-Pour conserver la signature originale dans la nouvelle version de l'article :
+Depuis version 2.0, lors du remplacement d'un article existant, la signature est appliquée
+de la même manière que pour d'autres nouvelles articles. Quand même, si vous souhaitez
+garder la signature de l'article que vous remplacez, vous pouvez:
 
-1. Dans flnews, sélectionnez l'intégralité de l'article avec la souris – de la
+1. dans flnews, sélectionnez l'intégralité de l'article avec la souris – de la
    première ligne (y compris toute introduction) jusqu'à la dernière ligne de
    la signature.
 
@@ -474,10 +478,9 @@ Pour conserver la signature originale dans la nouvelle version de l'article :
    dans le texte modifiable, contrairement à la situation normale où flnews
    supprime les signatures avant d'ouvrir l'éditeur.
 
-4. Envoyez l'article.
+4. Dans le `Dialogue pour désactiver des options`_ désactiver l'option pour les signatures.
 
-**Note :** Le dialogue de configuration (voir ci-dessous : `OVERRIDE_CONFIG`_)
-n'affecte pas les signatures lors d'un remplacement.
+5. Appuyez sur '0' pour valider vos choix et faire flnews envoyer l'article.
 
 Tester
 ------

data/doc/html/flnews_post_proc.html

@@ -257,6 +257,14 @@
               "#editing-footnotes">EDITING FOOTNOTES</a>,
               below.</p>
             </li>
+
+            <li>
+              <p>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.</p>
+            </li>
           </ul>
         </blockquote>
       </section>
@@ -714,10 +722,43 @@ comp.*: /home/[user]/.my_sigs</pre>
         <span id="signatures-in-supersedes"></span>
         <h3>Signatures in Supersedes</h3>
 
-        <p>Since version 2.0, signatures in supersedes are not
-        handled differently from other articles. This paragraph
-        will be removed in the next version of the
-        documentation.</p>
+        <p>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:</p>
+
+        <blockquote>
+          <ul class="simple">
+            <li>
+              <p>select the complete message body of the original
+              article, including the signature</p>
+            </li>
+
+            <li>
+              <p>Trigger the supersedes in flnews.</p>
+            </li>
+
+            <li>
+              <p>Write your new version of the article while
+              leaving the current signature intact.</p>
+            </li>
+
+            <li>
+              <p>In the Override Dialog (see <a class=
+              "reference internal" href=
+              "#dialog-for-overriding-settings">Dialog for
+              Overriding Settings</a>), clear the signature
+              option.</p>
+            </li>
+
+            <li>
+              <p>Hit '0' to confirm your options and to make flnews
+              send the article.</p>
+            </li>
+          </ul>
+        </blockquote>
       </section>
 
       <section id="testing-1">
@@ -825,7 +866,7 @@ comp.*: /home/[user]/.my_sigs</pre>
           "https://creativecommons.org/licenses/by-nd/4.0/">CC
           BY-ND 4.0</a></p>
 
-          <p>Date: 2026-08-01</p>
+          <p>Date: 2026-08-11</p>
         </blockquote>
 
         <p><strong>Ω</strong>
@@ -835,7 +876,7 @@ comp.*: /home/[user]/.my_sigs</pre>
   </main>
 
   <div id='page_dt'>
-    2026-08-01
+    2026-08-11
   </div>
 </body>
 </html>

data/doc/rst/flnews_post_proc.rst

@@ -97,6 +97,11 @@ Limitations of Basic Newsreaders
     describing the object further=%". See also the hints under 
     `EDITING FOOTNOTES`_, below.
 
+  * 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.
+
 .. _Dialog for Overriding Settings:
 
 Dialog for Overriding Settings
@@ -409,9 +414,24 @@ Editing footnotes
 
 Signatures in Supersedes
 ------------------------
-Since version 2.0, signatures in supersedes are not handled differently from
-other articles. This paragraph will be removed in the next version of the
-documentation.
+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:
+
+  * select the complete message body of the original article, including the
+    signature
+    
+  * Trigger the supersedes in flnews.
+
+  * Write your new version of the article while leaving the current signature
+    intact.
+
+  * In the Override Dialog (see `Dialog for Overriding Settings`_), clear the
+    signature option.
+
+  * Hit '0' to confirm your options and to make flnews send the article.
 
 .. _Testing:
 

data/lib/version.rb

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

metadata

@@ -1,139 +1,145 @@
 --- !ruby/object:Gem::Specification
 name: flnews_post_proc
 version: !ruby/object:Gem::Version
-  version: "2.04"
+  version: '2.05'
 platform: ruby
 authors:
-  - Michael Uplawski
+- Michael Uplawski
 bindir: bin
 cert_chain: []
-date: 2026-08-10 00:00:00.000000000 Z
+date: 2026-08-20 00:00:00.000000000 Z
 dependencies:
-  - !ruby/object:Gem::Dependency
-    name: diffy
-    requirement: !ruby/object:Gem::Requirement
-      requirements:
-        -
-          - ~>
-          - !ruby/object:Gem::Version
-            version: "3.4"
-        -
-          - ">="
-          - !ruby/object:Gem::Version
-            version: 3.4.4
-    type: :runtime
-    prerelease: false
-    version_requirements: !ruby/object:Gem::Requirement
-      requirements:
-        -
-          - ~>
-          - !ruby/object:Gem::Version
-            version: "3.4"
-        -
-          - ">="
-          - !ruby/object:Gem::Version
-            version: 3.4.4
-  - !ruby/object:Gem::Dependency
-    name: mimemagic
-    requirement: !ruby/object:Gem::Requirement
-      requirements:
-        -
-          - ~>
-          - !ruby/object:Gem::Version
-            version: "0.4"
-        -
-          - ">="
-          - !ruby/object:Gem::Version
-            version: 0.4.3
-    type: :runtime
-    prerelease: false
-    version_requirements: !ruby/object:Gem::Requirement
-      requirements:
-        -
-          - ~>
-          - !ruby/object:Gem::Version
-            version: "0.4"
-        -
-          - ">="
-          - !ruby/object:Gem::Version
-            version: 0.4.3
-  - !ruby/object:Gem::Dependency
-    name: new_rfc_2047
-    requirement: !ruby/object:Gem::Requirement
-      requirements:
-        -
-          - ~>
-          - !ruby/object:Gem::Version
-            version: "1.0"
-        -
-          - ">="
-          - !ruby/object:Gem::Version
-            version: 1.0.0
-    type: :runtime
-    prerelease: false
-    version_requirements: !ruby/object:Gem::Requirement
-      requirements:
-        -
-          - ~>
-          - !ruby/object:Gem::Version
-            version: "1.0"
-        -
-          - ">="
-          - !ruby/object:Gem::Version
-            version: 1.0.0
+- !ruby/object:Gem::Dependency
+  name: diffy
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '3.4'
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: 3.4.4
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '3.4'
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: 3.4.4
+- !ruby/object:Gem::Dependency
+  name: mimemagic
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '0.4'
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: 0.4.3
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '0.4'
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: 0.4.3
+- !ruby/object:Gem::Dependency
+  name: new_rfc_2047
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '1.0'
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: 1.0.0
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '1.0'
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: 1.0.0
+- !ruby/object:Gem::Dependency
+  name: io-console
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '0.9'
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: 0.9.2
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '0.9'
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: 0.9.2
 description: Post-processor for Usenet-articles created in flnews
 email: michael.uplawski@uplawski.eu
 executables:
-  - flnews_post_proc
+- flnews_post_proc
 extensions: []
 extra_rdoc_files: []
 files:
-  - README.md
-  - bin/flnews_post_proc
-  - changes.txt
-  - doc/fr/html/flnews_post_proc.html
-  - doc/fr/man/flnews_post_proc.1.gz
-  - doc/fr/pdf/flnews_post_proc.pdf
-  - doc/fr/rst/flnews_post_proc.rst
-  - doc/html/flnews_post_proc.html
-  - doc/license.txt
-  - doc/man/flnews_post_proc.1.gz
-  - doc/pdf/flnews_post_proc.pdf
-  - doc/rst/flnews_post_proc.rst
-  - lib/basic_logging.rb
-  - lib/body.rb
-  - lib/color_output.rb
-  - lib/configuration.rb
-  - lib/flnews_post_proc.conf
-  - lib/flnews_post_proc.rb
-  - lib/headers.rb
-  - lib/newsgroups.rb
-  - lib/override.rb
-  - lib/ruby_dlg
-  - lib/version.rb
+- README.md
+- bin/flnews_post_proc
+- changes.txt
+- doc/fr/html/flnews_post_proc.html
+- doc/fr/man/flnews_post_proc.1.gz
+- doc/fr/pdf/flnews_post_proc.pdf
+- doc/fr/rst/flnews_post_proc.rst
+- doc/html/flnews_post_proc.html
+- doc/license.txt
+- doc/man/flnews_post_proc.1.gz
+- doc/pdf/flnews_post_proc.pdf
+- doc/rst/flnews_post_proc.rst
+- lib/basic_logging.rb
+- lib/body.rb
+- lib/color_output.rb
+- lib/configuration.rb
+- lib/flnews_post_proc.conf
+- lib/flnews_post_proc.rb
+- lib/headers.rb
+- lib/newsgroups.rb
+- lib/override.rb
+- lib/ruby_dlg
+- lib/version.rb
 licenses:
-  - WTFPL
+- WTFPL
 metadata:
-  homepage_uri: "https://www.uplawski.eu/software/flnews_post_proc/"
-  documentation_uri: "https://www.uplawski.eu/div/flnews/gem_doc/html/flnews_post_proc.html"
-  changelog_uri: "https://www.uplawski.eu/div/flnews/gem_doc/changes.txt"
+  homepage_uri: https://www.uplawski.eu/software/flnews_post_proc/
+  documentation_uri: https://www.uplawski.eu/div/flnews/gem_doc/html/flnews_post_proc.html
+  changelog_uri: https://www.uplawski.eu/div/flnews/gem_doc/changes.txt
 rdoc_options: []
 require_paths:
-  - lib
+- lib
 required_ruby_version: !ruby/object:Gem::Requirement
   requirements:
-    -
-      - ">="
-      - !ruby/object:Gem::Version
-        version: "4.0"
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: '4.0'
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
-    -
-      - ">="
-      - !ruby/object:Gem::Version
-        version: "0"
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: '0'
 requirements: []
-rubygems_version: 4.1.0.dev
+rubygems_version: 4.0.18
 specification_version: 4
-summary: "Modify news posts, before flnews sends them."
+summary: Modify news posts, before flnews sends them.
 test_files: []