Search results

• Constraint-based lexical selection module
  '''apertium-lex-tools''' provides a module for compiling lexical selection rules and processing them in the pipeline. Rules can be manually ==Lexical transfer in the pipeline==
  19 KB (2,820 words) - 15:26, 11 April 2023
• Narimann/GSOC 2019 proposal: Kazakh-Turkish and Turkish-Kazakh
  * Write new transfer rules * Write constraint-based lexical selection
  8 KB (1,094 words) - 13:10, 14 April 2019
• Ideas for Google Summer of Code
  | rationale = Apertium-separable is a newish module to process lexical items with discontinguous dependencies, an area where Apertium has traditio ...n two existing language modules, focusing on the dictionary and structural transfer
  23 KB (3,198 words) - 09:15, 4 March 2024
• Testvoc
  ...it just expands an {{sc|sl}} dictionary, and runs each possibly analysed [[lexical form]] through all the translation stages to see that for each possible inp ...-quality language pair also needs testvoc on phrases consisting of several lexical units. Often one can find a lot of the errors by running a large corpus (wi
  9 KB (1,400 words) - 22:30, 18 January 2021
• User:Kamush/GSoC2021ProgresReport
  * Started sample Lexical selection rules; |Focus on transfer rules
  10 KB (1,179 words) - 11:51, 31 August 2021
• User:Lylax2/proposal2017
  ...ikit-learn, lxml, Django), R, Octave, Bash, Matxin(Apertium with syntactic transfer), Javascript(Jquery, D3) ...h as google translate, still make basic easily correctable grammatical and lexical errors.
  10 KB (1,554 words) - 08:37, 4 April 2017
• Ideas for Google Summer of Code/Automatic blank handling
  ...formatting / superblanks interacts with word/chunk reordering in Apertium. Transfer rules can reorder words, but never look at the tags themselves, and have no ...in the input to a transfer rule are always output before the output that a transfer rule gives; so a <p> will never be moved around by a rule.
  8 KB (1,364 words) - 12:15, 14 May 2017
• User:Hectoralos/GSOC 2020 proposal: French-Arpitan
  ...system of structural transfer in three steps. I consider the new recursive transfer very promising, and I indeed want to use in the new version of the French-C * Lexical selection rules
  14 KB (2,071 words) - 12:46, 30 March 2020
• User:Rafi kamal/Application
  ...for disambiguation of bidix output. These rules will be used by Apertium's lexical selection module. ==== 4. Adding transfer rules ====
  10 KB (1,432 words) - 10:24, 15 May 2014
• User:Quirille/GSOC proposal 2014
  Prototype recursive transfer implementations ...hance the transfer module in Apertium by adding a support of the recursive transfer rules.
  6 KB (948 words) - 19:03, 21 March 2014
• User:Khannatanmai/Wordbound blanks
  == Transfer ([https://github.com/apertium/apertium/pull/90 Pull Request 1], [https://gi === Chunker/Single-stage transfer ===
  13 KB (2,173 words) - 09:52, 30 August 2020
• English and Kazakh
  ** write lexical selection to generate "yesh-" forms from "any-" forms in negatives or "bir" ***lexical selection for "anything" as "yeshnarse" for negative sentences and as "bir
  20 KB (2,856 words) - 06:26, 27 May 2021
• Talk:Morphological dictionary
  ...ical processing systems, one of the tasks is the construction of efficient lexical processors from linguistic data. ...hological analysis and generation, along with word-for-word translation of lexical forms.
  18 KB (2,967 words) - 19:24, 11 December 2012
• Task ideas for Google Code-in
  |title=expand coverage of Kyrgyz to English structural transfer ...bilingual dictionary is not fully (or correctly) parsed by the <tt>kir-eng-transfer</tt> Apertium mode. Determine what rule(s) need(s) to be added (or fixed)
  32 KB (4,862 words) - 06:23, 5 December 2019
• User:Firespeaker/Steps for writing a language pair
  === Lexical Selection === ...xt level of problem, once you've chosen the correct morphological form, is lexical selection. The sort of problem this best solves is when you have one stem
  10 KB (1,721 words) - 07:55, 20 May 2013
• Quick and dirty guide addendum: other important things
  === Lexical Selection === ...xt level of problem, once you've chosen the correct morphological form, is lexical selection. The sort of problem this best solves is when you have one stem
  10 KB (1,615 words) - 07:43, 20 December 2015
• The quick and dirty guide to making a new language pair
  ...rules is detected in the source language text, Apertium will follow these transfer rules to create a grammatical translation in the target language. If this works, great! We move on to the next section: The addition of transfer rules.
  19 KB (3,164 words) - 20:58, 2 April 2021
• User:Marcriera/proposal
  ...ia articles and public domain books will be used. However, as the existing transfer rules lack any kind of organization, code refactoring will be absolutely ne ...e applies to constraint grammar; most of the new rules will be transfer or lexical selection rules, but some CG rules might be needed.
  13 KB (1,713 words) - 13:05, 29 May 2017
• User:Khannatanmai/GSoC2020Proposal Trimming
  ...as context for lexical selection and analysis of the input. Also, several transfer rules don't match as the word is shown as unknown. There are several other ...er, transfer rules would still suffer as there would be no analysis in the lexical unit.
  30 KB (4,918 words) - 16:55, 31 March 2020
• User:Lguyogiro/GSoC2023Proposal
  ...s for both, so I'm interested in developing the bilingual dictionaries and transfer rules. This would really nice to have, especially since speakers of both la * Lexical selection and transfer rules for nhi-azz and azz-nhi
  9 KB (1,296 words) - 17:42, 4 April 2023

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