Troy,
I've trawled through the curl header files and have found no mechanism
to determine if SSH is enabled for a build with it already enabled.
The libcurl docs I've read have said, regarding the ambiguous message
Peter received (stating that support is "either" disabled or
unavailable) that ther
Thanks, this was indeed the problem.
The zero width space character (which is used massively in Khmer) was for some
reason converted to a normal space.
Manfred
Am 19.12.2012 um 21:23 schrieb Kahunapule Michael Johnson :
> The first thing I would check is the handling of the zero-width space,
Hi.
Just to inform you.
I've moved all source code to Launchpad (https://launchpad.net/eloquent).
I've planed to also do all bug tracking and release planing there.
Regards,
Manfred
P.S.: I wish all a merry christmas and a good year 2013.
___
sword
So guys. What's the status on this one? Last I heard, we might want to
add libcurl ssh detection to prevent a flurry of support emails. Should
I commit as-is, or would you like more time to experiment with and add
detection?
Troy
On 12/19/2012 05:07 AM, Greg Hellings wrote:
If this gets
Thanks again for all the help on this one. I've committed a fix for
this and added the test case to our unit tests. Let me know if you find
it doesn't fix your problem, but it seems to fix the problem seen when
using: parsekey jn.2.3f.
Thanks again for the report and the detailed evaluation.
On Wed, Dec 19, 2012 at 9:06 PM, Greg Hellings wrote:
>> On Tue, Dec 18, 2012 at 9:27 PM, wrote:
>> Here's a patch that helps some with osistest. I still get the
>> following error when I run osistest, though:
>> UTF8Transliterator: ICU: no resource index to load
>> UTF8Transliterator: ICU: stat
