cool
Though, I never quite understood (and thus used) the usage of the 't Kofschip-trick. I mean, if you pronounce the past tense of the verb you can always clearly hear what letter you need to use (in 99,9999% cases*)...
*which is much more than using the 't kofschip-trick and remembering its exceptions.
Also, the 't Kofship-trick wont work with several verbs, especially verbs derived from English.
Eg: 'Faxen' => "Faxte" (not "Faxde").
(of course of you use your "XTC" prefix it would work for this particular verb
)
And of course irregular verbs like "kopen" wont work either (but that's obvious).
quote:
Originally posted by SmokingCookie
Yeah I know.. But I've spent a couple of hours straight trying to think of a verb base ending on c or h, but haven't really succeeded yet
"lachen", "crashen", ...
Dunno one with 'c' so quickly though...
Also take in account verbs like "skiën" in case you're searching the end of the string for "en", it will fail (haven't looked at the source).
Then there is also the problem of taking the base of that verb: the base is "skie" not "ski". In case of "'t kofschip" the trick will work ("e" isn't in "'t kopschip" so it is "skiede"), but if you use "koffieshop" it will fail, you'll have a "e" in there...
PS: maybe to further increase the use of the script you could hard code irregular verbs?
http://nl.wikipedia.org/wiki/Lijst_van_sterke_en_..._in_het_Nederlands
Also, I would remove the mandatory usage of the square brackets in the parameter. They seem useless imho; if no parameter is given, open the window. If a parameter is given, try to parse it.
/ 
