Re: modified base64
| From: | (Marcus Börger) | Date: | Wed, 10 Apr 2002 21:38:54 +0000 |
| Subject: | Re: modified base64 | ||
| References: | 1 2 3 4 5 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-82524@lists.php.net to get a copy of this message | ||
new functionality
if you like it better i could call id url64_encode/decode
marcus
At 23:35 10.04.2002, Markus Fischer wrote:
Yet it's not clear at least to me if you're talking about _modifying_ an existing functionality OR adding a new function.On Wed, Apr 10, 2002 at 10:59:14PM +0200, Marcus Börger wrote : At 20:26 10.04.2002, Markus Fischer wrote:On Wed, Apr 10, 2002 at 07:42:57PM +0200, Marcus Börger wrote :It is not a replacement for base64 it is a new encoding function with some big similarities to base64. So i can do whatever i want with it. When i wanted it as a replacement for base64 in MIME i had to use the character ' instead of -. No more than the four characters -_'! fulllfill all named requirements. But ' is bad for program parameters and such and - is bad for MIME. marcus -- Please always Cc to me when replying to me on the lists. GnuPG Key: http://guru.josefine.at/~mfischer/C2272BD0.asc "Mind if I MFH ?" "What QA did you do on it?" "the usual?" "ah... none :)"But modifying the way base64_encode() works is not the right thing [tm].At 19:39 10.04.2002, Richard Heyes wrote:base64url_(en|de)code You could simply use this: urlencode(base64_encode($blaat));After (v)spprintf i have another modified function here:Sure but the the encoding result grows in length (dynamically) what i wanted to avoid :-)