dopatoy.blogg.se

Spelling (SP) / Character (CH) for non-alphabetic languages:Ī spelling/character error occurs when a word or character in the translation is spelled/used incorrectly according to targetlanguage conventions. NOTE: In the Framework grid, the WF/PS error is a subcategory of Grammar (G) errors. A part of speech error occurs when the grammatical form (adjective, adverb, verb, etc.) is incorrect (e.g., “a conspire” instead of “a conspiracy”). number or case of noun or pronoun) is incorrect or nonexistent in the target language (e.g., “tooths,” or “conspiration” instead of “conspiracy”). NOTE: In the Framework grid, the SYN error is a subcategory of Grammar (G) errors.Ī word form error occurs when the root of the word is correct, but the form of the word (e.g. If incorrect syntax changes or obscures the meaning, the error is more serious and may be classified as a different type of error using the Flowchart and Framework. Errors in this category include improper modification, lack of parallelism, unnatural word order, and runon structure. (b) If a verb form is grammatically possible in the sentence but changes the meaning of the source text because of its tense, aspect, mood, etc., the category verb form (VF) should be used see explanation in Section 2 (Meaning Transfer).Ī syntax error occurs when the arrangement of words or other elements of a sentence does not conform to the syntactic rules of the target language. NOTES: (a) In applicable cases, the G error should be subcategorized as syntax (SYN) or word form/part of speech (WF/PS) see explanations below. Grammar errors include lack of agreement between subject and verb, incorrect verb inflections, and incorrect declension of nouns, pronouns, or adjectives.

For errors that do not overtly violate any rules but still “sound wrong,” see Section 3 (Writing Quality).Ī grammar error occurs when a sentence in the translation violates the grammatical rules of the target language.

For errors that affect (distort) the reader’s understanding of facts/ideas in the source text, see Section 2 (Meaning Transfer).

The following errors clearly violate one or more rules that prescribe the “correct” written forms of the Target Language (e.g., grammar and spelling).

It is often valuable to create a custom type for your exact situation, but in some of the simpler cases, you can use an off-the-shelf type instead. These kinds of situations are extremely common.

If we have a viewPreview : MaybePost -> Html msg function to preview valid posts, now we can give more specific error messages in the preview area when something goes wrong! Instead of just saying that the input is invalid, we are describing each of the ways things might have gone wrong. = Post - toPost "" "" = NoTitle - toPost "hi" "" = NoContent But what happens if they forget to add a title? Or there is no content in the post? We could model all these problems explicitly: type MaybePost This kind of thing comes up all the time! For example, maybe you want to turn a bunch of user input into a Post to share with others. From there, we use pattern matching which will ensure that both possibilities are accounted for. Valid input produces values like Age 24 and Age 99, whereas invalid input produces the InvalidInput value. No matter what input is given to the toAge function, it always produces a value. toAge "24" = Age 24 - toAge "99" = Age 99 - toAge "ZZ" = InvalidInput | InvalidInput toAge : String -> MaybeAge toAge userInput = You might create a custom type like this: type MaybeAge

For example, say you want to turn user input into an age. Rather than crashing, we model the possibility of failure explicitly with custom types.

This is partly because Elm treats errors as data. One of the guarantees of Elm is that you will not see runtime errors in practice.