Type	To find
responsible:me	tickets assigned to you
tagged:"@high"	tickets tagged @high
milestone:next	tickets in the upcoming milestone
state:invalid	tickets with the state invalid
created:"last week"	tickets created last week
sort:number, importance, updated	tickets sorted by #, importance or updated
Combine keywords for powerful searching.
Use advanced searching »

#126 ✓resolved

Bad uniclode support

Reported by Leonid Batizhevsky | 2010-12-15 05:53:32 UTC | in Rundeck 1.0

I use Russia unicode

locale

LANG=ru_RU.UTF-8
LC_CTYPE="ru_RU.UTF-8"
LC_NUMERIC="ru_RU.UTF-8"
LC_TIME="ru_RU.UTF-8"
LC_COLLATE="ru_RU.UTF-8"
LC_MONETARY="ru_RU.UTF-8"
LC_MESSAGES="ru_RU.UTF-8"
LC_PAPER="ru_RU.UTF-8"
LC_NAME="ru_RU.UTF-8"
LC_ADDRESS="ru_RU.UTF-8"
LC_TELEPHONE="ru_RU.UTF-8"
LC_MEASUREMENT="ru_RU.UTF-8"
LC_IDENTIFICATION="ru_RU.UTF-8"
LC_ALL=

And in the web interface there is a problem with displaying characters:

rundeck_unicode.png 13.3 KB

Comments and changes to this ticket

Alex-SF 2010-12-17 07:48:24 UTC
- Milestone set to “Rundeck 1.0”
- Milestone order changed from “17” to “0”
You flagged this item as spam.
Deleted User 2010-12-17 10:52:42 UTC
I was able to recreate on CentOS 5.5 by changing the locale to Russian.
You flagged this item as spam.
Deleted User 2010-12-17 11:14:21 UTC
- Tag set to “i18n, locale, utf8”
Checking the log file on disk, the content is correctly formatted.

httpd остановлен

Somewhere between the log file and presentation, the encoding is not being honored?
You flagged this item as spam.
Leonid Batizhevsky 2010-12-17 11:59:26 UTC
the encoding is not being honored? Yes, I're right! It's look like output is not in unicode, it's in ANSI (encoding iso 8859-1)
Greg Schueler 2010-12-20 17:51:53 UTC
- Assigned user set to “Greg Schueler”
Ok, I tracked this down. screenshot of fix
- unicode-ru.png 21.1 KB
- unicode-japanese.png 22 KB
You flagged this item as spam.
Deleted User 2010-12-20 17:56:05 UTC
- State changed from “new” to “resolved”
(from [57ab640567570fe360d850ed9e99985dc63da370]) Fix logfile parse code to support the file encoding, but maintain byte-oriented offset counts. update tests. [#126 state:resolved] https://github.com/dtolabs/rundeck/commit/57ab640567570fe360d850ed9...
You flagged this item as spam.
Rouie Dawis 2024-03-21 06:50:46 UTC
get it now..

Mr. Dawis--> kinderballet
You flagged this item as spam.
AliciBlackburn 2025-12-26 22:48:37 UTC
Ah, the dreaded Unicode gremlins strike again! Encountering similar issues with character encoding can be so frustrating. Specifically, a project once involved integrating user data from various sources, each with its own encoding quirks; just like running the Dinosaur Game . It was a nightmare of mojibake until we standardized to UTF-8. Now, where's my decoder ring?

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.