Language Support

From DSL Wiki

For Brazilian Language (Portuguese variation) there is a .dsl-file available.

These attempts have been done:

Contents

Booting with option "dsl lang=xx"

  • In the new version of DSL (3.1), it is possible to invoke a German keyboard layout with Umlauts by choosing the boot option dsl lang=de-latin1-nodeadkeys. Worked very well for me, while working from a USB-pen-drive.
  • With "lang=fr" it seems to be similar. It's a French AZERTY-keyboard afterwards. Only the accents and special characters are missing.
  • In Chinese language characters are not shown correctly.

It seems to be a character set problem ...

To browse Chinese web sites with firefox, just run these lines with dsl account:


wget http://www.newsclan.com/dsl/cn.sh

chmod +x cn.sh

./cn.sh


tested with dsl3.4.4 and dsl4.0 in qemu

and there is an online Chinese input tool

http://www.inputking.com/

patching a .dsl-file

If you use 7-zip you can easily open the directory-tree of the Brazilian version pbtr.dsl. There you can find and extract all files that are to be changed.

Please try to coordinate who is working on which language that there is no double work done by adding your name after the languageTLD-code:

  • de:
  • fr:
  • es:

Discussion should be done in the forum.


a cnpack.dsl for Chinese can be found here:

http://groups.google.com/group/dsl-cn

A traditional Chinese version DSL(support simplified Chinese too) created in 2005 can be found here and here is a tutorial on how to add other input methods(include simplified Chinese input methods) into its gcin input method.

DSL and Unicode

While the core bits of DSL are capable of handling files in Unicode encodings, most of the included apps cannot. This is either because they are tiny apps by nature and don't support Unicode (aterm, beaver) or they have been compiled without Unicode/multibyte support for space reasons (vim). If you want to use and display characters outside of the range included in the latin-1 encoding, you will generally need to install DSL extensions or compile your own apps which can handle the display and manipulation of your character set. DSL does include various point sizes of the X-font, -misc-fixed-..., which includes a surprising array of unicode ranges, but is a fixed-width font, and won't be suitable for some uses. And anyway, you've got to get an app to *display* it in. So everything hangs on the apps you want to use. Try them out individually.

What is known to work/not to work?

Greek

  • Text editing using polytonic Greek in gvim, (using a self-compiled version including +multibyte support),

Using vim's own keymap support (greek-utf_8) for input, and the font "misc (fixed)", also called -misc-fixed-... for display. This works great, but you must compile your own vim, since none of the vim_full extensions contain multi-byte support. Do this within vim to get off the ground:

      :set encoding=utf-8

All of this works because gvim itself has good features for handling non-latin languages, and already includes its own input methods. Your app may vary.

  • Standard X-window middle mouse button copy-paste works fine.
  • Some standard unix command-line text operations need the full GNU tools to work well with unicode text. Busybox seems not to play well with text files in the UTF-8 encoding.
  • Firefox seems to display utf-8 Greek fine.
  • The Open Office DSL extension works well to display, manipulate and print unicode Greek, but typing it in is a different issue.
  • I tried compiling rxvt as a substitute for DSL's standard aterm. Compiling was easy, and I could *display* greek on the terminal, but had no luck getting vim to work on it in non-GUI mode. Perhaps a $TERM problem.

Hebrew

  • Text editing using vocalized Hebrew works in gvim, using vim's own keymap for entry, and vim's Left-to-Right support. Again, using the -misc-fixed- font for display. Note that writing bi-directional text in vim is fully functional, but not pretty, since you always have to display the file using either RTL or LTR.


Translating DSL?

  • An informative post on what steps are needed to localize DSL is here