gtksourceview is used for highlighting, so support for mixed types would have to be added there, or a custom highlighting file could be created that included all the html and php highlighting rules in 1 file.
/usr/share/gtksourceview-1.0/language-specs contains all of them. They are simple xml files.
~/.gnome2/gtksourceview-1.0/language-specs/
is also looked in for highlighting files, so user specific ones can be added there.
As for the > becoming > this is a very long standing bug, a few ways have been tried to get around it that don't involved dropping support for the auto translation to >. It is preferable to keep it for non <?php ?> sections in the document, disabling it will be a last resort.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
is there a way to have a mixed PHP+HTML document type so that code from both languages is highlighted (ala Dreamweaver)?!
plus, is it possibile not to have ">" thanslated into ">" in PHP files?
Thanks
PS: great piece of software, keep going!
gtksourceview is used for highlighting, so support for mixed types would have to be added there, or a custom highlighting file could be created that included all the html and php highlighting rules in 1 file.
/usr/share/gtksourceview-1.0/language-specs contains all of them. They are simple xml files.
~/.gnome2/gtksourceview-1.0/language-specs/
is also looked in for highlighting files, so user specific ones can be added there.
As for the > becoming > this is a very long standing bug, a few ways have been tried to get around it that don't involved dropping support for the auto translation to >. It is preferable to keep it for non <?php ?> sections in the document, disabling it will be a last resort.