Alan knows well. He said:
The old X.org was an industry consortium, the new X.org Foundation is a non-profit open source group much like the GNOME Foundation. The difference is membership will no longer be restricted to companies who pay thousands of dollars per year and the honorary membership of the XFree86 Project, but will be open, allowing the community a much greater say in the ongoing development of the X Window System.
Alan.Coopersmith@Sun.COM said on the XFree86.org forum list:
X.org is not really "forking" - it's simply that as has been done several times in the past since XFree86 originally forked from X.org, X.org was bringing the latest XFree86 changes back into the X.org tree. This was being done on a new public CVS tree on freedesktop.org that was pulling over automatically from the XFree86 CVS. The "fork" was simply that the cron jobs doing so were stopped when the license changed until X.org has a chance to decide whether or not code under the new license should be
incorporated. I'm sure the XFree86 Board expected everyone using their code to stop and take a look at the new license before pulling in code using it - if nothing else, to understand what the new requirements were and determine if they were meeting them or wanted to meet them.
Firebird is a relational database offering many ANSI SQL-92 features that runs on Linux, Windows, and a variety of Unix platforms.
It would be nice if Firebird can connect to ooo.
What's wrong with the state of desktop GNU/Linux?
What's wrong with being traced back to the underlying window system, X.
Can Y be a modern windowing system?
The Y design has the following features, Mark Thomas says on http://www.y-windows.org/about.html
Modularity (plug-in style: dynamically unloadable and reloadable)
Consistency and Themeability
Support for hardware acceleration
Better internationalisation, localisation, and accessiblity:
In-server widgets means there can be exactly one current language, one complex input method system for languages that require them, and one set of accessibility features.
This sounds good, but "one complex input method"??
The Y is not yet usable on a day-to-day basis.
Unwary Experienced Builder. Sander gave me this name. I love it.
Unwary: yes, exactly.
Experienced: I build ooo a lot on Linux but I know some who do more.
Builder: I am a serial builder, not a parallel builder.
Anyway, I am happy now to be one of ooo bloggers.
At firstname.lastname@example.org, I see several European/American, who can't read Japanese, often ask the list how to use Japanese with ooo or how to input Japanese.
It is not a problem with ooo, but it is a problem with their platform, language environment, input method and installed fonts.
CJK solutions here:
If you get these requirements, you can input any language with ooo since ooo has got spadmin.
Now do they know how to type Japanese?
I didn't know how to type Chinese and Korean.
I have just learnt how to type "red" in Chinese and Korean from:
Four Language Engines (LE) are available:
iiimf-le-inpinyin for Simplified Chinese (zh_CN.UTF-8)
iiimf-le-xcin for Traditional Chinese (zh_TW.UTF-8)
iiimf-le-canna for Japanese (ja_JP.UTF-8)
iiimf-le-hangul for Korean (ko_KR.UTF-8)
Only GNOME (GTK) applications provide direct support for IIIMF.
There is a known issue which we are looking to fix hopefully soon.
"im-sdk cannaLE editting after commit broken"
Intranet/Internet Input Method Framework (IIIMF) is the next generation Input Method Framework set to replace the legacy X Window System Input Method (XIM).
IIIMF seems to work with gedit only on Fedra Core now.
It doesn't work with ooo yet.