2013/4/30 Jimmy O'Regan <[email protected]>
> On 29 April 2013 18:07, [email protected] <[email protected]> wrote:
> > Hi everybody,
> >
> > 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.
>
The automatic script already takes that kind of meta-configuration. You can
see an example at the end of (
http://wiki.apertium.org/wiki/User:Dtr5#Making_your_own_configuration_file
).
But that method has some problems: it is really slow (takes around 2 hours
for processing es-ca dictionaries with the sample configuration), it is
somewhat difficult to control its output, and should take some extra
constraints (for example, spanish verbs are duplicated, one with and other
without accent; linking them to work as one paradigm that inserts two nodes
at once would be great).
With some work, the process would be faster, wich can lead to a simple way
of showing users the output so they can see what they are doing, solving
the second problem.
Also, giving some extra info to the user would be great: for example, if a
paradigm has an inflection no other paradigm has, adding it to the
configuration file could lead to an easier work with the tool.
> > 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?
>
You can see an example on the wiki (
http://wiki.apertium.org/wiki/User:Dtr5#Word_insertion)
As you can see, the interface has some problems:
- xml of existing translations and new nodes. Should show a more
user-friendly representation, that needs to be configured for managing some
difficult cases, like multiword entries.
- translation direction configuration. Should be rethinked, because as
it is, it is meaningless for a new user.
- the button toolbar in the lower part of the interface. It could pass
unnoticed, some options are not clear, and it should not have options like
"Close session" and "Export dictionaries" at the same level as "Generate
insertions"
Also, as is, interface can not be used in smaller screens. I don't know if
any developers want to work on the dictionaries on their smartphones, but
as the interface needs a major rework, using a responsive overlay does not
seem out of place.
>
> > 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?
>
When you export the dictionaries, a simple xslt transformation puts all the
new entries at the end of the dictionary. I could provide only the
difference, greatly reducing the size of that download.
As for uploading, I think nothing can be done. The tool uses full
dictionaries for checking the existing entries. Currently, users can
provide his own configuration file, which acts as a simplified paradigms
section of the dictionary, so the tool could generate an empty dictionary
and start working from scratch.
Thank you for your feedback.
------------------------------------------------------------------------------
Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
Get 100% visibility into your production application - at no cost.
Code-level diagnostics for performance bottlenecks with <2% overhead
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap1
_______________________________________________
Apertium-stuff mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/apertium-stuff
