I'm not against updating the docs or having any of the things you suggested I just don't want to do the work... or at least all of the work to make it happen. I don't think I have the scripts I used for the conversion anymore, and a lot of things in the site have had side effects on how things look on those pages. For instance <CODE> tags are used somewhat differently in the Perl FAQs and throughout the rest of the site. <CODE> tags were added after these docs were and so I had to change the display page for them to accomodate this difference. If another import happened we could do things right.tags were added after the Perl Man

If someone wants to take on this task and come up with naming conventions for all of the links to use and handle the appropriate conversions I can make some of the magic happen on this side.

If this is something that is really of interest to you bounce me an e-mail and we can pound out some more details.

vroom | Tim Vroom | vroom@cs.hope.edu

2001-06-12 Edit by Corion: Fixed formatting

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.