On Sun, Aug 27, 2017 at 03:23:42AM +0200, Pavel Sanda wrote:
> Scott Kostyshak wrote:
> > Public release of LyX version 2.3.0beta1
>
> Scott, did you put on lyx wiki the release steps you are using when releasing
> tarballs?
> (If not, can you share it there?)
I just updated the wiki with the
On Sun, Aug 27, 2017 at 3:53 PM, mn wrote:
> On 27.08.17 22:41, Guenter Milde wrote:
>
> >>> The UserGuide currently is a real trouble maker.
> >
> > Can you have a look at the used fonts in this document?
> >
> The fonts used are just the defaults as set by opening the guide
On 27.08.17 22:41, Guenter Milde wrote:
>>> The UserGuide currently is a real trouble maker.
>
> Can you have a look at the used fonts in this document?
>
The fonts used are just the defaults as set by opening the guide from
help menu.
I experimented with the fonts. LatinModern (the default)
On 2017-08-27, Joel Kulesza wrote:
> [-- Type: text/plain, Encoding: quoted-printable --]
> On Sat, Aug 26, 2017 at 12:04 PM, mn wrote:
>> The UserGuide currently is a real trouble maker.
Can you have a look at the used fonts in this document?
> I can confirm strange behavior
On Sat, Aug 26, 2017 at 12:04 PM, mn wrote:
> The UserGuide currently is a real trouble maker.
>
> This is likely not the fault of LyX or LaTeX.
>
> Nevertheless, this is confirmed to happen – not on all but – on the
> clear majority of macOS Sierra systems tested. The bug has to
On Sun, Aug 27, 2017 at 04:09:41PM +0200, Enrico Forestieri wrote:
>
> I think that it suffices using a QCoreApplication instead of QApplication.
No, I was wrong. A QGuiApplication is necessary for using QPixmap.
--
Enrico
On Sun, Aug 27, 2017 at 02:48:14PM +0200, Stephan Witt wrote:
> Am 27.08.2017 um 14:35 schrieb Stephan Witt :
> >
> > Thank you for your ideas… your hint regarding the change for #9778 was
> > useful too. I’m not 100% sure how it works now.
Before the fix for #9778, no converter
Am 27.08.2017 um 14:35 schrieb Stephan Witt :
>
> Am 27.08.2017 um 12:01 schrieb Enrico Forestieri :
>>
>> On Sat, Aug 26, 2017 at 08:14:57PM +0200, Stephan Witt wrote:
>>>
>>> ATM, I don’t have a solution for this problem. The inclusion of ImageMagick
>>> as
Am 27.08.2017 um 12:01 schrieb Enrico Forestieri :
>
> On Sat, Aug 26, 2017 at 08:14:57PM +0200, Stephan Witt wrote:
>>
>> ATM, I don’t have a solution for this problem. The inclusion of ImageMagick
>> as part of the LyX bundle doesn’t look attractive. Much work and not a good
>>
Jürgen Spitzmüller wrote:
> Am Sonntag, den 27.08.2017, 13:20 +0200 schrieb Pavel Sanda:
> > Why not. Do you have in mind anything else than just dumping the macro
> > definition from the module directly to tex output when showing changes in
> > output is enabled?
>
> No. It's probably trivial.
Am Sonntag, den 27.08.2017, 13:20 +0200 schrieb Pavel Sanda:
> Why not. Do you have in mind anything else than just dumping the
> macro definition
> from the module directly to tex output when showing changes in output
> is enabled?
No. It's probably trivial. But it's a file format change, and we
Jürgen Spitzmüller wrote:
> > I stumbled upon the change bars module we include in LyX now and find it
> > pretty bad UI that we do not include this option as part of normal menu for
> > change tracking and hide it somewhere in module listing -- many people will
> > miss that. Apparently this
On Sat, Aug 26, 2017 at 08:14:57PM +0200, Stephan Witt wrote:
>
> ATM, I don’t have a solution for this problem. The inclusion of ImageMagick
> as part of the LyX bundle doesn’t look attractive. Much work and not a good
> system design. And definitively not possible for the LyX 2.3.0 release.
I
Am Sonntag, den 27.08.2017, 03:48 +0200 schrieb Pavel Sanda:
> Hi,
>
> I stumbled upon the change bars module we include in LyX now and find
> it pretty
> bad UI that we do not include this option as part of normal menu for
> change
> tracking and hide it somewhere in module listing -- many
14 matches
Mail list logo