If I want to use another language like Arabic with interfaces in grass, do I need to compile the grass?
I want to build different interfaces in TCL/TK and from them I will call GRASS’s functions, but my interfaces must be in Arabic ,so I ask you: Do I need to translate Grass messages to Arabic
- If I want to use another language like Arabic with interfaces in
grass, do I need to compile the grass?
No. Language can be set at runtime.
You do need the source code to help with translating new messages. (?)
- I want to build different interfaces in TCL/TK and from them I will
call GRASS's functions, but my interfaces must be in Arabic ,so I ask
you: Do I need to translate Grass messages to Arabic
Someone has to. Start with the modules most important to you.
> - If I want to use another language like Arabic with interfaces in
> grass, do I need to compile the grass?
No. Language can be set at runtime.
You do need the source code to help with translating new messages. (?)
Also, GRASS' text handling is quite primitive, and oriented towards
ASCII and ISO-8859-* encodings. At present, the internationalisation
support is limited to:
1. The use of message catalogues.
2. Support for user-specified encodings in a few specific places
(primarily those related to FreeType).
There certainly isn't any explicit support for right-to-left
languages. Also, any code which uses the curses library will only work
correctly with unibyte encodings (e.g. ISO-8859-*), and not with
multibyte encodings such as UTF-8.