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 316866 - PCRE UTF8 support vs. Syntaxhighlighting
PCRE UTF8 support vs. Syntaxhighlighting
Status: RESOLVED FIXED
Product: bluefish
Classification: Other
Component: application
1.0.4
Other Linux
: Normal major
: ---
Assigned To: Bluefish Maintainer(s)
Bluefish Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2005-09-21 18:07 UTC by Luis Roalter
Modified: 2005-09-25 17:59 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Luis Roalter 2005-09-21 18:07:46 UTC
Version details: worked in 1.0.1

when running a fresh build of bluefish (in this case 1.0.4, 1.0.1 therefore
worked fine) syntaxhighlighting does not seem to work anymore.

e.g. applying Highlighting Preferences there are many errormessages which are
kind of "This version of PCRE is not compiled with UTF8 support at offset 0".

I updated PCRE from version 5.0 to 6.4, and _enabled_ --enable-utf8 or similar
(read it in configure --help), but some problem. compiling the highlighting by
hand e.g. with pcretest anything works fine. 

Removing any PCRE_UTF8 from src/highlighting.c or replacing it by 0 solves the
problem that way, that you can use highlighting, but without definitiv utf8 support.

A solution would be fine. I don't know if pcre or bluefish fails.
Comment 1 Jim Hayward 2005-09-22 03:55:47 UTC
Bluefish <= 1.0.3 will currently work on systems where PCRE is not compiled with
UTF-8 support.

PCRE UTF-8 support was added to 1.0.4 to fix a highlighting bug with UTF-8
characters. Apparently your Linux distribution is not compiling PCRE with UTF-8
support. What Linux distribution/version are you using?

Too resolve this I'm going to add a configure check to see if PCRE is compiled
with UTF-8 support. Bluefish will fall back to compiling the highlighting
patterns without UTF-8 support. This is the behavior in Bluefish <= 1.0.3.

I have not tested Bluefish with PCRE versions newer then the 5.0.x branch. There
may be unknown issues when using the 6.x branch.
Comment 2 Olivier Sessink 2005-09-22 07:53:48 UTC
I thought I did have that check in place already, in the code there is somewhere
... #ifndef PCRE_UTF8 .... but obviously PCRE_UTF8 is defined but not supported.
We need a better check indeed.
Comment 3 Tomas Ruzicka 2005-09-24 11:41:10 UTC
I can confirm that behavior on SUSE 9.3, PCRE 5.0-3.2
Comment 4 Jim Hayward 2005-09-25 00:36:16 UTC
A configure check has been added to the 1.0 branch of CVS that checks to see if
PRCE on the users system is compiled with UTF-8 support. You can test this by
checking out the 1.0 branch from CVS. You can checkout the 1.0 branch of CVS
with the command below. This is a single line.

cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/bluefish co -d
bluefish-1_0 -r bluefish_1_0 bluefish-gtk2