Re: [Bibdesk-users] obscure error: possible runaway string started at line

[Christiaan H. <cmh...@gm...>]

On 28 Jul 2008, at 3:59 PM, Adam R. Maxwell wrote:

>
> On Jul 28, 2008, at 2:13 AM, Christiaan Hofman wrote:
>
>> Yes, I see the warning now. Should be harmless.
>>
>> I inserted the newlines for saving to avoid long lines. The base64
>> parser in the Omni frameworks ignores garnage characters like  
>> newlines
>> and spaces.
>
> [...]
>
>> The heuristic is as follows: anytime we have a
>> newline
>> * in a string, that's reason to suspect a runaway.
>
> [...]
>
>> So it's the newline in the long string in combination with the "=" at
>> the end that triggers the warning.
>>
>> Anyway, it's harmless.
>
> In general, that warning is not harmless, so users shouldn't get in  
> the habit of ignoring it. Unfortunately, it will likely be quite  
> common now since = often appears at the end of a base64 encoded  
> string.


Perhaps we could remove the "=" padding at the end, and re-attach them  
if necessary?

Christiaan