Greetings from Bali...
Beyond the immediate victims, the terrorist acts of 12 Oct 2002 in Bali send chilling shivers to the islands tourism industry, the very lifeblood of the island. Tourism industry in Bali employs hundreds of thousands of people, feeding around 3 million people in the island.&nbsp;If tourists stop coming, there will be a lot more victims...
We are calling for Backpackers around the world to help revive tourism to Bali!
To help do this, we have created a portal for&nbsp;Backpackers to visit Bali: http://www.budgetbali.com&nbsp;Please kindly visit the site.
You can book online over 100 bed-and-breakfasts at heavily discounted prices. Long stays deals, homestays and rental homes are coming soon. We will also be putting in a forum&nbsp;and continue to improve the site. Inputs and suggestions are most welcome, as well as other resources that would be useful and links exchanges with other backpacking resources on the net.
Sincerely,
--Eka Ginting
Enter your text here. ----------------------------------------------------------------------- *** indo.com CRM - Mailing List Management ***
indo.com - the leading internet company in indonesia
<br>
http://www.indo.com & http://www.orientmagix.com : great deals for traveling to Indonesia & ASEAN
<br>
http://www.paketrupiah.com : instant travel in comfort and good time for Indonesian residents
<br>
http://www.rajacraft.com : buy quality indonesian crafts at wholesale prices
<br>
http://www.siliconbali.com : deploy internet technology for your business
<br>
Sent using http://www.turbocustomer.com - guaranteed lower costs to send your email, SMS, and international faxes!<p>click <a href="http://www.turbocustomer.com/unsub.php3?op=unsub&email=docutils-users@...&coid=3">UNSUBSCRIBE</a&gt; to unsubscribe</p>

Brett g Porter wrote:
> I'm trying to document a C struct that's like:
>
> ::
> {
> int field1;
> int field2;
> }
>
> by keeping the code in literal blocks (in reality, it's a rather
> large struct, and not every member needs annotation, something like:
>
> ::
> {
> int field1;
>
> This is a clever note about field1
>
> ::
>
> int field2;
>
> this is another witticism
>
> ::
> }
>
> ...but the indentation for the literal ``int field2;`` is not
> consistent (because it doesn't have the curly braces to give it that
> indentation context any more.
>
> Suggestions for how to accomplish what I'm trying?
First, don't forget that you need a blank line after the "::" (it must
be alone or at the end of a paragraph).
The simplest way I can think of is to use some text to mark the left
edge of your literal block. I'd choose ellipsis ("..."), since it
indicates "continuing...":
::
...
int field2;
this is another witticism
::
...
}
Or the entire thing could be bordered on the left:
::
| {
| int field1;
| int field2;
| }
(When splitting up the block, preserve the border bars.)
Or even line numbers:
::
13: {
14: int field1;
15: int field2;
16: }
Another way would be to use the "parsed-literal" directive:
.. parsed-literal::
\
int field2;
The backslash establishes the left edge but disappears after parsing.
You have to be careful with parsed-literals though, becuase any inline
markup *is* parsed.
Finally, a runtime setting (set via directives and/or command-line
options) could be introduced to establish fixed indentation levels.
The parser could then assume, for example, that Literal blocks always
begin 4 spaces to the right of the surrounding text. This would
require implementation of course. The quickest way to implementation
is to submit a patch!
--
David Goodger <goodger@...> Open-source projects:
- Python Docutils: http://docutils.sourceforge.net/
(includes reStructuredText: http://docutils.sf.net/rst.html)
- The Go Tools Project: http://gotools.sourceforge.net/