Hi Kathy --
Fantastic! Thank you for the detailed description -- I was missing the use
of different directories to collect related-scope content. I'll give it a
shot.
Thanks again,
Ramon
On Wednesday, March 28, 2012 9:33:55 AM UTC-7, Kathy Tolbert wrote:
>
> Hello again, Ramon.
>
>
>
> Here
On Wed, Mar 28, 2012 at 6:46 AM, Guenter Milde wrote:
> On 2012-03-26, Gour wrote:
>
>
> PDF output requires configuring LaTeX via packages and preamble code. The
> details depend ou your choice between traditional 8-bit TeX and XeTeX or
> LuaTeX as back-end.
>
This is not necessarily true, thou
Hello,
We are planning to translate our documentation (http://manual.mahara.org)
into other languages. I was wondering if those of you who do the same thing
would like to share their experiences and tips as well as pitfalls to
avoid. I am particularly interested in learning how to deal best wit
Hello again, Ramon.
Here is how we approached the multi-level documentation using the include
directive.
Directory structure for this test:
Root product directory
-- 01_files_cast_basic
-- 02_files_cast_extended
-- 03_files_cast_advanced (contains the advanced .rst file:
content_advance
On 2012-03-26, Gour wrote:
> I'm considering which markup to use for our open-source project to write
> user's manuals as well as for general writing (study notes etc.)
I recommend to use Docutils_ for single documents (study notes etc.) and
Sphinx for projects (web sites, software documentation)
