G'day Apertium'ers,
On behalf of Jaipal Singh <jpsinghg...@gmail.com> who is doing the "Lint
for Apertium" GSoC project, I'm sending this BCC'ed to anyone who's
committed to Apertium in the last 3 years in order to get as much feedback
as possible. As one of your current benevolent overlords, I think this is
worth spamming everyone for.
We need feedback on what a linter should warn you about. Things that will
compile and pass current sanity checks, but really shouldn't have. So hard
errors that break the build aren't interesting - we're looking for soft
errors that only become apparent when it doesn't work the way you expected.
Things like:
- Incorrect constructs that creep into the various file types involved in
the translation pipeline (dictionaries, transfer files, tagger files, modes
files, etc).
- Conventions in these files you think should be followed but aren’t.
Anything at all you can think of. E.g., we've seen that transfer files
often have these silent errors.
You can come with suggestions via editing http://wiki.apertium.org/wiki/Lint
or just hitting Reply to me, Jaipal, or the mailing list.
-- Tino Didriksen
(161 people BCC'ed)
------------------------------------------------------------------------------
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
_______________________________________________
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff
