Georg Baum wrote:
What is better? This hack or the one which requires modifying the fonts? I
think we have to fix this problem to avoid a regression on OS X.
Forget this. I found and submitted a much better solution by extending the
already existing fallback mechanism.
Georg
Georg Baum wrote:
> What is better? This hack or the one which requires modifying the fonts? I
> think we have to fix this problem to avoid a regression on OS X.
Forget this. I found and submitted a much better solution by extending the
already existing fallback mechanism.
Georg
Benjamin Piwowarski wrote:
On the LyX-qt4/OSX build (OS X 10.9),
- maths symbols with codes 0x0009 and 0x00ad are not displayed.
- The first line is a b
Thanks, so we do not need to care for 169.
One question: why not switching to Stix for the symbols that cause a
problem and in 2.2
Benjamin Piwowarski wrote:
> On the LyX-qt4/OSX build (OS X 10.9),
>
> - maths symbols with codes 0x0009 and 0x00ad are not displayed.
> - The first line is a b
Thanks, so we do not need to care for 169.
> One question: why not switching to Stix for the symbols that cause a
> problem and in
2014-03-03 21:40 GMT+01:00 Georg Baum:
We have to distinguish between text and math here. For text qt is probably
right. For math we use a bad hack employing dangerous casts for symbol
fonts
(see the big comment at the beginning of GuiPainter::text()). This means
e.g. that \Omega is mapped
2014-03-05 11:57 GMT+01:00 Jürgen Spitzmüller:
2014-03-03 21:40 GMT+01:00 Georg Baum:
We have to distinguish between text and math here. For text qt is probably
right. For math we use a bad hack employing dangerous casts for symbol
fonts
(see the big comment at the beginning of
Jürgen Spitzmüller wrote:
2014-03-05 11:57 GMT+01:00 Jürgen Spitzmüller:
Done.
Thanks.
Am I right that the real (TM) solution would be to use proper
unicode-encoded fonts for math (i.e, STIX)? Then we could drop all code
point loopings.
I'd say so, unless somebody really wants the
On the LyX-qt4/OSX build (OS X 10.9),
- maths symbols with codes 0x0009 and 0x00ad are not displayed.
- The first line is a b
One question: why not switching to Stix for the symbols that cause a problem
and in 2.2 switch all the other symbols? Even if this not look perfect, at
least it is a
2014-03-03 21:40 GMT+01:00 Georg Baum:
> We have to distinguish between text and math here. For text qt is probably
> right. For math we use a bad hack employing dangerous casts for symbol
> fonts
> (see the big comment at the beginning of GuiPainter::text()). This means
> e.g. that \Omega is
2014-03-05 11:57 GMT+01:00 Jürgen Spitzmüller:
> 2014-03-03 21:40 GMT+01:00 Georg Baum:
>
> We have to distinguish between text and math here. For text qt is probably
>> right. For math we use a bad hack employing dangerous casts for symbol
>> fonts
>> (see the big comment at the beginning of
Jürgen Spitzmüller wrote:
> 2014-03-05 11:57 GMT+01:00 Jürgen Spitzmüller:
>
>>
> Done.
Thanks.
>> Am I right that the real (TM) solution would be to use proper
>> unicode-encoded fonts for math (i.e, STIX)? Then we could drop all code
>> point loopings.
I'd say so, unless somebody really
On the LyX-qt4/OSX build (OS X 10.9),
- maths symbols with codes 0x0009 and 0x00ad are not displayed.
- The first line is a b
One question: why not switching to Stix for the symbols that cause a problem
and in 2.2 switch all the other symbols? Even if this not look perfect, at
least it is a
03/03/2014 10:46, Juergen Spitzmueller:
diff --git a/src/frontends/qt4/GuiPainter.cpp b/src/frontends/qt4/GuiPainter.cpp
index ee0f65a..a1b0de0 100644
--- a/src/frontends/qt4/GuiPainter.cpp
+++ b/src/frontends/qt4/GuiPainter.cpp
@@ -352,6 +352,10 @@ int GuiPainter::text(int x, int y, docstring
Am Montag 03 März 2014, 11:35:04 schrieb Jean-Marc Lasgouttes:
Since force_paint_single_char will eventually go away, we'll probably
have to remove this code. OTOH, is it really the spirit of LyX to hide
this soft-hyphen? At least if we do so, we should mark it as a line
separator
Jean-Marc Lasgouttes wrote:
03/03/2014 10:46, Juergen Spitzmueller:
diff --git a/src/frontends/qt4/GuiPainter.cpp
b/src/frontends/qt4/GuiPainter.cpp index ee0f65a..a1b0de0 100644
--- a/src/frontends/qt4/GuiPainter.cpp
+++ b/src/frontends/qt4/GuiPainter.cpp
@@ -352,6 +352,10 @@ int
03/03/2014 10:46, Juergen Spitzmueller:
diff --git a/src/frontends/qt4/GuiPainter.cpp b/src/frontends/qt4/GuiPainter.cpp
index ee0f65a..a1b0de0 100644
--- a/src/frontends/qt4/GuiPainter.cpp
+++ b/src/frontends/qt4/GuiPainter.cpp
@@ -352,6 +352,10 @@ int GuiPainter::text(int x, int y, docstring
Am Montag 03 März 2014, 11:35:04 schrieb Jean-Marc Lasgouttes:
> Since force_paint_single_char will eventually go away, we'll probably
> have to remove this code. OTOH, is it really the spirit of LyX to hide
> this soft-hyphen? At least if we do so, we should mark it as a line
> separator
Jean-Marc Lasgouttes wrote:
> 03/03/2014 10:46, Juergen Spitzmueller:
>> diff --git a/src/frontends/qt4/GuiPainter.cpp
>> b/src/frontends/qt4/GuiPainter.cpp index ee0f65a..a1b0de0 100644
>> --- a/src/frontends/qt4/GuiPainter.cpp
>> +++ b/src/frontends/qt4/GuiPainter.cpp
>> @@ -352,6 +352,10 @@
18 matches
Mail list logo
