On Nov 8, 2005, at 11:52 AM, Angus Leeming wrote:
You have a strange definition of ``for free'', William. There are 295
files in the Qt frontend totalling some 27,000 lines of code. And
that's neglecting the .ui files that define the dialog structure.
Yes, but all those lines and the QT front-end don't get one the same
sort of user-experience and integration which ``just happens'' for
NeXT/OPEN/GNUstep and Mac OS X.
For those interested in such stats, the whole LyX source tree
(neglecting non-Qt frontend code) comprises 970 files and 170,000
lines of code. The thing is *big* and doesn't need to get any bigger.
I thought that the whole point to GUI-Independence was that it would be
possible to plug-in other front-ends w/o negatively impacting the
back-end code?
In particular, it'd jump-start native UTF-8 support.
<shrug>
Most modern toolkits have unicode support. So what? The Qt frontend
has native unicode support and works today.
</shrug>
Not on Mac OS X in any way I can fathom.
The Edit menu in 1.40 pre2 doesn't have a ``Special characters'' entry,
nor is there any way to choose an input method AFAICT. I just tried
switching to the Korean keyboard and it totally disabled typing in.
Maybe this works in Linux, but I haven't had that installed since the
last time I installed mklinux on my wife's PowerMac at home for a
contract job.
Swiching the LyX internals over to unicode is the "big plan" for a 1.5
release. The fun will come in getting unicode to fit seemlessly with
LaTeX. You're something of a LaTeX expert, no? I'm sure you could
point out some of the problems. (To the lyx-devel list please.)
I'll try to resubscribe and see if I can help out. Short version is
it'd be ideal if there were a cross-platform version of XeTeX
(http://scripts.sil.org/xetex) available now to make use of....
Thanks!
William
--
William Adams, publishing specialist
voice - 717-731-6707 | Fax - 717-731-6708
www.atlis.com
