Search results

There is a page named "Transfer rules" on this wiki. See also the other search results found.

• Ideas for Google Summer of Code/Add weights to lttoolbox
  # lexical transfer # structural transfer
  5 KB (816 words) - 02:32, 13 February 2018
• Constructions
  ...ok really like multiword expressions, other times they look like syntactic transfer, most of them have probably have some kind of fixed lexical element. ...sy to translate word-for-word, but also quite annoying to have in transfer rules.
  1 KB (207 words) - 07:51, 9 October 2014
• Sorani/Verbs
  ...tax in analysis, the clitics could simply be output in order, and transfer rules written accordingly. ...best to have the same pattern output regardless of clitic, for the sake of transfer. The third person singular as object is implied when there is no pronominal
  2 KB (357 words) - 12:40, 1 October 2016
• Google Summer of Code/Application 2019
  To transfer to the application Apertium is a shallow-transfer machine translation system, which uses finite state transducers for all of
  8 KB (1,230 words) - 06:02, 5 February 2019
• Weights in the pipeline
  transfer: Maybe transfer could combine them and output a single one.
  2 KB (307 words) - 14:29, 22 June 2020
• Incorporating guessing into Apertium
  * Bilingual transfer For the bilingual transfer things are more difficult, but one could imagine using techniques such as t
  4 KB (558 words) - 13:07, 26 June 2020
• Google Summer of Code/Application 2020
  To transfer to the application Apertium is a shallow-transfer machine translation system, which uses finite state transducers for all of
  8 KB (1,248 words) - 15:51, 17 February 2021
• Slovenian and Spanish
  * Think of rules to fix frequent disambiguation problems ;Slovenian→Spanish transfer
  4 KB (472 words) - 16:41, 7 June 2011
• Apertium-viewer
  * The tool validates XML dictionary and transfer files. * Support for trace of transfer/interchunk - with links to the applied rules - also works for online modes
  10 KB (1,606 words) - 20:54, 20 February 2022
• Kazakh and Russian/Pending tests
  # fix tags of "be" in transfer # transfer rules to get tags from beAdjVerb to new be{{tag|v}}
  14 KB (567 words) - 20:03, 24 March 2020
• Apertium-recursive/Cookbook
  This page is intended to be a collection of solutions to common transfer problems. It is sorted vaguely be complexity, so it could potentially also These rules will match a determiner, 0 or more adjectives, and a noun and make all the
  3 KB (428 words) - 06:11, 1 June 2023
• Setting up a build environment for a language pair
  ** Transfer rule files You need a <code>Makefile.am</code> which contains the build rules, and a <code>configure.ac</code> which contains the dependencies.
  972 bytes (144 words) - 12:09, 26 September 2016
• ReTraTos
  ...s useful for machine translation (MT): bilingual dictionaries and transfer rules. The induction systems and open linguistic data can be used with the [[Aper ...bilingual resources from aligned parallel corpora: application to shallow-transfer machine translation]". ''Machine Translation''
  8 KB (1,273 words) - 09:32, 3 May 2024
• English and Kazakh/Pending tests
  # fix tags of "be" in transfer # transfer rules to get tags from beAdjVerb to new be{{tag|v}}
  8 KB (741 words) - 03:41, 4 September 2017
• Parallel corpus pruning
  ...ated aligned segments. Ony of the obstacles to inducing effective transfer rules from parallel corpora is lack of literalness in translation. For example, f When making rules, we're more interested in "literal" translations, so for example:
  2 KB (392 words) - 13:47, 18 March 2009
• Kyrgyz and Kazakh
  ...aries (<code>.lexc</code> and <code>.twol</code> files) and disambiguation rules (<code>.rlx</code> files) are no longer kept in the bilingual module, and s ...x</code>, lexical selection is in the <code>.lrx</code> file, and transfer rules are in the <code>.t1x</code> and <code>.t2x</code> files.
  3 KB (304 words) - 01:51, 10 March 2018
• Apertium-kaz-kir/TODO
  ** Add lexical selection rules and transfer rules as needed
  2 KB (243 words) - 21:22, 19 August 2015
• Apertium Turkic
  ...ang2015-rakhimova.pdf Study of the problem of creating structural transfer rules and lexical selection for the Kazakh-Russian machine translation system on ...pertium-turklang-2015-papers/turklang2015-karibayeva.pdf Lexical selection rules for Kazakh-to-English machine translation in the free/open-source platform
  13 KB (1,710 words) - 20:32, 30 August 2018
• English and Catalan/Transfer Rules
  This page provides general documentation on the transfer rules used in the English-Catalan pair. The tables are generated from the data an |Adds 'més' before an adjective in comparative or superlative form (for rules with two adjectives).
  45 KB (7,840 words) - 10:56, 18 September 2017
• User-based chunking
  ...ven a default tag, a tag determined by a classifier or a tag determined by rules. after apertium-transfer:
  2 KB (356 words) - 21:15, 21 June 2020
• Ideas for Google Summer of Code/Adopt a language pair
  ...nvolve writing linguistic data, including morphological rules and transfer rules — which are specified in a declarative language. A good intro would be to
  6 KB (1,024 words) - 15:22, 20 April 2021
• Dialectal or standard variation
  strip tags, so after disambiguation with the following rules: ...ix and parametrized dictionaries]] on ''variants'' in monodix and transfer rules (not quite relevant any longer; most of the xslt features have been built i
  14 KB (2,355 words) - 10:33, 1 November 2022
• Iranian Persian and Tajik
  ...ved by means of a number of transfer rules. We can probably generate these rules by enumerating a large number of possible combinations of noun phrases and
  1 KB (161 words) - 05:46, 13 January 2013
• Documentation
  * [[Preparing to use apertium-transfer-tools]] * [[How to get started with lexical selection rules]]
  5 KB (599 words) - 19:04, 17 February 2020
• Google Summer of Code/Application 2016
  ...mproving the engine, improved source-language analysis, improved bilingual transfer, new end-user application, improve existing end-user application, easing la ...k will be frozen and we will report to Google, to proceed according to the rules of GSoC.
  10 KB (1,500 words) - 16:23, 18 February 2016
• LRLM
  ...al transfer, so if input is a determiner followed by a noun, and there are rules for "det", "n", and "det n", the "det n" rule will match.
  728 bytes (109 words) - 08:20, 24 February 2023
• Macedonian and Bulgarian
  16th August: Implement transfer rules in both directions based
  2 KB (208 words) - 16:53, 17 June 2010
• Sorani
  This could make for a number of good transfer rules. ''Para'''t''' haya'' -> You have money. The pattern would be like nominal<
  5 KB (855 words) - 19:23, 27 August 2017
• Romance languages
  ...for X→Y translation with the addition of a CG for language X and transfer rules / dictionary for the pair X→Y. Below is listed development progress for e
  18 KB (2,312 words) - 18:25, 18 September 2016
• PMC proposals/Move Apertium to Github
  ...an, sme, …) don't get testvoc problems, and possibly change their transfer rules/bidixes (and in some cases the easiest way is to update all the other other
  22 KB (3,325 words) - 14:06, 12 March 2018
• Bengali and English/Transfer Postchunk
  === Rules === ''Comment'' : just transfer the lexical unit
  323 bytes (27 words) - 16:41, 15 August 2011
• Evalution kaz-tur Machine Translation System
  ...ranslation output by the structural-transfer module to see if the applying rules with new apertium were better or worse than the old apertium. We found out
  2 KB (348 words) - 10:16, 24 October 2018
• Ambiguity
  ...pens after bidix lookup (word-translation), but before structural transfer rules. See [[Lexical selection]] for more information.
  4 KB (620 words) - 18:06, 26 September 2016
• Lttoolbox/weights
  * Having zero-context rules in your .lrx files. Now you can just put the weights directly in your bilin ...efault translation as "1.0" and then all others as >1.0 ... because of how transfer works, it will always take the first, which will be the one with the lowest
  2 KB (353 words) - 09:32, 30 January 2019
• Fragmentation
  [[Category:Writing transfer rules]]
  4 KB (706 words) - 07:05, 8 October 2014
• Google Summer of Code/Application 2021
  Apertium is a primarily shallow-transfer machine translation system, which uses finite state transducers for all of ...k will be frozen and we will report to Google, to proceed according to the rules of GSoC.
  10 KB (1,480 words) - 07:00, 23 February 2021
• Fragmentation : un exemple complet
  [[Category:Writing transfer rules]]
  16 KB (2,435 words) - 07:05, 8 October 2014
• Google Summer of Code/Application 2008
  ...data to induce the part-of-speech tagger and an initial set of translation rules from monolingual and bilingual corpora.
  8 KB (1,255 words) - 19:50, 12 April 2021
• Ideas for Google Summer of Code/Plain-text formats for Apertium data
  ...r to avoid having to write structural transfer (i.e., .t1x, .t2x and .t3x) rules in raw XML which is very overt and clear, but clumsy and hard to write. Bef
  2 KB (324 words) - 11:37, 16 February 2016
• Google Summer of Code/Application 2009
  ...data to induce the part-of-speech tagger and an initial set of translation rules from monolingual and bilingual corpora.
  10 KB (1,543 words) - 19:50, 12 April 2021
• Kazakh and Turkish/Verbs
  ==Transfer rules==
  2 KB (258 words) - 20:15, 5 February 2017
• Quality control
  ** [[Regression test]]s – "isolated" tests of transfer rules
  623 bytes (82 words) - 23:23, 23 July 2021
• Tagger training
  You can also write lexical rules, so for example in Afrikaans, the word "deur" is ambiguous, one meaning is (Clarification: it only works with ''one-stage transfer'', so Apertium 3 pairs which only have t1x can still use it.)
  7 KB (1,058 words) - 07:37, 4 July 2016
• Languages of Central Asia
  ...rs for each language, and then making individual dictionaries and transfer rules for every pair. The current status of these goals is listed below.
  6 KB (595 words) - 23:13, 22 December 2014
• Kazakh and Sakha/GSoC2018 report
  * Add transfer rules, etc.
  2 KB (233 words) - 07:41, 14 August 2018
• German to English
  : should be possible to make transfer rules like "NP sein am V.inf" => "NP be V.progressive"
  3 KB (442 words) - 00:36, 5 January 2013
• File names
  * XXX-YYY.t1x.bin :: the compiled transfer rules (stage 1 / chunking, or the only stage if no chunking used) when translatin
  890 bytes (126 words) - 10:10, 14 March 2017
• Apertium stream format
  ...blob/master/apertium/stream_entities.py https://github.com/krvoje/apertium-transfer-dsl/blob/master/apertium/stream_reader.py ...rtium stream format by declarative Esrap[https://github.com/scymtym/esrap] rules.
  6 KB (797 words) - 07:12, 29 March 2022

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