Hallo zusammen,

My agent 8.0 has been working with AgtEx for a year now and everything
is fine. :-)

Many thanks to Ralph!

German umlauts in the subject are not good - I know. But sometimes it
happens. German umlauts are not encoded in the subject. Is there a
solution to this problem?

current example:
M-ID: <news:3718ugttl9hqfnsqu483457ds5rqdg9aqk@4ax.com>

Thank you very much!

Thomas 😷
--
+++ +++ +++ +++ +++ +++ +++ +++ +++ +
Allradantrieb bedeutet,
dass man erst dort stecken bleibt,
wo der Abschleppwagen nicht hinkommt.

On Sun, 16 Jan 2022 17:16:47 +0100, Thomas Barghahn
<Th.Barghahn@t-online.de> wrote:

>Hallo zusammen,
>
>My agent 8.0 has been working with AgtEx for a year now and everything
>is fine. :-)

I searched for AgtEx on the web and couldn't find it. Can you point me
to a link?

Will it work with Agent 6?

On Sun, 16 Jan 2022 10:18:04 -0700, Ken Blake wrote:

> I searched for AgtEx on the web and couldn't find it. Can you point me
> to a link?

MID: <news:unp7if1aabatv2p9qn6oidru81qu2cpc85@4ax.com>
GG: <https://groups.google.com/g/alt.usenet.offline-reader.forte-agent/c/d-df6Rd7yng>
NK: <https://alt.usenet.offline-reader.forte-agent.narkive.com/ULH3A64h>
NB: <https://www.novabbs.com/computers/article-flat.php?id=1433&group=alt.usenet.offline-reader.forte-agent#1433>

> Will it work with Agent 6?

Yes.

--
Kind regards
Ralph

*Ken Blake* meinte:
>On Sun, 16 Jan 2022 17:16:47 +0100, Thomas Barghahn

>>My agent 8.0 has been working with AgtEx for a year now and everything
>>is fine. :-)

>I searched for AgtEx on the web and couldn't find it. Can you point me
>to a link?

>Will it work with Agent 6?

File "READ ME" says:

| [...]
| B. SYSTEM REQUIREMENTS
|
| One of the following:
|
| (a) Agent 8.00 (only) running in Windows or WINE.
| or
| (b) Agent 1.7 - 7.20 running in Windows 2000 or later.
| (Agent 7.10 or 7.20 is recommended for best results.)
| | [...]

Download the ZIP file AgtEx_beta_0.3.2020.700.zip from
<https://ralphfoxnz.blogtown.co.nz/>

See also:

| From: Ralph Fox <-rf-nz-@-.invalid>
| Newsgroups: alt.usenet.offline-reader.forte-agent
| Subject: Announcement: Unicode Extension beta version 0.3.2020.700 for Forte Agent
| Organization: No; Y2.038Chaos instead!
| Message-ID: <unp7if1aabatv2p9qn6oidru81qu2cpc85@4ax.com>

Thomas 😷
--
*Ihre Hausapotheke empfiehlt zum Thema*:
*** Wenn Oma und Opa auf die Nerven gehen ***
Vermengen Sie zwei doppelte Wodka mit ca. 1/2l heißem Bier und reichen
es den quengelnden Personen in einem Kaffeepott ... *danach ist Ruhe*!

On Mon, 17 Jan 2022 06:47:42 +1300, Ralph Fox <-rf-nz-@-.invalid>
wrote:

>On Sun, 16 Jan 2022 10:18:04 -0700, Ken Blake wrote:
>
>> I searched for AgtEx on the web and couldn't find it. Can you point me
>> to a link?
>
> MID: <news:unp7if1aabatv2p9qn6oidru81qu2cpc85@4ax.com>
> GG: <https://groups.google.com/g/alt.usenet.offline-reader.forte-agent/c/d-df6Rd7yng>
> NK: <https://alt.usenet.offline-reader.forte-agent.narkive.com/ULH3A64h>
> NB: <https://www.novabbs.com/computers/article-flat.php?id=1433&group=alt..usenet.offline-reader.forte-agent#1433>
>
>
>> Will it work with Agent 6?

OK, thanks very much. It's installed and successfully tested. I'll let
you know how well it works after I receive some messages that need it.

I see you're the author. Your instructions were very clear. Thanks
again.

On Sun, 16 Jan 2022 19:04:38 +0100, Thomas Barghahn
<Th.Barghahn@t-online.de> wrote:

>*Ken Blake* meinte:
>>On Sun, 16 Jan 2022 17:16:47 +0100, Thomas Barghahn
>
>>>My agent 8.0 has been working with AgtEx for a year now and everything
>>>is fine. :-)
>
>>I searched for AgtEx on the web and couldn't find it. Can you point me
>>to a link?
>
>>Will it work with Agent 6?
>
>File "READ ME" says:
>
>| [...]
>| B. SYSTEM REQUIREMENTS
>|
>| One of the following:
>|
>| (a) Agent 8.00 (only) running in Windows or WINE.
>| or
>| (b) Agent 1.7 - 7.20 running in Windows 2000 or later.
>| (Agent 7.10 or 7.20 is recommended for best results.)
>|
>| [...]
>
>
>Download the ZIP file AgtEx_beta_0.3.2020.700.zip from
><https://ralphfoxnz.blogtown.co.nz/>
>
>See also:
>
>| From: Ralph Fox <-rf-nz-@-.invalid>
>| Newsgroups: alt.usenet.offline-reader.forte-agent
>| Subject: Announcement: Unicode Extension beta version 0.3.2020.700 for Forte Agent
>| Organization: No; Y2.038Chaos instead!
>| Message-ID: <unp7if1aabatv2p9qn6oidru81qu2cpc85@4ax.com>
>
>Thomas ?

Thanks to you too.

On Sun, 16 Jan 2022 14:28:08 -0700, Ken Blake <Ken@invalid.news.com>
wrote:

>On Mon, 17 Jan 2022 06:47:42 +1300, Ralph Fox <-rf-nz-@-.invalid>
>wrote:
>
>>On Sun, 16 Jan 2022 10:18:04 -0700, Ken Blake wrote:
>>
>>> I searched for AgtEx on the web and couldn't find it. Can you point me
>>> to a link?
>>
>> MID: <news:unp7if1aabatv2p9qn6oidru81qu2cpc85@4ax.com>
>> GG: <https://groups.google.com/g/alt.usenet.offline-reader.forte-agent/c/d-df6Rd7yng>
>> NK: <https://alt.usenet.offline-reader.forte-agent.narkive.com/ULH3A64h>
>> NB: <https://www.novabbs.com/computers/article-flat.php?id=1433&group=alt..usenet.offline-reader.forte-agent#1433>
>>
>>
>>> Will it work with Agent 6?
>
>
>OK, thanks very much. It's installed and successfully tested. I'll let
>you know how well it works after I receive some messages that need it.

I should add that I don't get such messages often, so it might be a
while before I post back about this.

*Ken Blake* meinte:
>On Sun, 16 Jan 2022 14:28:08 -0700, Ken Blake <Ken@invalid.news.com>
>wrote:

[...]

>>OK, thanks very much. It's installed and successfully tested. I'll let
>>you know how well it works after I receive some messages that need it.

>I should add that I don't get such messages often, so it might be a
>while before I post back about this.

𝕳𝖊𝖑𝖑𝖔 𝕶𝖊𝖓,
𝖈𝖆𝖓 𝕴 𝖍𝖊𝖑𝖕 𝖞𝖔𝖚?

Thomas 😷
--
+++ +++ +++ +++ +++ +++ +++ +++ +++ +++
Erst im Jahre 2160 fällt Himmelfahrt
wieder auf den 1.Mai!
+++ +++ +++ +++ +++ +++ +++ +++ +++ +++

On Sun, 16 Jan 2022 23:35:28 +0100, Thomas Barghahn
<Th.Barghahn@t-online.de> wrote:

>*Ken Blake* meinte:
>>On Sun, 16 Jan 2022 14:28:08 -0700, Ken Blake <Ken@invalid.news.com>
>>wrote:
>
>[...]
>
>>>OK, thanks very much. It's installed and successfully tested. I'll let
>>>you know how well it works after I receive some messages that need it.
>
>>I should add that I don't get such messages often, so it might be a
>>while before I post back about this.
>
>𝕳𝖊𝖑𝖑𝖔 𝕶𝖊𝖓,
>𝖈𝖆𝖓 𝕴 𝖍𝖊𝖑𝖕 𝖞𝖔𝖚?

Thanks. Going to Edit, language fixed the ??????? that I first saw.
It's a bit of a nuisance, but it works, and I don't have to do it so
often that's it's a big problem.

One of things I liked better about Thunderbird when I used it for
Usenet was that it would do this automatically. But like so many
things, each choice of program has its advantages and disadvantages,
and I decided that going back to Agent was a better choice for me.

On Sun, 16 Jan 2022 16:22:40 -0700, Ken Blake <Ken@invalid.news.com>
wrote:

>On Sun, 16 Jan 2022 23:35:28 +0100, Thomas Barghahn
><Th.Barghahn@t-online.de> wrote:
>
>>*Ken Blake* meinte:
>>>On Sun, 16 Jan 2022 14:28:08 -0700, Ken Blake <Ken@invalid.news.com>
>>>wrote:
>>
>>[...]
>>
>>>>OK, thanks very much. It's installed and successfully tested. I'll let
>>>>you know how well it works after I receive some messages that need it.
>>
>>>I should add that I don't get such messages often, so it might be a
>>>while before I post back about this.
>>
>>????? ???,
>>??? ? ???? ????
>
>
>Thanks. Going to Edit, language fixed the ??????? that I first saw.
>It's a bit of a nuisance, but it works, and I don't have to do it so
>often that's it's a big problem.
>
>One of things I liked better about Thunderbird when I used it for
>Usenet was that it would do this automatically. But like so many
>things, each choice of program has its advantages and disadvantages,
>and I decided that going back to Agent was a better choice for me.

One more question: is there any way to change the default language to
Unicode UTF-8 (English)? If there is, is there any disadvantage to
doing so?

On Mon, 17 Jan 2022 09:22:18 -0700, Ken Blake wrote:

> One more question: is there any way to change the default language to
> Unicode UTF-8 (English)? If there is, is there any disadvantage to
> doing so?

Yes, there is a way.
[For all of Agent] Folder >> Default Properties >> Default Language
[For a single folder] (select folder) >> Folder >> Properties >> Default Language

Yes, there is a disadvantage.
This can mess up non-ASCII characters in the message list pane.

AgtEx only supports the message body pane and compose window. Agent
handles transcoding text in the message list pane in a different way
to how it handles transcoding text in the message body pane. What
works with the message body pane does not work with the message list
pane.

You may be better off keeping the message list pane as ANSI, not Unicode.

--
Kind regards
Ralph

On Tue, 18 Jan 2022 06:16:02 +1300, Ralph Fox <-rf-nz-@-.invalid>
wrote:

>On Mon, 17 Jan 2022 09:22:18 -0700, Ken Blake wrote:
>
>> One more question: is there any way to change the default language to
>> Unicode UTF-8 (English)? If there is, is there any disadvantage to
>> doing so?
>
>Yes, there is a way.
> [For all of Agent] Folder >> Default Properties >> Default Language
> [For a single folder] (select folder) >> Folder >> Properties >> Default Language

Thanks again. I just did that.

>Yes, there is a disadvantage.
>
> This can mess up non-ASCII characters in the message list pane.

I care less about the message list pane then about the message pane.
I'll see how it works out. I can always go back to the way it was if
need be.

>AgtEx only supports the message body pane and compose window. Agent
>handles transcoding text in the message list pane in a different way
>to how it handles transcoding text in the message body pane. What
>works with the message body pane does not work with the message list
>pane.
>
>You may be better off keeping the message list pane as ANSI, not Unicode.

On Sun, 16 Jan 2022 17:16:47 +0100, Thomas Barghahn wrote:

> Hallo zusammen,
>
> My agent 8.0 has been working with AgtEx for a year now and everything
> is fine. :-)
>
> Many thanks to Ralph!
>
> German umlauts in the subject are not good - I know. But sometimes it
> happens. German umlauts are not encoded in the subject. Is there a
> solution to this problem?
>
> current example:
> M-ID: <news:3718ugttl9hqfnsqu483457ds5rqdg9aqk@4ax.com>
>
> Thank you very much!
>
> Thomas 😷

AgtEx supports Unicode in the message body and in parts of the
compose window (the compose body, and the compose subject for some
combinations of Agent and Windows).

Agent handles transcoding message list text in a very different way
to how it handles transcoding message body text. This difference
means AgtEx does not support Unicode in the message list.

To show how this applies to M-ID: <news:3718ugttl9hqfnsqu483457ds5rqdg9aqk@4ax.com>

That message is posted in the character set ISO-8859-1.

👉 MESSAGE BODY

Agent uses late transcoding for the message body.
When you download the message body, Agent stores the message body
in the original ISO-8859-1 charset.
When you view the message body in Unicode UTF-8, Agent transcodes
the message to UTF-8 and sends that UTF-8 to display in a UTF-8 font.
You see the message body as it should be.

👉 MESSAGE LIST

Agent uses early or no transcoding for the message list
(early for 'RFC2047' MIME subject headers, none for 7-bit/8-bit
subject headers).
in this case the subject header is 8-bit (not 'RFC2047' MIME).
When you get headers, Agent will assume it is already in the
required code page and will not transcode it.
If you view the message list in Unicode UTF-8, Agent will do
no further transcoding. Agent assumes its saved copy of the
message list is already in the correct code page.
Agent sends the subject text (which is in ISO-8859-1) to display
in a UTF-8 font. Because the subject text is not in UTF-8, you
get mojibake characters like � in place of the é and Ü.

Your best settings for now might be like so:

1) Do not use UTF-8 fonts for the message list.
Screen-shot: <http://img4.imagetitan.com/img.php?image=24_agtex-font-settings.png>

The reason is to avoid the problem described in
"MESSAGE LIST" above.

2) If you do #1 above, then also...
In the Unicode UTF-8 language settings, put a check-mark in
'MIME Headers' for Usenet text as well as for Email Text.

The reason for this is that
* If this is not checked, Agent will post the subject in raw UTF-8.
* When displaying the message list, Agent will not transcode
the subject from UTF-8 to Western codepage 1252.
* Characters like Ü in the message list will appear as mojibake
in a Western font.

3) If you do #1 above, and you or anyone else is doing #2 above (posting
with 'RFC2047' MIME subject headers), then...

Do not use UTF-8 for the newsgroup folder language.

The reason for this is that:
* When you download newsgroup headers, Agent will immediately
transcode 'RFC2047' MIME subject headers into the code page
for the newsgroup language -- which would be UTF-8 when the
newsgroup folder language is UTF-8.
* When displaying the message list, Agent will not transcode
the subject from raw UTF-8 to Western codepage 1252.
* Characters like Ü in the message list will appear as mojibake
in a Western font.

--
Kind regards
Ralph
😷️💉︎💉︎ ✔️

*Ralph Fox* meinte:
>On Sun, 16 Jan 2022 17:16:47 +0100, Thomas Barghahn wrote:

[...]

>> German umlauts in the subject are not good - I know. But sometimes it
>> happens. German umlauts are not encoded in the subject. Is there a
>> solution to this problem?

[...]

>Your best settings for now might be like so:

> 1) Do not use UTF-8 fonts for the message list.
> Screen-shot: <http://img4.imagetitan.com/img.php?image=24_agtex-font-settings.png>

This picture gave the decisive clue! *I foolishly* overlooked the option
"Use the variable-pitch body font for headers" or deactivated it! :-(
Now everything works perfectly! :-)

Thank you very much for your detailed advice!
Please all stay healthy!

Greetings from Germany! :-)

Thomas 😷
--
+++ +++ +++ +++ +++ +++ +++ +++ +++
Dat mit dem "dat", dat hat wat! :-)
+++ +++ +++ +++ +++ +++ +++ +++ +++