New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Description text with special letters is not shown #1072

Open
wpcata opened this Issue Dec 6, 2017 · 2 comments

Comments

Projects
None yet
2 participants
@wpcata

wpcata commented Dec 6, 2017

I may have found one of the strangest bugs...

Expected behaviour

A description text with "ä", "ö", "ü" or "ß" should be shown in the timesheet-view.

Actual behaviour

If the 49th letter in a description is a "ä", "ö", "ü" or "ß" and the previous part contains exactly one of these special letters the description is not shown.
For example: " ä ß"

Steps to reproduce

Write a random description text with one special letter and a special letter on the 49th position.

Reproducable on demo.kimai.org? [yes|no]

Yes

Kimai version [for example: dev 1.1.0.1389|github master|github develop]

Kimai 1.1.0.1389
Kimai dev 1.2.1.1393

Relevant log entries from log file (debug tab or temporary/logfile.txt)


@wpcata

This comment has been minimized.

Show comment
Hide comment
@wpcata

wpcata Dec 7, 2017

I just saw that my example string got cut...
This should (not) work:
"1234 ä234 1234 1234 1234 1234 1234 1234 1234 124ß"

wpcata commented Dec 7, 2017

I just saw that my example string got cut...
This should (not) work:
"1234 ä234 1234 1234 1234 1234 1234 1234 1234 124ß"

@simonschaufi

This comment has been minimized.

Show comment
Hide comment
@simonschaufi

simonschaufi Dec 7, 2017

Member

yeah, I can also confirm that on my own server in dev branch. Maybe it has something to do with multibyte character or html escaping

Member

simonschaufi commented Dec 7, 2017

yeah, I can also confirm that on my own server in dev branch. Maybe it has something to do with multibyte character or html escaping

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment