On Monday, July 28, 2008, at 07:56AM, "Christiaan Hofman" <[EMAIL PROTECTED]> 
wrote:
>
>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?

That sounds worse than the warning, and a potential nightmare for 
compatibility.  If you implemented this, then saved a file with a nightly 
build, could you then read it with 1.3.18?  If not, I'd guess that a few users 
would be fairly upset.  Not that it matters to me personally...I'm using 
openssl for base64 in my own version.

Why add newlines in the first place?  A single line is easier to ignore in text 
editors that allow long lines, and updates to the alias will only cause a 
single-line diff for people who use version control systems.  Inserting 
newlines seems like a solution in search of a problem.




-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bibdesk-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bibdesk-users

Reply via email to