Re: Impending String Freeze
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 English documents and turn it on by default ? Don't think that's needed. We have the option Language Package none, which can be used to create english documents without babel. Jürgen
Re: Impending String Freeze
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 the source. Only because the language package logic was completely upside down (something I fixed for 2.0.5), babel was loaded nevertheless. But then, people are now used to this obviously. As far as KOMA-Letter is concerned (only the letter class is affected!), the KOMA maintainer told me that is is a long-known bug, but he considers it cosmetic. So the chance this gets fixed in KOMA soon is not high. Jürgen
Re: Impending String Freeze
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 the revised layouts (moderncv et al) should stay in branch? These affect the strings. Jürgen
Re: Impending String Freeze
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 Christmas. Is there a decision whether the revised layouts (moderncv et al) should stay in branch? These affect the strings. The alternative is to release 2.0.5.1 with only this bug fix; we already did such kind of release in the past. Pavel
Re: Impending String Freeze
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 English documents" and turn > it on by default ? Don't think that's needed. We have the option "Language Package none", which can be used to create english documents without babel. Jürgen
Re: Impending String Freeze
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 the source. Only because the language package logic was completely upside down (something I fixed for 2.0.5), babel was loaded nevertheless. But then, people are now used to this obviously. As far as KOMA-Letter is concerned (only the letter class is affected!), the KOMA maintainer told me that is is a long-known bug, but he considers it "cosmetic". So the chance this gets fixed in KOMA soon is not high. Jürgen
Re: Impending String Freeze
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 the revised layouts (moderncv et al) should stay in branch? These affect the strings. Jürgen
Re: Impending String Freeze
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 Christmas. > > Is there a decision whether the revised layouts (moderncv et al) should stay > in branch? These affect the strings. The alternative is to release 2.0.5.1 with only this bug fix; we already did such kind of release in the past. Pavel
Re: Impending String Freeze
Op 22-12-2012 17:40, Richard Heck schreef: 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. I know the timing is bad, but the bug is bad, too. (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.) This will break again the documents that I recently fixed (in a suboptimal way) for LyX2.0.5 ? Can't we have an option Use Babel even for English documents and turn it on by default ? Vincent
Re: Impending String Freeze
Op 22-12-2012 17:40, Richard Heck schreef: 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. I know the timing is bad, but the bug is bad, too. (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.) This will break again the documents that I recently fixed (in a suboptimal way) for LyX2.0.5 ? Can't we have an option "Use Babel even for English documents" and turn it on by default ? Vincent
