[ Skip to the content ]

Institute of Formal and Applied Linguistics Wiki

[ Back to the navigation ]

You are here: start » user » zeman » interset » how-to-write-a-driver

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
Next revision Both sides next revision
user:zeman:interset:how-to-write-a-driver [2007/10/01 17:38]
zeman 		user:zeman:interset:how-to-write-a-driver [2007/10/01 17:58]
zeman Listing available drivers.
Line 124: Line 124:
  
 See [[user:zeman:interset:Common Problems]] for a list of suggestions for phenomena difficult to match between tagsets and the Interset. See [[user:zeman:interset:Common Problems]] for a list of suggestions for phenomena difficult to match between tagsets and the Interset.
 +
 +
 +
  
  
 ===== Test your driver ===== ===== Test your driver =====
  
-When you have written a driver for a new tagset, you should test it. The driver package contains a test script called ''driver-test.pl''. When running it, give the driver name as argument, without the ''tagset::'' prefix. You can also use the ''-d'' option to turn on debug messages (list of tags being tested):+When you have written a driver for a new tagset, you should test it. The driver package contains a test script called ''driver-test.pl''. When running it, give the driver name as argument, without the ''tagset::'' prefix. You can also use the ''-d'' option to turn on debug messages (list of tags being tested). 
 + 
 +<code>driver-test.pl ar::conll</code>
  
-<code> +Running ''driver-test.pl'' without arguments will list the drivers available on the system.
-driver-test.pl ar::conll +
-</code>+
  
 Note that only drivers implementing the ''list()'' function can be tested. Note that only drivers implementing the ''list()'' function can be tested.

[ Back to the navigation ] [ Back to the content ]