Hi
the following bug is present in the revision 37872: if I choose
"formated ref" for a cross reference, the package prettyref is loaded in
the LaTeX preamble but the reference is traduced by \ref{...} instead of
\prettyref{...}.
Philippe Charpentier
Public release of LyX version 2.0.0 (release candidate 1)
=
We are pleased to announce the first release candidate of LyX 2.0.0.
Since the last beta releases became stable enough for a regular work
we switched to release candidate, freezed n
Am 07.03.2011 um 15:36 schrieb Stephan Witt:
> Am 07.03.2011 um 14:32 schrieb Anders Ekberg:
>
>> On 2011-03-07 14.29, "Stephan Witt" wrote:
>>
>>> Am 07.03.2011 um 13:32 schrieb Anders Ekberg:
>>>
On 2011-03-07 12.44, "Stephan Witt" wrote:
> Sorry, I cannot reproduce it.
>
Am 07.03.2011 um 14:32 schrieb Anders Ekberg:
> On 2011-03-07 14.29, "Stephan Witt" wrote:
>
>> Am 07.03.2011 um 13:32 schrieb Anders Ekberg:
>>
>>> On 2011-03-07 12.44, "Stephan Witt" wrote:
>>>
Sorry, I cannot reproduce it.
(I tried it with the LyX.app started from the .dmg volume
On 2011-03-07 14.29, "Stephan Witt" wrote:
>Am 07.03.2011 um 13:32 schrieb Anders Ekberg:
>
>> On 2011-03-07 12.44, "Stephan Witt" wrote:
>>
>>> Sorry, I cannot reproduce it.
>>> (I tried it with the LyX.app started from the .dmg volume).
>>> Perhaps it depends on the document you start with. I
On 03/06/2011 05:47 PM, Tommaso Cucinotta wrote:
One question: can anyone point me to where exactly, in the code, there
is the
distinction between the use of prettyref as opposed to refstyle, for
the generated
xref macros ?
Do you mean where the code is generated? In InsetRef::getFormattedCm
Am 07.03.2011 um 13:32 schrieb Anders Ekberg:
> On 2011-03-07 12.44, "Stephan Witt" wrote:
>
>> Sorry, I cannot reproduce it.
>> (I tried it with the LyX.app started from the .dmg volume).
>> Perhaps it depends on the document you start with. Is it somewhat special?
>>
>> Stephan
>
> Seems to
On 2011-03-07 12.44, "Stephan Witt" wrote:
>Sorry, I cannot reproduce it.
>(I tried it with the LyX.app started from the .dmg volume).
>Perhaps it depends on the document you start with. Is it somewhat special?
>
>Stephan
Seems to be triggered with every document for me (at least that the pasted
Am 07.03.2011 um 11:33 schrieb Anders Ekberg:
>
>
> On 2011-03-07 11.26, "Stephan Witt" wrote:
>
>> Am 07.03.2011 um 11:13 schrieb Anders Ekberg:
>>
>>> One more nasty bug on Mac (latest SnowLeopard):
>>> The alt key modifier seems to be broken. As an example, alt+m m (which
>>> should give y
Am 07.03.2011 um 11:33 schrieb Anders Ekberg:
> On 2011-03-07 11.26, "Stephan Witt" wrote:
>
>> Am 07.03.2011 um 11:13 schrieb Anders Ekberg:
>>
>>> One more nasty bug on Mac (latest SnowLeopard):
>>> The alt key modifier seems to be broken. As an example, alt+m m (which
>>> should give you an
Stephan Witt wrote:
> PS. Pavel, obviously I forgot to make this change more clear in the .dmg.
> It would be no real change to the code base if I add a README to the
> distribution media.
> Would it better to add another .dmg with this addition for RC1?
no. but i can add a sentence to announceme
On 2011-03-07 11.26, "Stephan Witt" wrote:
>Am 07.03.2011 um 11:13 schrieb Anders Ekberg:
>
>> One more nasty bug on Mac (latest SnowLeopard):
>> The alt key modifier seems to be broken. As an example, alt+m m (which
>> should give you an inline formula) give ¹m, alt+p gives you ¼ etc.
>
>Sorry
Am 07.03.2011 um 11:13 schrieb Anders Ekberg:
> One more nasty bug on Mac (latest SnowLeopard):
> The alt key modifier seems to be broken. As an example, alt+m m (which
> should give you an inline formula) give ¹m, alt+p gives you ¼ etc.
Sorry for the inconvenience... but this is (partly) intende
For the first step, we would need project ideas and mentors who could
supervise. I would put forward the following:
1.) Improved XHTML export and ePub support. (See other email for a more
thorough discussion.)
2.) ODF/DOC/DOCX import library (perhaps developed jointly with KOffice)
3.) UI Impr
One more nasty bug on Mac (latest SnowLeopard):
The alt key modifier seems to be broken. As an example, alt+m m (which
should give you an inline formula) give ¹m, alt+p gives you ¼ etc.
/Anders
On 2011-03-07 09.10, "Stephan Witt" wrote:
>Am 07.03.2011 um 01:06 schrieb Pavel Sanda:
>
>> Pavel Sa
Anders Ekberg wrote:
>
>
> On 2011-03-07 09.54, "Pavel Sanda" wrote:
>
> >Anders Ekberg wrote:
> >> - Open an existing document with a Preamble
> >> - Create a new document
> >> - Choose Document > Settings... and then LaTex Preamble in the new
> >>document
> >
> >now you close the dialog or le
On 2011-03-07 09.54, "Pavel Sanda" wrote:
>Anders Ekberg wrote:
>> - Open an existing document with a Preamble
>> - Create a new document
>> - Choose Document > Settings... and then LaTex Preamble in the new
>>document
>
>now you close the dialog or let it open?
Leave it open
>
>> - Switch to
Anders Ekberg wrote:
> - Open an existing document with a Preamble
> - Create a new document
> - Choose Document > Settings... and then LaTex Preamble in the new document
now you close the dialog or let it open?
> - Switch to the existing document and choose Document > Settings... and
> then LaTe
Thanks, it seems to work fine.
But I ran into a nasty bug:
- Open an existing document with a Preamble
- Create a new document
- Choose Document > Settings... and then LaTex Preamble in the new document
- Switch to the existing document and choose Document > Settings... and
then LaTex Preamble in
Am 07.03.2011 um 01:06 schrieb Pavel Sanda:
> Pavel Sanda wrote:
>> Pavel Sanda wrote:
>>> only doc or translations can go in.
>>
>> trunk is completely frozen now.
>
> trunk is opened for bug fixing again.
> tarballs are on usual place, i'll announce rc1 at monday night.
>
> give it a try.
It
20 matches
Mail list logo
