2012/3/21 Aaron Rubin <[email protected]>
>
> But not all of those would necessarily take up a week, and there's no way
> that all of this will take 12 weeks! So I've been thinking about common
> errors that might show up in transfer rules files, but nothing's really
> come to mind. Has anyone else noticed common mistakes in .dix or transfer
> rules files that would be suitable for this kind of program to look for?
>
>
This might not strictly be a lint checkers job, but have a look at
'beginner errors' like breaking the XML or not following the XML Schema:
- forgetting an end tag (like writing <s n="adj"> instead of <s n="adj"/>
- messing up the " 's, like writing <s n="adj>
- mis-naming an attribute
- forgetting attributes
etc.
I am not sure these kinds of errors are always reported to the user in a
meaningfull way by the compiler.
However, I *am* sure that there are some users that use a lot of time
struggling with such errors.
So I'd suggest leaving a week for seeing if there is something you could
do to help out dix editor novices.
Jacob
--
Jacob Nordfalk <https://plus.google.com/114820443085046080944>
http://javabog.dk
Android-udvikler og underviser på
IHK<http://cv.ihk.dk/diplomuddannelser/itd/vf/MAU>og
Lund&Bendsen <https://www.lundogbendsen.dk/undervisning/beskrivelse/LB1809/>
------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
Apertium-stuff mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/apertium-stuff
