2010/10/14 Daniel Veillard :
> On Wed, Oct 13, 2010 at 10:47:57PM +0200, Matthias Bolte wrote:
>> 2010/10/13 Daniel Veillard :
>> > On Wed, Oct 13, 2010 at 11:06:44AM +0200, Matthias Bolte wrote:
>> >> VMware uses a mix of percent-, pipe- and base64-encoding in
>> >> different combinations in diffe
On Wed, Oct 13, 2010 at 10:47:57PM +0200, Matthias Bolte wrote:
> 2010/10/13 Daniel Veillard :
> > On Wed, Oct 13, 2010 at 11:06:44AM +0200, Matthias Bolte wrote:
> >> VMware uses a mix of percent-, pipe- and base64-encoding in
> >> different combinations in different places.
> >>
> >> Add a testca
2010/10/13 Daniel Veillard :
> On Wed, Oct 13, 2010 at 11:06:44AM +0200, Matthias Bolte wrote:
>> VMware uses a mix of percent-, pipe- and base64-encoding in
>> different combinations in different places.
>>
>> Add a testcase for this.
>> ---
>> src/esx/README | 25
On 10/13/2010 07:19 AM, Daniel Veillard wrote:
+{ "A쿀Z", "A+7L+A-Z" },
Ouch :-)
One question for the C purists. How do we know how characters outside of
the ASCII range may be interpreted by a compiler ?
Until C+1x is finalized, we cannot rely on the new Unicode string
literals U"xxx"
On Wed, Oct 13, 2010 at 11:06:44AM +0200, Matthias Bolte wrote:
> VMware uses a mix of percent-, pipe- and base64-encoding in
> different combinations in different places.
>
> Add a testcase for this.
> ---
> src/esx/README | 25
> src/esx/esx_driver.c
VMware uses a mix of percent-, pipe- and base64-encoding in
different combinations in different places.
Add a testcase for this.
---
src/esx/README | 25
src/esx/esx_driver.c | 72 ++-
src/esx/esx_storage_driver.c | 42 +
