Search results

• Matxin-eng-eus
  ==Data and modules==
  663 bytes (81 words) - 04:22, 21 April 2017
• Ideas for Google Summer of Code/Spell checker web interface
  ...d making sure [[APy]] has a mode that allows access to Apertium voikospell modules. The end result should be a slick, easy-to-use interface for proofing text * An [[APy]] mode for voikko modules
  1 KB (166 words) - 22:19, 18 January 2021
• Documentation
  ====Introductions to Modules====
  5 KB (599 words) - 19:04, 17 February 2020
• Matxin-spa-eus
  ==Data and modules==
  3 KB (311 words) - 13:02, 5 May 2016
• Курсы машинного перевода для языков России/Session 6
  ...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,969 words) - 12:00, 31 January 2012
• Sentence segmenting
  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-Pro
  14 KB (2,232 words) - 12:51, 26 September 2018
• Ideas for Google Summer of Code/Automatic blank handling
  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 blanks
  8 KB (1,364 words) - 12:15, 14 May 2017
• Apertium system architecture
  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 o
  6 KB (873 words) - 14:35, 28 July 2020
• Matxin 1.0 New Language Pair HOWTO
  ...'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, cry
  26 KB (4,167 words) - 13:05, 11 May 2016
• Begiak
  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-mo
  8 KB (1,234 words) - 17:01, 3 December 2020
• PMC proposals/Repository reorganisation
  ...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 should
  6 KB (874 words) - 22:16, 3 August 2013
• Install Apertium core by compiling
  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 t
  5 KB (821 words) - 02:55, 27 July 2022
• Kyrgyz and Kazakh
  ...language pair, you will need to run autogen.sh in the individual language modules, and compile each of those before configuring and compiling the pair. To edit the monolingual dictionaries, please edit the individual language modules ([[apertium-kaz]] and [[apertium-kir]]). NOTE: The monolingual dictionarie
  3 KB (304 words) - 01:51, 10 March 2018
• Création d'une nouvelle paire avec Matxin
  ...un endroit. Ci dessous voici un fichier de configuration minimal pour les modules que nous avons utilisé ci-dessus. Toutes les options sont obligatoires, si
  29 KB (4,618 words) - 07:18, 8 October 2014
• Generating lexical-selection rules from monolingual corpora
  *** <code>-multi</code> which is all the modules after lexical transfer (see apertium-mk-en/modes.xml) *** <code>-pretransfer</code> which is all the modules up to lexical transfer (see apertium-mk-en/modes.xml)
  12 KB (1,634 words) - 18:26, 26 September 2016
• Annotatrix/Work plan
  *Implement the system's modules '''Done''' *Implement the system's modules
  12 KB (1,602 words) - 15:47, 10 October 2013
• Task ideas for Google Code-in
  ...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 complaints
  32 KB (4,862 words) - 06:23, 5 December 2019
• Apertium for Dummies
  ...), 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 int
  17 KB (2,835 words) - 16:16, 24 January 2017
• English and Catalan/GSOC 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 improv
  5 KB (887 words) - 22:24, 31 August 2017
• Named entity recognition
  ...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 e
  3 KB (492 words) - 16:52, 10 March 2018

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)