comparison doc/upgrading.txt @ 1386:7ca01821df2c

notes about upgrading to unicode
author Andrey Lebedev <kedder@users.sourceforge.net>
date Sun, 19 Jan 2003 16:15:38 +0000
parents 944bd3c6d365
children cd28e3b5db2e
comparison
equal deleted inserted replaced
1385:2bd4822f96a6 1386:7ca01821df2c
9 9
10 Migrating from 0.5 to 0.6 10 Migrating from 0.5 to 0.6
11 ========================= 11 =========================
12 12
13 - Introduced EMAIL_FROM_TAG config variable. 13 - Introduced EMAIL_FROM_TAG config variable.
14
15 - Added internationalization support. This is done via encoding all data
16 stored in roundup database to utf-8 (unicode encoding). To support utf-8 in
17 web interface you should add the folowing line to your tracker's html/page
18 and html/_generic.help files inside <head> tag:
19
20 <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
21
22 Sinse latin characters in utf-8 has the same codes as in ASCII table, this
23 modification is optional for users who use only plain latin characters.
24
25 After this modification, you will be able to see and enter any world
26 character via web interface. Data received via mail interface also converted
27 to utf-8, however only new messages will be converted. If your roundup
28 database contains some of non-ASCII characters in one of 8-bit encoding,
29 they will not be visible in new unicode environment. Some of such data (e.g.
30 user names, keywords, etc) can be edited by administrator, the others
31 (e.g. messages' contents) is not editable via web interface. Currently there
32 is no tool for converting such data, the only solution is to close
33 appropriate old issues and create new ones with the same content.
14 34
15 35
16 Migrating from 0.4.x to 0.5.0 36 Migrating from 0.4.x to 0.5.0
17 ============================= 37 =============================
18 38

Roundup Issue Tracker: http://roundup-tracker.org/