On 12 February 2015 at 08:23, Per Tunedal <[email protected]> wrote:
> One way of improved checking would be not to just have separate programs
> like Jimmy O'Regan's lint-tool for tsx-files, but also make the make
> script be more explicit about errors. Some helpful hints about common
> errors. Print the offending line with explicit info. Or rather the
> offending expression? This applies to make scripts for dictionaries as
> well as for tagger training.
The normal build process already does this. Maybe not with as much detail
as you'd like, but it certainly validates all files and stops the build if
any error is found.
Also, any DTD-enabled XML editor will be able to tell you what's wrong
while editing those files.
Making the errors and warnings more descriptive is an ongoing process - not
sure that really qualifies as a GSoC project.
-- Tino Didriksen
------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Apertium-stuff mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/apertium-stuff
