Re: rfc2396 url encoding

Re: rfc2396 url encoding

[Clint Adams]

On Sun, Nov 06, 2005 at 07:49:11PM +0000, Bart Schaefer wrote:
> urlencode() {
>     setopt localoptions extendedglob
>     input=( ${(s::)1} )
>     print ${(j::)input/(#b)([^A-Za-z0-9_.!~*\'\(\)-])/%$(([##16]#match))}
> }

This changed behavior in that ó (UTF-8) becomes %F3 instead of %C3%B3 .
Thoughts?

Re: rfc2396 url encoding

[Bart Schaefer]

On Apr 24, 11:47pm, Clint Adams wrote:
}
} >     input=( ${(s::)1} )
} >     print ${(j::)input/(#b)([^A-Za-z0-9_.!~*\'\(\)-])/%$(([##16]#match))}
} 
} This changed behavior in that ó (UTF-8) becomes %F3 instead of %C3%B3 .
} Thoughts?

(Is that actually wrong?  When I cut and paste from your email message,
there's only one byte at ó.)

I see the point, though, I think.  (s::) is now splitting between wide
characters rather than between raw bytes.

What happens if you simply unsetopt multibyte within the function?

  urlencode() {
    setopt localoptions extendedglob nomultibyte
    input=( ${(s::)1} )
    print ${(j::)input/(#b)([^A-Za-z0-9_.!~*\'\(\)-])/%$(([##16]#match))}
  }

If that doesn't work, we'll have to come up with some way to force $1
to be re-interpreted as a raw byte string rather than a wide character
string before splitting it up.

Re: rfc2396 url encoding

[Peter Stephenson]

Bart Schaefer wrote:
> What happens if you simply unsetopt multibyte within the function?
> 
>   urlencode() {
>     setopt localoptions extendedglob nomultibyte
>     input=( ${(s::)1} )
>     print ${(j::)input/(#b)([^A-Za-z0-9_.!~*\'\(\)-])/%$(([##16]#match))}
>   }

That's supposed to work and is the approved method of treating strings
as individual bytes.  I haven't tried it since the last thing I need at
the moment is being drawn into another bug fix.

-- 
Peter Stephenson <pws@csr.com>                  Software Engineer
CSR PLC, Churchill House, Cambridge Business Park, Cowley Road
Cambridge, CB4 0WZ, UK                          Tel: +44 (0)1223 692070


To access the latest news from CSR copy this link into a web browser:  http://www.csr.com/email_sig.php

To get further information regarding CSR, please visit our Investor Relations page at http://ir.csr.com/csr/about/overview

Re: rfc2396 url encoding

[Clint Adams]

> (Is that actually wrong?  When I cut and paste from your email message,
> there's only one byte at ó.)

Your mailer is likely converting my UTF-8 to Latin-1 or Latin-9.

> What happens if you simply unsetopt multibyte within the function?

That does the trick.