Search results

• Crimean Tatar and Turkish/GSoC Report
  ==Transfer== There are 51 structural transfer rules that take Crimean Tatar constructions and turn them into their Turkis
  4 KB (551 words) - 23:52, 28 August 2017
• Kiel aldoni novan lingvoparon
  ...por substantivoj. Transiraj regulaj dosieroj havas siajn proprajn DTD-on (transfer.dtd) kiujn oni povas trovi en la Apertium-a enpako. Se vi bezonas krei regu <transfer>
  34 KB (5,392 words) - 07:13, 16 February 2015
• Multiwords
  #* <pre>after disambiguation and pre-transfer: ^coffee# with milk<n><sg>$</pre> #* <pre>after disambiguation and pre-transfer: ^coffee# with milk<n><pl>$</pre>
  21 KB (3,521 words) - 05:17, 10 December 2017
• Layouts
  ....af-en.t1x || Afrikaans&mdash;English first stage transfer file (transfer) |apertium-en-af.af-en.t2x || Afrikaans&mdash;English second stage transfer file (interchunk)
  5 KB (583 words) - 11:17, 18 November 2013
• User:Khannatanmai/Alternate stream modification
  ...tial to ensure accurate reordering. These secondary tags are a part of the Lexical Unit. * '''Information availability''': The transfer of information in the Apertium pipeline is largely on a need basis, which m
  10 KB (1,408 words) - 09:25, 17 July 2020
• Norwegian Nynorsk and Norwegian Bokmål/arkiv
  For no er dette gjort med ein spesiell kategori ngen_time_meas i transfer; sidan regelen for ngen_time_meas kjem først i fila, prøver me ikkje meir ...practical problems come when trying to integrate this with disambiguation, transfer and generation in Apertium.
  13 KB (2,051 words) - 10:24, 22 September 2010
• User:SilentFlame/Progress
  * Make lt-proc correctly disperse inline blanks onto each lexical unit until the next <code><nowiki>[</nowiki></code> * Make hfst-proc correctly disperse inline blanks onto each lexical unit until the next <code><nowiki>[</nowiki></code>
  4 KB (695 words) - 20:11, 16 July 2017
• User:Srj31/GSOC 2020 proposal:Bengali-Hindi pair
  Learn more regarding the Apertium dictionaries and tools(transfer rules, CG, anaphora resolution) and look at other language pairs and their Adding verbs, pronouns, conjunctions in the bilingual dictionaries and make lexical selection rules
  12 KB (1,663 words) - 12:53, 31 March 2020
• User talk:Popcorndude/Recursive Transfer
  == Linguistic/transfer phenomena == How do we transfer between these in Turkic?
  11 KB (1,582 words) - 20:16, 9 May 2019
• User:Popcorndude
  ...nance]]. I'm much less certain about similar contributions to monodix. For transfer though you could probably make something that shows the tree that gets buil Tricky things: non-projective stuff? transfer?
  6 KB (972 words) - 18:06, 23 December 2022
• Ambiguity
  * word-sense / lexical selection ambiguity ==Word-Sense / Lexical Selection ambiguity==
  4 KB (620 words) - 18:06, 26 September 2016
• Apertium stream format
  ...s should only appear escaped in the input stream unless they are part of a lexical unit, chunk or superblank. ...e characters <code>^</code> and <code>$</code> are reserved for delimiting lexical units
  6 KB (797 words) - 07:12, 29 March 2022
• VM for transfer
  .../sub> &rarr; ^(lexical_unit)$ || Pops 'N' values from the stack, creates a lexical unit ^...$ with them and pushes the lu back onto the stack | lu-count || - || N/A || [empty] &rarr; number || Pushes the number of lexical units (words inside the chunk) in the rule onto the stack
  14 KB (2,020 words) - 13:58, 7 October 2014
• Linguistic issues for North Saami to Inari Saami machine translation
  === [[sme-smn sátneválljen|Sátneválljen (Lexical selection)]] === === [[Errors in the North Saami transfer component|Transfer]] ===
  3 KB (557 words) - 12:11, 31 March 2017
• User:Pmodi/GSOC 2020 proposal: Hindi-Punjabi/progress
  ...analyzer was picked up from a very nascent state. WER should improve once lexical selection is done on corpus. ===Transfer Rules===
  10 KB (1,507 words) - 10:49, 7 September 2020
• Chunking: A full example
  First a little overview of how 3-stage transfer normally works: * Transfer stage: Words are translated using the bidix and categorized and put into ch
  15 KB (2,237 words) - 12:41, 21 August 2015
• Generating lexical-selection rules from monolingual corpora
  This page describes how to generate lexical selection rules without relying on a parallel corpus. *** <code>-multi</code> which is all the modules after lexical transfer (see apertium-mk-en/modes.xml)
  12 KB (1,634 words) - 18:26, 26 September 2016
• User:Mlforcada/Sandbox/basque
  == Lexical coverage == Lexical coverage may be improved in different ways:
  6 KB (921 words) - 10:21, 19 November 2008
• Task ideas for Google Code-in (2012)
  ...ds. For further information, you can consult the [[How to get started with lexical selection rules|getting started guide]]. || [[User:Francis Tyers|Francis Ty ...ies to a transfer lexicon of your choice. This will involve adding lexical transfer entries, which consist of a translation, and its corresponding grammatical
  14 KB (2,007 words) - 03:06, 27 October 2013
• User:Memduh/GSoC 2017
  ...Crimean Tatar and Turkish. This involves writing and revising transfer and lexical selection rules to the point that the output of the system becomes intellig **Transfer rules
  4 KB (575 words) - 10:03, 16 April 2017

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