/[papo]/gnue/common/doc/technotes/00002.txt
ViewVC logotype

Diff of /gnue/common/doc/technotes/00002.txt

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1.2 by charlie, Tue Aug 27 18:15:51 2002 UTC revision 1.3 by styxman, Fri Nov 15 15:32:54 2002 UTC
# Line 61  i18n in this project takes care of follo Line 61  i18n in this project takes care of follo
61    
62      .gfd files: user probably will have to create different .gfd files for      .gfd files: user probably will have to create different .gfd files for
63      different languages himself, some automated translation may be added later.      different languages himself, some automated translation may be added later.
64        Also it is possible to write .gfd files in any language (stuff like labels
65        and etc.) either in unicode or one-byte font - the only requirement would
66      This is already finished.      be to define file encoding in XML header, like:
67          <?xml version="1.0" encoding="utf-8"?>
68        or
69   2. User data - everything that user stores/works with will be stored in        <?xml version="1.0" encoding="iso8859-13"?>
70      unicode (encoded in UTF-8).  
71    
72        Using wx UI driver, it's possible to work with 8bit (one-byte; non-unicode)
73        fonts - gettext takes care of labels, status bar messages, user can input
74        text, save it to database, read from there and see it nicely. It is not
75        possible to enter/edit/save/view unicode text, unless xterm (from what
76        forms client is started) is unicode, then it is possible only to view
77        unicode text.
78    
79        Using gtk2 UI driver, it's possible to work with unicode fonts - user can
80        input text (in unicode, not in some one-byte font), save it to database,
81        read from there and see it nicely. However, gettext translations for labels
82        and etc. breaks it (sometimes they are not displayed, sometimes it's only
83        half of them). If client is started from non-unicode xterm, it's only
84        possible to read unicode characters.
85    
86        Note that 'Hack for dn encoding' parameter in gnue.conf has also influence
87        on data - with iso8859-13 xterm, wx user interface and utf-8 db encoding,
88        it was not possible to write some chars correctly, as well as chars written
89        previously with iso8859-13 db encoding were not displayed correctly.
90        Also, with iso8859-13 db encoding (iso8859-13 xterm, wx user interface)
91        chars previously written with utf-8 db encoding were not displayed
92        correctly.
93    
94    
95     2. User data - everything that user stores/works with final decision should
96        depend on user, but both one-byte encodings (like iso8859-13) and unicode
97        (encoded as utf-8) should be available.
98    
99      For data that's entered as 8bit encoded data. This was checked with      For data that's entered as 8bit encoded data. This was checked with
100      postgresql database, with adapter psycopg and for iso8859-13 encoding and it      postgresql database, with adapter psycopg, with iso8859-13 encoding, wx
101      worked fine.      user interface driver and it worked fine.
102      Settings in gnue.conf were:      Settings in gnue.conf were:
103    
104        # hack for db encoding        # hack for db encoding
# Line 80  i18n in this project takes care of follo Line 107  i18n in this project takes care of follo
107        # Font encoding to be used in forms        # Font encoding to be used in forms
108        formFontEncoding = iso8859-13        formFontEncoding = iso8859-13
109    
110        For data that's entered as unicode data. This was checked with postgresql
111        database, with adapter psycopg, with gtk2 uiser interface driver and it
112        worked fine.
113    
114    
115   3. Regional settings - this is time\date, money and etc. format and other   3. Regional settings - this is time\date, money and etc. format and other
116      country specific data.      country specific data.

Legend:
Removed from v.1.2  
changed lines
  Added in v.1.3

savannah-hackers-public@gnu.org
ViewVC Help
Powered by ViewVC 1.1.26