- the first patch bformats math's infoize messages (fixes bug #1908)
- the second one add tex2lyx support for all libertine font variants
OK for LyX 2.1.3?
regards Uwe
src/mathed/InsetMathBox.cpp| 6 +-
src/mathed/InsetMathColor.cpp | 6 +-
src/mathed/InsetMathDecoration.cp
On Wed, Nov 19, 2014 at 8:01 PM, Uwe Stöhr wrote:
> commit 5c9667d8b843777ac66a0bd4977c27e8a79f76b2
> Author: Uwe Stöhr
> Date: Thu Nov 20 02:01:05 2014 +0100
>
> tex2lyx: support for the libertine fonts
>
> - all libertine font variants are now supported
>
> @@ -727,14 +728,19 @@ void
On 11/19/2014 04:43 PM, Georg Baum wrote:
Hi,
while investigating http://www.lyx.org/trac/ticket/9336 I found out a
fundamental problem with our multithreaded export: The GNU libstdc++ gives
only a relatively weak thread-safety guarantee about std::basic string. It
is not completely thread-safe
Hi,
while investigating http://www.lyx.org/trac/ticket/9336 I found out a
fundamental problem with our multithreaded export: The GNU libstdc++ gives
only a relatively weak thread-safety guarantee about std::basic string. It
is not completely thread-safe in the POSIX sense. The reason for this l
Richard Heck wrote:
> You know what would be really cool? The ability to custom-define default
> macros in a module, including ones with arguments.
Yes. And I guess it would not be difficult to implement. If I find some time
I might at least extend lib/symbols to support macros with arguments, s
Jean-Marc Lasgouttes wrote:
> Le 18/11/2014 12:38, MAILLARD Serge a écrit :
>> Good morning,
>> Actually, my organization tells I may not install the new LyX version on
>> my machine because there is no official Debian package for it. Is there
>> a possibility for you to create such a package?
>
Stephan Witt wrote:
> Yes, it didn't work. I had to remove the const keyword to get it to
> compile. Yesterday I couldn't figure it out.
Yes, this is the standard way to catch exceptions (unless you work with
libraries that ignore the standards and define their own thing, like the
Microsoft Fou
