Hi community members,
After a discussion with Kevin(Unhammer), it became obvious that my
previous mail was not clear and a bit misleading. Therefore I am reframing
that message again.
I am working on the implementation of the idea '*Extend lttoolbox to have
the power of HFST*' under the guidance of Tommi Pirinen for GSoC 2018. The
project involves addition of weight based analyses and morphographemics in
lttoolbox to enable complex transductions in lttoolbox itself. For the
completion of this project, I need to enable morphographemics in lttoolbox,
for which we need to have new entries in lttoolbox monolingual
dictionaries. The points that need to be sorted out are:
1. For enabling twol rules in lttoolbox, we can either have two separate
files as it is there in Hfst or we can specify the rule entries in a single
dix file.
2. We must also have a proper syntax for twol rules which we either
directly copy from Hfst or modify it according to the requirements of the
xml file format in the dix files.
3. We must also make sure that the syntax for rules do not result in
conflicting situations and can be easily understood and written by new
language pair developers.
4. We must also decide the new tags we will be using for the rule
entries.
To be clear, *Rule here implies twol rules required for morphological
transformations. *I hope we figure out a suitable format which everyone
agrees upon, before the beginning of the third coding phase for the
successful completion of the project.
Regards,
Abinash Senapati
Pre-final Year Undergraduate,
Department of Electronics and Electrical Communication Engineering,
Indian Institute of Technology, Kharagpur-721302, India
*Website: *https://techievena.github.io
On Fri, May 4, 2018 at 11:14 PM, Abinash Senapati <[email protected]>
wrote:
>
> Hi community members,
> I am a student developer working on the implementation of the idea 'Extend
> lttoolbox to have the power of HFST' under the guidance of Tommi Pirinen. I
> want some ideas regarding the syntax of the rule entries in the dix files.
> Should we have all the rules and lexical entries in a single file or we
> have multiple files for them like HFST? How should be the syntax for the
> rules such that it won't be conflicting and can be easily written and read
> by a new language pair developer? What should be the new tags for the rule
> entries?
>
> I plan to work on the implementation of rule-based analysis in my third
> coding phase but it would be better to clear out all the ambiguities now.
> So I ask all the community members to provide their input and and figure
> out a format everyone agrees upon.
>
> Regards,
>
> Abinash Senapati
> Pre-final Year Undergraduate,
> Department of Electronics and Electrical Communication Engineering,
> Indian Institute of Technology, Kharagpur-721302, India
> *Website: *https://techievena.github.io
> <https://link.getmailspring.com/link/canonrd2eqxotyjhn7u-u9icjg0h3vm7m-baq3xu8nh2phak...@mail.gmail.com/0?redirect=https%3A%2F%2Ftechievena.github.io&recipient=YXBlcnRpdW0tc3R1ZmZAbGlzdHMuc291cmNlZm9yZ2UubmV0>
>
> [image: Mailtrack]
>
> <https://link.getmailspring.com/link/canonrd2eqxotyjhn7u-u9icjg0h3vm7m-baq3xu8nh2phak...@mail.gmail.com/1?redirect=https%3A%2F%2Fmailtrack.io%3Futm_source%3Dgmail%26utm_medium%3Dsignature%26utm_campaign%3Dsignaturevirality2%26&recipient=YXBlcnRpdW0tc3R1ZmZAbGlzdHMuc291cmNlZm9yZ2UubmV0>
> Sent
> with Mailtrack
> <https://link.getmailspring.com/link/canonrd2eqxotyjhn7u-u9icjg0h3vm7m-baq3xu8nh2phak...@mail.gmail.com/2?redirect=https%3A%2F%2Fmailtrack.io%3Futm_source%3Dgmail%26utm_medium%3Dsignature%26utm_campaign%3Dsignaturevirality2%26&recipient=YXBlcnRpdW0tc3R1ZmZAbGlzdHMuc291cmNlZm9yZ2UubmV0>
> [image: Open Tracking]
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Apertium-stuff mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/apertium-stuff
