Am Mittwoch, den 28.12.2016, 22:46 +0100 schrieb Jean-Marc Lasgouttes:
> commit eeb6e8333c5d4207a22a23f09e71b8334bdf7532
> Author: Jean-Marc Lasgouttes
> Date: Wed Dec 28 22:44:40 2016 +0100
>
> Fixup c49cd699: QString::toStdString is not always available
>
> This method requires S
Le 27/12/2016 à 23:11, Scott Kostyshak a écrit :
On Tue, May 31, 2016 at 01:15:38AM +0200, Guillaume Munch wrote:
commit 1cc14a31ca8320d881b674f93c34a09cf1666cca
Author: Guillaume Munch
Date: Mon May 30 21:42:08 2016 +0100
TocWidget: fix an erroneous collapse and optimise updates based o
Am Dienstag, den 25.10.2016, 23:52 +0200 schrieb Uwe Stöhr:
> Am 25.10.2016 um 02:10 schrieb Joel Kulesza:
>
> > I hereby grant the right to publish my work for LyX under the
> > license GPL
> > version 2 or later.
>
> Many thanks Joel.
>
> As soon as your first patch goes in for LyX we will add
Am Mittwoch, den 28.12.2016, 11:41 + schrieb Guenter Milde:
> I see. But as the tests should correspond to "normal" LyX behaviour,
> we
> should rather
>
> a) fix the document: we can set a custom non-tex font that contains
> the
> missing characters. This way a user just clicking "use non-
On 2016-12-28, Jürgen Spitzmüller wrote:
> [-- Type: text/plain, Encoding: quoted-printable --]
> Am Mittwoch, den 28.12.2016, 05:20 -0500 schrieb Scott Kostyshak:
>> > Note, though, that the missing glyphs message is a warning, not an
>> > error. We treat it as an error in the GUI, for good reas
On Wed, Dec 28, 2016 at 11:25:51AM +0100, Jürgen Spitzmüller wrote:
> Am Mittwoch, den 28.12.2016, 05:20 -0500 schrieb Scott Kostyshak:
> > > Note, though, that the missing glyphs message is a warning, not an
> > > error. We treat it as an error in the GUI, for good reasons (since
> > it
> > > seve
Am Mittwoch, den 28.12.2016, 05:20 -0500 schrieb Scott Kostyshak:
> > Note, though, that the missing glyphs message is a warning, not an
> > error. We treat it as an error in the GUI, for good reasons (since
> it
> > severely can impact the output), but it does not stop LaTeX from
> > processing.
>
On Wed, Dec 28, 2016 at 11:13:59AM +0100, Jürgen Spitzmüller wrote:
> Am Mittwoch, den 28.12.2016, 04:27 -0500 schrieb Scott Kostyshak:
> > I know nothing about this so I'll go along with whatever others
> > decide.
> > Günter might have an opinion.
> >
> > If we do implement the above we might wa
Am Mittwoch, den 28.12.2016, 04:27 -0500 schrieb Scott Kostyshak:
> I know nothing about this so I'll go along with whatever others
> decide.
> Günter might have an opinion.
>
> If we do implement the above we might want a general solution for
> ignoring other errors. I think there might be an enh
On Wed, Dec 28, 2016 at 10:38:02AM +0100, Jürgen Spitzmüller wrote:
> Probably not. But there are free alternatives that might suffice:
> https://en.wikipedia.org/wiki/Open-source_Unicode_typefaces
OK thanks.
Scott
signature.asc
Description: PGP signature
Am Mittwoch, den 28.12.2016, 04:09 -0500 schrieb Scott Kostyshak:
> > Note that the
> > CJK quotation marks used in sec. 3.9.3.2 are not covered in some
> fonts.
> > You will probably need a rather comprehensive font (such as Arial
> > Unicode MS).
>
> I don't have this font. Is it free?
Probably
On Wed, Dec 28, 2016 at 10:11:16AM +0100, Jürgen Spitzmüller wrote:
> A more general and probably generally useful solution is to add a
> command line option that makes LyX (again) proceed despite the missing
> glyphs warning (and just report the warning). Then the tests could use
> this option.
Am Mittwoch, den 28.12.2016, 09:58 +0100 schrieb Jürgen Spitzmüller:
> For the sake of the tests, we could just add something like the
> following to the preamble that intentionally ignores these missing
> chars:
>
> \AtBeginDocument{%
> \usepackage{newunicodechar}
> \newcommand\lyxbypasschar[2]{%
On Wed, Dec 28, 2016 at 09:58:08AM +0100, Jürgen Spitzmüller wrote:
> However, I am reluctant to include it in the UG's preamble just for the
> sake of making the tests happy.
I agree.
Scott
signature.asc
Description: PGP signature
On Wed, Dec 28, 2016 at 09:07:45AM +0100, Jürgen Spitzmüller wrote:
> Am Dienstag, den 27.12.2016, 16:02 -0500 schrieb Scott Kostyshak:
> > The following tests on current master are failing:
> >
> > export/doc/UserGuide_dvi3_systemF (Failed)
> > export/doc/UserGuide_pdf4_systemF (Failed)
> >
Am Mittwoch, den 28.12.2016, 09:07 +0100 schrieb Jürgen Spitzmüller:
> Am Dienstag, den 27.12.2016, 16:02 -0500 schrieb Scott Kostyshak:
> > The following tests on current master are failing:
> >
> > export/doc/UserGuide_dvi3_systemF (Failed)
> > export/doc/UserGuide_pdf4_systemF (Failed)
> >
Am Dienstag, den 27.12.2016, 16:02 -0500 schrieb Scott Kostyshak:
> The following tests on current master are failing:
>
> export/doc/UserGuide_dvi3_systemF (Failed)
> export/doc/UserGuide_pdf4_systemF (Failed)
> export/doc/UserGuide_pdf5_systemF (Failed)
Does "systemF" mean non-TeX fonts?
17 matches
Mail list logo
