On Mon, 17 Jul 2006, Michal A. Valasek wrote:
>
>>> I'm talking about user variables, set using "uservarsset" in CTRL
>>> protocol. Things like "Full name" etc.
>> =20
>> XMail is basically trasparent on this data. What you get is what you
>> set.
>
> Well, but if I send non-ASCII data (in Unicod
> > I'm talking about user variables, set using "uservarsset" in CTRL
> > protocol. Things like "Full name" etc.
>
> XMail is basically trasparent on this data. What you get is what you
> set.
Well, but if I send non-ASCII data (in Unicode or ANSI) using CTRL
protocol, xmail terminates connectio
On Mon, 17 Jul 2006, Michal A. Valasek wrote:
>
>>> how it is with Non-ASCII characters (like letters with diacritic
>>> marks) in XMail configuration files?=3D20
>>>
>>> What charset should I use? Or I must encode it, using for example
>>> quoted printable or URL encode?
>> =20
>> Which variable
As the final display of variables is dependent of the renderer, you can
choose encoding and charset you like.
But I think using a quoted printable encoding with unicode charset could be
the best choice (both are universal and many languages and tools handle them
well)
Francis
>-Message d'or
> > how it is with Non-ASCII characters (like letters with diacritic
> > marks) in XMail configuration files?=20
> >
> > What charset should I use? Or I must encode it, using for example
> > quoted printable or URL encode?
>
> Which variables are you talking about? In general, XMail does not
care
On Sun, 16 Jul 2006, Michal A. Valasek wrote:
> how it is with Non-ASCII characters (like letters with diacritic marks)
> in XMail configuration files?=20
>
> What charset should I use? Or I must encode it, using for example quoted
> printable or URL encode?
Which variables are you talking about
