CC BY
57THEORY AND METHODOLOGY OF TEACHING FOREIGN LANGUAGES
UDC 81'276.6
DOI: 10.17223/24109266/7/5
SEMANTIC, STYLISTIC AND GRAMMATICAL NUANCES OF SPECIALIST TRANSLATION
Radoslaw Gajda
Pedagogical University of Cracow (Cracow, Poland).
E-mail: [email protected]
Abstract. The text draws attention to these aspects of the translation process, which in technical texts play an important role and, above all, cause the most trouble, in particular, terminology, measurement units, abbreviations, key words, rules of spelling and punctuation, style of the text. Keywords: specialist translation; semantic; polysemy; monosemy.
Introduction
The problem of specialist languages has been a live issue for a long time. It attracts a lot of interest from language specialists due to the fact that it has gone beyond the limits of social sciences to appear with all the sharpness in other scientific disciplines. In linguistic research in order to capture the general language in its diversity it has been assumed beneficial to divide it into more homogeneous subsystems. One of such possible divisions is the "external" division of the language as a whole into sub-languages called the functional ones [1: 40-43].
It is also worth noticing that the expression specialist language and general language cover only the subset of the language i.e. the subset of lexemes. It is a matter of terminology to name various notions and morphology, phonology or syntax are only its side-interests. Therefore, it is a matter of priority for terminology to research lexis and that is specialist lexis which within each national language covers proportionally the richest part. This way, translation of specialist texts, apart from standard requirements connected with any translation, enforces one more demand, i.e. the necessity for the translator to study scientific and technical documents in order to find precise terminology and encyclopaedic information in the particular field. Therefore it can be accepted after E. Wüster, that the number of specialist languages is equal to the number of existing scientific and technical disciplines [2: VIII-X].
Annalysis
In this outline I would like to pay attention to some chosen semantic and grammatical aspects of translation especially to spelling, punctuation and terminology. The first two aspects are often treated with some kind of disrespect by not only students of translation studies, but also by the very same translators.
It is worth underlining the importance of how numbers and numeral values should be written. Multiple numbers should be divided into three-digit numbers separated with spaces. The numbers which are not divided into blocks of digits are more difficult to read. (ex. 183286, 20000000) Three-digit blocks are definitely not to be separated with commas, since this mark is used to separate fractions. Also, on the right of the comma it is possible to separate three-digit blocks with spaces. It is suggested to distinguish groups of digits only in numerals longer than four-digit ones. So we will write 8191, but 11 474.
In practice to avoid moving to the next line in the middle of a long number it is advisable to separate three-digit blocks with no-break spaces. The numbers indicating year, page or identification, etc. are not to be separated into three-digit numbers.
Equally important role is played by units of measurement. In translations one should use SI units or the ones derived from them. If the original version contains different units, ex. pounds, ounces, miles, yards, gallons, etc. it is necessary to make precise calculation and convert the values into the units used in the country which language we are translating into - i.e. the Polish language providing the data in kilograms, grams, kilometres meters, litres, and etc. Naturally, there are some justifiable exceptions where there is no use to recalculate, ex. in case of the size of paper it is better to leave the original measurement in inches. As with everything, it is necessary to implement common sense.
While writing the units of capacity of hard disk (disk storage), the size of files, or data rate it is necessary to remember that:
a) bits (binary digits) are to be written with small' 'b' and bytes - with capital letter 'B';
b) small k stands for kilo (1000) and capital K - kilo (1024);
c) Capital 'M' symbolises mega and capital 'G' - giga;
d) between the number and the unit a space should be placed, so we will write correctly 1,4 MB or 130 KB so writing 2GB is wrong.
It is worth noticing that money values can also cause problems to translators. Therefore, the amount of money is to be written in the same way as other numerals and placing proper symbol of currency after the amount after the space (refers to the Polish language! - translator's remark). Wherever it is possible one should use local currency units and recalculate and if needed provide the amount
in Polish zloty and grosz. If it is necessary to write the amount in a foreign currency one ought to use its full name or the abbreviation commonly accepted. Below a few correctly written examples of some amount of money in Polish: 1 078 zl, 12 800,99 zl, 11 500 zl 79 gr, 800 dolarow, 900 USD.
It is necessary to emphasize that writing dates and hours also follows certain rules. Time ought to be given in 24-hour recording (from 0 till 23). Time can be written in the way: hours: minutes: seconds (ex. 22:55:34 or 22:55) [3].
Dates may be written using numbers or (seldom) with full name of the month. It is worth remembering that a month can be written with Roman numerals and using word name one provides the name of the month in possessive case and with small letter, ex. 28.04.1989, 28.04.89, 28 IV 19989, 28 kwietnia 1989.
Weekdays are to be written with small letters and in well justified cases it is possible to use these abbreviations: pon., wt., sr., czw., pt., sob., nd. If it happens that the space limit does not allow us to use three-letter abbreviations, but only two-letter ones one shouldn't tear his hair out. Needs must when the devil drives. A common sense ought to tell the translator what to do in such a case.
A period of years can be written in two ways. If these are following years, it can be written with a mark of slash (/), ex. 1993/94. If a longer period of time is meant a mark minus (-) is used, ex. 1996-2001.
In translations quite often we can find some procedures. A procedure is such part of the text where the information is given point after point how to do a particular activity or activities. The steps of the procedure are usually numbered. Procedures are the only parts of the text where one can and even has to refer to the user (reader) using imperative forms.
A typical procedure consists of a sentence or a few introductory ones and several points. Sometimes there are no introductory sentences but a headline of the type: Moving objects with the help of a mouse. Below an example:
To write a file under a different name:
1. From the menu File choose the commend - Write as.
2. In the open window Write as provide a new name of the file.
3. Press the button OK.
In each text punctuation plays an important role. Correct use of punctuation marks enables to write the text in an explicit and unambiguous way. Punctuation marks divide text into logical parts and separate particular parts of the sentences. This outline covers the use of punctuation marks appearing in the Polish language referring to specialist translation.
Full stop is one of the most important punctuation marks. It is used to close a certain entity within which some other punctuation marks may ap-
pear. In particular cases, instead of full stop, a question mark, an exclamation mark or suspension points are used.
A full stop is to be placed (these rules concern translations into Polish - translator's remark):
- at the end of a sentence starting with capital letter;
- after an abbreviation containing the last letter of the shortened word;
- after initials, ex. J.K;
- after numbers indicating ordinal numbers, if the lack of the full stop arouses doubts as whether it refers to the ordinal or cardinal numbers;
A full stop should not be placed:
- at the end of a sentence, when the last word is an abbreviation followed by a full stop (It is enough to have one full stop);
- after titles and headlines;
- in catchphrases and advertising slogans;
- after acronyms and some abbreviations;
- semicolon is a dividing mark which has the function in-between a full stop and a comma. Using semicolon one separates also elements which are logically equal.
A semicolon ought to be put:
- in particular cases between complex sentences or simple sentences
- in all kinds of specifications, if in at least one of the parts there is a comma; the last part should be closed with a full stop.
The most often exploited punctuation mark is a comma. In a sentence it can serve one of the two functions: either divide the elements of the sentence or separate a part of a sentence from the whole entity. In the latter case, two commas are implemented, the first one - opening one, and the latter closing one. A comma is to be placed between subordinate dependent clauses and superordinate ones. It is used to separate two compound (coordinate) sentences, gerund clauses and particular parts within one complex sentence.
The rules concerning the usage of commas in English are different from the ones functioning in Polish. In English a comma is sometimes used before the words 'and' and 'or', whereas in Polish we do not put a comma either before 'i' or before 'lub', except in order to separate an insertion, ex. Wskaz plik, ktory nalezy otworzyc, lub wybierz wartosc domyslnq (Provide a new name for the file which is to be left open or leave the assumed name).
Using comma, one should not separate conjunctions form adverbs and particles in such as: chyba ze, tylko ze, podczas gdy, tym bardziej ze, wiasnie gdy, zwiaszcza ze, etc.
If a word plays a role of a conjunction, a comma is not placed in front of it, ex.: ObiektXznajduje siq miqdzy obiektem Ya obiektem Z.
(There is an object X between the object Y and Z.)
Nie istnieje w oknie ani poza nim. (It/He isn't either in the window or out of the window.)
Trudno okreslic, czy ta wersja jest lepsza czy po prostu aktualniejsza. (It is difficult to say whether this version is better or simply a newer one.)
(In Polish translation: 'whether' is a particle here and 'or' - a conjunction.)
In constructions with repeated conjunction the first element ought to be separated from the second one, ex.:
Mozna to zrobic albo tak, albo calkiem inaczej. (It can be done either in this way or in a different one.)
Operacji takiej nie da siq zrealizowac ani w typowym arkuszu kalku-lacyjnym, ani w bazie danych. (Such task cannot be performed either on a typical spreadsheet or in database.)
A comma is to be put in front of:
a) adversative conjunctions, such as ale, lecz, a, czyli, etc. (but, and, in other words, etc.);
b) with introductory expressions to jest, to znaczy, etc. (that is, it means, etc.);
c) expressions of the type: na przyklad, przynajmniej, zwlaszcza, etc. (for example, at least, especially, etc.) but provided they introduce some additional information; so we shall write: Jesli dane zostanq dodane na przyklad do pliku DANE. TXT (without a comma), but Duzo spacerowal, na przyklad do pobliskiego ogrodu (with a comma).
Naturally there still exist a lot of rules defining where and where not to use a comma. In case of having any doubts while translating it is best to consult a dictionary or a grammar handbook.
Suspension points is a punctuation mark which consists of three dots. They are used first of all instead of an omitted word or an omitted group of words. If suspension points substitute one word, it is necessary to leave some space in front of it and following it. If suspension points substitute a few words, they can be placed in brackets. If they appear at the beginning of a sentence, they should be separated from the rest of the sentence with some space. If suspension points are close to a comma a semi-colon or full stop we live them. If it means the break in the utterance implicit statement it is necessary to place it directly after the last word without the dividing space.
Then, a colon is a mark preceding quotations enumeration, specification justifications, explanations or announcement, etc. Text following the colon starts with capital letter if it consist of more than one sentence. The quoted text may be placed in inverted commas or distinguished in italics.
Now it is worth paying attention to the role of dash (em-dash, en-dash, a hyphen an minus) in specialist translation.
A dash is a punctuation mark dividing expressions and it can be used:
- in the place of understood part of the sentence (if in this case a comma was required because of some other reasons, we live it out), e.g. the first element place symbolical function and the second one illustrative one;
- to distinguish interference (instead of the comma), e.g. Powinno to byc - o ile dobrze pamiqtam - w roku 1965. (It must have been, as far as I remember, 1965);
- in other to indicate suspension of the voice, a rhetoric pause, e.g. Swiat jest oceanem szczqscia - to wiadomo. (The world is a ocean of happiness - it is known);
- in front of generalizing statement of what has mentioned before, e.g. kosmos, gory, morza - wszystko to sklada siq z atomow (stars, mountains, and oceans - all this is made up of atoms).
The graphical representation of a dash in print is em-dash (—) and en-dash (-). The choice of which we use depends only on a aesthetic criteria. It is necessary not to mistake hyphen for dash. It is advisable to use em-dash which is more coherent graphically with the text and doesn't allow huge spaces between words so as not to distract the attention of the reader. The concept of em-dash an en-dash refers to visual side of the text (graphic notion) and the term "dash" refers to language side. A dash (em-dash and en-dash) is always separated from the words with spaces (in contrast to hyphen, minus). A hyphen is also called a linking dash and is used among others:
- to join words written with capital letters (e.g. pseudo-Polak);
- in names of some towns (e.g. Bielsko-Biala);
- to write surnames consisting of two parts (e.g. Dolqga-Mostowicz);
- to create two-part nouns (e.g. kupno-sprzedaz, program-klient);
- to join to equal adjectives or adverbs, e.g.: bialo-czerwony (containg some white and some red), polsko-angielski (Polish-English), wejscia-wyjscia (out-and in-device, playing two roles at the same time), klient-serwer (clientserver architect) but jasnozielony (light green throughout), targi ogolnopolskie (national fairs in Poland), magistrala szesciobitowa (6-bit data-bus);
- to separate stem from inflectional endings in case of an acronym, e.g. DOS-a, w IBM-ie;
- to move words to a new line (dividing words).
In compound nouns and adjective were the first part is a numeral written with digits a hyphen appears between the number and the word connected with it, e.g.: 40-percent, 19-year-old.
It is worth remembering that the forms of witting: 18-sto bitowy (18bit), 4-cio stopniowe (4-step), 9-mio cyfrowy (9-digit) are wrong.
If a sentence contains in turns several compound adjectives which differ in the first part, the second part is written only in the last expression. e.g. urzqdzenia 16-, 32- i 64-bitowe (16-, 32- and 64-bit devices) [3].
A hyphen is the shortest among all printing marks and it comes in the shape of horizontal line. It resembles the marks of minus and dash but in the text it place an absolutely different role and it appears as an independent typographic sign. It is not a punctuation mark therefore it divides the parts of a word and not parts of a sentence (just like a dash).
A minus sometimes called as hyphen is used in:
- mathematics expressions (usually a minus with a space in front of and after it);
- between numbers indicating proximate values or indicating the period or range, e.g. the description has been provided on pages 124-131 in years 1994-1998 or in years 1994-98.
Similar to a hyphen, a minus (-) isn't precisely a punctuation mark but ma thematic one and it has different width and place from a hyphen. It agrees with other ma thematic symbols, such as: a plus, equals to, division line.
Professional typographers in publication with high aesthetic values use so-called (figure dash, code symbol U+2012). Figure dash differ from en-dash that they are always in the middle of the height of a given cipher whereas en-dashes are usually below the middle of the height.
Every translator knows that special marks play very important role. While writing the text it is sometimes necessary to use very special marks, e.g. spaces and non-dividing hyphens, dashes, en-dashes, em-dashes or inverted commas.
Sometimes it is necessary to prohibit from moving a group of words or a phrase to the next line. In order to do this one can use hard marks, in other words non-diving once. There are two such marks: hard space and a hard hyphen. Each of these marks, placed between two words enables the connected words during the process of formatting lines to be treated as a one word. It means that they will never be separated, and either they will stay in this line or they will be move to another line.
The blocks of ciphers of telephone number are to be separated with the use of hard space of hyphens. Three-digit blocks while writing numbers and amount of money are to be divided with the use of hard spaces. If after the number there is a symbol of currency it ought to be also separated with non-dividing space.
One shouldn't divide acronyms joined with a hyphen, e.g. MS-DOS.
There is a rule stating that one oughtn't to leave one-letter words (a, i, w, z) by the end of the line. Sometimes it is possible to prevent such situation connecting the one-letter word occurring in the end of the line with the word following it using the inseparable space. It is worth remembering that this method is useless if the text is aligned to the right or the left margin. Inseparable space is distinguished in the aligned text because it has fixed width. In such a case it is also possible to use any other method to move one-letter word to the next line, for example to put in front of it a symbol at the end of the verse. At the same time it is necessary to remember that each change of the length of the sentence finished in this way will cause the disruption of the layout of the paragraph. Therefore, such method makes no sentence in case of texts appearing in windows whose width can be regulated by the user (help and "readme" file).
In English texts three symbols can appear in the shape of horizontal line ("-", "-", "-"). Each of the has different length and absolutely different function. The shortest line is called a hyphen (the button next to number 9), a bit longer - a minus or en-space (usually with the code 150) and the longest one a dash or em-dash (usually coded 151). Depending on the situation one should use the proper type of the line.
Between the words one should writhe only one pace. Before submitting the translation it is necessary to check if he text doesn't contain any unnecessary spaces. The custom of witting two spaces separating sentences in an English idea which we do not use in the Polish or Russian languages. A space is not to be put in front of punctuation marks (in front of a full stop, comma, a colon, a semi-colon, a question mark, etc.). It shouldn't be placed also in front of closing part of brackets (inverted comma) or following the opening brackets (inverted comma).
If documents contain drawings some notices can also be found, especially captions under the drawings and some explanations. One ought to translate them in a nut-shell and according their contents. The notices could be descriptive (what can be seen in the picture) or can be direct instructions for the user (what he is spouse to do). Captions under the pictures just like user's instructions should be written with capital letters. The expressions being the names and the descriptions of the elements of the drawings (usually far away from the drawing and linked with lines and arrows indicating these elements in the picture) ought to be written with small letters, e.g. ikona pliku, przycisk Start (a file icon, start button), etc. In each of above cases one shouldn't use full stops ending the utterance unless the given caption consist of two or more sentences (then the sentences are divided with full stops and only the last one doesn't end with it).
Tasks which are to be done while translating documents:
- translate materials according to the guidelines shown in these paper;
- check the spelling with the use of available tools of text editor;
- to edit the files linguistics t(o give it to be edited by a language consultant);
- to edit the files concerning the substance (to compare the translation with the original text to ensure coherence);
- to translate all the example files necessary to prepare screenshots;
- to ensure the cohesion of screenshots with the contents of the documents;
- to check the correct numbers of pages in contents and indexes.
Tasks, which are to be done within the translation of a software:
- to translate the material according to the guideline providing to this
paper;
- to translate all the elements of the user's interface;
- if it is possible to compare with already existing translations to introduce proper language and stylistic changes;
- if there the need to introduce the change if terminology get the acceptance of changes from the language consultant;
- translate new terms, introduce the concepts into database and get the acceptance from the language consultant;
- while translating user's interface one ought to follow the recommendations of the translation provider, especially one shouldn't translate the elements when they are indicated as not translatable (Do not translate command);
- if it is necessary to translate the names of files, catalogue and variables;
- to check precisely the layout of the elements of dialogue windows and in case of need to change the size and the location of wrongly displayed elements;
- to correct spelling mistakes in the translated interface of the user;
- to check precisely the correctness and cohesion of the used shortcuts;
- to check the correctness of translation and the displayed messages about mistakes;
- to check the translation of all the example file;
- to test all ready-made product (everything as above).
The Polish language enables the possibility of formally distinguishing the meanings of the words: piloty / piloci, klienci / klienty, absolwenci / ab-solwenty (the name of the vodka), agenci / agenty, edytorzy / edytory, krea-torzy / kreatory, translatorzy / translatory (the first words referring to animated nouns, the latter once to computer technology).
The plural form of the word klient (client) meaning a men is to be formed as klienci (clients) and from the word klient meaning the programme (the opposite of the server) as klienty. Similarly kratorzy mody are to be called kreatorzy (fashion creators) moduly programowe (program modules) consisting of the series of windows are kreatory [4: 103].
In the English language a word attributed is always after the attributing one (e.g. file name = nazwa pliku, name file = plik nazw). In case of Polish it is not always the same. Usually an attribution loosely connected with the object comes as the first one, e.g. zielony sweter, stary samolot, and permanently connected with the object (creating a new category) as the last one, e.g. rower gorski. There are some exceptions, eg. okrqgly stol, Stary Teatr in Cracow. That's why the problem whether one should say dysk twardy or twardy dysk ought to be left to the usage (the frequency with which these expressions are found in the language). However, due to the need to provide the coherence the binding form is dysk twardy [3].
Generally in the translation of computer software a rule prevails that a new collocations (such which are just entering the language) where one word describes a permanent feature of an object ought to be formed by placing an
attributing word after the word attributed, e.g. instalacja pelna, wersja testowa, etc.
It is better to leave operating system UNIX uninflected and write it simply as in the system UNIX or in UNIX-ie. According to the rules governing the incorporation of foreign word into Polish a Polish adjective created from the name UNIX should sound uniksowy (with a letter "k" not "x" - because the Polish alphabet doesn't contain the letter "x"). However, very few people have enough courage to use these form properly.
It's the same in case of the words BASIC and Basic. If the name of this language is to be treated as any acronym we shall write problemy z BASIC-iem but if it refers to a common name z Basikiem. One can doublecheck it in Nowy slownik ortograficznym PWN [5: 43].
The word order of the Polish language is almost free. One can say Adam bije Piotra albo Piotr bije Adama. In the old Polish it was said Adam bije Piotra because then the accusative form of a masculine noun was equal to nominative case.
This equality of accusative and nominative cases is still to be found in archaic forms of the type wyjsc za mqz and na mily Bog and in case of inanimate nouns, e.g. widzq dom, kocham pieniqdze, siadam na fotel.
There is still a further evolution and more and more exceptions appear from the above rule: jesc kotlet (kotleta), grac w tenis (tenisa), podac pilot (pilota), palic papierosa, jesc kurczaka. It is worth remembering that most of such forms are still labelled as informal or are simply mistakes e.g. ukroic torta czyprzeczytac bestsellera [4: 134].
The reference to computer text is clear. A problem appears for example whether to write uruchomic kreator czy uruchomic kr eat or a. I support the concept of the first form, similarly uruchomic edytor tekstow, and not uruchomic edytora tekstow. It's the same in case of podac pilot and not pilota, since me mean to distinguish animated from inanimate meanings. Maybe some time in the future this norm will have changed. So far we should to remember that written language ought to be characterised with more formality (conservatism) than the spoken one.
In lots of computer translations one can encounter the translation of the word customize into Polish dostosowac. It is not a bad idea, however, it is often forgotten that the expression requires to say that dostosowuje siq cos do czegos, and not just - generally dostosowuje. (something is adjusted to something, not just customized). The word dostosowac (customize) requires an additional explanation. On the other hand, sometimes it is not a good idea to hold on to the equivalents of the type 'one to one'. After all the word customize can also be well translated into: konfigurowac, modyfikowac, adaptowac, etc. (adjusted, made according to the needs, etc.) [3].
The same refers to the word drag, which is always definitely translated into przeciqgac. It is understandable in case, for example an operation in which you drag a file icon from one window into the other one using the mouse (really, dragging is involved) but also in case of changing the size of an object pulling it by its frame. It also moves like a cursor. You can also pociqgnqc (drag) or ciqgnqc (pull) something. It is not worth limiting yourself to the vicious circle of one translation equivalent.
By the way, it is necessary to mention that in programme documents it happens that a given word is to have a precise reference to particular instruction. Then the fact that some particular activity is called in this, and not any other way, carries some additional information which allows the user to figure out what command is meant. This deeper meaning ought to be conveyed in the final version in the Polish text. Similar thing happens with the ill-fated word dostosowac. If in the programme we have a command Dostosuj (customize) in the description of how the programme works, then you will have to use this word while writing, for example: Program A umozliwia do-pasowanie wyglqdu okna do potrzeb uzytkownikow.
(The programme enables customizing the appearance of windows according to users' demands.) It is best not to translate commands like Customize into Dostosuj, but, for example as Zindywidualizuj [3].
Translators of computer texts should cope with logic remarkably well. For sure they are also familiar with de Morgan's laws: the negation of a conjunction is the disjunction of the negations and the negation of a disjunction is the conjunction of the negations. What does it have to do with a language? If in a statement one uses a conjunction of an alternative (or), then it cannot be used in a negation, e.g. choose A or B, but don't choose either A or B, choose neither A nor B. An example of a wrong sentence: ...ma jednq duzq wadq: nie radzi sobie ze znakami graficznymi lub kontrolnymi (has a huge disadvantage, it can't cope with neither graphic nor control signs (it should have either, or).
Quite often the writers forget that they have a choice of various conjunctions and they blindly follow (sometimes a mistaken concept) a word 'or' from an English sentence, e.g.
I don't know if it's good or bad - should be translated as: Nie wiem, czy to dobre czy zle. Depending on the context the word 'or' may be translated as lub, i, oraz, ani, albo, czy, bqdz, tudziez [Ibid].
By the way, we should mention here placing commas [6: 74]. In front of 'czy' used as a conjunction joining compound utterances or their elements one shouldn't place a comma.
A comma is to be put in front of 'czy' used as an indication of combining introducing subordinate utterances (not a conjunction, but a relative pronoun). Both cases are well exemplified by a sentence: nie wiem, czy to dobre czy zle.
This is an eternal problem that Poles have been dealing with. The problems of this type can be found discussed in dictionaries where we find among others such expressions as 'unikalny' (unique) and 'unikatowy' (one of the kind), therefore, it is necessary to accept both of these forms or even indicate the first one as the one used more often [7: 338].
You can also find there a recommendation that synonyms - such as wyjqtkowy (exceptional), niepowtarzalny (incomparable), jedyny w swoim rodzaju (unexampled) - can be sometimes even better. I would like to pay attention to the fact that the English word 'unique' (in computer language, e.g. while talking about data base indexing) isn't well translated either into 'unikalny', or 'unikatowy', or even 'niepowtarzalny'. So how to translate the expression 'unique index'? It is best to probe deeply into its meaning and provide a more descriptive expression, yet referring to the reality in a better way: 'index bez powtarzajqcych siq rekordów czy index nie uwzglqdniajqcy powtarzajqcych siq rekordów' (literary - an index of non-recurrent records). In the same way, a unique ID is an identification whose values do not repeat or an identification accepting various values (an injective one).
For the German languages (including English) it is common to use often capital letters.
a) An example could be every word of a heading or subheading which starts with a capital letter (e.g. Formatting Numbers). In Polish it is enough to write the first word of a heading/subheading with capital letter. The same refers to proper names, e.g. Profile Wizard becomes Kreator profili, and not Kreator Profili.
b) Often the words which used to be proper names appear in the role of a common nouns (e.g. schowek (clipboard), pulpit (panel, board), kreator (wizard). There is no need to write them with capital letters.
c) If the text contains personal pronoun: ty, twój, ciebie, etc (you, your, for you, etc.) writing it with capital letter is justifiable only when the utterance is solemnly addressed to the user, e.g. in the advertising, marketing texts or in a letter, etc.
As a side-note it is worth mentioning an incorrect translation of the word your and about the existence of the word swój, which is often forgotten. The sentence Zachowaj je w twoim folderze lokalnym should be replaced by the one Zachowaj je w swoim folderze lokalnym without fail.
Conclusion
To polish the translation it is necessary to detect gross alliterations (the sequence of the words starting with the same letter) or other clashes which are found only while reading the text aloud. The basic functions of specialist language are an informative and communicative ones. Specialist
language serves most of all getting acquainted with and passing specialist contents of a language message [8: 264].
According to Jerzy Pienkos, specialist language marks aim at univocal character of nature (monosemy), whereas the marks of general language convey complex psychological and social connotations so in the very nature of things they have to be characterised by bigger polysemy [Ibid: 265].
The difficulty of a proofreader's work could lead to the conclusion that to do such a job one has to be a far better expert than the translator himself. However, it seems that in our conditions, one can risk a paradoxical thesis, that the translator should be possibly the best one and the proofreader may be only meticulous in carefully checking the conformity of the translation to the original in order to notice any possible shortcomings, omissions, etc.
References
1. F. de Saussure (1916) Cours de linguistique generale.
2. Wüster, E. (1973) Kaleidoskop der Fachsprachen.
3. Available from: http://kresak.pl (Accessed: 04.03.2016).
4. Miodek, J. (1998) Rozmyslajcie nad mowq. Warszawa.
5. Slownik Ortograficzny. (1997) PWN.
6. Podracki, J. (1994) Slownik interpunkcyjny jgzyka polskiego z zasadami przestankowania,
Warszawa.
7. Banko, M. & Krajewska, M. (1995) Slownik wyrazow klopotliwych. Warszawa.
8. Pienkos, J. (1993) Przeklad i tlumacz we wspolczesnym swiecie. Warszawa.
9. Gural, S.K. & Smokotin, V.M. (2014) Language of global communication and linguistic and cultural globalization. Language and Culture. 1.
10. Pshenkina, T.G. (2014) Interdisciplinary translation as a reflection of the integrative processes in modern linguistics. Language and Culture. 1.
Information about the author:
Radoslaw Gajda, Doctor of Humanities in Linguistics, Faculty of Philology, Pedagogical University of Cracow, Poland. E-mail: [email protected]
