[sylpheed:37330] Re: Unicode not treated correctly - links do not work

[Anton Shepelev]

Joachim Selinger to Anton Shepelev:

> > Joachim Selinger:
> >
> > > Unicode Hex Character Code = =
> > > Symbol Name:  Equals Sign
> > > Html Entity:
> > > Hex Code:      =
> > > Decimal Code:  =
> > > Unicode Group: Basic Latin
> >
> > EQUALS SIGN is not specific to Unicode, but rather a
> > basic ASCII character.
>
> The problem was not the = sign, but its unicode encoding
> that wasn't decoded properly.

The code you provide above -- 0x3d or 61 -- identifies the
ASCII character, so I fail to see what Unicode endoding you
are referring to.

> Nevertheless, the way the URL is encoded does not work
> directly in the browser URL input field, so firefox and
> chrome expect that the unicode decoding of the = sign is
> done by the mail client before passing on the URL, either
> via click or via 'copy link'.

The browsers does not expect anything from the e-mail
client, because it does not interact with it. Sylpheed,
however, may be failing to render HTML correctly, but it is
already doing more than is required.  After all, HTML has no
place in e-mail (see my sig).

> Without knowing what the respective RFC says, I cannot say
> if Sylpheed is working as expected or not. It would be
> nice anyway for sylpheed to handle his the way the
> browsers expect it.

The RFC says that e-mail clients are not browsers.  I
suggest that you contact the institution that send you that
e-mail ask them to please use more compatible URLs.  When
sending an HTML e-mail, it is only polite in addition to
text/html also to provide a text/plain version usable with
normal client, e.g.:

        https://wordpress.stackexchange.com/q/210244

That plain-text version must have URLs ready for the
browser.

> But thx to your work around suggestion, I live with it and
> it is at most a priority B fix request from my side :-)

You are welcome.