search

giellalt / bugzilla-dummy

0 stars 0 forks source link

xdoc Russian num.*.html files do not handle UTF-8 (Bugzilla Bug 1205) #1572

Closed albbas closed 12 years ago

albbas commented 13 years ago

This issue was created automatically with bugzilla2github

Bugzilla Bug 1205

Date: 2011-11-02T14:53:49+01:00 From: Trond Trosterud <> To: Tomi Pieski <> CC: borre.gaup, sjur.n.moshagen

Last updated: 2012-09-07T20:35:35+02:00

albbas commented 13 years ago

Comment 5408

Date: 2011-11-02 14:53:49 +0100 From: Trond Trosterud <>

We have problems with the num.sme.html etc. files (there are 5 of them). They are html, and not .xml, and must be written with html entities. This becomes very cumbersome with the russian file, which now do not work at all.

To see: open http://giellatekno.uit.no/num.rus.html http://giellatekno.uit.no/num.sme.html http://giellatekno.uit.no/num.nno.html

albbas commented 13 years ago

Comment 5409

Date: 2011-11-02 16:05:33 +0100 From: Børre Gaup <>

A solution for this is to change the line char-encoding=latin1 to char-encoding=utf8 in the file $FORREST_HOME/main/webapp/WEB-INF/jtidy.properties

I have done it on the machine (xserve) that builds our sites, but we need a more permanent solution (meaning moving jtidy.properties inside our own svn)

albbas commented 12 years ago

Comment 6721

Date: 2012-09-07 20:35:35 +0200 From: Trond Trosterud <>

The solution looks permanent to me:

Генерирование саамских числительных

Здесь вы можете генерировать саамские числительные

Введите число между 1 и 999999999. Просто напишите, например, "123", и компьютер отвечает: "čuođiguoktelogigolbma"

. The solution Børre alluded to has been done: grep char-encoding $FORREST_HOME/main/webapp/WEB-INF/jtidy.properties char-encoding=utf-8 ... probably in january: hum-tf4-ans176:xdocs ttr000$ svn log $FORREST_HOME/main/webapp/WEB-INF/jtidy.properties ------------------------------------------------------------------------ r1234657 | crossley | 2012-01-23 01:28:55 +0100 (Mon, 23 Jan 2012) | 4 lines Use JAVA_TOOL_OPTIONS to ensure UTF-8 everywhere. Contributed by: Karl Wright Issue: FOR-1231 I close.