By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 1946 - [Regression] kate will not open php files with highlighting
Summary: [Regression] kate will not open php files with highlighting
Status: RESOLVED FIXED
Alias: None
Product: TDE
Classification: Unclassified
Component: tdelibs (show other bugs)
Version: R14.0.0 [Trinity]
Hardware: Other Linux
: P5 normal
Assignee: Michele Calgaro
URL:
Depends on:
Blocks:
 
Reported: 2014-02-19 13:09 CST by Darrell
Modified: 2014-02-20 15:06 CST (History)
3 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:

Attachments
Last known Trinity copy of javascript-php.xml that does not cause errors (12.13 KB, text/xml)
2014-02-19 13:09 CST, Darrell 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Darrell 2014-02-19 13:09:06 CST 
Created attachment 1939 [details]
Last known Trinity copy of  javascript-php.xml that does not cause errors

When I open a php file I receive two dialogs. The first dialog is kate is unable to open the file. The file then opens with a second dialog that syntax highlighting will be disabled.

Using previous package sets to test, commit bf4e405e 2014-01-08 is the cause of the regression.

Further testing reveals the problematic file is javascript-php.xml.

Attached is a copy of the last known Trinity version of javascript-php.xml that does not cause errors.
Comment 1 Michele Calgaro 2014-02-20 01:19:20 CST 
Thanks Darrell,
next week I will update the syntax files again, so I will take a look at this as well.
Comment 2 Michele Calgaro 2014-02-20 08:10:10 CST 
Fixed in commit d0c4804.

The file javascript-php.xml is generated automatically from javascript.xml by a perl script at build time.
The problem was not the file itself, but the generating script.

The fix works fine on my system, no more dialogs when opening php files.
Please confirm it works also for you.
Comment 3 Darrell 2014-02-20 15:06:39 CST 
Seems resolved here. Thank you.