Le 14/10/2011 03:17, Uwe Stöhr a écrit :
I cannot parse what you mean. You are certainly not indicating that
any LaTeX list, like itemize or
enumerate environment, are designed with free spacing in mind, are you?
You misunderstood me. The LaTeX list allows to use multiple spaces. The
other lists are indeed derived from the basic LaTeX list but forbid this.
Can you point me to a document that support this claim? I find it hard
to believe (or I still misunderstand you). In latex, nothing supports
multiple spaces unless explicitly coded (eg verbatim).
I am not against this, but this will be a change for existing
documents. Some people are actually
happy that the lines do not break and go through the right margin...
But this doesn't make sense: You can't print it and also not publish
this. So I doubt that people do this purposely.
Do you really mean that you never saw people who do not care that their
listing protrudes by 5mm outside of the right margin and would be
annoyed to have a word alone on a line for correctness' sake?
Heiko Oberdiek told me that this would have drawbacks as this change
take place globally. (I didn't understand the TeX-internal details.)
Moreover it doesn't work for multiple spaces, see the attached file.
Do you have a lik to this discussion (I think you posted it already, but
I lost it)? Maybe I can understand what he means.
It also doesn't solve the bug, because it is:
- when the user presses SPACE we insert a ~
As long as we don't change this, we can redefine whatever we want.
So my plan is to remove this special code that inserts explicit ~ and to
upgrade our environments instead. THat would mean, with the following
arbitrary numbering
>> 0: no free spacing
>> 1: output space as "~"
>> 2: output space as "\ "
>> 3: output space as " "
to ship with LyX only environments that use values 0 or 3, and keep 1
and 2 for weird latex things we have no control on.
So why should we take risks and add some more definitions when there is
a clean solution that was recommended by LaTeX experts?
It is you who propose to take risks and change the way LyX-Code behaves
wrt line breaks. I agree that the original choice was unfortunate, but
we have to live with it. I would propose to keep LyX-Code with its
broken semantics, but maybe move it to a module (that lyx2lyx would
insert automatically as needed) and ship layouts supporting verbatim and
alltt instead.
But lyxcode code _is_ standard. It correctly uses TeX's list environment
in exactly or the purpose why it is defined in TeX. The LaTeX gurus had
a look at our code and said it is correct.
We cannot use something else and this would also don't make sense.
Naturally spoken, we need a bus, not a car and not a lorry and we
already have this bus. We only need to change to change the arrangement
of its seats.
I wonder how the rest of the LaTeX community manges to produce documents
without our very special environment. They don't know what they are
missing :)
What is wrong with verbatim or alltt, seriously? Or even more fancy
verbatim alternatives? What it the unique feature of LyX-Code that makes
its existence worth it?
With LyX-Code, we reinvented a new wheel. The fact that an expert
testified that our wheel is round is not enough to warrant using it.
Using standard environment means that tex-html or tex-odt fileter can
understand our files. Is this worth nothing to you?
JMarc
JMarc
