Domain: li18nux.org
Stories and comments across the archive that link to li18nux.org.
Comments · 6
-
Just a note for developers...
There's a new input method system called Internet/Intranet Input Method Framework (IIIMF). It was released to the free software community by Sun just over 2 years ago. Currently it's hosted at Li18nux.
Among its advantages over the old X Input Method (XIM) system are:
- Not tied to X Window anymore. It should be possible to write an IIIMF client for a console app. In fact there's a sample client implementation for Emacs.
- Not tied to the old locale/encoding model; everything is in Unicode. For example it is possible to enter Chinese in en_US locale.
- Being Sun, IIIMF uses a client/server model. Theoretically an IIIMF client can access an IIIMF server on a Beowulf cluster...
Disclaimer: I am a voting member on the Li18nux Steering Commitee, and I'm also working on a commercial Chinese IIIMF input method for my employer.
-
Why incorporate and what it all meansSo why incorporate?
Up until this point, the LSB and Li18nux were operating as unincorporated organizations, which is bad for a number of reasons: legal liability, the inability to accept and distribute funding for development and other expenses, no entity to hold copyrights for the group, anti-trust issues (you need to be careful when you have competitors meeting in the same room), and more. We needed to incorporate (as a non-profit, of course).
As far as the Li18nux and the LSB are concerned, they will more or less continue as before, although we'll be able to put more resources on each project so things will speed up. We'll be working closer together and referring to each other's specification, but the LSB and Li18nux specifications will probably be separate standards for some time.
Why incorporate together? It makes sense and it's less overhead. We didn't need separate legal entities for these open-source standardization efforts.
Some LSB specifics:
Will the LSB be multi-architecture? Yes, although x86 is the main target, we are trying to draft the specification to apply for multiple architectures. Recompile the sample implementation and test suite and everything should work fine for other architectures. (The reality is that most third party software is released for Linux on x86.)
Another thing: the whole "LSB stifles development" argument is very misleading. You can ship development libraries along with stable LSB versions if you want both environments. (It will be up to the distribution and system administrators.) Kernel developers like Alan Cox, Ted Ts'o, and H. Peter Anvin have been participating in the LSB for a long time - I don't think that would happen if we were going to stifle forward progress.
Will having more members slow us down? Quite the opposite, actually. The main thing slowing us down is the amount of work to be done, not slow decision-making or the lack of consensus.
Finally, recall that the word "base" is part of the Linux Standard Base name. Distributions will still have the same amount of room to add value, innovate, and distinguish themselves. We like the fact that there are different Linux distributions, each with something unique to offer. We just disagree about requiring commercial and non-commercial providers of software to port and test their software for five or ten different Linux distributions.
-
Internationalization and localizationMandrake has been quite proactive is adding any available support for as many languages as possible. They have a localization page dedicated to it. They aren't the only organization working on it, but they are trying to make it widely available in an easily usable form. The Translation Project and Linux International which has sponsored mailing lists for it, have probably been doing it as actively as anyone else out there. There are other projects working on it as well:
- Linux Internationalisation Initiative
- Linux i18n Project, which is at least loosely affiliated with Mandrake since one of their employees is the contact for the project
- Free Mulitilingual Platforms
- Gnome and KDE have also both been actively pursuing internationalization
-
Linux Internationalisation Initiative
I don't know what's their status right now,
but it's worth looking into it.
http://www.li18nux.org/ -
Linux internationalization/localization effortsAnd a lot of different countries would LOVE to have true internationalization and localization done, so just by changing a message catalog (or adding to it) an operating system or application could be localized for a particular culture.
Jon, thanks for mentioning this. I'm not surprised since Linux International is hosting the mailing lists for the Free Translation Project teams. I wanted to mention that there are several projects going to to try to achieve internationalization of Linux and free software in general. If I have left any out of this list, please speak up.
- The Free Translation Project, doing translation of the messages from free software into quite a few languages.
- The Linux I18N Project
- The Linux Internationalization Initiative
There are also pages for internationalization and localization of several projects and distributions (URLs welcome). -
Re:i18n == international?! Please!
In other words, I don't think i18n or L10N are well-established, but that's just me.
Well, for those doing any work at all in the field, those terms are very well established. Since the project is initially to coordinate all those working in the field to be unified on Linux, it seems like a very good choice of names. See their charter for why I have that impression.
For The Java stuff, try the Java documentation itself. http://java.sun.com/products/jdk/1.1/docs/guide/i
n tl/index.html