Hi Coalan,
I'm using metacity. I agree that this behavior is not something that OOo
code should have to deal with, but I can't tell users to go fix their
window managers. Some users don't even know what a terminal is, but they
still want to use OOo on Linux. So I need a solution that will work with
users. Until now, I've eliminated the use of the formatting characters
from all of OOo in Linux, but that causes bidi problems elsewhere. So
I'd like to know how to catch the title strings before metacity or some
other window manager messes them up.
Alan
Caolan McNamara wrote:
On Wed, 2006-11-15 at 10:46 +0200, Alan Yaniger wrote:
Hi list-members,
I work on an RTL version of OOo, and I rely heavily on Unicode
formatting characters to make Bidi text look the way I want. However,
this causes a problem in Linux. The text in OOo looks fine, but text in
window titles is not displayed by OOo, but by a window manager.
Sometimes the window manager does not know how to handle these
formatting chars, and displays them as ugly boxes with hex numbers in
them. I would like to strip the formatting chars from such strings
before they are passed to the window manager. Where in the code would I
do this?
What window manager is this, something like metacity should be using
pango and fontconfig and be able to render (in theory at least) CTL
text. It might be a better long term strategy to fix the window manager
in this case.
C.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
