Fixed Bug with Cyrillic symbols
- Thread starter Yoskaldyr
- Start date
mlx
Well-known member
This seems to be a bug with all non-latin characters.
Some German examples:
für groß etc.
[edit 1] Hmm, or maybe not. It's showing up OK now. Looked like it in that other German thread here: http://xenforo.com/community/threads/für-deutschprachige-user-for-german-langue-speaking.328/
[edit 2] OK I'm totally confused now. It showed up fine without spaces when I replied. It's broken up with spaces now after I edited it and the page reloaded.
Some German examples:
für groß etc.
[edit 1] Hmm, or maybe not. It's showing up OK now. Looked like it in that other German thread here: http://xenforo.com/community/threads/für-deutschprachige-user-for-german-langue-speaking.328/
[edit 2] OK I'm totally confused now. It showed up fine without spaces when I replied. It's broken up with spaces now after I edited it and the page reloaded.
I've been having problems reproducing this, though no one else seems to have a problem. 
It seems that there are situations where it doesn't happen, but I don't see any reason why that's the case.
What browser are you using, and can you reproduce it with others?
It seems that there are situations where it doesn't happen, but I don't see any reason why that's the case.
What browser are you using, and can you reproduce it with others?
Enigma
Well-known member
You can also see the problem with most of the language text posted here: http://xenforo.com/community/threads/this-is-a-test.500/ The scripts that have the outlined circles attached to them mean they are displaying incorrectly, they should be overlapping/connected to the previous character.
Edit: Added a screenshot. Edit2: This is in FF3.5 using the quick reply box.
Edit: Added a screenshot. Edit2: This is in FF3.5 using the quick reply box.
Attachments
This is fixed now. Really weird bug. The word wrap regex was supposed to match \S{50} (50 non-white-space characters), but it seemed to be triggering when it shouldn't. When I flipped it to [^\s]{50}, which is logically identical, it worked correctly.
Also, the reason I couldn't reproduce it was because I was mostly doing tests on my local forum, and it didn't happen there, so it looks like it may be a PCRE bug.
Also, the reason I couldn't reproduce it was because I was mostly doing tests on my local forum, and it didn't happen there, so it looks like it may be a PCRE bug.
F
Floris
Guest
Good job, amazing how the team just actually listens to customers and fixes bugs within reasonable time. It's still possible!
Similar threads
