headers
Guenter Milde | 1 Jan 2009 23:46
Picon

listing pros and cons

Dear docutils useres,

what is the most elegant way to compile a list of (dis-) advantages with
rst?

itemize:
  + concise
  + clear source

  - shows only dots in output

option list:
  +1  concise
  +1  clear source
  -2  does not work reliably (needs number)
  -1  less straightforward
  -2  "abusing" special list type

line block:
  | + works reliably, correct output
  | + list items not aligned (+ wider than -)
  | - rating "hidden" in source
  | - no semantic markup (generic block for special list type)

field list:
  :+: aligned markers and items
  :-: "ugly" source
  :-: colon in output

Any other?
(Continue reading)

Permalink | Reply | 2 comments |
headers
Trent W. Buck | 2 Jan 2009 02:38
Picon

Re: listing pros and cons

Guenter Milde <milde <at> users.berlios.de> writes:

> Dear docutils useres,
>
> what is the most elegant way to compile a list of (dis-) advantages with
> rst?

I would do it thusly (two sorted, itemized lists):

    In descending order, advantages of foo are:

    - lorem ipsum dolor sit amet;
    - consectetur adipisicing elit; and
    - sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.

    In descending order, disadvantages of foo are:

    - ut enim ad minim veniam, quis nostrud exercitation ullamco laboris
      nisi ut aliquip ex ea commodo consequat;

    - duis aute irure dolor in reprehenderit in voluptate velit esse
      cillum dolore eu fugiat nulla pariatur;

    - excepteur sint occaecat cupidatat non proident; and
    - sunt in culpa qui officia deserunt mollit anim id est laborum.

------------------------------------------------------------------------------
Permalink | Reply | 0 comments |
headers
David Goodger | 2 Jan 2009 03:37
Favicon

Re: listing pros and cons

On Thu, Jan 1, 2009 at 17:46, Guenter Milde <milde <at> users.berlios.de> wrote:
> what is the most elegant way to compile a list of (dis-) advantages with
> rst?
>
> itemize:
>  + concise
>  + clear source
>
>  - shows only dots in output

You could apply a class and use CSS to specify bullet symbols.

> line block:
>  | + works reliably, correct output
>  | + list items not aligned (+ wider than -)

You could use U+2212 "minus sign" ("−"; "-" is U+002D "hyphen-minus").
U+2212 "−" should be the same width as "+".

--

-- 
David Goodger <http://python.net/~goodger>
------------------------------------------------------------------------------
_______________________________________________
Docutils-users mailing list
Docutils-users <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/docutils-users

Please use "Reply All" to reply to the list.
Permalink | Reply | 0 comments |
headers
Alan G Isaac | 12 Jan 2009 20:32
Picon
Favicon

container content

Apparently a ``container`` cannot contain section headers?
Does this mean section headers are not "body elements",
or are the docs misleading?
http://docutils.sourceforge.net/docs/ref/rst/directives.html#container

Might this restriction be dropped?

Thanks,
Alan Isaac

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
Permalink | Reply | 1 comment |
headers
David Goodger | 12 Jan 2009 20:38
Favicon

Re: container content

On Mon, Jan 12, 2009 at 14:32, Alan G Isaac <aisaac <at> american.edu> wrote:
> Apparently a ``container`` cannot contain section headers?

Correct.

> Does this mean section headers are not "body elements",
> or are the docs misleading?
> http://docutils.sourceforge.net/docs/ref/rst/directives.html#container

Sections are not body elements.

> Might this restriction be dropped?

No, it will always be there. It is intrinsic to the Docutils document model.

--

-- 
David Goodger <http://python.net/~goodger>

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
Permalink | Reply | 0 comments |
headers
Alan G Isaac | 13 Jan 2009 15:40
Picon
Favicon

Re: [Docutils-develop] default length unit?

On 1/13/2009 9:34 AM David Goodger apparently wrote:
> I think pt.

Note that LaTeX has both pt and bp,
http://www-h.eng.cam.ac.uk/help/tpl/textprocessing/teTeX/latex/latex2e-html/ltx-86.html
and for this purpose I think bp is preferred.

Alan

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
Permalink | Reply | 2 comments |
headers
Guenter Milde | 14 Jan 2009 10:26
Picon

Re: [Docutils-develop] default length unit?

On 2009-01-13, Alan G Isaac wrote:

> Note that LaTeX has both pt and bp,
> and for this purpose I think bp is preferred.

That is the "Postscript point" used outside LaTeX, right?

Actually, pdflatex even has px (screen pixel). However 

* as the end-format is a document on pages with fixed size, it seems more
  reasonable to use a fixed size for the default length unit as well.

* it is (to me) unclear at what stage the screen-resolution is used to
  compute the actual size in the document (generation vs.
  viewing/printing).

* it is not supported by "non-pdf" latex, so I hesitate to use it as
  default.

I vote for bp as default.

Günter  

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Docutils-users mailing list
(Continue reading)

Permalink | Reply | 1 comment |
headers
grubert | 14 Jan 2009 17:21
Picon
Gravatar

Re: [Docutils-develop] default length unit?

On Wed, 14 Jan 2009, Guenter Milde wrote:

> On 2009-01-13, Alan G Isaac wrote:
>
>> Note that LaTeX has both pt and bp,
>> and for this purpose I think bp is preferred.
>
> That is the "Postscript point" used outside LaTeX, right?
>
> Actually, pdflatex even has px (screen pixel). However
>
> * as the end-format is a document on pages with fixed size, it seems more
>  reasonable to use a fixed size for the default length unit as well.
>
> * it is (to me) unclear at what stage the screen-resolution is used to
>  compute the actual size in the document (generation vs.
>  viewing/printing).
>
> * it is not supported by "non-pdf" latex, so I hesitate to use it as
>  default.
>
> I vote for bp as default.

0 from me, i use images seldom.

cheers

--

-- 

------------------------------------------------------------------------------
(Continue reading)

Permalink | Reply | 0 comments |
headers
Chris G | 15 Jan 2009 17:04

Setting text colour in Docutils

Is the 'right' way to set text colour (and background colour, etc.) in
Docutils to use CSS?  I.e. use a Docutils "class" directive and then
CSS for that class.

All I actually want to do is use grey instead of black to de-emphasise
some text without changing its size at all.

--

-- 
Chris Green

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
Permalink | Reply | 2 comments |
headers
David Goodger | 15 Jan 2009 18:58
Favicon

Re: Setting text colour in Docutils

On Thu, Jan 15, 2009 at 11:04, Chris G <cl <at> isbd.net> wrote:
> Is the 'right' way to set text colour (and background colour, etc.) in
> Docutils to use CSS?  I.e. use a Docutils "class" directive and then
> CSS for that class.

Yes.

> All I actually want to do is use grey instead of black to de-emphasise
> some text without changing its size at all.

You can also use a custom interpreted text role, if the text is a
portion of a paragraph. For example:

.. role:: de

Here is some :de:`de-emphasized text`.

--

-- 
David Goodger <http://python.net/~goodger>

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
Permalink | Reply | 1 comment |

Gmane