Jacob Nordfalk <[email protected]> writes: > 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.
Couldn't the lint just run apertium-validate-dictionary first? Although, one issue is what to do about those who use xslt transformed dictionaries (e.g. using the alt attribute). I'm guessing it would be easier to run lint on the transformed dictionary, but not as helpful since line number would have changed. On the other hand, if you run lint on the source dictionary, it won't validate (though you can still check that it's well-formed XML). -Kevin ------------------------------------------------------------------------------ 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
