Vincent van Ravesteijn wrote:
> This will break again the documents that I recently fixed (in a
> suboptimal way) for LyX2.0.5 ?
Which ones? I don't think this will break anything, though (unless people now
manually call babel with fixed options).
> Can't we have an option "Use Babel even for E
Richard Heck wrote:
> (It isn't, by the
> way, entirely clear that it is our bug, but it is problematic, as it
> breaks Koma compilation with some documents.)
It's not our bug, and actually, the current behavior (no babel for English-
only documents) always was the intended behavior according to
Richard Heck wrote:
> I am intending to release 2.0.6 as soon as we can, due to bug #8423, now
> fixed in branch. If you have any string-changing commits you'd like to
> make, please make them as soon as possible. I'll announce the string
> freeze around Christmas.
Is there a decision whether t
Jürgen Spitzmüller wrote:
> Richard Heck wrote:
> > I am intending to release 2.0.6 as soon as we can, due to bug #8423, now
> > fixed in branch. If you have any string-changing commits you'd like to
> > make, please make them as soon as possible. I'll announce the string
> > freeze around Chris
On 12/23/2012 06:43 AM, Pavel Sanda wrote:
Jürgen Spitzmüller wrote:
Richard Heck wrote:
I am intending to release 2.0.6 as soon as we can, due to bug #8423, now fixed
in branch.
The alternative is to release 2.0.5.1 with only this bug fix; we already did
such kind of release in the past.
Richard Heck wrote:
> Opinions? That would be relatively easy.
Certainly the safest way. Since we do not have any other really urgent fix, I
would probably go for this one.
Jürgen
Jürgen Spitzmüller wrote:
> Oh, I see. At the moment, such arguments need to be inserted in the first
> paragraph. This is also the case for layout sequences (such as lists) and
> it has been like this always (cf. item list in beamer in 2.0, for
> instance).
>
> Alas, it is not trivial to change
