Difference between revisions of "I18n"

From GNUstepWiki
Jump to navigation Jump to search
 
(6 intermediate revisions by 4 users not shown)
Line 1: Line 1:
−
Internationalisation (or localisation) touches:
+
I'm trying to form a gnustep-i18n team and list all relevant subjects. If you are experienced in this field, please help.
−
* '''Input''' - how a user writes a text
 
−
* '''Presentation''' (or output) - how a text is presented to the user
 
−
* Aids - writing aids and processing mechanisms with and without user interaction
 
−
* Localisation of user interface
 
  
−
== Related information ==
+
==Input==
  
−
Input method standards and implementations:
+
* 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 ([http://ftp.xfree86.org/pub/XFree86/4.5.0/doc/xim.txt old documentation])
 
* X11 Input Method (XIM) system ([http://ftp.xfree86.org/pub/XFree86/4.5.0/doc/xim.txt old documentation])
Line 14: Line 17:
 
* kinput2 is a Japanese input server for XIM ([http://www.nec.co.jp/canna/ homepage])
 
* kinput2 is a Japanese input server for XIM ([http://www.nec.co.jp/canna/ homepage])
 
* [http://www.gnu.org/software/emacs GNU Emacs] has long had extensive input support in its [http://savannah.gnu.org/cgi-bin/viewcvs/emacs/emacs/leim/ 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.gnu.org/software/emacs GNU Emacs] has long had extensive input support in its [http://savannah.gnu.org/cgi-bin/viewcvs/emacs/emacs/leim/ 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/
 +
*[http://wmuim.sourceforge.jp/ wmuim]is a dockapp and can be instead of uim-helper-toolbar-gtk
 +
*[http://www.digital-genes.com/~yatsu/macuim/ MacUIM] is written in Cocoa.
 +
*[http://scim-im.org/ 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:
+
== Output ==
  
 
* vertical text layout
 
* vertical text layout
 
* bidi text layout
 
* bidi text layout
 
* opentype support
 
* opentype support
−
* [http://www.w3.org/TR/css3-text/ CSS3 Text Module]
+
* NSTextView
 +
* Word hyphenation
 +
* Word segmentation
 +
* font substitution
  
−
== Requirements ==
+
===Current Status===
  
−
Output:
+
* Gnustep has font substitution support.
 +
** The GSPreferredFonts default should be set to a list of font names that the text system will fall back on, when a glyph isn't available in the system fonts
  
−
* NSTextView
+
===Related Information===
−
* Typesetters
 
−
* Opentype supports
 
−
* Word hyphenation
 
−
* Word segmentation
 
  
−
Input:
+
* freetype
 +
* pango
 +
* [http://www.w3.org/TR/css3-text/ CSS3 Text Module]
  
−
* NSTextInput protocol
+
===Comments===
−
* NSInputManager
 
  
−
Aid:
+
* what output method(s) is used? How? Why?
  
−
* Spell-checking NSSpellChecker
 
  
−
== Status ==
+
== Writing aids and processing mechanisms ==
  
−
I'm trying to form a gnustep-i18n team and list all relevant subjects.
+
* Spell-checking NSSpellChecker
−
If you are experienced in this field, please help.
 
  
−
== FIXME ==
+
===Current Status===
  
−
* what input method(s) GNUstep currently uses and for what backend? How?
+
*The spellchecker uses libaspell for its backend
−
**Correct me if I were wrong. Currently we use XIM that only available in back-x11. Many input systems, eg. IIIMF, kinput2 have their own XIM bridges. Do we have those pop-up helpers with XIM yet?
 
−
* what output method(s) is used? How? Why?
 
−
* what aids are available? how they are backed? (for example, what spellchecking backend is used and how
 
−
**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)
 
**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 [http://aspell.sourceforge.net/man-html/Unsupported.html unsupported] by aspell.
 
**some languages are [http://aspell.sourceforge.net/man-html/Unsupported.html 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.
 
**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
 
**Continuous spellchecking isn't implemented
 +
 +
===Related Information===
 +
 +
===Comments===
 +
 +
* what aids are available? how they are backed?
 +
 +
 +
== Localization ==
 +
 +
===Current Status===
 +
 +
[[Translation_collaboration]]
 +
 +
===Related Information===
 +
 +
===Comments===

Latest revision as of 04:47, 7 November 2007

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 has font substitution support.
    • The GSPreferredFonts default should be set to a list of font names that the text system will fall back on, when a glyph isn't available in the system fonts

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

Retrieved from "https://mediawiki.gnustep.org/index.php?title=I18n&oldid=4887"