Skip to content

Commit 43222e7

Browse files
author
Andrey Lebedev
committed
notes about upgrading to unicode
1 parent 9123586 commit 43222e7

File tree

1 file changed

+20
-0
lines changed

1 file changed

+20
-0
lines changed

doc/upgrading.txt

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,26 @@ Migrating from 0.5 to 0.6
1212

1313
- Introduced EMAIL_FROM_TAG config variable.
1414

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.
34+
1535

1636
Migrating from 0.4.x to 0.5.0
1737
=============================

0 commit comments

Comments
 (0)