Cirion75
2009-09-19 06:19:33 UTC
I have been translating and retranslating over and over again almost a week
now.
Finally I have found out what happens...
Sometimes the translation tools somehow switches from UTF-8 to ISO-8859 and
crashes with a error message when trying to save or update the database. If
I save the file too, it is saved with ISO-8859 ecoding.
If I manually convert the file from ISO-8859 to UTF-8 I can save the
translation and load it up in translation tools, saving & updating the
database then usually works.
If I do not convert it, the next time I load the same file and press save,
all special characters are lost, and translations fail every time I try to
enter a special character. I can still save the file, but now it has no
special chars from the previous translation and new special chars have
strange chars instead. I have to manually convert the file to UTF-8 and
retranslate the whole file (adding all the special characters) to get
translation of special characters to work again.
This is the error message:
Database error
Invalid SQL: INSERT INTO egw_lang (message_id,app_name,lang,content) VALUES
('%1 contact(s) %2, %3 failed because of insufficent rights
!!!','addressbook','no','%1 kontakt(er) %2, %3 feilet pᅵ grunn av manglende
rettigheter !!!'):
ERROR: invalid byte sequence for encoding "UTF8": 0xe52067
HINT: This error can also happen if the byte sequence does not match the
encoding expected by the server, which is controlled by "client_encoding".
now.
Finally I have found out what happens...
Sometimes the translation tools somehow switches from UTF-8 to ISO-8859 and
crashes with a error message when trying to save or update the database. If
I save the file too, it is saved with ISO-8859 ecoding.
If I manually convert the file from ISO-8859 to UTF-8 I can save the
translation and load it up in translation tools, saving & updating the
database then usually works.
If I do not convert it, the next time I load the same file and press save,
all special characters are lost, and translations fail every time I try to
enter a special character. I can still save the file, but now it has no
special chars from the previous translation and new special chars have
strange chars instead. I have to manually convert the file to UTF-8 and
retranslate the whole file (adding all the special characters) to get
translation of special characters to work again.
This is the error message:
Database error
Invalid SQL: INSERT INTO egw_lang (message_id,app_name,lang,content) VALUES
('%1 contact(s) %2, %3 failed because of insufficent rights
!!!','addressbook','no','%1 kontakt(er) %2, %3 feilet pᅵ grunn av manglende
rettigheter !!!'):
ERROR: invalid byte sequence for encoding "UTF8": 0xe52067
HINT: This error can also happen if the byte sequence does not match the
encoding expected by the server, which is controlled by "client_encoding".
--
View this message in context: http://www.nabble.com/Encoding-bug-in-translation-tools.-tp25518971s3741p25518971.html
Sent from the eGroupWare-translation mailing list archive at Nabble.com.
View this message in context: http://www.nabble.com/Encoding-bug-in-translation-tools.-tp25518971s3741p25518971.html
Sent from the eGroupWare-translation mailing list archive at Nabble.com.