Fabrice Popineau wrote:
>> i simply can not use a program that i
>> know will be replaced within 5 years
>
> And there are not so many stable tools.
> TeX and Lisp.
>
> :-)
and hopefully lua -)
Hans
-
> i simply can not use a program that i
> know will be replaced within 5 years
And there are not so many stable tools.
TeX and Lisp.
:-)
Fabrice
___
If your question is of interest to others as well, please add an
On Jul 29, 2008, at 2:44 PM, Aditya Mahajan wrote:
> Hi Gerben,
>
> On Tue, 29 Jul 2008, Gerben Wierda wrote:
>
>> This should be based on (imo) merging the content of the excursion
>> and
>> the manual.
>
> Here (and sometime earlier in the thread) you have suggested that
> you find
> the sca
On Jul 29, 2008, at 8:05 PM, Hans Hagen wrote:
>> I was wondering if you already know what you would have to use if not
>> TeX. Is there an alternative at all?
>
> no, i'd probably choose a completely other job then (ok, maybe general
> programming as part time then) ... i simply can not use a pro
Gerben Wierda wrote:
> I was wondering if you already know what you would have to use if not
> TeX. Is there an alternative at all?
no, i'd probably choose a completely other job then (ok, maybe general
programming as part time then) ... i simply can not use a program that i
know will be repl
Hi Gerben,
On Tue, 29 Jul 2008, Gerben Wierda wrote:
> This should be based on (imo) merging the content of the excursion and
> the manual.
Here (and sometime earlier in the thread) you have suggested that you find
the scattered documentation of ConTeXt confusing and would like to see an
exha
On Jul 28, 2008, at 10:36 PM, Hans Hagen wrote:
> Gerben Wierda wrote:
>
>> Somehow, this might be applied to ConTeXt I think ;-). Three out of
>> four afaic...
>
> well, it's one reason why we have multiple smaller manuals (often made
> in sync with the specific feature)
>
> anyhow ... taco and i
Hello,
Am Montag, 28. Juli 2008 schrieb Gerben Wierda:
> I have an idea. Why not have a live ConTeXt manual.pdf where you add
> something in the proper location and compile the document every time
> you answer a question from a user? As you are the person answering
> anyway, it should be little ex
Gerben Wierda wrote:
> Somehow, this might be applied to ConTeXt I think ;-). Three out of
> four afaic...
well, it's one reason why we have multiple smaller manuals (often made
in sync with the specific feature)
anyhow ... taco and i only have one livetime, 24h/day etc etc
currently we spen
On Jul 28, 2008, at 4:20 PM, Hans Hagen wrote:
> there's the matter of what a user expects ... the core of context is
> rather stable and in that respect the 'old documentation' is still
> valid
> i.e. apart from 'new features, which may of interest to only a small
> group', the date on a manual
David wrote:
> documentation makes all other bugs insignificant. (In fact, many
> apparent bugs turn out to have secret workarounds anyway, and those
> would obviously be in the documentation.)
this is not entirely true ... there is often more than one way to solve
a problem (esp if there is n
On Mon, 28 Jul 2008, Taco Hoekwater wrote:
>
>
> Gerben Wierda wrote:
>>
>> I have an idea. Why not have a live ConTeXt manual.pdf where you add
>> something in the proper location and compile the document every time
>> you answer a question from a user? As you are the person answering
>> anyway,
Gerben Wierda wrote:
>
> I have an idea. Why not have a live ConTeXt manual.pdf where you add
> something in the proper location and compile the document every time
> you answer a question from a user? As you are the person answering
> anyway, it should be little extra work.
This is a goo
On Jul 28, 2008, at 12:46 PM, Taco Hoekwater wrote:
>
> Hi,
>
> While most of what Gerben states is close enough to the truth to
> be a matter of opinion, I really object to the tone of 'there is no
> documentation'. There is, in fact, a whole lot of documentation.
> It may be incomplete (especial
Hi,
While most of what Gerben states is close enough to the truth to
be a matter of opinion, I really object to the tone of 'there is no
documentation'. There is, in fact, a whole lot of documentation.
It may be incomplete (especially when it comes to recent developments),
but that is quite diff
On Jul 27, 2008, at 9:40 PM, David wrote:
>> From my own selfish point of view, the solution is simple. A freeze
>> on
>> all code, not even allowing bug fixes, until there's a comprehensive
>> and unified document written by Hans and Taco (plus whoever else)
>> that
>> explains how to use al
On Sat, 26 Jul 2008 04:38:42 +0200, Gerben Wierda wrote:
> My expectation is that the situation with respect
> to user documentation is not going to improve soon.
I don't know one way or the other about this. I do know that there are
only a few people (fewer than ten) who can even think of fix
On Jul 26, 2008, at 1:31 AM, Aditya Mahajan wrote:
> The sources are very well documented in the most
> part. But then, that is not user interface documentation, it is code
> documentation
Exactly. Let's give a simple example. My project needs both footnotes
and endnotes. For footnotes I have
On Fri, 25 Jul 2008, Gerben Wierda wrote:
> On Jul 22, 2008, at 2:37 AM, John Culleton wrote:
>
>> There are days when I feel like collecting all the bits and pieces and
>> writing somthing myself. But then I lie down until the fit passes.
>
> The lack of proper end user documentation is one of th
These are all my opinions, of course.
>
> The lack of proper end user documentation is one of the main problems
> with ConTeXt.
Eventually, actually one of the main problems is the lack of
people like Wolfgang Schuster .
For sure the things can be better if everyone uses the wiki to search an
On Jul 22, 2008, at 2:37 AM, John Culleton wrote:
> There are days when I feel like collecting all the bits and pieces and
> writing somthing myself. But then I lie down until the fit passes.
The lack of proper end user documentation is one of the main problems
with ConTeXt. There was talk of a
On Monday 21 July 2008 07:58:55 pm [EMAIL PROTECTED] wrote:
> Hi,
>
> Why not submit cont-enp.pdf (ConTeXt the manual) to lulu? I do
> appreciate the hard work that's going into the documentation, but
> at some places the english doesn't flow that well. Out of curiosity
> how many people proof read
Hi,
Why not submit cont-enp.pdf (ConTeXt the manual) to lulu? I do appreciate
the hard work that's going into the documentation, but at some places the
english doesn't flow that well. Out of curiosity how many people proof read
the documentation before they're released?
--
Thanks
Mohamed Bana
23 matches
Mail list logo
