Search results

• 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
• Ideas for Google Summer of Code/Apertium FST CG
  ...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
• Infrastructure discussion
  :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. [[U
  3 KB (406 words) - 14:29, 13 April 2008
• Apertium-pn-recogniser
  ...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
  801 bytes (124 words) - 07:43, 16 October 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
• Bash completion
  ...ve got a language pair that depends on monolingual [[Languages|languages]]-modules, you can put the following function in your ~/.bashrc, open a new terminal
  4 KB (614 words) - 15:27, 27 April 2017
• Install Apertium core using packaging
  If you know you need the HFST or CG3 modules, packages are available, or see [[Installation of grammar libraries]]. You
  6 KB (1,006 words) - 18:26, 27 April 2021
• Using Git
  ...tor]], [[nursery]], [[staging]]</code> &mdash; these hold work-in-progress modules (mostly language pairs) that have not yet made it into <code>trunk</code> o
  8 KB (1,173 words) - 20:16, 10 March 2018
• PMC proposals/Move Apertium to Github
  ...ages we'd need to install to test all of Apertium's different tools, core, modules, etc. For an example of continuous integration in action, see: https://gith
  22 KB (3,325 words) - 14:06, 12 March 2018
• Assimilation Evaluation Toolkit
  '''Week 4''': Added modules to generate text-based task sets with original text, reference translation
  9 KB (1,368 words) - 09:04, 23 April 2015
• Hectoralos/GSOC 2020 rapport final
  (Je n'affiche ici que les modules dans lesquels il y a des données dans les trois référentiels <code>apert
  31 KB (5,141 words) - 14:45, 13 September 2021
• Writing Makefiles
  ...eating a new monolingual module or pair, use [[apertium-init]]. It creates modules that Just Work. If you've got a problem with an old makefile, throw it all
  4 KB (612 words) - 13:09, 18 February 2015

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