Feature req: ROT13 function: Page 2 - Usenapp

Feature req: ROT13 function

Snit

I know I would like it... though I think I have / had a text service which allowed me to add it to any program. 🙂

Jaimie

The worst thing is I could read Alan's encoded text directly, without needing a decoder... Too many years on Usenet modifies your brain!

hein_dd

Did anybody solved this request?
I would like to have this feature also!

I use usenet also for several years, but I never found a place in my brain to store an automatic converter for Rot13. Smaller number in Hex I can translate into decimal number, but Rot13, no way :-)
Best wishes...
hein_dd

Andre

hein_dd Did anybody solved this request?

Not yet, but it's still on the list.

Preparations are currently made for the official Usenapp release and all open requests are scheduled to be included after this release.

hein_dd

Hi. Usenapp is released now, had you found time to look into these nice request?

Andre

I am currently focusing on the file search part, as this also needed to be done.

When finished I will continue with the development of the newsreader.

Snipe

Is there any progress with adding the ROT13 function, please? I too would find this very useful.

Andre

ROT13 has been implemented in v0.95.
Released today.

There is no way to detect if a message is in ROT13, so pressing the ROT13 button will always Do/Undo the entire body text (if encoded it will be decoded, otherwise the text will be encoded).

If you reply to a message that is ROT13 encoded, you first need to decode it, enter your text and then encode it again before posting to usenet.

Questions/ideas or improvements are always welcome.

Snipe

Thank you very much, Andre, that works nicely. --Sn!pe

Andre

Do you know 'old' postings/newsgroups in ROT13?
I would like to know if the prefixes and signatures are normally also encoded in ROT13 when posting to usenet.

Alan_B

Gunaxf sbe gur hcqngr. V'z fher V jvyy svaq n hfr sbe vg.

Andre

Alan_B Gunaxf sbe gur hcqngr. V'z fher V jvyy svaq n hfr sbe vg

I know how the encoded text look like, but I would like to know if the prefixes and signatures are normally also encoded in ROT13 when posting to usenet.

Snipe

In MacSOUP, my usual reader:-
Cmd-3 ROTs/UnROTs everything in the article body pane, including the .signature.
If I select a portion of text in the article body (and/or .sig) and then hit Cmd-3, only the selection is ROTted/UnROTted.
Headers would not be touched unless I had chosen a view that included the headers with the article body and then
ROTted/UnROTted as above.
Usually ROT/UnROT is only relevant to the body of the article.

HTH --Sn!pe

Snipe

Here is a test message example for you, Andre:

From: snipeco.2@gmail.com (Sn!pe)
Newsgroups: alt.test
Subject: ROT test for Andre -- Ignore
Date: Wed, 30 Dec 2020 15:24:02 +0000
Message-ID: <1p28ddu.q3s5bv1semhpN%snipeco.2@gmail.com>

Andre

Snipe Here is a test message example for you, Andre:

Can you post a full quoted ROT13 reply to that message with MacSoup, please?

Alan_B

This sort of suggests encoding of the signature is optional, in the opinion of the MacSOUP developer at least.

Snipe

Yes, I agree. --Sn!pe

Andre

What I will do it is not encode:

1) The prefix: "On .. wrote .."
2) The signature.

Okay?

Andre

Changed in v0.95.1

Alan_B

Using 0.95.1 - When composing a new message, the body text does not appear to be encoded when ROT13 button pressed. However the whole body and the prefix IS encoded when composing a follow-up. The signature remains un-encoded which is OK.

Andre

Alan_B Using 0.95.1 - When composing a new message, the body text does not appear to be encoded when ROT13 button pressed. However the whole body and the prefix IS encoded when composing a follow-up. The signature remains un-encoded which is OK.

Fixed in v0.95.3

Thanks.

« Previous Page