Preserving carraige returns causes extra lines in browser
Reported by Jason Garber | July 11th, 2008 @ 08:23 AM | in 4.0
Everything works fine when your input is from a Unix system (\n line endings), but when you get \r\n like from Windows, the carriage returns cause a problem. The linefeed/newline is translated into
\n
\n@, which puts the
on a line all by itself in the browser.
Comments and changes to this ticket
-
Jason Garber July 11th, 2008 @ 09:05 AM
- State changed from “new” to “resolved”
-
Jason Garber July 11th, 2008 @ 09:01 AM
(from [42abe0b55972956749d97b9a9a5f12a7ca6c1375]) Strip carriage returns and deal only with linefeeds
Carriage returns before linefeeds are a problem. The easiest solution is to strip them out before parsing. RedCloth 3 doesn't preserve them either, so it must be okay with users. Plus, it makes the output more predictable and standardized.
[#11 state:resolved]
[#14 state:resolved]
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
RedCloth is a Ruby library for converting Textile into HTML
People watching this ticket
Jason Garber
Tags
Referenced by
-
4
Segfault with links
#14 0x00007f6f38e8e2ea in ?? () from /usr/lib/libruby1.8...