Search results

Jump to navigation Jump to search

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

  • ==Transfer rules German->Danish== ===Single word rules German->Danish===
    2 KB (351 words) - 18:50, 30 October 2016
  • # Constraint rules (sensible ones) # Transfer rules
    6 KB (928 words) - 13:57, 3 April 2009
  • Case tags would need to be removed using appropriate transfer rules. This difference in word order would need to be dealt with in transfer rules.
    5 KB (783 words) - 02:36, 16 December 2016
  • ...orphological generator for the target language. Lexical units added in the transfer stage should also have entries in the target language generator. This must ...ode>#</code> mark errors in the lexical transfer, and in the morphological transfer/generation respectively.
    18 KB (2,490 words) - 12:00, 31 January 2012
  • ...orphological generator for the target language. Lexical units added in the transfer stage should also have entries in the target language generator. This must ...ode>#</code> mark errors in the lexical transfer, and in the morphological transfer/generation respectively.
    18 KB (2,493 words) - 08:39, 10 May 2013
  • ...orphological generator for the target language. Lexical units added in the transfer stage should also have entries in the target language generator. This must ...ode>#</code> mark errors in the lexical transfer, and in the morphological transfer/generation respectively.
    18 KB (2,493 words) - 10:59, 30 October 2015
  • ==Derivations: general rules and exceptions== Sámi has a lot of derivation rules. There are various strategies used for translating these:
    10 KB (1,676 words) - 10:53, 16 April 2015
  • ...when there are ''unknown'' proper nouns in the input. One is that transfer rules that work on &lt;np&gt;-tagged words do not apply when the word is unknown. ==Unknown proper nouns in transfer==
    3 KB (492 words) - 16:52, 10 March 2018
  • ...has an [http://apertium.svn.sourceforge.net/viewvc/apertium/trunk/apertium-transfer-tools/example/ example] directory in the source package, which should be th apertium-transfer:
    6 KB (1,022 words) - 08:15, 8 October 2014
  • Some pointers to useful Wiki pages for writing transfer rules: * [[A long introduction to transfer rules]]
    520 bytes (44 words) - 17:12, 20 December 2016
  • Applying forbid and enforce rules... Applying forbid and enforce rules...
    7 KB (1,177 words) - 08:34, 8 October 2014
  • * Transfer ** Multi-stage [[chunk]] transfer
    1 KB (160 words) - 10:44, 23 September 2016
  • .... A lint tester would help people write standard code for dictionaries and transfer files. ...at least check [[lttoolbox]] (dix) dictionary data, perhaps also transfer rules. The [[Apertium New Language Pair HOWTO]] should introduce most of the term
    5 KB (789 words) - 10:36, 31 May 2016
  • <li> "Add 200 words to the bilingual dictionary" or "Add 1 lexical transfer rule" </li> <li> "Add 500 words to the bilingual dictionary" or "Add 10 lexical transfer rules" or "Write a constrastive grammar" or ... </li>
    10 KB (1,668 words) - 02:46, 10 February 2018
  • ...ge to cover more words of the languages. We also need to add more transfer rules to cover all the [https://wiki.apertium.org/wiki/Hindi_and_Bengali/Pending- * <s>Hin > Ben transfer rules on nouns, verbs tenses and adj added.</s>
    4 KB (557 words) - 05:45, 25 August 2021
  • ...rchunk (see "advanced transfer" in the official documentation). Interchunk transfer uses 3 steps and cascaded interchunk uses more than 3. ...ia.org/wiki/Parse_tree Parse tree on Wikipedia]. 1-stage transfer, 3-stage transfer, and n-stage cascaded interchunk are all shallow.
    4 KB (669 words) - 14:12, 6 July 2012
  • ...s from the analyser will have some match in the bidix, and all output from transfer will have some entry in the generator.<ref>Typically this goes for both tra ...certain nouns, and gender is not even present in the source language. The transfer rule expects to have this information; without it, not only will the noun b
    4 KB (679 words) - 16:06, 3 May 2020
  • ...share a prefix ''cant-''. Therefore, both Apertium's tagger and structural transfer assume that the [[lexical form | lexical forms]] corresponding to these [[s ...ed for more languages, we need to modify the part-of-speech tagger and the transfer.
    6 KB (935 words) - 13:49, 21 August 2018
  • ...uzkas evit an anvioù-kadarn. Restroù DTD eo ar restroù reolennoù treuzkas (transfer.dtd) a c'haller kaout e pakad Apertium. Mar fell deoc'h enplementañ ur reo <transfer>
    35 KB (5,602 words) - 07:14, 16 February 2015
  • https://svn.code.sf.net/p/apertium/svn/branches/weighted-transfer/ ...nsfer module from https://svn.code.sf.net/p/apertium/svn/branches/weighted-transfer/apertium/.
    11 KB (1,215 words) - 14:43, 17 April 2018
  • ...cal methods: it takes only two smaller corpora and a dictionary containing rules to conjugate verbs and to match nouns and adjectives. ...nt languages. New language pairs can be added by creating dictionaries and rules containing linguistic data in XML format.
    15 KB (2,339 words) - 00:41, 4 June 2018
  • | Transfer tutorials * How to go from a word-order or agreement difference to a working transfer rule in either formalism
    6 KB (849 words) - 17:59, 25 March 2022
  • ==Transfer== ...constructions and turn them into their Turkish equivalents. Many of these rules cover constructions that are analytic in Qırımtatar and synthetic in Turk
    4 KB (551 words) - 23:52, 28 August 2017
  • ==Transfer== ==== SOV to SVO transfer ====
    14 KB (2,140 words) - 15:42, 30 November 2010
  • Vi anvender 1-trins "shallow transfer" med 17 transferregler. Yderligere oplysninger kan findes i artiklen "Shallow-transfer rule-based
    9 KB (1,406 words) - 20:34, 29 October 2010
  • <transfer default="chunk"> <section-rules>
    24 KB (709 words) - 12:00, 31 January 2012
  • I had to write the transfer rules from scratch, but this also went Apertium documentation; nn-nb uses only one-stage transfer since the
    12 KB (1,886 words) - 12:20, 20 June 2019
  • ...13/08&mdash;19/08 || - || || - || - || Disambiguation and transfer. ...al variants added, some translation mistakes ironed out, a cpl of transfer rules
    6 KB (625 words) - 16:54, 1 July 2013
  • ...tal that people can apply and suggest new words, or new symbols,<br>or new rules but with a interface that guide for end users can do it. === Transfer Rules (Future, only for Post ideas) ===
    4 KB (640 words) - 21:20, 2 April 2009
  • ...ing entries and counting transfer rules, but might be extended to count CG rules as well. It can be run: This will show the count of rules per file, and the entry count per file. It also shows the totals and unique
    12 KB (1,931 words) - 17:06, 24 October 2018
  • Apertium structural transfer rules are currently encoded in XML-based formats. These are very overt and clear, ...rrent XML-based language, allows for a graphical, intuitive editing of the rules, and writes compilable .t1x, .t2x or .t3x files)
    1 KB (162 words) - 01:11, 18 August 2015
  • .... I have worked on adding vocabulary, disambiguation rules in CG, transfer rules and lexical selection. ! CG Rules
    2 KB (335 words) - 10:29, 23 August 2016
  • ...and gold. Expected outputs are what the pipeline should produce, given the rules that have been written whereas gold is what the output would be if the pipe # make changes to dictionaries, transfer rules, etc.
    11 KB (1,823 words) - 12:17, 6 June 2023
  • ...otrebna su nam pravila prevoda za imenice. Pravila prevoda imaju svoj DTD (transfer.dtd), koji se može naći u paketu Apertiuma. Ako treba da implementirate p <transfer>
    26 KB (4,259 words) - 07:00, 16 February 2015
  • ...k the lemmata of verbs that can be used in separable contexts. We then use rules to say for example: ...dealt with either in transfer or pre-transfer. If it was dealt with in pre-transfer,
    8 KB (1,265 words) - 08:11, 2 January 2016
  • ...s may necessitate a change in the lexical form formats that the structural transfer modules deal with. * What happens if new words are added by a structural transfer rule? What should they be equipped with?
    9 KB (1,486 words) - 19:56, 24 March 2020
  • '''Constraint grammar and transfer rules''' ...ifferent lexical meanings based on the grammatical and lexical context. CG rules work both for disambiguation within one part of speech and between words of
    4 KB (570 words) - 18:43, 23 August 2016
  • However, in some cases we might like attributes to be available to transfer that we don't want to put in our morphological analyser or CG. So the idea is that we have a separate file (or it can go in the transfer file), which allows us to define arbitrary attributes and have them filled
    2 KB (318 words) - 12:25, 5 February 2014
  • | <code>apertium-sme-fin.sme-fin.dix</code> || Transfer lexicon / Bilingual dictionary || | <code>fin-sme.autobil.bin</code> || Compiled transfer lexicon ||
    16 KB (2,457 words) - 08:19, 12 April 2017
  • ...vernance" often mismatches between the the two languages, so some transfer rules will be required. ...st up the coverage - they seem to be quite frequent!) and work on transfer rules if they are needed.
    8 KB (1,205 words) - 21:50, 19 July 2012
  • ==Editing XML (dix, transfer rules) in vim==
    2 KB (359 words) - 16:00, 2 January 2021
  • ==Transfer rules==
    2 KB (248 words) - 13:34, 10 December 2010
  • * Write transfer rules for function words * Write transfer rules for nominals
    4 KB (423 words) - 17:08, 14 June 2018
  • ...hrase co-ordinators from noun phrase co-ordinators lets you write transfer rules to merge two co-ordinated NPs. ...nting part of it can prove useful in writing transfer or lexical selection rules.
    7 KB (922 words) - 08:16, 8 October 2014
  • ...th the Ordbank, and the constraint grammar, and wrote a series of transfer rules. ...en another week converting the Oslo-Bergen tagger. Three weeks on transfer rules, and then another three weeks expanding the dictionaries. Two weeks were th
    12 KB (1,679 words) - 12:00, 31 January 2012
  • ...th the Ordbank, and the constraint grammar, and wrote a series of transfer rules. ...en another week converting the Oslo-Bergen tagger. Three weeks on transfer rules, and then another three weeks expanding the dictionaries. Two weeks were th
    12 KB (1,683 words) - 08:42, 10 May 2013
  • ===Visual interface for editing transfer rules===
    2 KB (200 words) - 08:21, 13 January 2015
  • ...th the Ordbank, and the constraint grammar, and wrote a series of transfer rules. ...en another week converting the Oslo-Bergen tagger. Three weeks on transfer rules, and then another three weeks expanding the dictionaries. Two weeks were th
    12 KB (1,683 words) - 11:00, 30 October 2015
  • ...k. Use the relations GF returns (all of which are hard-coded for different rules). Bonus: use closely related language treebanks in UDPipe; transfer the lemmas, assume the POS tags remain the same (reasonable assumption). Us
    4 KB (657 words) - 08:58, 3 April 2017
  • ===Transfer rules=== Adding to section <section-rules>
    2 KB (240 words) - 09:55, 24 April 2018
  • ...s also contained in the transducers generated by <code>apertium-preprocess-transfer</code>. ...e rules which generate different output in different situations as well as rules which generate multiple outputs, the simplest way do deal with them is to t
    3 KB (525 words) - 06:12, 1 June 2023
  • | 142 || apertium-preprocess-transfer doesn't allow DOCTYPE declaration.... | 140 || apertium-transfer -b outputs tl tag when asked for sl tag if sl tag empty...
    12 KB (1,254 words) - 22:08, 7 March 2018
  • ...', but it's un- or under-documented how this should be done using apertium-transfer. <transfer default="chunk">
    2 KB (209 words) - 11:06, 24 March 2012
  • ==Transfer== * [[A long introduction to transfer rules]]
    2 KB (182 words) - 08:35, 16 May 2013
  • This page provides general documentation on the transfer rules used in the Romanian-Catalan pair. The tables are generated from the data a === Extra transfer (T4X) ===
    14 KB (1,989 words) - 10:06, 28 November 2018
  • The t2x rules may have completely "correct" blank handling in that they output all input # Transfer modules have to treat the inline-blanks differently from other superblanks
    10 KB (1,676 words) - 18:32, 21 June 2020
  • [[VM for transfer|In English]] | align=center | Header || <code>#<assembly><br /> #<transfer default="chunk"></code> || align=center | ---- || Cette section établit le
    14 KB (2,144 words) - 14:05, 7 October 2014
  • ...pertium-preprocess-transfer (or make), then you can check out the relevant rules by doing e.g. (exchanging apertium-dan-nor.nor-dan.t1x for your transfer file)
    1 KB (187 words) - 19:29, 13 December 2016
  • Lexical transfer: Lexical selection rules:
    6 KB (412 words) - 23:31, 31 January 2020
  • ...0]. We would like linguists to be able to fearlessly write recursive (rtx) rules based on what makes linguistic sense, and have rtx-proc/rtx-comp deal with ...Google_Summer_of_Code/Robust_recursive_transfer]] The first GsoC recursive transfer project
    1 KB (211 words) - 09:22, 6 February 2024
  • ...ning corpus by taking into account the patterns detected by the structural transfer module, and translates to the target language all possible disambiguation p ...ansfer rules (right now, it only "understands" one-level, shallow-transfer rules).
    2 KB (260 words) - 19:55, 24 March 2020
  • ..., CG performance, regression and pending tests targeted mainly at transfer rules, a “gold standard” parallel corpus to measure the WER and to always hav * transfer
    4 KB (603 words) - 21:20, 31 August 2015
  • apertium-transfer $DATA/trules-$DIRECTION.xml $DATA/trules-$DIRECTION.bin $AUTOBIL |\ apertium-transfer $DATA/$DIRECTION.t1x $DATA/$DIRECTION.t1x.bin $DATA/$DIRECTION.autobil.bi
    12 KB (1,625 words) - 08:20, 8 October 2014
  • 2. The current .twol file is empty. Need to add all the morphographemic rules to it. ...ive clause appear.There are few transfer rules in the bidix. More transfer rules need to be added to all .t1x .t2x and .t3x files.
    4 KB (669 words) - 14:42, 13 August 2018
  • ...will involve working with dictionaries, lexical selection rules, transfer rules, scripting, corpora. The objective is to facilitate the generation of varie ** Add all the words, and cover all the structures with transfer rules.
    2 KB (377 words) - 19:18, 25 January 2023
  • Recursive transfer bytecode files are written using <code>Lttoolbox/compression.h</code>. The Number of input-time rules
    10 KB (1,387 words) - 06:09, 1 June 2023
  • ...analyser for turkish, a generator for Azerbaijani, a bidix and a set of CG rules. ; Rules
    7 KB (1,091 words) - 18:40, 25 August 2011
  • ...tionary case and there is no need to track the proper placement of case in transfer. ...capitalization of the target language surface forms according to a set of rules whose format is described below.
    7 KB (1,042 words) - 19:44, 4 March 2024
  • ...cy wykorzystuje słowniki oraz płytkie reguły transferowe (shallow transfer rules). Zasadniczą różnicą pomiędzy głębokimi i płytkimi zasadami jest to ...lementowanie zasad dla rzeczowników. Pliki tego typu posiadają własne DTD (transfer.dtd) znajdującym się w pakiecie Apertium. Gdy zaistnieje potrzeba zaimple
    36 KB (5,643 words) - 07:04, 16 February 2015
  • ...d as definite. One way of dealing with this is a lot of rules and lists in transfer, but those are hard to do. So, how about looking at a corpus for informatio ...ream processor (see [[Apertium stream format]]) for the output of apertium-transfer (both default/chunk possibilities) that parses character by character.
    2 KB (262 words) - 11:19, 9 February 2015
  • * transfer rules as constraints (dank idea): ** es-ca will have a (structural) transfer rule X
    1 KB (203 words) - 12:56, 29 January 2018
  • ...ictionaries, improving disambiguation, and writing new structural transfer rules. ...frequently mistranslated and that can be easily repaired with a structural transfer rule
    2 KB (213 words) - 19:48, 24 March 2020
  • ...y in a way which shows that there is a decision to be made in the transfer rules where the lexical information of the word doesn't directly allow a decision ...module. These tags must be changed into these others in the output of the transfer module:
    2 KB (334 words) - 07:45, 8 October 2014
  • The '''bilingual dictionary''' (also known as '''bidix''' and '''transfer lexicon''') contains translation between two languages. It is one of the ma ...you will find some notes on how to work with bilingual dictionaries (or ''transfer lexica'') in Apertium, they aren't complete but should give an overview of
    7 KB (1,244 words) - 16:41, 17 March 2018
  • ...n-line'' because of the high failure rate, due to either disambiguation or transfer, just incomplete entries. apertium-transfer /home/fran/local/share/apertium/apertium-is-en/apertium-is-en.is-en.t1x /h
    9 KB (1,470 words) - 11:28, 24 March 2012
  • ...rs for each language, and then making individual dictionaries and transfer rules for every pair. The current status of these goals is listed below. ...th the addition of a [[Constraint Grammar|CG]] for language X and transfer rules / dictionary for the pair X→Y. Below is listed development progress for e
    32 KB (3,684 words) - 06:16, 28 December 2018
  • ...translation quality. This will involve working with dictionaries, transfer rules, scripting, corpora. The objective is to make an Apertium language pair sta ** Add all the words, and cover all the structures with transfer rules.
    2 KB (383 words) - 19:46, 2 March 2023
  • <spectie> --- maybe make LRX rules for the differences described on the wikipedia page http://en.wikipedia.org * transfer, and transfer examples in both directions (Hrvoje)
    2 KB (223 words) - 15:58, 23 April 2013
  • ...rs for each language, and then making individual dictionaries and transfer rules for every pair. The current status of these goals is listed below. ...th the addition of a [[Constraint Grammar|CG]] for language X and transfer rules / dictionary for the pair X→Y. Below is listed development progress for e
    22 KB (2,532 words) - 11:36, 30 July 2018
  • ...rs for each language, and then making individual dictionaries and transfer rules for every pair. The current status of these goals is listed below. ...th the addition of a [[Constraint Grammar|CG]] for language X and transfer rules / dictionary for the pair X→Y. Below is listed development progress for e
    22 KB (2,520 words) - 23:09, 22 December 2014
  • ...rs for each language, and then making individual dictionaries and transfer rules for every pair. The current status of these goals is listed below. ...th the addition of a [[Constraint Grammar|CG]] for language X and transfer rules / dictionary for the pair X→Y. Below is listed development progress for e
    19 KB (2,201 words) - 09:21, 9 December 2019
  • ...used to discard possible analysis of the word, according to the following rules: ...less it is decided not to do so. The case can be changed in the structural transfer module; this option is useful, for example, when there is a reordering of w
    5 KB (801 words) - 07:13, 8 October 2014
  • =Malayalam Sandhi Rules Implementation(Handling agglutination )= =Transfer Rules=
    14 KB (1,774 words) - 15:47, 18 August 2014
  • This should be fairly straightforward, then we write rules that say "Choose the feminine possessive when the noun that follows is subj * <code>apertium-ga-gd.pre-<math>x</math>.t1x</code> &mdash; Transfer rules which add tags defining the mutation to the beginning of words which should
    6 KB (1,000 words) - 07:12, 8 October 2014
  • ...ertium-kaz-rus]. It contains only the kaz→rus direction, recycled transfer rules from tat–rus,  and a few words in the dictionary, but the KazNU team has Transfer rules in tat-rus require the addition of some paradigms to bilingual dictionary e
    1 KB (228 words) - 18:24, 19 August 2017
  • ...rs for each language, and then making individual dictionaries and transfer rules for every pair. The current status of these goals is listed below. ...th the addition of a [[Constraint Grammar|CG]] for language X and transfer rules / dictionary for the pair X→Y. Below is listed development progress for e
    10 KB (1,263 words) - 06:04, 23 December 2014
  • '''Transfer rules (Romanian to Catalan):''' 118 (T1X), 7 (T2X), 1 (T3X) '''Transfer rules (Catalan to Romanian):''' 33 (T1X), 5 (T2X), 1 (T3X), 1 (T4X)
    538 bytes (72 words) - 10:08, 28 November 2018
  • ...rs for each language, and then making individual dictionaries and transfer rules for every pair. The current status of these goals is listed below. ...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
    12 KB (1,308 words) - 19:27, 27 August 2017
  • ...rs for each language, and then making individual dictionaries and transfer rules for every pair. The current status of these goals is listed below. ...th the addition of a [[Constraint Grammar|CG]] for language X and transfer rules / dictionary for the pair X→Y. Below is listed development progress for
    35 KB (3,577 words) - 15:24, 1 October 2021
  • ...rs for each language, and then making individual dictionaries and transfer rules for every pair. The current status of these goals is listed below. ...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
    9 KB (987 words) - 23:25, 22 December 2014
  • ...own words will give a better indication of "best-case" working of transfer rules. (Stats pages currently do not show number of CG or transfer rules.)
    9 KB (1,233 words) - 09:10, 21 November 2021
  • ...rs for each language, and then making individual dictionaries and transfer rules for every pair. The current status of these goals is listed below. ...th the addition of a [[Constraint Grammar|CG]] for language X and transfer rules / dictionary for the pair X→Y. Below is listed development progress for e
    20 KB (2,336 words) - 18:10, 14 April 2015
  • ...rs for each language, and then making individual dictionaries and transfer rules for every pair. The current status of these goals is listed below. ...th the addition of a [[Constraint Grammar|CG]] for language X and transfer rules / dictionary for the pair X→Y. Below is listed development progress for
    12 KB (1,017 words) - 09:06, 18 January 2022
  • * Making constraint grammar rules more CG-like * Write rules to do initial mutations for generation.
    2 KB (381 words) - 09:59, 8 May 2011
  • ...nd finally emit an epsilon symbol as flag diacritics defined by constraint rules do, or process the input and output the transducer's computation. ...at makes possible to avoid the possibly infinite definition of not regular rules in a dictionary to work with more complex forms of inflection.
    6 KB (842 words) - 06:41, 20 October 2014
  • ...separate lexcs and twols (.lat and .cyr) with the continuation lexica and rules and all, though you may be able to get by with one twol considering how sim ...ambiguation rules to be as script-agnostic as possible. For word-specific rules, make a version for each script?
    4 KB (601 words) - 17:49, 8 March 2018
  • * Constraint grammar of Tatar containing at least 1000 rules, which makes 90-95% of all words unambiguous, with at least 95% retaining t |colspan="4" style="text-align:center"| transfer rules for pending wiki tests (focus on phrases and clauses, not single words)
    8 KB (1,006 words) - 12:48, 9 March 2018
  • |Sranan rlx rules |Sranan-English t1x rules
    4 KB (543 words) - 21:59, 3 September 2017
  • ...yntax to other Apertium modules (dictionaries, lexical selection, transfer rules, etc). ...] could be used as reference implementation, as it handles similar type of rules, but it looks to the source language (left part) to decide over the target
    1 KB (234 words) - 19:48, 24 March 2020
  • ** Number of disambiguation rules ** Number of lexical selection rules
    2 KB (246 words) - 02:32, 1 June 2019

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