Re: UFT-8 or???
Bob O'Dyne
<kilowa...@use-reply-to.invalid> wrote:
> Reinstall Agent and install the support for additional character sets.
Can't support for additional characters sets be installed without
having to reinstall Agent?
--
Ann's Little Brother Bob
Carroll Robbins
09:18:12 +0100 in <v4nuh5l3reshc3493...@4ax.com>
>On Tue, 08 Dec 2009 19:41:39 -0800, in
>alt.usenet.offline-reader.forte-agent Keith
><kilowa...@use-reply-to.invalid> wrote:
>
>>On 12/8/09 2:31 PM, Otto J锟絩gensen wrote:
>>> Normal is the option to Agent as
>>> | MIME-Version: 1.0
>>> | Content-Type: text/plain;
>>> | charset="iso-8859-1"
>>> | Content-Transfer-Encoding: quoted-printable
>>> but sometimes I have received message in UFT-8 and the message is
>>> mostly garbarge.
>>> Is the some additonal setting in Agent to handle bot set?
>>
>> Reinstall Agent and install the support for additional character sets.
>
>why?
>When I updated to 5.0 thee was no question about any additional add-in
>to have this, so why should I have a full update and new installation
>and now build from 1171 to 1186?
Reinstalling Agent won't help. Agent 5 and 6 have no difference in this
area. Agent is not a Unicode application and can only display characters
from one code page for a message.
What are the MIME headers for the utf-8 message?
What are your settings at "Tools -> Options -> Languages"?
What are your settings at "Tools -> Options -> Fonts" for the relevant
languages?
Are all the characters in the message in one code page and which code page
is it?
--
Carroll B. Robbins, Jr.
Ralph Fox
Otto J�rgensen <otjoerge%�f��%@online.norway> wrote:
> X-Newsreader: Forte Agent 5.00/32.1171
> Normal is the option to Agent as
> | MIME-Version: 1.0
> | Content-Type: text/plain;
> | charset="iso-8859-1"
> | Content-Transfer-Encoding: quoted-printable
> but sometimes I have received message in UFT-8 and the message is
> mostly garbarge.
> Is the some additonal setting in Agent to handle bot set?
If you cannot read a UTF-8 message, this is most likely due to one of the following
two causes
A. You have "View � Display as Raw Message" turned on; or
B. The message is written in a foreign script; and one of
(i) Either, you have not yet configured Agent to have a "language" with that script;
(ii) Or, Agent is not automatically selecting the "language" with that script
which you have configured.
Do the following
1. Make sure "View � Display as Raw Message" is turned off.
2. Configure Agent with a "language" to display the foreign script.
See the help file at "Help � Index � Fonts � Configuring International Fonts"
and read the Google archives of this NG for more details.
3. If Agent still does not display the message correctly after you have done #1 and #2,
you will need to manually set the "language" for the message.
Select the message and use "Edit � Language" to select the language which
uses that foreign script.
--
Regards
Ralph
Carroll Robbins
>On Wed, 09 Dec 2009 03:50:03 -0500, in
>alt.usenet.offline-reader.forte-agent Carroll Robbins
><carroll...@charter.net.invalid> wrote:
>
>>Otto J锟絩gensen <otjoerge%锟絝锟斤拷%@online.norway> wrote on Wed, 09 Dec 2009
>>09:18:12 +0100 in <v4nuh5l3reshc3493...@4ax.com>
>>
>>>On Tue, 08 Dec 2009 19:41:39 -0800, in
>>>alt.usenet.offline-reader.forte-agent Keith
>>><kilowa...@use-reply-to.invalid> wrote:
>>>
>>>>On 12/8/09 2:31 PM, Otto J锟絩gensen wrote:
>>>>> Normal is the option to Agent as
>>>>> | MIME-Version: 1.0
>>>>> | Content-Type: text/plain;
>>>>> | charset="iso-8859-1"
>>>>> | Content-Transfer-Encoding: quoted-printable
>>>>> but sometimes I have received message in UFT-8 and the message is
>>>>> mostly garbarge.
>>>>> Is the some additonal setting in Agent to handle bot set?
>>>>
>>>> Reinstall Agent and install the support for additional character sets.
>>>
>>>why?
>>>When I updated to 5.0 thee was no question about any additional add-in
>>>to have this, so why should I have a full update and new installation
>>>and now build from 1171 to 1186?
>>
>>Reinstalling Agent won't help. Agent 5 and 6 have no difference in this
>>area. Agent is not a Unicode application and can only display characters
>>from one code page for a message.
>>
>>What are the MIME headers for the utf-8 message?
>MIME-Version: 1.0
>Content-Type: multipart/mixed;
> boundary="----=_NextPart_000_0009_01CA7862.BDA7A850"
>X-Priority: 3
>X-MSMail-Priority: Normal
>Importance: Normal
>X-Mailer: Microsoft Windows Live Mail 14.0.8089.726
A charset is not specified so the default will be used.
>>What are your settings at "Tools -> Options -> Languages"?
>
>English (International)
What is the default charset?
>>What are your settings at "Tools -> Options -> Fonts" for the relevant
>>languages?
>
>MS Sans Serif 10 pt (Western)
>Courier new
>
>>Are all the characters in the message in one code page and which code page
>>is it?
>
>some of them are found here
>http://www.typeart.com/special_characters.asp#ACCENTED_VOWELS
Ralph Fox
Carroll Robbins <carroll...@charter.net.invalid> wrote:
> Otto J�rgensen <otjoerge%�f��%@online.norway> wrote on Wed, 09 Dec 2009
> 12:45:07 +0100 in <sn2vh5lnp2vd4npbe...@4ax.com>
>
> >On Wed, 09 Dec 2009 03:50:03 -0500, in
> >alt.usenet.offline-reader.forte-agent Carroll Robbins
> ><carroll...@charter.net.invalid> wrote:
> >
> >>What are the MIME headers for the utf-8 message?
> >MIME-Version: 1.0
> >Content-Type: multipart/mixed;
> > boundary="----=_NextPart_000_0009_01CA7862.BDA7A850"
> >X-Priority: 3
> >X-MSMail-Priority: Normal
> >Importance: Normal
> >X-Mailer: Microsoft Windows Live Mail 14.0.8089.726
>
> A charset is not specified so the default will be used.
The message is multipart/mixed, so the charset will be specified in the
first text/* MIME section headers and not in the main headers.
Otto posted only the main headers.
Otto did not post the MIME section headers.
--
Regards
Ralph
Carroll Robbins
23:32:43 +0100 in <knt2i591g9vbu1ejh...@4ax.com>
>On Thu, 10 Dec 2009 15:18:01 -0500, in
>alt.usenet.offline-reader.forte-agent Carroll Robbins
><carroll...@charter.net.invalid> wrote:
>>What is the default charset?
>
>speaking about codepage?
I assume the code page is 1252 Western Europe. What is the settings at
"Tools -> Options -> Languages -> English International -> Default
Charset"?
Per Ralph's message, what are the MIME section headers?
Ralph Fox
Otto J�rgensen <otjoerge%�f��%@online.norway> wrote:
> >Per Ralph's message, what are the MIME section headers?
>
> MIME-Version: 1.0
> Content-Type: multipart/alternative;
> boundary="----=_NextPart_000_0008_01CA785A.71A15A30"
That appears to be taken from the main headers, not the section headers in one of the MIME sections.
Scroll down the raw message, look for a line something like this
------=_NextPart_000_0008_01CA785A.71A15A3
followed by several header lines including another "Content-Type:" header
which has text/ and not multipart/ in it.
--
Regards
Ralph
Carroll Robbins
09:07:46 +0100 in <jiu3i5p4beqfq7r6a...@4ax.com>
>> What is the settings at
>>"Tools -> Options -> Languages -> English International -> Default
>>Charset"?
>
>correct
This is not an answer. What is the setting? Eg., ASCII, UTF-8, UTF-7, or
Western Europe.
You also need to answer Ralph's question.
Ralph Fox
> Tenk milj=C3=B8 f=C3=B8r du skriver meldinga p=C3=A5 papir
> ------=_NextPart_000_0008_01CA785A.71A15A30
> Content-Type: text/html;
> charset="UTF-8"
> Content-Transfer-Encoding: quoted-printable
>
---snip---
> Ville det v=C3=A6re mulig =C3=A5 legge inn =
> Unicode (UFT-8) i=20
> slektsprogrammet slik at det ogs=C3=A5 h=C3=A5ndterer samiske =
> spesialbokstaver, som =C3=A1, =C3=81,=20
> =C4=8D, =C4=8C, =C4=91, =C4=90, =C5=8B,=C5=8A, =C5=A1, =C5=A0, =C5=A7,
> =
> =C5=A6, =C5=BE, =C5=BD. N=C3=A5r jeg bruker disse spesialbokstaver =
> takler=20
> ikke programmet bokstavene, og det kommer opp helt andre =
> tegn.
---snip---
Agent does not come preconfigured with Saami character support,
but this can be added to Agent.
General instructions for configuring Agent are at
Help � Index � Languages � Configuring International Fonts
Exactly what is required in each step can depend on the language.
For steps 1 and 2, here are a few more details for Saami...
1. Fonts
Windows does not have a font "Script" setting for Saami, which means
you will need to install NLS fonts for Saami.
At the moment I don't know where one can find free NLS fonts for Saami.
2. character set mapping (.cod) file
Although Fort� do not bundle a character set mapping (.cod) file for Saami
with Agent, one can easily be made.
--
Regards
Ralph
Ralph Fox
Otto J�rgensen <otjoerge%�f��%@online.norway> wrote:
> On Tue, 15 Dec 2009 11:16:31 +1300, in
> alt.usenet.offline-reader.forte-agent Ralph Fox <-rf-nz-@-.invalid>
> wrote:
>
> >
> >Agent does not come preconfigured with Saami character support,
> >but this can be added to Agent.
> >
> >General instructions for configuring Agent are at
> >
> >Help � Index � Languages � Configuring International Fonts
> >
> >Exactly what is required in each step can depend on the language.
> >For steps 1 and 2, here are a few more details for Saami...
> >
> >1. Fonts
> >
> > Windows does not have a font "Script" setting for Saami, which means
> > you will need to install NLS fonts for Saami.
> >
> > At the moment I don't know where one can find free NLS fonts for Saami.
> >
> >
> >2. character set mapping (.cod) file
> >
> > Although Fort� do not bundle a character set mapping (.cod) file for Saami
> > with Agent, one can easily be made.
> >
>
> Will this effect on the ordinary selected language/codepage or be
> additional.
It will be additional. Your existing language/codepage will not be affected.
> There are many nonw-English characters used in Europe so here is a
> need for multiuse
The Agent settings for English will handle all of the characters
in this diagram, but no more:
http://msdn.microsoft.com/en-au/goglobal/cc305145.aspx
To handle other characters, you will need to configure additional
languages/codepages in Agent. For example, to handle Central European
languages you will configure another language/codepage which will display
all of these characters:
http://msdn.microsoft.com/en-au/goglobal/cc305143.aspx
> The basic is not to write whole message in Sami or Russian or Creeck,
> but to have a readiable view in Agent for those characters that are
> non-English/Norwegian/Latin
Agent cannot display characters from more than one code page at the same time.
� You may find a single codepage which can display the entire message.
� Otherwise, you may need to flip back and forth between several
languages/codepages to read a message written with characters from
more than one codepage.
--
Regards
Ralph
Ralph Fox
> Tenk milj=C3=B8 f=C3=B8r du skriver meldinga p=C3=A5 papir
> ------=_NextPart_000_0008_01CA785A.71A15A30
> Content-Type: text/html;
> charset="UTF-8"
> Content-Transfer-Encoding: quoted-printable
>
---snip---
> Ville det v=C3=A6re mulig =C3=A5 legge inn =
> Unicode (UFT-8) i=20
> slektsprogrammet slik at det ogs=C3=A5 h=C3=A5ndterer samiske =
> spesialbokstaver, som =C3=A1, =C3=81,=20
> =C4=8D, =C4=8C, =C4=91, =C4=90, =C5=8B,=C5=8A, =C5=A1, =C5=A0, =C5=A7,
> =
> =C5=A6, =C5=BE, =C5=BD. N=C3=A5r jeg bruker disse spesialbokstaver =
> takler=20
> ikke programmet bokstavene, og det kommer opp helt andre =
> tegn.
---snip---
I set up a new language/codepage for S�mi in Agent, and used it to
view your sample message.
This image shows the results in Agent's plain text viewer: http://i50.tinypic.com/1zy7y1e.png
All of the S�mi special letters are showing correctly,
and the Danish/Norwegian letters in the message are also showing correctly.
--
Regards
Ralph