Search results

=== Using a Linguistic Resources Document === You can define a [[Linguistic Resources Document]] (LRD) and use it to indicate which dictionaries will b

This page is a translation from Spanish into English of most of the documentation of [[Matxin]] with some minor ...on can be found [http://matxin.svn.sourceforge.net/viewvc/matxin/trunk/doc/documentation-es.pdf here]. This page does not describe how to install or use Matxin, for

...stic Resources Document''' (LRD) is an XML document consisting of a set of linguistic resources (dictionaries, cross models, corpora, links to other LRDs, etc.). ** '''lrd''': link to Linguistic Resource Document.

=== Linguistic Resources Document === Finally, a document with references to the linguistic resources needed.

This is a guide on how to add linguistic data directly to an existing language pair in Apertium. It gets a bit techn Apertium has data for many languages pairs. These linguistic data include mainly dictionaries (monolingual and bilingual), structural tr

==Collecting linguistic data== Before these files can be produced, you need a collection of linguistic data which can be inserted into them. This data might consist of wordlists

Here you will find the documentation for the Anaphora Resolution module created during the Google Summer of Code :'''Anaphor:''' A linguistic unit that refers to an earlier linguistic unit in discourse.

...Language Engineering ([http://www.prompsit.com http://www.prompsit.com]). Linguistic data are being developed by Transducens, the Seminario Current versions of the engine, linguistic data and documentation can be found on our SourceForge project page ([http://www.sf.net/projects/a

If you edit the linguistic data, do not forget to type "make" to update, and "sudo make install" to in ===Compiling all the linguistic data===

[[Documentation (français)|En français]] ...rtium.org/w/images/d/d0/Apertium2-documentation.pdf Apertium 2.0: Official documentation] (222 pages)'''

[https://wiki.apertium.org Apertium's wiki] and other documentation are out of date, poorly organized, not visible enough, and just plain not u ..., to our best how-to guides reflecting how things were done a decade ago. Documentation is scattered between the Apertium wiki, individual GitHub repos, an out-of-

| [[Linguistic Resources Document]] | [[Using linguistic resources]]

* {{sc|documentation}}: Tasks related to creating/editing documents and helping others learn mor | {{sc|documentation}}, {{sc|quality}} || test and document init scripts for [[apertium-apy]] ||

...y the syntactic or morphological behaviour of the word in question. Common linguistic categories include noun and verb, among others. There are open word classes [[Category:Documentation in English]]

...list, I will make these two pairs work stably in that direction, given my linguistic knowledge. Choosing from the given tasks, this task is more related to 1.2 * Documentation

...the details. Here is an example in which I'm deliberately not going to use linguistic names for the different parts, to try and avoid assumptions. ...(Confusingly, tags can be {{xtag|XML}} tags like the above or they can be linguistic tags in the input like {{tag|adv}}, both types surrounded by < and >;

...module allows weighing the rules to guess at a translation (this is crazy linguistic programming, but the option is there). ...age can be used by itself, ignoring the following two 'chunker' stages. In documentation this is called 'shallow transfer'. However, as Apertium has developed, a mo

# tools to manage the linguistic data necessary to build a machine translation system for a given language p # linguistic data for a growing number of languages and language pairs

...bilingual dictionaries and transfer rules. The induction systems and open linguistic data can be used with the [[Apertium]] toolbox to build open-source MT syst [[Category:Documentation in English]]

Language pairs can now have any number of linguistic or stylistic preferences that the user can choose between. Before, we had o == Documentation about preference variation ==

==From the documentation== linguistic data are compiled these dictionaries are pre-processed, so

The same applies for other linguistic phenomena. Linguists tend to focus [[Category:Documentation]]

| 64 || Apertium-tolk should give proper warning when no linguistic data is installed || 2008-03-31 || Wynand [[Category:Documentation]]

...of the surrounding words, searching for those which might have some useful linguistic information. For example, a determiner might mark the gender of a form in t [[Category:Documentation]]

...ile the required language-pair data follow the instruction provided at the linguistic package itself. Usually you only need to type <code>./configure</code> and [[Category:Documentation]]

...r are generated from a format specification in XML. Rules for format, like linguistic data, are specified in XML, and they contain regular expressions with flex [[Category:Documentation]]

...hich specify which programs should be run and in what order. Normally each linguistic package has one of these files which specifies various ways in which you ca [[Category:Documentation]]

=== Linguistic data === ! documentation

<li>To favour the interchange and reuse of existing linguistic data.</li> <li>Developers are volunteers who are contributing time, code, documentation, or resources to Apertium. A developer that makes sustained, welcomed contr

Here is a list of current language pair (linguistic package) maintainers. [[Category:Documentation in English]]

The task is to catalogue as many of the available linguistic resources as possible. Dictionaries, grammars, accademic papers, etc., are [[Category:Documentation]]

* linguistic grammars of the language [[Category:Tasks_for_Google_Code-in|Documentation of resources]]

[[Category:Linguistic documentation]]

...e engine, and have a look at the ''[[Incubator]]'' if you're interested in linguistic issues. If you can't find anything that interests you or piques your intere [[Category:Documentation in English]]

[[Using linguistic resources|In English]] [[Category:Documentation en français]]

...e engine, and have a look at the ''[[Incubator]]'' if you're interested in linguistic issues. If you can't find anything that interests you or piques your intere [[Category:Documentation in English]]

[[Linguistic Resources Document|In English]] [[Category:Documentation en français]]

Each linguistic package contains a <tt>modes.xml</tt> file, which specifies which programs [[Category:Documentation in English]]

...task of automatic interpretation of nominal phrases and compounds: A cross-linguistic study." ''Computational Linguistics'' 35, no. 2 (2009): 185-228.] [[Category:Documentation in English]]

[[Category:Linguistic documentation]]

...piling <code>RL</code> usually creates a ''generator''.<ref>In all current linguistic packages, the left-to-right direction of compilation is ''analysis'', where [[Category:Documentation in English]]

<li>To favour the interchange and reuse of existing linguistic data.</li> <li>Developers are volunteers who are contributing time, code, documentation, or resources to Apertium. A developer that makes sustained, welcomed contr

German-English bilingual dictionary (>216,000 entries), generated from linguistic data (GPL Version 2 or later) available for [http://www-user.tu-chemnitz.de [[Category:Documentation in English]]

<li>To favour the interchange and reuse of existing linguistic data.</li> <li>Developers are volunteers who are contributing time, code, documentation, or resources to Apertium. A developer that makes sustained, welcomed contr

This could be extended to other linguistic data files such as structural transfer files (.t1x, .t2x, etc.). The corres [[Category:Documentation in English]]

* Write documentation ...ng other Romance languages, but my knowledge of them is mainly passive and linguistic. That’s why I’ll work mainly translating from Italian and Portuguese in

cross: cross 2 language pairs (using linguistic res. XML file - see [[Cross Model]]) [[Category:Documentation in English]]