Discussion:
Diacritical characters like è à ù recoding in subject in reply
(too old to reply)
Otomatic
2021-06-10 09:07:30 UTC
Permalink
Hi,

I use your explanation:
[Unicode] How to -- Full Unicode display in Agent's message body pane
Message-ID: <***@4ax.com>
By the way, thank you very much for this.

But I have a problem with recoding Subjects when I reply to a message
and the Subject contains diacritical characters.
For example:
Subject: Firefox 89 et barre en haut de la fenêtre
When responding, it becomes:
Subject: Re: Firefox 89 et barre en haut de la fenêtre

I'm putting it in the subject line of this post on purpose.
Ralph Fox
2021-06-10 10:02:24 UTC
Permalink
Post by Otomatic
Hi,
[Unicode] How to -- Full Unicode display in Agent's message body pane
By the way, thank you very much for this.
But I have a problem with recoding Subjects when I reply to a message
and the Subject contains diacritical characters.
Subject: Firefox 89 et barre en haut de la fenêtre
Subject: Re: Firefox 89 et barre en haut de la fenêtre
I'm putting it in the subject line of this post on purpose.
It works correctly when you use this method instead:
Announcement: Unicode Extension beta version 0.3.2020.700 for Forte Agent
Message-ID: <***@4ax.com>
provided that, in the font settings for Unicode, you also have a
check-mark in the setting "Use the variable-pitch body font for
Headers". Screen-shot: <Loading Image...> 😊


This method:
[Unicode] How to -- Full Unicode display in Agent's message body pane
Message-ID: <***@4ax.com>
only supports Unicode in the message body pane, not in the subject field. 🙁


I used the Unicode Extension for this reply, and the accented characters
in your subject line came through correctly when responding. 👍
--
Kind regards
Ralph
🦊
Otomatic
2021-06-10 13:05:15 UTC
Permalink
Post by Ralph Fox
Post by Otomatic
Hi,
[Unicode] How to -- Full Unicode display in Agent's message body pane
By the way, thank you very much for this.
But I have a problem with recoding Subjects when I reply to a message
and the Subject contains diacritical characters.
Subject: Firefox 89 et barre en haut de la fenêtre
Subject: Re: Firefox 89 et barre en haut de la fenêtre
I'm putting it in the subject line of this post on purpose.
Announcement: Unicode Extension beta version 0.3.2020.700 for Forte Agent
provided that, in the font settings for Unicode, you also have a
check-mark in the setting "Use the variable-pitch body font for
Headers". Screen-shot: <https://i.imgur.com/AC3dqNF.gif> 😊
[Unicode] How to -- Full Unicode display in Agent's message body pane
only supports Unicode in the message body pane, not in the subject field. 🙁
I used the Unicode Extension for this reply, and the accented characters
in your subject line came through correctly when responding. 👍
Thank you very much!
I have just used the same method to reply and all is well in the best of
worlds.
Valerio Vanni
2022-01-01 20:21:32 UTC
Permalink
Post by Ralph Fox
Post by Otomatic
Subject: Firefox 89 et barre en haut de la fenêtre
Subject: Re: Firefox 89 et barre en haut de la fenêtre
I'm putting it in the subject line of this post on purpose.
Announcement: Unicode Extension beta version 0.3.2020.700 for Forte Agent
provided that, in the font settings for Unicode, you also have a
check-mark in the setting "Use the variable-pitch body font for
Headers". Screen-shot: <https://i.imgur.com/AC3dqNF.gif> 😊
First of all, Ralph, thank you for Unicode Extension.

I've installed it and now with some help from Notepad++ I can manage
unicode characters in body field.

For Subject field, I see 2 different behaviors:

-With "Use the variable-pitch body..." unmarked, if I post accented
characters I find them messed up (like the "fenêtre" case reported
above)

-With "Use the variable-pitch body..." marked, I can post accented
characters and I can see them correctly. But if answer to that post,
accented characters are stripped down. Not messed, they just vanish,
"fenêtre" would become "fentre".
The only workaround is adding them again by hand when I answer.
--
Ci sono 10 tipi di persone al mondo: quelle che capiscono il sistema binario
e quelle che non lo capiscono.
Ralph Fox
2022-01-03 08:53:04 UTC
Permalink
Post by Valerio Vanni
First of all, Ralph, thank you for Unicode Extension.
I've installed it and now with some help from Notepad++ I can manage
unicode characters in body field.
-With "Use the variable-pitch body..." unmarked, if I post accented
characters I find them messed up (like the "fenêtre" case reported
above)
-With "Use the variable-pitch body..." marked, I can post accented
characters and I can see them correctly. But if answer to that post,
accented characters are stripped down. Not messed, they just vanish,
"fenêtre" would become "fentre".
The only workaround is adding them again by hand when I answer.
If you want to reply in full Unicode to a message, then:

i) Make sure Agent has the message body for the message which you
are replying to.
ii) Change the language of the original message to "Unicode UTF-8"
_before_ replying.
iii) Then click reply.
The language of the composition window will be automatically
set to "Unicode UTF-8", the same as the original message
(assuming Agent has the message body for the original message).
iv) Keep the language of the composition window as "Full Unicode" when
sending.

That is what I did for this reply, and the accented characters è à ù in
this thread's subject were not messed up or stripped out in my reply.


If "fenêtre" is changing to "fentre" in the subject, then one of
three things might be happening.

(a) You click "Reply" and then change the language to Unicode
in the compose window;

(b) Or, you are replying to a message without a body
(with some additional conditions to make this happen);

(c) Or, you are using Agent 1.92 or earlier
(with some additional conditions to make this happen).


It is best not to change the message language on the compose window.
Doing so is likely to mess up Unicode characters already in the message.
My case (a) above is if this were what was happening to "fenêtre" in the
subject.


When you change the language of the original message to "Unicode UTF-8"
and then click Reply, having the subject come through correctly can also
depend on both of the following [^1]:
1) You are using Agent 1.93 or later
2) And, Agent has the body for the message you are replying to.

When you are using Agent 1.93 or later and Agent has the message body,
Agent will get the reply subject from the 'full' headers of the
original message (which you can see in the message body pane when you
turn on "View >> Show All Header Fields"). If the language of the
original message has been set to Unicode, Agent knows how to populate
the reply subject with the correct Unicode.

When Agent does not have the message body, or when you are using
Agent 1.92 or earlier, Agent will get the reply subject from the
'overview' headers (calculated when you get headers and which appear
in the message list pane). The 'overview' headers do not always work
too well with full Unicode. My cases (b) and (c) above are this.


* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

One other thing I noticed. If "fenêtre" is changing to "fentre"
in the subject, then you are probably using Windows XP or earlier.
In Windows 7 and later under the same conditions, "fenêtre" would
change to "fen�tre" or to "fen?tre".

* Readers: to see the difference between "fen�tre" and "fen?tre",
view this message in Full Unicode. Or, use your Unicode web
browser to view my reply here, here or here:
[GG] <https://groups.google.com/g/alt.usenet.offline-reader.forte-agent/c/o2KSO5L4-LI/m/RRmWm2kUAwAJ>
[NB] <https://www.novabbs.com/computers/article-flat.php?id=3044&group=alt.usenet.offline-reader.forte-agent#3044>
[NK] <https://alt.usenet.offline-reader.forte-agent.narkive.com/fiiAwYUl/diacritical-characters-like-e-a-u-recoding-in-subject-in-reply#post4>


____
FOOTNOTES

[^1] There was a change in Agent 1.93 to fetch the reply subject from the
original message full headers (if possible), rather than from the
'overview' headers.

Help >> Index >> Release Notes >> Release Notes for Agent 1.x (Archive) >> Version 1.93

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ QUOTE ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
* When composing a reply, Agent now uses the actual subject from
the original message, not the subject retrieved in the message
header. This ensures that the correct subject is used in the
reply if there is some discrepancy between the two.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ QUOTE ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--
Kind regards
Ralph
🦊
Valerio Vanni
2022-01-07 01:36:59 UTC
Permalink
Post by Ralph Fox
Post by Valerio Vanni
-With "Use the variable-pitch body..." unmarked, if I post accented
characters I find them messed up (like the "fenêtre" case reported
above)
-With "Use the variable-pitch body..." marked, I can post accented
characters and I can see them correctly. But if answer to that post,
accented characters are stripped down. Not messed, they just vanish,
"fenêtre" would become "fentre".
The only workaround is adding them again by hand when I answer.
i) Make sure Agent has the message body for the message which you
are replying to.
ii) Change the language of the original message to "Unicode UTF-8"
_before_ replying.
I adopted unicode only for some newsgroup.
For most of them, I don't need Unicode so I left original language
settings based on Codepage 1252 and Charset "Western with Euro".
The same for "Sent folder", I left it with original language.

For newsgroups where I need it, I made parallel archive folders with
old "kept" messages (set on original language, just to avoid messing
something).

But then on those newsgroup properties news language "Unicode" is
default, if I select "edit->language" I find already "Unicode".
Post by Ralph Fox
One other thing I noticed. If "fenêtre" is changing to "fentre"
in the subject, then you are probably using Windows XP or earlier.
In Windows 7 and later under the same conditions, "fenêtre" would
change to "fen�tre" or to "fen?tre".
Yes, I'm using Windows XP. Agent version is 8.
--
Ci sono 10 tipi di persone al mondo: quelle che capiscono il sistema binario
e quelle che non lo capiscono.
Valerio Vanni
2022-01-07 01:41:32 UTC
Permalink
On Fri, 07 Jan 2022 02:36:59 +0100, Valerio Vanni
Post by Valerio Vanni
Post by Ralph Fox
Post by Valerio Vanni
-With "Use the variable-pitch body..." unmarked, if I post accented
characters I find them messed up (like the "fenêtre" case reported
above)
-With "Use the variable-pitch body..." marked, I can post accented
characters and I can see them correctly. But if answer to that post,
accented characters are stripped down. Not messed, they just vanish,
"fenêtre" would become "fentre".
The only workaround is adding them again by hand when I answer.
One other thing I noticed. If "fenêtre" is changing to "fentre"
in the subject, then you are probably using Windows XP or earlier.
In Windows 7 and later under the same conditions, "fenêtre" would
change to "fen�tre" or to "fen?tre".
Yes, I'm using Windows XP. Agent version is 8.
Look at this answer and at the previous: when I answer to one of your
messages, è à ù appear (no, I didn't add them by hand); when I
answer to one of mine, they disappear.
--
Ci sono 10 tipi di persone al mondo: quelle che capiscono il sistema binario
e quelle che non lo capiscono.
Ralph Fox
2022-01-23 01:26:16 UTC
Permalink
Post by Valerio Vanni
On Fri, 07 Jan 2022 02:36:59 +0100, Valerio Vanni
Post by Valerio Vanni
Post by Ralph Fox
Post by Valerio Vanni
-With "Use the variable-pitch body..." unmarked, if I post accented
characters I find them messed up (like the "fenêtre" case reported
above)
-With "Use the variable-pitch body..." marked, I can post accented
characters and I can see them correctly. But if answer to that post,
accented characters are stripped down. Not messed, they just vanish,
"fenêtre" would become "fentre".
The only workaround is adding them again by hand when I answer.
One other thing I noticed. If "fenêtre" is changing to "fentre"
in the subject, then you are probably using Windows XP or earlier.
In Windows 7 and later under the same conditions, "fenêtre" would
change to "fen�tre" or to "fen?tre".
Yes, I'm using Windows XP. Agent version is 8.
Look at this answer and at the previous: when I answer to one of your
messages, è à ù appear (no, I didn't add them by hand); when I
answer to one of mine, they disappear.
Q.1 Do the è à ù disappear as soon as you click reply,
or do the è à ù disappear when you change the language
in the compose window?


Q.2 Is the problem fixed by updating the setting below?

On the the fonts panel for Unicode UTF-8, there should be a
check-mark in the setting "Use the variable-pitch body font
for Headers".

Agent requires this when the font does not use your default
Windows ANSI character set, and you want the different
character set to display correctly in the compose subject
field.

Your default Windows ANSI character set is code page 1252
while the Unicode UTF-8 character set is code page 65001.
--
Kind regards
Ralph
Valerio Vanni
2022-01-23 14:41:47 UTC
Permalink
Post by Ralph Fox
Post by Valerio Vanni
Post by Valerio Vanni
Post by Ralph Fox
Post by Valerio Vanni
-With "Use the variable-pitch body..." unmarked, if I post accented
characters I find them messed up (like the "fenêtre" case reported
above)
-With "Use the variable-pitch body..." marked, I can post accented
characters and I can see them correctly. But if answer to that post,
accented characters are stripped down. Not messed, they just vanish,
"fenêtre" would become "fentre".
The only workaround is adding them again by hand when I answer.
One other thing I noticed. If "fenêtre" is changing to "fentre"
in the subject, then you are probably using Windows XP or earlier.
In Windows 7 and later under the same conditions, "fenêtre" would
change to "fen�tre" or to "fen?tre".
Yes, I'm using Windows XP. Agent version is 8.
Look at this answer and at the previous: when I answer to one of your
messages, è à ù appear (no, I didn't add them by hand); when I
answer to one of mine, they disappear.
Q.1 Do the è à ù disappear as soon as you click reply,
or do the è à ù disappear when you change the language
in the compose window?
As soon as I click reply.
I don't change language, because I keep some newsgroup (this too) with
unicode language setting by default.
Post by Ralph Fox
Q.2 Is the problem fixed by updating the setting below?
On the the fonts panel for Unicode UTF-8, there should be a
check-mark in the setting "Use the variable-pitch body font
for Headers".
Agent requires this when the font does not use your default
Windows ANSI character set, and you want the different
character set to display correctly in the compose subject
field.
The check mark is selected.

If I don't select it, the behavior is different:
-I can answer to my posts and accented letters do not disappear
but
-If I answer to your (or others' ones here in this thread) posts, I
see accented letters scrambled
-If I compose a new message, other (tested from google group) find
accented letters scrambled (don't remember if I see them scrambled too
when download the post).
Post by Ralph Fox
Your default Windows ANSI character set is code page 1252
while the Unicode UTF-8 character set is code page 65001.
Inside this language I have:
Code Page: Unicode FULL UTF-8
Send usenet and mail as: Unicode FULL UTF-8
Default charset: ISO-8859-15

But shouldn't the last option act only when a post has no declaration
inside?
Both mine and yours are defined "UTF-8".
--
Ci sono 10 tipi di persone al mondo: quelle che capiscono il sistema binario
e quelle che non lo capiscono.
Ralph Fox
2022-01-29 08:14:29 UTC
Permalink
Post by Valerio Vanni
Post by Ralph Fox
Post by Valerio Vanni
Post by Valerio Vanni
Post by Ralph Fox
Post by Valerio Vanni
-With "Use the variable-pitch body..." marked, I can post accented
characters and I can see them correctly. But if answer to that post,
accented characters are stripped down. Not messed, they just vanish,
"fenêtre" would become "fentre".
The only workaround is adding them again by hand when I answer.
One other thing I noticed. If "fenêtre" is changing to "fentre"
in the subject, then you are probably using Windows XP or earlier.
In Windows 7 and later under the same conditions, "fenêtre" would
change to "fen�tre" or to "fen?tre".
Yes, I'm using Windows XP. Agent version is 8.
Look at this answer and at the previous: when I answer to one of your
messages, è à ù appear (no, I didn't add them by hand); when I
answer to one of mine, they disappear.
Q.1 Do the è à ù disappear as soon as you click reply,
or do the è à ù disappear when you change the language
in the compose window?
As soon as I click reply.
I don't change language, because I keep some newsgroup (this too) with
unicode language setting by default.
Post by Ralph Fox
Q.2 Is the problem fixed by updating the setting below?
On the the fonts panel for Unicode UTF-8, there should be a
check-mark in the setting "Use the variable-pitch body font
for Headers".
Agent requires this when the font does not use your default
Windows ANSI character set, and you want the different
character set to display correctly in the compose subject
field.
The check mark is selected.
-I can answer to my posts and accented letters do not disappear
but
-If I answer to your (or others' ones here in this thread) posts, I
see accented letters scrambled
-If I compose a new message, other (tested from google group) find
accented letters scrambled (don't remember if I see them scrambled too
when download the post).
Post by Ralph Fox
Your default Windows ANSI character set is code page 1252
while the Unicode UTF-8 character set is code page 65001.
Code Page: Unicode FULL UTF-8
Send usenet and mail as: Unicode FULL UTF-8
Default charset: ISO-8859-15
But shouldn't the last option act only when a post has no declaration
inside?
Both mine and yours are defined "UTF-8".
There are two separate causes going on here:

1. When replying to these messages:
<***@4ax.com>
<***@4ax.com>
<***@4ax.com>
<***@4ax.com>
<***@4ax.com>

These messages have RFC2047 MIME-encoded headers.
* The first 4 are encoded with charset UTF-8
* The last 1 is encoded with charset ISO-8859-1

For these messages, there is a practical difference between
doing one or other of these two things:

1.1 Not setting the message language to Unicode because the
newsgroup has Unicode language setting by default.
1.2 Setting the message language to Unicode (whether or not
the newsgroup has Unicode language setting).

In case 1.1, accented characters are corrupted in the reply.
In case 1.2, accented characters are not corrupted in the reply.

I would suggest using 1.2.

If you want to use 1.1 and reply to those using MIME headers
with charset UTF-8...
* You will need to edit Agent's cp1252.cod file and
remove utf-8 from the "Inbound-Charsets:" line.
* This may prevent you from replying to any utf-8 messages
except in Language Unicode UTF-8.
* If your Windows' System ANSI code page is not Western code
page 1252, then you may need to edit other Agent cp*.cod files.

If you want to use 1.1 and reply to those using MIME headers
with charset ISO-8859-1...
* At this point in time it is probably not a good idea to remove
ISO-8859-1 from the "Inbound-Charsets:" line in Agent's cp1252.cod.
* I would *strongly* recommend using 1.2 instead.


2. When replying to these messages
<***@4ax.com>
<***@4ax.com>

These messages have 8-bit headers in charset ISO-8859-1.

For these messages, there is not much one can do to make it
work *automatically*.

The problem here is that Agent will not transcode 8-bit headers at all.
Agent does not transcode the ISO-8859-1 8-bit subject to UTF-8.

With 'Western' languages using ANSI code page 1252, this has
previously not been much of an issue. The Internet charsets
ISO-8859-1 is close to Windows ANSI code page 1252. Failure to
transcode rarely caused much of a problem.

With Russian, this has been an issue for a long time. The Internet
charsets ISO-8859-5 and KOI8-R are very different to Windows ANSI
code page 1251.
Post by Valerio Vanni
Code Page: Unicode FULL UTF-8
Send usenet and mail as: Unicode FULL UTF-8
Default charset: ISO-8859-15
But shouldn't the last option act only when a post has no declaration
inside?
Both mine and yours are defined "UTF-8".
In Agent, the 'Default charset' does not act on headers...

1. If the subject header is RFC2047 MIME-encoded, then the MIME
encoded 'words' in the subject contain their own charset
declaration. It does not matter whether the post has a
Content-Type header with a charset declaration or not.

2. If the subject has raw 8-bit characters, Agent will not transcode it.
The post's charset declaration will not be used. If the post
has no charset declaration, the 'Default charset' will not be used.


In Agent, the 'Default charset' acts on bodies and only when
the post has no charset declaration.
--
Kind regards
Ralph

𝐿𝑖𝑣𝑒 𝑒𝑎𝑐ℎ 𝑑𝑎𝑦 𝑎𝑠 𝑖𝑓 𝑖𝑡 𝑤𝑒𝑟𝑒 𝑦𝑜𝑢𝑟 𝑙𝑎𝑠𝑡 - 𝑏𝑢𝑡 𝑝𝑎𝑦 𝑡ℎ𝑒 𝑏𝑖𝑙𝑙𝑠 𝑗𝑢𝑠𝑡 𝑖𝑛 𝑐𝑎𝑠𝑒 𝑖𝑡 𝑖𝑠𝑛'𝑡.
Valerio Vanni
2022-01-30 21:19:03 UTC
Permalink
Post by Ralph Fox
Post by Valerio Vanni
The check mark is selected.
-I can answer to my posts and accented letters do not disappear
but
-If I answer to your (or others' ones here in this thread) posts, I
see accented letters scrambled
-If I compose a new message, other (tested from google group) find
accented letters scrambled (don't remember if I see them scrambled too
when download the post).
Post by Ralph Fox
Your default Windows ANSI character set is code page 1252
while the Unicode UTF-8 character set is code page 65001.
Code Page: Unicode FULL UTF-8
Send usenet and mail as: Unicode FULL UTF-8
Default charset: ISO-8859-15
But shouldn't the last option act only when a post has no declaration
inside?
Both mine and yours are defined "UTF-8".
These messages have RFC2047 MIME-encoded headers.
* The first 4 are encoded with charset UTF-8
* The last 1 is encoded with charset ISO-8859-1
Now, viewing messages as raw I see.

But I don't understand why my agent encodes headers when I answer to
your message but doesn't encode when I answer to mine.
Post by Ralph Fox
For these messages, there is a practical difference between
1.1 Not setting the message language to Unicode because the
newsgroup has Unicode language setting by default.
1.2 Setting the message language to Unicode (whether or not
the newsgroup has Unicode language setting).
In case 1.1, accented characters are corrupted in the reply.
In case 1.2, accented characters are not corrupted in the reply.
I would suggest using 1.2.
Let's go with 1.2 :-)

But, how can I set a language already set?
Should I change it to another language and change it again?

Should I act on original message or on mine in composition window?
Post by Ralph Fox
2. When replying to these messages
These messages have 8-bit headers in charset ISO-8859-1.
For these messages, there is not much one can do to make it
work *automatically*.
The problem here is that Agent will not transcode 8-bit headers at all.
Agent does not transcode the ISO-8859-1 8-bit subject to UTF-8.
With 'Western' languages using ANSI code page 1252, this has
previously not been much of an issue. The Internet charsets
ISO-8859-1 is close to Windows ANSI code page 1252. Failure to
transcode rarely caused much of a problem.
In Agent, the 'Default charset' does not act on headers...
Understood, thank you.
--
Ci sono 10 tipi di persone al mondo: quelle che capiscono il sistema binario
e quelle che non lo capiscono.
Ralph Fox
2022-01-31 09:41:07 UTC
Permalink
Post by Valerio Vanni
But I don't understand why my agent encodes headers when I answer to
your message but doesn't encode when I answer to mine.
My messages which had è à ù in the subject, were using 8-bit UTF-8 for
the subject header.
* So even though Agent dos not transcode 8-bit headers, the subject
line was already in the required UTF-8 codepage to populate the
subject of your reply.


Your messages which had è à ù in the subject, were using RFC2047
MIME-encoded words for the subject header. The MIME-encoded words
were encoded with UTF-8.
* To populate the subject in a reply, Agent will transcode the
MIME-encoded words into *some* codepage.
* But if the original message's language is "[Default: Unicode UTF-8]"
and not "Unicode UTF-8", then Agent may transcode the MIME-encoded
words into some other codepage not the codepage of your UTF-8 reply.
And diacritical characters will be messed up.

I don't know for certain how Agent picks the codepage to transcode
MIME-encoded words into, but it may be something like this:

If the charset in the MIME-encoded words is UTF-8, then
1. If your OS system ANSI codepage has UTF-8 in its
"Inbound-Charsets:" line, then pick your OS system ANSI
codepage (in Western Europe, cp1252).
2. Otherwise find the first [Language<n>] section in your
AGENT.INI file whose codepage .COD file has UTF-8 in its
"Inbound-Charsets:" line, and pick that language's
codepage.
Post by Valerio Vanni
But, how can I set a language already set?
Should I change it to another language and change it again?
Should I act on original message or on mine in composition window?
Change the language of the original message
from "[Default: Unicode UTF-8]"
to "Unicode UTF-8"
before you click Reply.

I have not yet seen any problems replying to a MIME-encoded subject when
the language of the original message is already set to "Unicode UTF-8"
and not to "[Default: Unicode UTF-8]".
--
Kind regards
Ralph

Ὁ βίος βραχύς, ἡ δὲ τέχνη μακρή
Vīta brevis, ars longa
The lyf so short, the craft so long to lerne
Valerio Vanni
2022-02-03 22:43:31 UTC
Permalink
Post by Ralph Fox
Your messages which had è à ù in the subject, were using RFC2047
MIME-encoded words for the subject header. The MIME-encoded words
were encoded with UTF-8.
* To populate the subject in a reply, Agent will transcode the
MIME-encoded words into *some* codepage.
* But if the original message's language is "[Default: Unicode UTF-8]"
and not "Unicode UTF-8", then Agent may transcode the MIME-encoded
words into some other codepage not the codepage of your UTF-8 reply.
And diacritical characters will be messed up.
I don't know for certain how Agent picks the codepage to transcode
If the charset in the MIME-encoded words is UTF-8, then
1. If your OS system ANSI codepage has UTF-8 in its
"Inbound-Charsets:" line, then pick your OS system ANSI
codepage (in Western Europe, cp1252).
2. Otherwise find the first [Language<n>] section in your
AGENT.INI file whose codepage .COD file has UTF-8 in its
"Inbound-Charsets:" line, and pick that language's
codepage.
Post by Valerio Vanni
But, how can I set a language already set?
Should I change it to another language and change it again?
Should I act on original message or on mine in composition window?
Change the language of the original message
from "[Default: Unicode UTF-8]"
to "Unicode UTF-8"
before you click Reply.
It seemed that it should be the same to have "Default" and explicit (I
set "default" to avoid changing every time".

But I tried and it works.
--
Ci sono 10 tipi di persone al mondo: quelle che capiscono il sistema binario
e quelle che non lo capiscono.
Valerio Vanni
2022-02-03 22:17:11 UTC
Permalink
On Fri, 07 Jan 2022 02:36:59 +0100, Valerio Vanni
Post by Valerio Vanni
Post by Ralph Fox
One other thing I noticed. If "fenêtre" is changing to "fentre"
in the subject, then you are probably using Windows XP or earlier.
In Windows 7 and later under the same conditions, "fenêtre" would
change to "fen�tre" or to "fen?tre".
Yes, I'm using Windows XP. Agent version is 8.
Reply after having changed langage from [Default-Unicode] to
[Unicode].
In this moment (composition) letters do appear.
--
Ci sono 10 tipi di persone al mondo: quelle che capiscono il sistema binario
e quelle che non lo capiscono.
Loading...