[seqfan] Re: A011784 formatting issue

[David Wilson]

I guess I can see what you were after. If the browser chooses to break 
the line, it looks like a standard line continuation. But if the browser 
doesn't, it looks weird and unnecessary. Personally, I think forcing the 
line break would be preferable, but it's just a preference.

Russ Cox wrote:
> On Tue, Jan 20, 2009 at 7:25 AM, David Wilson <dwilson at gambitcomm.com> wrote:
>   
>> In the "long" and "short" formats, a backslash continuation appears on
>> the %U line, but the line is not broken after the backslash as it
>> presumably should be.
>>
>> Since the backslash does not appear in the database itself, I assume it
>> is added by the formatter.
>>     
>
> The formatter adds backslash+space in the middle of very
> large numbers (search for multiplicative encoding), to give
> web browsers a chance to break incredibly large numbers
> rather than make the window unreasonably wide with a
> horizontal scroll bar.  If you are seeing a backslash in a
> sequence with no big numbers (70+ digits) then there is
> a bug somewhere.
>
> In the specific case of A011784, I don't see any.
>
> Russ
>
>
> _______________________________________________
>
> Seqfan Mailing list - http://list.seqfan.eu/
>
>
>