On 29 April 2013 18:07, [email protected] <[email protected]> wrote: > Hi everybody, > > I am Daniel Torregrosa, student in the Official master in computer > technologies and graduated in Computer science engineering, both in > Universidad de Alicante. Two years ago, I knew that Apertium development > started here, and got somewhat involved with the project during the last > years of my career. As last year project, I developed Simpledix, a simple > web-based dictionary maintenance tool, mentored by Mikel. I am interested in > applying to GSoC with this project, giving it some of the functionality it > needs for becoming part of the toolset of Apertium developers. > > As Mikel stated, the tool needs some work for being useful. I propose some > tasks for this project: > > A simple, painless way of generating the configuration. Currently, you can > only generate configuration files manually, by using an interactive script > (that asks you to include each paradigm of the dictionary), or by using a > configurable automatic script. Improving the automatic script or making a > GUI could be answers to this problem. This task includes improving the > configuration files for adding some functionality to them, like the ordering > of the paradigms.
I'd prefer to have a meta-configuration: if it sees 'vblex', then generate 'pri.p3.sg', 'inf' and 'pp.m.sg', etc. and generate the configuration based on that. It would be trivial to add a task to dixtools to do this, and should be easy enough to do otherwise. > Interface improvements. Current interface is somewhat cumbersome, and it > shows some raw xml data that could distract the user. I could further extend > this making a responsive interface, so developers can work on the > dictionaries using a tablet or smartphone. Can you elaborate on that a little? > Supporting more kinds of entries and dictionaries. Currently, tool only > manages “standard” dix files, and the simplest (but most usual) kind of > entry ( <e> <i/> <par/> </e>). I think adding support to some metadix > formats, and for the most usual entries in the dictionaries needs to be on > the project. > Ok. > I encourage developers to test Simpledix > (http://apertium.vm.bytemark.co.uk/simpledix). It only has configuration > files for the es-ca pair, but it would give you a better understanding of > the current state of the tool, and see how it could be improved. > > If somebody needs a bit more information, you can read the tutorial on the > wiki (http://wiki.apertium.org/wiki/User:Dtr5). > > I am looking forward to hearing some feedback on this project. I really like the idea of having an easy to use interface for editing the dictionaries, but I'd like you to give some thought to the _next_ problem, too: what to do with the changes, to make it easier for users to contribute them. Passing whole dix files around can work, but would be quite a pain - it would be much better to be able to pass just the changes. Do you have any thoughts on that? -- <Sefam> Are any of the mentors around? <jimregan> yes, they're the ones trolling you ------------------------------------------------------------------------------ Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, & servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr _______________________________________________ Apertium-stuff mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/apertium-stuff
