From: Jano Kula <jano.kula@tiscali.cz>
Subject: Re: XML and title page rule
Date: Tue, 28 Mar 2006 18:12:30 +0200 [thread overview]
Message-ID: <e0bn9e$dql$1@sea.gmane.org> (raw)
In-Reply-To: <4423B7F0.6050700@wxs.nl>
Hi,
> <title>Something &emdash; or <i>Something else</i></title>
can somebody explain to a complete newbie why entity &emdash; isn't
expanded out of the box?
(I use texexec -pdf document.tex for processing.)
> Here is the hint - needs to be wikified now ... -)
I can't resist to do so (that's why I need an explanation), cause as a
newbie I see the only weakness of the ConTeXt in the lack of documentation.
Well, there is a lot of it, maybe there is too much of it spread all
over the different places (that's why wiki is here), maybe I'm not
familiar enough with ConTeXt yet, but as a long term user of LaTeX I'm
still quite confused after a week or so of browsing through the
documentation, trying to find out how the things work and how they are
related. Well, it took some time to understand LaTeX, too. I would buy
the book mentioned here immediatelly.
These are not complaints, just another hint how to smooth starting with
ConTeXt. As I see the possibilities I become addicted ;) and I do
understand the developers have a lot of work with developing.
Would anybody who suggests the wikifying mind the proper place to put it
in the wiki, if known? Or I shouldn't care and the administators tide it
up occasionally. As a newbie I might not to think of writing to wiki,
but better something than nothing, right?
As the new one here, I can add some small examples as I learn and test
the things, what would be nice for the newcomers, if somebody
experienced would add to wiki an explanation of the documentations in
terms of user experience
1. "must read"
2. how the things work (texexec, etc.)
3. simple topics
4. advanced features
If I see the all-manuals page (http://www.pragma-ade.com/show-man.pdf) I
really don't know where to start. All the titles look so interesting!
Such overview could postpone the temptation to seek for advanced topic
and subsequently get lost, as in my case. (Might be only my fault.)
Sorry for the desperade bigginer's notes, hope they help. To finish it
why I can't get these two (advanced) pages?
http://www.pragma-ade.com/makeres.html
http://www.pragma-ade.com/general/manuals/xcorresp.pdf_Serial_Letters
Looking forward to use ConTeXt,
Jano
next prev parent reply other threads:[~2006-03-28 16:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-24 4:36 Johannes Graumann
2006-03-24 9:12 ` Hans Hagen
2006-03-24 18:04 ` Johannes Graumann
2006-03-28 16:12 ` Jano Kula [this message]
2006-03-28 16:40 ` Hans Hagen
2006-03-28 17:38 ` Jano Kula
2006-03-29 14:15 ` documents to (print and) read Geert Stappers
2006-03-30 8:38 ` Taco Hoekwater
2006-04-03 17:43 ` Jano Kula
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='e0bn9e$dql$1@sea.gmane.org' \
--to=jano.kula@tiscali.cz \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).