I18n

From GNUstepWiki
Revision as of 08:06, 5 September 2005 by Cbv (talk | contribs) (DeSPAM)
Jump to navigation Jump to search

I'm trying to form a gnustep-i18n team and list all relevant subjects. If you are experienced in this field, please help.

Input

  • NSTextInput protocol
  • NSInputManager

Current Status

  • Currently we use XIM. It is only available on systems that use the X11 backends.

Related Information

  • X11 Input Method (XIM) system (old documentation)
  • Internet/Intranet Input Method Framework (IIIMF) is a new input management system from the same people who brought you XIM (project information)
  • UIM is an embeddable C library providing input methods (project page)
  • kinput2 is a Japanese input server for XIM (homepage)
  • GNU Emacs has long had extensive input support in its LEIM library. (See info docs within emacs if you have it on your system.) On the pro side it's GPL'd already and more complete than other implementations; on the con side it's mostly in elisp and also may be built around an odd encoding ("Emacs-MULE"), except possibly in the unicode-2 branch.
  • http://www.freedesktop.org/Software/uim is obsolte. See http://uim.freedesktop.org/wiki/
  • wmuimis a dockapp and can be instead of uim-helper-toolbar-gtk
  • MacUIM is written in Cocoa.
  • SCIM (Smart Common Input Method) is a one of major input methods.

Both UIM and SCIM support more Japanese engines (e.g. Anthy, PRIME...)than kinput2 and iiimf.

Comments

  • Many input systems, eg. IIIMF, kinput2 have their own XIM bridges. Do we have those pop-up helpers with XIM yet?


Output

  • vertical text layout
  • bidi text layout
  • opentype support
  • NSTextView
  • Word hyphenation
  • Word segmentation
  • font substitution

Current Status

  • Gnustep currently doesn't support font substitution. but there is a patch available.

Related Information

Comments

  • what output method(s) is used? How? Why?


Writing aids and processing mechanisms

  • Spell-checking NSSpellChecker

Current Status

  • The spellchecker uses libaspell for its backend
    • aspell has dictionaries for at least these languages - af, br, ca, cs, cy, da, de, el, en, eo, es, fo, fr, ga, he, hr, is, it, nl, no, pl, pt, ro, ru, sk, sl, sv, uk (list taken from gentoo portage)
    • some languages are unsupported by aspell.
    • In the case where the currently selected NSLanguage doesn't have a dictionary available, an error dialog will show, telling you that the dictionary isn't available. It won't allow you to spell check with another dictionary until you manually open the spell check panel, and select a different dictionary. I mention this becuase its easy to get the impression that the spellchecker is broken if your NSLanguage is for example set to Thai.
    • Continuous spellchecking isn't implemented

Related Information

Comments

  • what aids are available? how they are backed?


Localization

Current Status

Translation_collaboration

Related Information

Comments