Hello Lyx people,
Jean-Marc Lasgouttes replied :
> Uwe Stöhr a écrit :
Both of you are using UTF-8, but even the mailers seem not
to agree about what is or what is not UTF-8. Isn't one diffrence
between machines and men that we can choose when to break out
behavior loops that could end up in locks, as machines has to go
up to locks before being able to change something (if not in
deadlocks at this time) ?
>> Besides the one in my last reply to this post, inconsistencies break
>> our docs. How should I write a documentation about a feature that is
>> not present under all OSes? (I have no Linux.) Having consistent
>> dialogs makes also the life easier for writing documentations.
> We do not write the program in terms of what is easier to document.
I'm the one who knows what has to be simple and what has not to be here.
But if I had to use simple things, using LaTeX could be a safer choice
than LyX with an inaccurate doc (I haven't read it all at this time).
I have not written billions lines of code yet, and lesser doc lines
but I can see one thing. One can write a long program with no parameters
that computes Pi. As complex as the code could be, the doc would remain
simple (as it doesn't document Pi, but the program that computes it).
On the other hand, a program that would eat n boolean parameters so that
it can exhibit 2^n possible behaviors, could be much more longer to
document
than documenting the code itself, and than coding it too ! So if the doc
folks, that are aware of that, should learn that there are still many
parameters to be added up in that same way, they could desperate
(and desperados don't write full docs)...
For example Thunderbird's configuration tool is inside the "Options"
menu under Windows, but under the "Edit" one under Linux. However you're
both using it, aren't you ?
So, what is LyX doc written with ? If there is a way to have os dependant
outputs, this kind of problems could be as painless a possible.
Recalling (explaining ?) how to make a shortcut to the exemples
could as welle be a good solution (while waiting for Qt5 ;-).
--
herve
