Subject: Win32 BIDI build
From: Kenneth J.Davis (jeremyd@computer.org)
Date: Wed Jan 09 2002 - 16:04:57 CST
Hello,
I have some questions about the Win32 BIDI build.
In ev_Toolbar_Labels.cpp
EV_Toolbar_Label::EV_Toolbar_Label(...)
within #ifdef BIDI_ENABLED section there is the following chunk of code
"
#if 1
// this has been crashing with en-US (but not en-GB), due to some
// weird memory managment in the fribidi library; so I defined
// USE_SIMPLE_MALLOC for it, which solved the problem
fribidi_log2vis ( /* input */
fbdStr,
iStrLen,
&fbdDomDir,
/* output */
fbdStr2,
NULL,
NULL,
NULL);
#endif
"
There still appears to be some issues with it, as I am now experiencing
the crashing (on startup). However it requires certain conditions,
I am using WinXP-RC2 (yeah yeah, I'm updating to plain XP sometime in
the next 9 days I think it is :-) and with the BIDI (non DEBUG) build
it dies, with Win 95b it starts fine. Also if you compile with
debugging information (either by enabling DEBUG build or by editing
makefile for nonDEBUG build to include debug information) it starts
fine. This was a real pain to track to here (but once I found this
comment I realized someone else had already seen this) as it also
does not crash when ran under a debugger (with or without debug info).
And in fact changing this to #ifdef 0 does allow Abiword BIDI build to
start for me.
What exactly does this do (as needed by AbiWord)?
The fribidi docs are less than helpful,
// fribidi_log2vis() calls the function_analyse_string() and then
// does reordering and fills in the output strings.
How uptodate is the fribidi library in cvs? I know at one point
(long while ago) it seemed a bit old comparatively, but appears
to have been updated since I last looked (at least the glaring
bug I remembered doesn't seem to be in Abi's cvs version anymore).
And because I don't feel like duplicating work, I figured I'd
ask now (I intend to search the mailing list & reread the docs
with Abi, but haven't had a chance yet), is anyone else aware that
some strings (titlebar/menus) are displayed wrong in the BiDi build,
[bug 2535] but are displayed fine in the nonbidi build. Specifically,
I'm asking is anyone else working on this, noticed this, or is it a
known issue that a fix is being delayed for some other reason?
Thanks. Now that I can run BiDi enabled AbiWord again (see above)
I am planning on looking into this in the next day or two, but if
there is no point then maybe I'll see if there are any other bugs
I can work on.
OT: David Chart's mail about CREDITS.TXT reminded me of something
I've been curious of for a while. The bottom of that file says
"To get your name added to this list, see:
http://www.abisource.com
abiword-dev@abisource.com"
but where exactly on www.abisource.com does it mention this
information? And what constitutes deserving of mentioning in
this file? Just idle curiousity, but maybe one day I'll have
enough free time to really work on AbiWord and it would be nice
to know then.
Thank you,
Jeremy Davis
jeremyd@computer.org
This archive was generated by hypermail 2b25 : Wed Jan 09 2002 - 16:03:53 CST