Thanks for the suggestions, everyone! This is my tentative schedule, as of
now:
Weeks 1-7, .dix files:
Week 1: Redundant Entry Finder
Week 2: Testing Full Entries in Lemmas where Part of the Lemma is Specified
by the Pardef
Week 3: Testing Misspelled Tags and Pardefs
Week 4: Testing Incompatible Tags
Week 5: Testing Tag Missing on One Side of Translation Equivalents
Week 6: Testing Missing Gender on Gendered Languages
Week 7: Bundling all of these features together in one program; testing.
Weeks 8-10, Transfer rules:
Week 8: Checking inappropriate uses of <equal>, <begins-with>,
<ends-with>, and <let> in transfer rules. Perhaps contains substring (<cmp
substr>) and <in> as well? I'm having a bit of trouble figuring out where
and why those two are used.. if someone could point me to a tutorial page
with an illustrative example, I'd appreciate it. The same for <begins-with>
and <ends-with>, for that matter.
Week 9: Checking for cases where the user asks for nonexistent tags.
Week 10: Checking for incorrect number of arguments in calls to macro
(Weeks 9 and 10 will probably take less than a week, but Week 8's task
might be intricate enough to compensate)
Week 11-12: Bundling all features together into one program. Possibly
combining with .dix files checker, with a feature to check which type of
file is being input. Writing and running tests (adding deliberate errors to
sample .dix and transfer rules files to see whether the program catches
them). Writing documentation to ensure that code is maintainable.
-Aaron
On Thu, Mar 22, 2012 at 6:03 AM, Francis Tyers <[email protected]> wrote:
> El dj 22 de 03 de 2012 a les 10:05 +0000, en/na Jimmy O'Regan va
> escriure:
> > On 22 March 2012 09:04, Kevin Brubeck Unhammer <[email protected]>
> wrote:
> > > "Jimmy O'Regan" <[email protected]>
> > > writes:
> > >
> > >> On 22 March 2012 08:29, Francis Tyers <[email protected]> wrote:
> > >>> isn't there. (b) Or using <lit> when you mean <lit-tag> because what
> > >>> you're checking against can only be a tag.
> > >>>
> > >>
> > >> Counter example:
> > >> <let>
> > >> <clip pos="1" side="tl" part="some_part"/>
> > >> <lit v=""/>
> > >> </let>
> > >
> > > http://permalink.gmane.org/gmane.comp.nlp.apertium/1676 so def-attrs
> can
> > > be empty lit's, lit-tags, or variables (but not non-empty lit's), and
> > > this goes for at least <equal>, <begins-with> (<ends-with>? can't
> > > remember if we have that),
> >
> > Yes. And begins-with-list, ends-with-list, and contains-substring
> >
> > > and <let>.
> > >
> > > Another exception is that you can do stuff like
> > >
> > > <concat><lit v="&lt;"/><lit v="tag"/><lit v="&gt;"/></concat>
> > >
> > > on the right hand side. I'm not sure why you'd want to though (unless
> > > you were using a variable, in which case we're out of lint's league
> > > anyway), and in the above example I would want a warning.
>
> If I see someone doing that, I'll kick them in the shins... There's the
> warning! :D
>
> Fran
>
>
>
> ------------------------------------------------------------------------------
> 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
>
------------------------------------------------------------------------------
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
