Op 24 okt. 2015 20:42 schreef "Uwe Stöhr" :
>
> Am 23.10.2015 um 10:25 schrieb Jean-Marc Lasgouttes:
>
>> If you look closely, they are not closer than the vertival line over B_V
>> is fromthe text. Seriously this is a much bigger problem
>
>
> But it still doesn't look as good
Op 24 okt. 2015 20:42 schreef "Uwe Stöhr" >:
> But it still doesn't look as good as with \raisebox in my opinion.
The header and the line before the header are definitely better, and I
would say that the line with the raisebox are too tall. It is
Am 23.10.2015 um 10:25 schrieb Jean-Marc Lasgouttes:
If you look closely, they are not closer than the vertival line over B_V
is fromthe text. Seriously this is a much bigger problem
But it still doesn't look as good as with \raisebox in my opinion.
Besides this, if you prefer formal
On Fri, Oct 23, 2015 at 06:46:59PM -0700, Pavel Sanda wrote:
> Vincent van Ravesteijn wrote:
> > IMO, a separate hard string freeze is not needed as long as we act
> > reasonable.
>
> I meant it as a part of feature freeze. Whether you are working on
> documentation
> or translation only, you
Am 24.10.2015 um 22:04 schrieb Jean-Marc Lasgouttes:
I really think that formal tables should be given a very prominent place
in the docs.
Then we should default to formal border style.
We still lack proper support for booktab's \cmidrule:
http://www.lyx.org/trac/ticket/3072
regards Uwe
Am 24.10.2015 um 21:49 schrieb Vincent van Ravesteijn:
Hmm we, as the experts, should not set the bad example. The fact that LyX's
docs don't use floats will be used by the unbelievers as an argument
against it.
The Math manual is the only one where floats are not used.
These tables are not
On Fri, Oct 23, 2015 at 12:15:26AM -0700, Pavel Sanda wrote:
> Vincent van Ravesteijn wrote:
> > >> - Will there be a code-freeze after that strings can still be changed?
> > >
> > > Is this what is normally done? I'm new at this.
> >
> > I've actually no clue what is meant with a code freeze
Original Message
From: Scott Kostyshak
Sent: Donnerstag, 22. Oktober 2015 18:45
On Thu, Oct 22, 2015 at 08:55:05AM +0200, Vincent van Ravesteijn wrote:
> On Thu, Oct 22, 2015 at 7:13 AM, Scott Kostyshak wrote:
> > On Mon, Oct 19, 2015 at 04:33:43PM +0200, Uwe Stöhr
Original Message
From: Scott Kostyshak
Sent: Donnerstag, 22. Oktober 2015 18:45
> Uwe, can you explain
why it is useful to have the beta released before starting to work on
the documentation? Why not start right after the feature freeze?
I need fixed strings. In my experience string
Op 23-10-2015 om 9:15 schreef Pavel Sanda:
So back to Uwe's question, it would be good you announce at some point
- features won't change ( except of bugfixing ) - translatable strings
are not going to be changed (except obvious bugs/typos). and maybe
give some hint when this might occur :)
Vincent van Ravesteijn wrote:
> IMO, a separate hard string freeze is not needed as long as we act
> reasonable.
I meant it as a part of feature freeze. Whether you are working on documentation
or translation only, you don't want people mess with UI logic and strings.
Pavel
Vincent van Ravesteijn wrote:
> >> - Will there be a code-freeze after that strings can still be changed?
> >
> > Is this what is normally done? I'm new at this.
>
> I've actually no clue what is meant with a code freeze after that
> strings an be changed ?
I think the question was, whether the
Le 23/10/2015 02:57, Uwe Stöhr a écrit :
I had now a look and the formal tables doesn't solve the spacing
problems: The "V" of the underscript/subscript are too close.
If you look closely, they are not closer than the vertival line over B_V
is fromthe text. Seriously this is a much bigger
On Thu, Oct 22, 2015 at 7:13 AM, Scott Kostyshak wrote:
> On Mon, Oct 19, 2015 at 04:33:43PM +0200, Uwe Stöhr wrote:
>> Dear LyXers,
>>
>> I would like to have a beta release short after the feature-freeze.
>> During the beta and RC-cycle the docs will be updated because this
>>
Am 21.10.2015 um 12:06 schrieb Jean-Marc Lasgouttes:
What do you mean? Apparently I missed your mail too.
Sorry, I should have given the references:
https://www.mail-archive.com/lyx-devel@lists.lyx.org/msg183726.html
Hi JMarc,
I had now a look and the formal tables doesn't solve the
On Thu, Oct 22, 2015 at 08:55:05AM +0200, Vincent van Ravesteijn wrote:
> On Thu, Oct 22, 2015 at 7:13 AM, Scott Kostyshak wrote:
> > On Mon, Oct 19, 2015 at 04:33:43PM +0200, Uwe Stöhr wrote:
> >> Dear LyXers,
> >>
> >> I would like to have a beta release short after the
On Mon, Oct 19, 2015 at 04:33:43PM +0200, Uwe Stöhr wrote:
> Dear LyXers,
>
> I would like to have a beta release short after the feature-freeze.
> During the beta and RC-cycle the docs will be updated because this
> usually takes some weeks.
Sounds good to me.
>
> - Will there be a code-freeze
Le 20/10/2015 23:16, Uwe Stöhr a écrit :
Am 19.10.2015 um 16:42 schrieb Jean-Marc Lasgouttes:
PS: and of course my idea of replacing ugly tables with nice formal
tables and remove all the spacing hacks you had to do is still waiting
for your answer ;)
What do you mean? Apparently I missed
Am 19.10.2015 um 16:42 schrieb Jean-Marc Lasgouttes:
Welcome back!
Thanks JMarc for the info.
PS: and of course my idea of replacing ugly tables with nice formal
tables and remove all the spacing hacks you had to do is still waiting
for your answer ;)
What do you mean? Apparently I missed
Le 19/10/15 16:33, Uwe Stöhr a écrit :
- what is the timetable for LyX 2.2?
Maybe an alpha release next week.
- Will there be a code-freeze after that strings can still be changed?
Don't know
- Who is the release manager for 2.2
Scott.
- A request: could anybody please add all new
Dear LyXers,
after some months without time for LyX I want to re-join the
development. Since my time is very limited I could not browse all the
many mails in the list and therefore ask for the basic news:
- what is the timetable for LyX 2.2? In May me was told to stop adding
new features.
21 matches
Mail list logo