#1281 fix README file CSS for plain text [15583]

v1.0.0
closed
General
nobody
2015-08-20
2011-01-06
Chris Tsai
No

https://sourceforge.net/apps/trac/sourceforge/ticket/15583

I use sf.net beta. There, in the subversion tool, you can browse the repository tree which is awesome.

It also automatically shows any README files, if present.

However, if these files contain carets, they get eaten and some undisplayable characters result. everything contained in the carets is eaten, too.

Example:
https://sourceforge.net/p/gerbil/svn/4/tree/

See below under "DATA FORMAT". Original text is:

The software reads images as an array of image files (depicting one filter band each), each grayscale (8 or 16 bit) and in any image format that OpenCV understands. All files have to be of the same spatial size. A descriptor file is needed in the following format:
<number of bands n>
<base directory where files are located>
<filename 1> [<peak wavelength> | <lower wl bound> <upper wl bound>]
<filename 2> ...
...
<filename n> ...

Where the user says "carets" I think he means inequality signs. I actually saw the same issue while filing this ticket, when I tried to "quote" the paragraph that contained the inequality signs, like so:

The software reads images as an array of image files (depicting one filter band each), each grayscale (8 or 16 bit) and in any image format that OpenCV understands. All files have to be of the same spatial size. A descriptor file is needed in the following format:
<number of="" bands="" n="">
<base directory="" where="" files="" are="" located="">
<filename 1=""> [<peak wavelength=""> | <lower wl="" bound=""> <upper wl="" bound="">]
<filename 2=""> ...
...
<filename n=""> ...

Discussion

  • Dave Brondsema

    Dave Brondsema - 2011-02-18
    • summary: SVN tool README file viewer has problems with inequality signs [15583] --> fix README file CSS for plain text [15583]
    • milestone: --> feb-21
     
  • Dave Brondsema

    Dave Brondsema - 2011-02-18

    I believe the original issues was fixed when we started using pypeline (although the example no longer works).

    The https://sourceforge.net/p/gerbil/svn/ README still renders bad though, needs some 'pre' action. Lets fix that and then close this ticket.

     
  • Dave Brondsema

    Dave Brondsema - 2011-02-18
    • size: --> 1
     
  • Jenny Steele - 2011-02-23
    • status: open --> in-progress
    • assigned_to: Jenny Steele
     
  • Dave Brondsema

    Dave Brondsema - 2011-02-24
    • size: 2 --> 1
     
  • Jenny Steele - 2011-02-28
    • status: in-progress --> closed
     
  • Dave Brondsema

    Dave Brondsema - 2011-02-28
    • status: closed --> open
     
  • Dave Brondsema

    Dave Brondsema - 2011-02-28

    There's a

     around all readme files now, but not all readme files are plain text.  Some are Markdown, for example https://sourceforge.net/p/allura/git/  The preformatted style should only be applied if the readme type is plain text.

     
  • Jenny Steele - 2011-03-01
    • status: open --> in-progress
     
  • Jenny Steele - 2011-03-03
    • status: in-progress --> closed
     

Log in to post a comment.