Corporate Information | Software | Support | Contact Us
Corporate Information
Software
Messenger Pro
Messenger Pro Downloads
Beta and Archived Downloads
Evaluate
Support
Messenger Pro FAQ
Messenger Pro Change Log
Messenger Pro (Windows/Linux/Mac) Mailing List Archive
Messenger Pro (RISC OS) Mailing List Archive
Bug Tracker
Contact Us

accent causes end of the URL -- TWO MPro bugs

From:Jim Nagel Date:20 Jul 2015 10:55
Replies: Re: accent causes end of the URL -- TWO MPro bugs ("David J. Ruck")
Re: accent causes end of the URL -- TWO MPro bugs (Richard Mellish)

The following message appeared in the Netsurf mailinglist today, 
saying that the recent version of the browser has cured a problem.  
But viewing the message in MPro 7.08 shows that Mpro needs a fix.

David Pitt posted:

     In June 2014 there was a thread on accents in URLs not 
     working in the RISC OS NetSurf. ... The issue is now fixed 
     in #2859.

     http://bugs.netsurf-browser.org/mantis/view.php?id=2137

     The URLs were:-
      http://dahlström.net
     or
      http://dahlström.net/svg/favicon/favicon.html

     (In the event of character mangling that's o-umlaut, 
     alt-246.)

     My thanks to the NetSurf developers.

My original intention in re-posting this here on the MPro list was to 
show that the URL as displayed by MPro (green and underlined and 
clickable) stops short:  the o-umlaut and everything following is not 
included.

But hey!  In copying that text from the MPro window and pasting it 
into this Email Edit window, a second ugly bug bites.

MPro correctly shows the problem character (246 = &F6) as o-umlaut.
But after copy-and-paste it has become cap-A-tilde followed by pilcrow 
(paragraph mark) -- ie, characters 195 and 182 (= &C3 and &B6).
The live URL now includes the 195 character and then stops.

HOWEVER, if while looking at David Pitt's message displayed in MPro I 
click "Reply to sender", an Email Edit window opens with the complete 
URL shown correctly AND the o-umlaut shown correctly.  !!

So SOMETHING in the route out of MPro to other apps is inconsistent.

In case it's relevant, the headers in David Pitt's message to the 
Netsurf list show that he was using MPro on MacOS; another header says
"Content-Type: text/plain; charset=utf-8".



In general, exporting from MPro as text fails to render top-bit 
characters correctly.  The result contains all sorts of gobbledygook.

For instance, a smart apostrophe (Windows?) comes out as a string of 
three characters:  a-circumflex (226 = &E2) + something looking like 
squareroot in StrongEd font but euro in Trinity and blank in System 
(128 = &80) + minus sign (153 = &99).  All of that string should be 
character 145 (= &91) in Ro; even simple character 39 (&27) would do.

If that smart apostrophe is sent from Hotmail, MPro displays it 
literally as "=91".


-- 
Jim Nagel                        www.archivemag.co.uk

______________________________________________________________________
This message was sent via the messenger-l mailing list
To unsubscribe, mail messenger-l+unsubscribe@...



© 2024 intellegit ltd. - info@intellegit.com