On May 29, 2006, at 11:16 AM, IOhannes m zmoelnig wrote:

Hans-Christoph Steiner wrote:

...

Would it be possible to bump up the font sizes in RST? The `` ``

why not use StructuredText ? (i found rst impractical at the least) (oh again one of those IO answers: "you don't want to do that"...)

The syntax is horrid when trying to include code. It was interpreting all of the *'s in the functions (char *, etc). Actually, I'd much prefer mediawiki/dokuwiki style syntax, it works much better. I spend very little time reading syntax charts with those, while with ST and RST I find I am constantly debugging the syntax.

...

inline quote font is almost unreadable.

in such cases i usually push "Ctrl++" on my firefox...

Hardly a solution. Everyone should really just use lynx with the console font.

.hc

...

Here's an example: http://puredata.org/docs/developer/PdAPI

i agree it looks ugly. i might have a look when i find the time.

mfd.sdr IOhannes

________________________________________________________________________ ____

"Terrorism is not an enemy. It cannot be defeated. It's a tactic. It's about as sensible to say we declare war on night attacks and expect we're going to win that war. We're not going to win the war on terrorism." - retired U.S. Army general, William Odom

Hallo, IOhannes m zmoelnig hat gesagt: // IOhannes m zmoelnig wrote:

Hans-Christoph Steiner wrote:

...

The syntax is horrid when trying to include code. It was interpreting all of the *'s in the functions (char *, etc). Actually, I'd much

oh, does it? this is bad.

Quoting the reST reference:

For example, none of the following are recognized as containing inline markup start-strings:

* asterisks: * "*" '*' (*) (* [*] {*} 1*x BOM32_* * double asterisks: ** a**b O(N**2) etc. * backquotes: ` `` etc. * underscores: _ __ __init__ __init__() etc. * vertical bars: | || etc.

It may be desirable to use inline literals for some of these anyhow, especially if they represent code snippets. It's a judgment call.

These cases do require either literal-quoting or escaping to avoid misinterpretation:

*4, class_, *args, **kwargs, `TeX-quoted', *ML, *.txt

The inline markup recognition rules were devised intentionally to allow 90% of non-markup uses of "*", "`", "_", and "|" without resorting to backslashes. For 9 of the remaining 10%, use inline literals or literal blocks:

"``*``" -> "*" (possibly in another font or quoted)

Only those who understand the escaping and inline markup rules should attempt the remaining 1%. ;-)

however, i usually use single quotes (ST) to get 'code' and it works pretty well.

"Until you want to quote 'something' with single quotes."

Ciao

On May 29, 2006, at 12:57 PM, Frank Barknecht wrote:

Hallo, Hans-Christoph Steiner hat gesagt: // Hans-Christoph Steiner wrote:

...

The syntax is horrid when trying to include code. It was interpreting all of the *'s in the functions (char *, etc).

Well, it was interpreting all * because a * is an inline markup element in reST to do e.g. **bold**. If one prefers <b>bold like this</b>, one should not use reST but HTML.

You could either use ``inline literals`` or convert all code to literal blocks.

A literal block is an indented block after a paragraph that ends with a double colon like this one does::

Nothing easier than formatting code like this.

You can also use a lone double colon.

::

void(*code)
{
    block;
}

I made the conversion on http://puredata.org/docs/developer/PdAPI, so you can see the result. It also fixed the font size issue.

Yeah, I tried that, but its a lot of work for a simple formatting. Plus I want to be able to have a function name, then the plain text description, like the Externals HOWTO. This syntax makes it a lot of work to do that.

ST is a pain to edit in the web form because you always have to indent everything manually. I gotta say both of these syntaxes were not designed well to be edited within a text form. Mediawiki style is much better for that. But I can edit ST pretty well in python- mode in Emacs. Alas, so much for quick edits...

.hc

________________________________________________________________________ ____

¡El pueblo unido jamás será vencido!

Hallo, IOhannes m zmoelnig hat gesagt: // IOhannes m zmoelnig wrote:

Hans-Christoph Steiner wrote:

...

Would it be possible to bump up the font sizes in RST? The `` ``

why not use StructuredText ? (i found rst impractical at the least)

"Structured text is really a great idea for certain situations; reST is a much better implementation of the idea than any versions I've seen before." Guido van Rossum

...

inline quote font is almost unreadable.

I didn't look too deeply into it yet, but there are no CSS-styles active for the docutils/reST classes. The default docutils stylesheet ("html4css1.css" [1]) however doesn't actually fix the font-size.

For that, one could use e.g. the entry:

tt.docutils { font-size: 110%; }

But generally I think there are some conflicting styles hidden inside Plone (like IMO <h6> shouldn't be smaller than <p>.)

[1] http://docutils.sourceforge.net/docs/howto/html-stylesheets.html

Ciao