Content-Type: multipart/alternative; boundary="------------050001080402030603010301" --------------050001080402030603010301 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit I am using the language file attached to validate the ini settings files of eZ Publish (tested on geshi 1.8.6 and 1.8.10). It mostly works, but when I try to analyze the following file (2 lines): [RegionalSettings] TranslationExtensions[]=monextension I get the following output: span style="background-color: yellow;"> [RegionalSettings]... IE. in the results the opening angle bracket for "span" is missing. This does not happen if there is eg. an empty line at the beginning of the file being highlighted. Is it due to a bug in the parser itself, or is something wrong with the language definition? Thanks Gaetano ps: any chance to get the ezini and eztemplate language definitions included in the next release? I submitted them a long time ago... --------------050001080402030603010301 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit I am using the language file attached to validate the ini settings files of eZ Publish (tested on geshi 1.8.6 and 1.8.10).

It mostly works, but when I try to analyze the following file (2 lines):

[RegionalSettings]
TranslationExtensions[]=monextension

I get the following output:
span style="background-color: yellow;"> <span style="">&#91;</span></span>RegionalSettings<span style="">&#93;</span>...
 
IE. in the results the opening angle bracket for "span" is missing.
This does not happen if there is eg. an empty line at the beginning of the file being highlighted.
Is it due to a bug in the parser itself, or is something wrong with the language definition?

Thanks
Gaetano

ps: any chance to get the ezini and eztemplate language definitions included in the next release? I submitted them a long time ago...


--------------050001080402030603010301--