After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 326887 - UTF-8 characters mess up fancy colouring
UTF-8 characters mess up fancy colouring
Status: RESOLVED FIXED
Product: bluefish
Classification: Other
Component: application
1.0.4
Other All
: Normal minor
: ---
Assigned To: Bluefish Maintainer(s)
Bluefish Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2006-01-13 19:14 UTC by Vincent Lönngren
Modified: 2006-01-18 09:55 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Vincent Lönngren 2006-01-13 19:14:40 UTC
Please describe the problem:
By default, class names (.some_class) in CSS files are reddish and in italics.
If one of them contains UTF-8 characters, and probably other non-ASCHII
characters although I haven't checked that, they will be black and upright from
that character onward. I wouldn't be surprised if this is a problem with
identifiers (#some_identifier) too, or with other formats than CSS, but I
haven't checked it.

Steps to reproduce:
1. Create a CSS file with UTF-8 characters in class names
2. Save it with the .css extention or change the document type to stylesheet
3. Look at the class names with UTF-8 characters


Actual results:
You will see the part of the class name from the UTF-8 character until the end
of the name in black, upright style (with default settigngs, anyway)

Expected results:
It might be expected that the whole name should look the same.

Does this happen every time?
Yes.

Other information:
Here is a real-life CSS file that uses them: http://www.mf.lu.se/mf.css
Comment 1 Daniel Leidert 2006-01-13 19:39:17 UTC
Confirmed. The reason is the search pattern, which is actually: '[#.][a-z0-9\-_]+'

To also consider UTF-8 characters, we need to change this pattern to something like: '[#.][^ ,{<>/]+'.

That solves the problem. Or did I miss a character, which could end an identifier, or a valid part of an identifier?
Comment 2 Jim Hayward 2006-01-14 05:29:40 UTC
Hmm, looks alright. However, I've only tested it with a few different CSS files. Doesn't appear to break anything else so far.
Comment 3 Daniel Leidert 2006-01-18 09:55:55 UTC
Ok. I also did not observe any problems. So I commited the pattern fix. Closing this bug now.