AplikaceAplikace
Nastavení

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
en:manualy:morfio [2018/05/28 13:03] – [Principle] michalskrabalen:manualy:morfio [2020/07/02 17:13] – [Alternations] michalskrabal
Line 14: Line 14:
 Generally every morphological relation -- excluding the semantic component, which cannot be easily grasped computationally -- is created by two other factors: Generally every morphological relation -- excluding the semantic component, which cannot be easily grasped computationally -- is created by two other factors:
  
-  - a formal congurence/similarity in particular parts of the word, so-called **bases** (e.g. //dřev-// is held in common by the words //dřevo// and //dřevěný//) +  - a formal congruence/similarity in particular parts of the word, so-called **bases** (e.g. //dřev-// is held in common by the words //dřevo// and //dřevěný//) 
   - formal differences in specific parts, so-called **formants** (morphs //-o// and //-ěný// from the previous example).    - formal differences in specific parts, so-called **formants** (morphs //-o// and //-ěný// from the previous example). 
  
Line 35: Line 35:
 The output of the Morfio application is not and cannot be free of errors and without any further adjustments, revisions and linguistic manipulations cannot generate directly publishable results. It is rather a tool which can rework a large amount of data for linguistic purposes, making analysis faster and more accessible for researchers. As with other corpus search engines, the aim is only to reach a success rate of 100% when searching for a given type ([[en:pojmy:recall|recall]]) and to provide an organized sorting of the results, while their relevance and [[en:pojmy:precision|precision]] is left solely to the user's judgement: i.e. the actual query formulation and the subsequent interpretation of the findings. The output of the Morfio application is not and cannot be free of errors and without any further adjustments, revisions and linguistic manipulations cannot generate directly publishable results. It is rather a tool which can rework a large amount of data for linguistic purposes, making analysis faster and more accessible for researchers. As with other corpus search engines, the aim is only to reach a success rate of 100% when searching for a given type ([[en:pojmy:recall|recall]]) and to provide an organized sorting of the results, while their relevance and [[en:pojmy:precision|precision]] is left solely to the user's judgement: i.e. the actual query formulation and the subsequent interpretation of the findings.
  
-==== Alternace ====+==== Alternations ====
  
  
-To require a precise congruence of form between the individual members of the morphological model would be impractical for a language such as Czech, due to the fact that within the morphological processes there are frequently cases of regular phoneme **alternations** in the base.  The Morfio application reckons with alternations and their range acan be set (e.g. the alternation of //e -- é// in //letět -- létat//; //i -- e// in //prosit -- prošen//; //r -- ř// in //starý -- stařec//; //sk -- šť// in //český -- čeština// etc.).+To require a precise congruence of form between the individual members of the morphological model would be impractical for a language such as Czech, due to the fact that within the morphological processes there are frequently cases of regular phoneme **alternations** in the base.  The Morfio application reckons with alternations and their range can be set (e.g. the alternation of //e -- é// in //letět -- létat//; //i -- e// in //prosit -- prošen//; //r -- ř// in //starý -- stařec//; //sk -- šť// in //český -- čeština// etc.).
  
 ===== Application images ===== ===== Application images =====

Trace: • konkordance • srovnatelny • novy_dotaz • frekvence • start • multiword • verze10 • koditex • novy_dotaz • koligace