Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
tecdoc:vf_gloss_creation [2016/08/10 19:40] manuel |
tecdoc:vf_gloss_creation [2017/05/09 14:08] (current) |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Instructions for providing target terms ====== | + | ====== Instructions for using wildcards when providing target terms ====== |
| We need your help to complete the target terms in a glossary that will be used, among other things, for term consistency checks. | We need your help to complete the target terms in a glossary that will be used, among other things, for term consistency checks. | ||
| - | In column B, please enter the equivalent term in the target language. Please do not simply translate the source term -- this task entails some research to find out how that concept/object/reality is expressed in your language (the target language). | + | In column B, please enter the //equivalent// term in the target language. Please do not translate the source term -- this task entails some research to find out how that concept/object/reality is expressed in your language (the target language). For example, "state school" in, say, Spanish might be "escuela pública" and not "escuela del estado". |
| - | The term in the target language must be entered in its dictionary form (e.g. in singular, in lower case, etc.), according to what is common practice in your language, except for lexicalized inflected or capitalized forms. | + | The term in the target language must be entered in its dictionary form (e.g. singular nouns, singular/masculine adjectives, infinite verbs, in lower case, etc.), according to what is common practice in your language, except for lexicalized inflected expressions or capitalized forms. |
| - | Terms might vary so as to agree with their context through inflection (e.g. number, gender, conjugation, etc.), declination (cases like accusative, dative, etc.), derivation (suffixes to build lexical families), determination (e.g. articles, etc.). The glossary needs to reflect potential variability and we use **wildcards** to avoid having to write all possible forms. | + | When being used, terms might change so as to agree with their context through inflection (e.g. number, gender, conjugation, etc.), declension (cases like accusative, dative, etc.), derivation (suffixes to build lexical families, e.g. education -> educative), determination (e.g. articles, etc.). The glossary needs to reflect potential variability and we use **wildcards** to avoid having to write all possible forms. |
| - | 1. If the base form of the word may change by adding a suffix, simply add an asterisk ("*") at the end. For example: | + | ==== 1. Additional suffixation ==== |
| - | (ENG) //teacher// -> (ESP) the base form is //profesor// (masc, sing) but it might inflect in number and gender as //profesor**a**// (fem, sing), //profesor**es**// (pl, masc) and //profesor**as**// (pl, fem). In all cases, the base form //profesor-// does not change. | + | If the dictionary form of the term may change by simply __adding__ a suffix, simply add an asterisk ("*") at the end. For example: |
| + | |||
| + | (ENG) //teacher// -> (ESP) the base form is //profesor// (masc, sing) but it might inflect in number and gender as //profesor**a**// (fem, sing), //profesor**es**// (pl, masc) and //profesor**as**// (pl, fem). In all those cases, the base form //profesor// does not change. | ||
| The target term would be: //profesor*// | The target term would be: //profesor*// | ||
| - | 2. If the target term contains a root that does never change and another suffix that might be replaced with different suffixes in different contexts, then use a pipe ("|") to separate the invariable part and the variable part. For example: | + | ==== 2. Replaceable suffix ==== |
| + | |||
| + | If the the dictionary form includes a suffix that might be __replaced__ with other suffixes in different contexts, then use a pipe ("|") to separate that variable part from the preceding invariable part. For example: | ||
| (ENG) //lawyer// -> (ESP) the base form is //abogad**o**// (sing, masc), which can vary as //abogad**a**// (sing, fem) | (ENG) //lawyer// -> (ESP) the base form is //abogad**o**// (sing, masc), which can vary as //abogad**a**// (sing, fem) | ||
| Line 21: | Line 25: | ||
| The target term would be: //abogad|o// | The target term would be: //abogad|o// | ||
| - | 3. If there are several possibilities that are plausible (i.e. that are actually used in that domain and are equally correct) and do not have a common base/root, you should provide the different forms separated by a semi-colon (";"). For example: | + | In this case you wouldn't use an asterisk because //abogad*// is an incomplete word and we need the full word for different purposes. |
| + | |||
| + | ==== 3. Alternative expressions ==== | ||
| + | |||
| + | If there are __several__ possibilities that are plausible (i.e. that are actually used in that domain and are equally correct) and do not have a common base/root, you should provide the different forms separated by a semi-colon (";"). For example: | ||
| (ENG) //household// -> (ITA) is expressed as both //famiglia// and //nucleo familiare// | (ENG) //household// -> (ITA) is expressed as both //famiglia// and //nucleo familiare// | ||
| Line 29: | Line 37: | ||
| Do not use a stroke ("/"), a hyphen ("-") or any other symbol to separate the alternative terms. | Do not use a stroke ("/"), a hyphen ("-") or any other symbol to separate the alternative terms. | ||
| - | Be careful when providing alternatives (synonyms or variants). You only need to provide the actual equivalents of the source term that are actually used in that domain. You should not provide more terms than the one(s) that is/are actually used in your language (regardless of how many alternative terms may be used in the source language to express that concept). | + | Be careful when providing alternatives (synonyms or variants). You only need to provide the equivalents of the source term that are actually used in that domain and that should be used in that project. You should not provide more terms than the ones/s that is/are actually used in your language (regardless of how many alternative terms may be used in the source language to express that concept in different contexts). |
| + | |||
| + | In the few cases where the alternatives are part of the term/expression rather than the full expression, you can encircle them with parenthesis. For example: | ||
| + | |||
| + | (ENG) //household// -> (ESP) is expressed as both //núcleo familiar// and //núcleo doméstico// (fictional example) | ||
| - | If the alternatives are part of the term/expression rather than the full expression, you can encircle them with parenthesis. For example: | + | The target term would be: //núcleo (familiar;doméstico)// |
| - | //household// -> //núcleo (familiar;doméstico)// | + | Or if the above looks a bit too complex, you can simply write The target term would be: //núcleo familiar; núcleo doméstico//, even if you repeat "núcleo". |
| + | ---- | ||
| If for any reason there's no target equivalent in your language, leave the cell empty -- do not write "N/A", "not existing" or anything at all, but please insert a pop-up comment (in Review -> New Comment). | If for any reason there's no target equivalent in your language, leave the cell empty -- do not write "N/A", "not existing" or anything at all, but please insert a pop-up comment (in Review -> New Comment). | ||
| - | If you have the slightest doubt, please ask. | + | If you have the slightest doubt, please please please ask. |