Discussion:
Font spacing issue again
(too old to reply)
BH
2011-01-06 15:13:36 UTC
Permalink
This is a follow-up to problems we've had with on-screen display of
fonts, where the spacing between words and cursor position was not
calculated correctly due to ligatures, swooshes, or other font
features. My guess is that the fix to that problem was too general,
creating problems with monospaced fonts.

In a LyX document, insert ERT, and enter a string of (for example)
"m"s, filling up most of the line. For me with all mono-spaced fonts
I've tried, the cursor position gradually moves too far to the right,
leaving a gap between it and the last "m". Moving the cursor to the
left and typing inserts the new characters in an unexpected position.

This seems to work for all characters *except* lower-case "f", which
results in the cursor being properly positioned. Thus, position the
cursor at the end of the long string of "m"s (so that there is the gap
between the cursor and the last "m"). Now type two "f"s: the first one
appears immediately to the right of the last "m", with the cursor
still placed too far to the right, but the second one appears after a
gap and immediately to the left of the cursor.

Let me know if you want screenshots.

BH
BH
2011-01-06 18:21:33 UTC
Permalink
Post by BH
This is a follow-up to problems we've had with on-screen display of
fonts, where the spacing between words and cursor position was not
calculated correctly due to ligatures, swooshes, or other font
features. My guess is that the fix to that problem was too general,
creating problems with monospaced fonts.
You refer to LyX 2.0?
Yes -- current svn with Qt-4.7.1 (Carbon, 32 bit). I'm on OS X 10.6.5,
using the 10.5 SDK.

...
Post by BH
Let me know if you want screenshots.
I believe you!
But now the bad news: I don't have it here.
I tried Courier and Courier New for typewriter and it didn't "work".
I've tested it with Qt-4.6.2 and Qt-4-7.1... (32bit builds)
Hmm. I've tried with Courier, Courier New, and Monaco, all of which
exhibit the problem with Qt-4.7.1. When I recompile with Qt-4.4.2
(self-compiled), I don't see the problem.

BH
Stephan Witt
2011-01-06 20:55:27 UTC
Permalink
Post by BH
Yes -- current svn with Qt-4.7.1 (Carbon, 32 bit). I'm on OS X 10.6.5,
using the 10.5 SDK.
OS X 10.6.5, Qt-4.7.1 (Carbon, 32 bit), 10.5 SDK.
It's all the same here.
Post by BH
I tried Courier and Courier New for typewriter and it didn't "work".
I've tested it with Qt-4.6.2 and Qt-4-7.1... (32bit builds)
Hmm. I've tried with Courier, Courier New, and Monaco, all of which
exhibit the problem with Qt-4.7.1. When I recompile with Qt-4.4.2
(self-compiled), I don't see the problem.
Qt-4.7.1 is self compiled too? Or the download from Nokia?

Stephan
BH
2011-01-06 21:02:46 UTC
Permalink
Post by Stephan Witt
Post by BH
Yes -- current svn with Qt-4.7.1 (Carbon, 32 bit). I'm on OS X 10.6.5,
using the 10.5 SDK.
OS X 10.6.5, Qt-4.7.1 (Carbon, 32 bit), 10.5 SDK.
It's all the same here.
Post by BH
I tried Courier and Courier New for typewriter and it didn't "work".
I've tested it with Qt-4.6.2 and Qt-4-7.1... (32bit builds)
Hmm. I've tried with Courier, Courier New, and Monaco, all of which
exhibit the problem with Qt-4.7.1. When I recompile with Qt-4.4.2
(self-compiled), I don't see the problem.
Qt-4.7.1 is self compiled too? Or the download from Nokia?
The downloaded version.

BH
Peter Kümmel
2011-01-06 21:18:15 UTC
Permalink
Post by BH
Post by Stephan Witt
Post by BH
Yes -- current svn with Qt-4.7.1 (Carbon, 32 bit). I'm on OS X 10.6.5,
using the 10.5 SDK.
OS X 10.6.5, Qt-4.7.1 (Carbon, 32 bit), 10.5 SDK.
It's all the same here.
Post by BH
I tried Courier and Courier New for typewriter and it didn't "work".
I've tested it with Qt-4.6.2 and Qt-4-7.1... (32bit builds)
Hmm. I've tried with Courier, Courier New, and Monaco, all of which
exhibit the problem with Qt-4.7.1. When I recompile with Qt-4.4.2
(self-compiled), I don't see the problem.
Qt-4.7.1 is self compiled too? Or the download from Nokia?
The downloaded version.
The new version uses Cocoa by default and 4.4 was Carbon.
I'm no Mac expert, but this could be enough differences
to show up new bugs.

Peter
Peter Kümmel
2011-01-06 21:26:38 UTC
Permalink
Post by Peter Kümmel
Post by BH
Post by Stephan Witt
Post by BH
Yes -- current svn with Qt-4.7.1 (Carbon, 32 bit). I'm on OS X 10.6.5,
using the 10.5 SDK.
OS X 10.6.5, Qt-4.7.1 (Carbon, 32 bit), 10.5 SDK.
It's all the same here.
Post by BH
I tried Courier and Courier New for typewriter and it didn't "work".
I've tested it with Qt-4.6.2 and Qt-4-7.1... (32bit builds)
Hmm. I've tried with Courier, Courier New, and Monaco, all of which
exhibit the problem with Qt-4.7.1. When I recompile with Qt-4.4.2
(self-compiled), I don't see the problem.
Qt-4.7.1 is self compiled too? Or the download from Nokia?
The downloaded version.
The new version uses Cocoa by default and 4.4 was Carbon.
I'm no Mac expert, but this could be enough differences
to show up new bugs.
Sorry, should read the whole thread, you use Carbon. But
what' the reason not to use the Cocoa download?
Backward-compatibility? As I understand it for the Trolls
Carbon is legacy.

Peter
Stephan Witt
2011-01-06 21:55:54 UTC
Permalink
Post by Peter Kümmel
Post by Peter Kümmel
Post by BH
Post by Stephan Witt
Post by BH
Yes -- current svn with Qt-4.7.1 (Carbon, 32 bit). I'm on OS X 10.6.5,
using the 10.5 SDK.
OS X 10.6.5, Qt-4.7.1 (Carbon, 32 bit), 10.5 SDK.
It's all the same here.
Post by BH
I tried Courier and Courier New for typewriter and it didn't "work".
I've tested it with Qt-4.6.2 and Qt-4-7.1... (32bit builds)
Hmm. I've tried with Courier, Courier New, and Monaco, all of which
exhibit the problem with Qt-4.7.1. When I recompile with Qt-4.4.2
(self-compiled), I don't see the problem.
Qt-4.7.1 is self compiled too? Or the download from Nokia?
The downloaded version.
Than the self compiled libs seem to work - I'll try the downloaded 4.7.1
too and test it...
Post by Peter Kümmel
Post by Peter Kümmel
The new version uses Cocoa by default and 4.4 was Carbon.
I'm no Mac expert, but this could be enough differences
to show up new bugs.
Sorry, should read the whole thread, you use Carbon. But
what' the reason not to use the Cocoa download?
Backward-compatibility? As I understand it for the Trolls
Carbon is legacy.
I tried it some time ago once and I couldn't get it to work out of the box.
I'll retry it - as I'm very interested in using the Cocoa version too.
As I cannot remember the details anymore I'll start again and report the result.

Stephan
Stephan Witt
2011-01-07 12:47:51 UTC
Permalink
Post by Stephan Witt
Post by Peter Kümmel
Post by Peter Kümmel
Post by BH
Post by Stephan Witt
Post by BH
Yes -- current svn with Qt-4.7.1 (Carbon, 32 bit). I'm on OS X 10.6.5,
using the 10.5 SDK.
OS X 10.6.5, Qt-4.7.1 (Carbon, 32 bit), 10.5 SDK.
It's all the same here.
I have to correct my statement: it's Qt-4.6.2(resp. 3) Carbon, 32bit!
Post by Stephan Witt
Post by Peter Kümmel
Post by Peter Kümmel
Post by BH
Post by Stephan Witt
Post by BH
I tried Courier and Courier New for typewriter and it didn't "work".
I've tested it with Qt-4.6.2 and Qt-4-7.1... (32bit builds)
Hmm. I've tried with Courier, Courier New, and Monaco, all of which
exhibit the problem with Qt-4.7.1. When I recompile with Qt-4.4.2
(self-compiled), I don't see the problem.
Qt-4.7.1 is self compiled too? Or the download from Nokia?
The downloaded version.
Than the self compiled libs seem to work - I'll try the downloaded 4.7.1
too and test it...
Post by Peter Kümmel
Post by Peter Kümmel
The new version uses Cocoa by default and 4.4 was Carbon.
I'm no Mac expert, but this could be enough differences
to show up new bugs.
That's indeed a difference. I missed the change in defaults :(
Blush.
Post by Stephan Witt
Post by Peter Kümmel
Sorry, should read the whole thread, you use Carbon. But
what' the reason not to use the Cocoa download?
As I started using 4.7.1 I went the source code route.
The reason was to be able to build LyX with OS X 10.4 support.
Post by Stephan Witt
Post by Peter Kümmel
Backward-compatibility? As I understand it for the Trolls
Carbon is legacy.
I tried it some time ago once and I couldn't get it to work out of the box.
I'll retry it - as I'm very interested in using the Cocoa version too.
As I cannot remember the details anymore I'll start again and report the result.
Obviously I did something else in the past as I got the problems.
Perhaps it was when trying Cocoa with 4.6 when I failed to build Qt for LyX.

Since I'm using the LyX-Mac-binary-release.sh for build and bundle Qt and LyX
I only had to change the paths to build with 4.7.1 instead of 4.6.3.
So I've not seen the change in default -cocoa/-carbon switches.
Compliments to Qt-people for the smooth switch, really!

Until beta2 I used 4.6.3 to bundle with LyX.

If I test with 4.7.1 I have the problems, Bennett reported.
Sorry for my confusion! It looks like a problem we have with Qt 4.7!

It doesn't matter if I try it with the Carbon or Cocoa based build.
I'm a little bit short on disk space... so I need some time to verify
all these variants. Next I'll do is to recheck the 4.6.3 Qt-Library.

When using the Cocoa build I noticed LyX is linked with Carbon anyway.
This I have to sort out to finally make a statement regarding Cocoa.

Stephan

Stephan Witt
2011-01-06 17:03:35 UTC
Permalink
Post by BH
This is a follow-up to problems we've had with on-screen display of
fonts, where the spacing between words and cursor position was not
calculated correctly due to ligatures, swooshes, or other font
features. My guess is that the fix to that problem was too general,
creating problems with monospaced fonts.
You refer to LyX 2.0?

The work-around is to force a "work break" after a "f". The word
effectively gets painted in three parts "ef", "f" and "ectively".
Nothing else is changed. That's why it may very well affect other
characters with "kerning" when used in combination.
Post by BH
In a LyX document, insert ERT, and enter a string of (for example)
"m"s, filling up most of the line. For me with all mono-spaced fonts
I've tried, the cursor position gradually moves too far to the right,
leaving a gap between it and the last "m". Moving the cursor to the
left and typing inserts the new characters in an unexpected position.
It seems "mm" is shorter on screen then "m" and "m".
Post by BH
This seems to work for all characters *except* lower-case "f", which
results in the cursor being properly positioned. Thus, position the
cursor at the end of the long string of "m"s (so that there is the gap
between the cursor and the last "m"). Now type two "f"s: the first one
appears immediately to the right of the last "m", with the cursor
still placed too far to the right, but the second one appears after a
gap and immediately to the left of the cursor.
Let me know if you want screenshots.
I believe you!

But now the bad news: I don't have it here.

I tried Courier and Courier New for typewriter and it didn't "work".
I've tested it with Qt-4.6.2 and Qt-4-7.1... (32bit builds)

Stephan
Loading...