Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.javascript > #17674

Re: Potential FAQ mechanism on GitHub

Show all headers | View raw

On Tue, 11 Dec 2012 11:02:59 +0000, in comp.lang.javascript John G
Harris <john@nospam.demon.co.uk>
<uYnIguEjLxxQFwH9@J.A830F0FF37FB96852AD08924D9443D28E23ED5CD> wrote:

>| On Mon, 10 Dec 2012 at 11:03:57, in comp.lang.javascript, Scott Sauyet 
>| wrote:
>| >John G Harris wrote:
>| 
>|    <snip>
>| >> Is this a suitable way to show drafts for comment ?
>| >>
>| >>   <http://www.jghnorth.org.uk/faqdesign/faq1.html>
>| >>
>| >> It's not serious yet; some changes are outstanding.
>| >
>| >I believe so.  At a quick glance, it looks to me as though you wrapped
>| >up the main body of the output generated through the process I
>| >described in some additional markup.  The infrastructure would support
>| >that in a fairly simple manner.  If you were looking instead to
>| >*modify* the generated markup to support your design, it would be
>| >significantly harder to accommodate.
>| 
>| Perhaps I should have made it clearer. It's a draft css file that's 
>| being demonstrated. The html file is there just to show the effect of 
>| the draft styles. Part of it comes from the FAQ, possibly amended; part 
>| is demo environment.
>| 
>| I've updated the css file, see the link above. I've also amended one 
>| part of the FAQ text by replacing
>|    <code> ... </code>
>| with
>|    <pre><code> ... </code></pre>
>| This puts code on a separate line and also avoids problems with browsers 
>| that haven't implemented code elements yet. Would this change be much of 
>| a problem?
>| 
>|    John

Huh???? The HTML code element has been around since HTML 1.0.
The code element is an inline element much like em, b, u etc.
The pre element is a block element which must enforce the whitespace
used within it and forces a new line at the beginning and end of the
block.

Back to comp.lang.javascript | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Potential FAQ mechanism on GitHub Scott Sauyet <scott.sauyet@gmail.com> - 2012-12-09 20:12 -0800
  Re: Potential FAQ mechanism on GitHub John G Harris <john@nospam.demon.co.uk> - 2012-12-10 11:26 +0000
    Re: Potential FAQ mechanism on GitHub Scott Sauyet <scott.sauyet@gmail.com> - 2012-12-10 04:29 -0800
      Re: Potential FAQ mechanism on GitHub John G Harris <john@nospam.demon.co.uk> - 2012-12-10 18:35 +0000
        Re: Potential FAQ mechanism on GitHub Scott Sauyet <scott.sauyet@gmail.com> - 2012-12-10 11:03 -0800
          Re: Potential FAQ mechanism on GitHub John G Harris <john@nospam.demon.co.uk> - 2012-12-11 11:02 +0000
            Re: Potential FAQ mechanism on GitHub Jeff North <jnorthau@yahoo.com.au> - 2012-12-12 01:27 +1100
              Re: Potential FAQ mechanism on GitHub John G Harris <john@nospam.demon.co.uk> - 2012-12-11 14:52 +0000
              Re: Potential FAQ mechanism on GitHub Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2012-12-11 22:31 +0100
                Re: Potential FAQ mechanism on GitHub John G Harris <john@nospam.demon.co.uk> - 2012-12-12 15:41 +0000
                Re: Potential FAQ mechanism on GitHub "Jukka K. Korpela" <jkorpela@cs.tut.fi> - 2012-12-12 18:47 +0200
                Re: Potential FAQ mechanism on GitHub Tim Streater <timstreater@greenbee.net> - 2012-12-12 23:20 +0000
            Re: Potential FAQ mechanism on GitHub Scott Sauyet <scott.sauyet@gmail.com> - 2012-12-11 06:30 -0800
      Re: Potential FAQ mechanism on GitHub Dr J R Stockton <reply1250@merlyn.demon.co.uk.invalid> - 2012-12-12 21:13 +0000
  Re: Potential FAQ mechanism on GitHub Dr J R Stockton <reply1250@merlyn.demon.co.uk.invalid> - 2012-12-12 21:27 +0000
    Re: Potential FAQ mechanism on GitHub Scott Sauyet <scott.sauyet@gmail.com> - 2012-12-13 08:29 -0800

csiph-web