[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kwrite-devel
Subject:    Re: Procedure for submitting highlighters?
From:       Dominik Haumann <dhdev () gmx ! de>
Date:       2006-07-31 21:06:38
Message-ID: 200607312306.38835.dhdev () gmx ! de
[Download RAW message or body]

Hi Matthew,

new highlighting files right now should go to the list.
New files are not added to kde 3.5 anymore because of string freeze.
For KDE 4 I hope we can provide a way where users can upload and maintain 
their files, as it's hard to maintain all the files ourselves (we have 120 
files!).

Bug fixes are welcome for sure, and I btw. still have your Makefile bugfix 
lying around in my inbox folder which I still did not commit yet.

--
Dominik


On Monday 31 July 2006 18:59, mwoehlke wrote:
> Noticing that someone just dropped a ChordPro highlighter on the list, I
> have a question: what is the proper procedure for submitting new syntax
> highlighters for 'official' distribution?
>
> I have created:
> ----------
> Scripts/MS-DOS Batch - only alpha quality ATM
>
> Assembler/Nasm - nasm (x86) source code

Don't we already have nasm highlighting?


> Scripts/Tcsh - also only alpha quality
>
> Sources/C Preprocessor - a very full-featured parser for the C
> preprocessor, including error checking. However it has bugs that I have
> not been able to solve (I need KATE to give me highlighter debugging
> info), and also to work without being monstrously large it needs syntax
> stack manipulation ala 'Somecontext#pop#pop' (pop twice, then push
> 'Somecontext'). Meant to be IncludeRule'd, naturally.
>
> Markup/MoinMoin - for the MoinMoin flavor of Wiki
>
>
> If anyone might be interested, I also have ones for dbx output of SPARC
> assembly (v8 and v9 flavors), and MS Installshield 6 script (not sure
> what newer versions use).
>
>
> I have also made improvements to:
> ----------
> Other/Diff - now supports folding, treats context diff changes as
> old/new, but still has some bugs with folding (maybe problems with KATE?)
>
> Sources/C - recognizes Windows data types (_int32, etc), uses Alerts
> instead of duplicating this functionality.
>
> Other/Alerts - add additional keywords DEPRECATED, LEGACY and WARNING
>
> Scripts/Bash - Support for extended ${} substitution, bug fixes, speed
> enhancements, better path highlighting, recognition of more commands,
> allow '_' in quasi-long-options (e.g. '-link_libs'), recognize valid
> tests (-f, -x, etc) in [] expressions.
>
>
> In particular, I would like to make the alpha-quality highlighters
> available for any other interested parties to hack on, but they aren't
> really ready for mainstream, as there are still noticeable holes in them
> (in fact I think both have parsing errors ATM).
_______________________________________________
KWrite-Devel mailing list
KWrite-Devel@kde.org
https://mail.kde.org/mailman/listinfo/kwrite-devel
[prev in list] [next in list] [prev in thread] [next in thread]