Search results
Jump to navigation
Jump to search
- Next, cd to <code>modules/niffler</code>. Build by using: ...it cannot find jpl.jar. Open <code>nachtigaller.properties</code> in <code>modules/niffler</code> and set <code>swi.home</code> to where you installed SWI-Pro14 KB (2,232 words) - 12:51, 26 September 2018
- ...central repositories (such as incubator) which link to all of the included modules. Github also provides an issue tracker and a system for making commits in a ...m modules, such as the contents of nursery and incubator. The more central modules, such as lttoolbox and apertium itself, can be moved last. Documentation wi7 KB (1,057 words) - 03:39, 23 February 2015
- ...a postchunk. This design can be extended to contain two or more interchunk modules if needed. ...e translated into the target language in this first module; the subsequent modules only work with lexical forms in the target language.14 KB (1,975 words) - 08:36, 10 May 2013
- plugin are in [https://github.com/goavki/phenny/blob/master/modules/git.py modules/git.py]. [https://github.com/goavki/phenny/tree/master/modules/git.py modules/git.py], in the `MyHandler' class' `do_POST' method which handles all the P8 KB (1,370 words) - 21:21, 22 November 2018
- ...Makefile rules for speller compilation that are usable in our monolingual modules ...pell checking (minimally, OpenOffice, which can be convinced to use voikko modules if you ask nicely, but also potentially ispell or aspell or OS X's spelling2 KB (282 words) - 13:47, 17 March 2016
- ...a postchunk. This design can be extended to contain two or more interchunk modules if needed. ...e translated into the target language in this first module; the subsequent modules only work with lexical forms in the target language.14 KB (1,975 words) - 10:58, 30 October 2015
- *Implement the system's modules '''Done''' *Implement the system's modules12 KB (1,602 words) - 15:47, 10 October 2013
- ...tstrap a new translation pair between two languages which have monolingual modules already in Apertium. To see if a translation pair has already been made, s ...ger a script that updates the Apertium wiki with statistics about Apertium modules. There have been [https://github.com/apertium/phenny/issues/485 complaints32 KB (4,862 words) - 06:23, 5 December 2019
- ...), try the [[lexical selection]] module. This module is one of the easiest modules to understand in Apertium, a later addition made after much theorising and ...re interested, have a look at [[Multiwords | multi-words]]. Or the chunker modules, Chunker, Interchunk and Post-chunk, in [[Chunking:_A_full_example | an int17 KB (2,835 words) - 16:16, 24 January 2017
- ...ture Apertium developers and to define the current status of the different modules better. The most important work has been to build a catalogue of all the tr ...he perceptron tagger). Given that most new pairs depend on shared language modules, tidiness and organisation is crucial. Hopefully, this will not only improv5 KB (887 words) - 22:24, 31 August 2017
- ...nouns in the input and marks them as unknown words so that the rest of the modules in the pipeline do not process them. This avoids the common case of wrong t ...proper noun recogniser must be invoked between the tagger and the transfer modules. Option -p is needed in the tagger, so a version from Apertium greater or e3 KB (492 words) - 16:52, 10 March 2018
- ...ipeline, and it's also very different in terms of syntax to other Apertium modules (dictionaries, lexical selection, transfer rules, etc).1 KB (234 words) - 19:48, 24 March 2020
- :All modules communicate using text streams, so it would be definitely possible to say u ...makes it a moduler system, and different projects could try out different modules, where the core translation engine probably would be the common ground. [[U3 KB (406 words) - 14:29, 13 April 2008
- ...nouns in the input and marks them as unknown words so that the rest of the modules in the pipeline do not process them. This avoids the common case of wrong t ...proper noun recogniser must be invoked between the tagger and the transfer modules. Option -p is needed in the tagger, so a version from Apertium greater or e801 bytes (124 words) - 07:43, 16 October 2018
- With this format, there is no way for the individual modules like lt-proc or apertium-transfer to separate inline from block level tags * Ensure all other modules are fine with the new format for inline blanks8 KB (1,364 words) - 12:15, 14 May 2017
- Details of what many of these modules do can be found [[Workflow_reference|here]]. Note that this example includes what all modules would do, even though the English-Spanish pair does not currently use all o6 KB (873 words) - 14:35, 28 July 2020
- ...'ve used above in one place. Below is a minimal configuration file for the modules we've used above. All of the options are mandatory, if one is left out, cry26 KB (4,167 words) - 13:05, 11 May 2016
- Begiak was set up by conor_f for [[Google Code-in|GCI 2012]], and several modules were written and fixed by [[User:Sushain|sushain]], Qasim, and a number of A good tutorial on creating Phenny modules can be found [https://github.com/myano/jenni/wiki/How-to-create-a-phenny-mo8 KB (1,234 words) - 17:01, 3 December 2020
- ...ng</tt> would contain pairs that build, and have an advanced status in all modules (dictionaries with closed categories and a decent coverage, an "ad hoc" PoS * We do not propose to formalise transition between modules: we consider that a matter for separate, later consideration, if it should6 KB (874 words) - 22:16, 3 August 2013
- The next step is to configure, build and install each of the modules you checked out, in this order: If you know you need the HFST or CG3 modules, see [[Installation of grammar libraries]]. You may also be interested in t5 KB (821 words) - 02:55, 27 July 2022
