Search results

• Anaphora resolution module
  Here you will find the documentation for the Anaphora Resolution module created during the Google Summer of Code Anaphora Resolution is the process of resolving references to earlier items in discourse.
  20 KB (3,107 words) - 21:13, 24 June 2022
• Quick and dirty guide addendum: other important things
  ...t be shy to get creative in your use of resources, but be wary of mistakes in various resources (even seemingly reputable ones!) or over-all low-quality ...h pages include [[English and Esperanto/Outstanding tests]] and [[Welsh to English/Regression tests]]. Like with these pages, you should probably plan to kee
  10 KB (1,615 words) - 07:43, 20 December 2015
• Chunking
  Shallow transfer means there is no parse trees (which are used in "deep transfer"). By chunking (in three-stages): First we reorder words in the chunk, then we reorder chunks.
  4 KB (584 words) - 06:55, 8 October 2014
• Uputstvo za novi jezički par za Apertium
  ...lish is not. So for example: I see in English would be translated as vidim in Serbo-Croatian. ...dictionary, we need to add both the verb, and the personal pronouns in the English morpohlogical dictionary. We'll go through both of these.
  26 KB (4,259 words) - 07:00, 16 February 2015
• Conjoined lexical units
  ...considered one lexical unit (all of it is within the same <code>^…$</code> in the output of the analyser), while during transfer they are considered sepa ...not in the dictionary, e.g. if <i>vier</i> and <i>letter</i> have analyses in the dictionary that give the non-final hidden tag, and <i>woorden</i> with
  4 KB (654 words) - 08:31, 6 April 2021
• Corpora
  ::Use this if you want to do English--<something> (funny alignments for non-English pairs) ...heast European Times &mdash; http://opus.lingfil.uu.se/SETIMES.php &mdash; English,Turkish,Bulgarian,Macedonian,Serbo-Croatian,Albanian,Greek,Romanian &mdash;
  5 KB (746 words) - 20:36, 25 January 2020
• Matxin
  ...e related to [[Apertium]]. It allows for deeper transfer than can be found in Apertium. This page describes how to install the system, see [[Matxin#Documentation]] below for how to create or maintain language pairs.
  1 KB (164 words) - 20:29, 7 May 2016
• Morphological dictionary
  ...ctionary is to model the rules that govern the internal structure of words in a language. ...stood by the speaker reflect specific patterns and regularities in the way in which words are formed from smaller units and how those smaller units inter
  15 KB (2,200 words) - 12:04, 6 October 2014
• List of symbols
  This page lists the symbols in Apertium used to denote part-of-speech and further morphological features, ...es have the same grammatical features (most don't have spatial distinction in articles for example).
  38 KB (4,492 words) - 15:36, 9 May 2024
• Apertium on openSUSE
  ...''/home/kevin/downloads/linguistics'', but it can be anything you choose. In this note, this choice will be referred to as ''[homedir]''. Obviously, replace ''[homedir]'' here and in subsequent instances by your real path.
  5 KB (808 words) - 02:48, 9 March 2018
• Language codes
  ...code. For example, you may wish to create a dictionary for a language not in Apertium repositories. If you invent a new language, or identify a new dial ...ect of the city of London called 'Cockney Rhyming Slang' is a variation on English, mainly substituting nouns. Cockney Rhyming Slang is well-known, but is/was
  4 KB (620 words) - 12:36, 24 January 2017
• Romance languages
  ...ing levels of mutual intelligibility. Many of these languages are included in Apertium already. Romance languages that are not yet covered in [[Apertium]] include [[Aromanian]], [[Arpitan]], [[Corsican]], [[Friulan]],
  18 KB (2,312 words) - 18:25, 18 September 2016
• Bytecode for transfer
  Currently transfer is the bottleneck in Apertium, processing here takes 95% CPU. ...is because the transfer file is being interpreted (tree walking of the XML in the transfer t1x file) instead of being compiled into machine code.
  16 KB (2,276 words) - 10:47, 9 December 2014
• Transfer rules examples
  ...used by the tool ''apertium-transfer''. Writing tags used for [[chunking]] in a 3-stage transfer is not approached there. ...e text not to be translated. For example, HTML tags must not be translated in another language, but only the text of the Web page.
  58 KB (8,365 words) - 20:16, 26 June 2018
• Langues romanes
  [[Romance languages|In English]] * [[English and Portuguese|Anglais et portugais]]
  2 KB (213 words) - 12:37, 7 October 2014
• Chebrolutejasvi/GSOC 2020 proposal: Hindi-Telugu
  E-Mail: tejasvi.chebrolu@research.iiit.ac.in == '''Why is it that I am interested in Apertium?'''==
  9 KB (1,391 words) - 16:41, 31 March 2020
• Lextor
  languages than the ones dealt with in the first stages of the engine, are more cases, and more critical, in which a source language word can
  11 KB (1,814 words) - 03:22, 9 March 2019
• Using Git
  ...s kept in [https://github.com/apertium GitHub]. To browse the repositories in a more compact fashion, ...ode>[[incubator]], [[nursery]], [[staging]]</code> &mdash; these hold work-in-progress modules (mostly language pairs) that have not yet made it into <co
  8 KB (1,173 words) - 20:16, 10 March 2018
• Ideas for Google Summer of Code/Use preferences in pair
  ...n choose between. Before, we had only fixed sets, e.g. British vs American English, which required compiling a new pipeline for each set of preferences. These ...e variation is possible and useful, systematising it, and then enabling it in the language pair by turning hard restrictions into ambiguity and selectors
  2 KB (239 words) - 09:33, 4 March 2024
• Documentation (français)
  [[Documentation|In English]] ''La [[Documentation|version anglaise de cette page]] mentionne les pages de ce wiki disponibles
  2 KB (329 words) - 13:41, 7 October 2014

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