25.12.2013 Views

0 INTRODUCTION

0 INTRODUCTION

0 INTRODUCTION

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

6. FINDINGS<br />

The data presented above seems to indicate that, generally, Romance nominals are<br />

borrowed as wholes into English. Later, when they are assimilated into the language, their<br />

bases are used to create new words using native suffixes. However, since the way of<br />

introduction of Romance nominalizations will be extensively analyzed in Section 6.2<br />

below, it is at this point that we will analyze why these new hybrid formations, apparently<br />

synonyms of already existing words, are needed in the language.<br />

6.1.5.3. Frequency of the elements of the doublet<br />

Table 16 shows the origin of the most frequent element of the doublet. In the majority of<br />

cases, the Romance element is employed more frequently (59.2% vs. 13.3% for the –ing<br />

nominal). These results are in line with those of Table 14, which showed that<br />

nominalizations formed from Romance suffixes have a higher token frequency than native<br />

ones. Going back to Table 16 below, when both elements show the same frequency, this is<br />

usually low, with only one or two occurrences in the text.<br />

Table 16. Origin of the most frequent element of the doublet. 19<br />

–ing nominal Romance Equal<br />

13 (13.4%) 58 (58.8%) 27 (27.8%)<br />

6.1.5.4. Constituents of each nominalization phrase<br />

In order to give an account of possible differences in the grammar of the two elements of<br />

the doublets, they were then classified according to the type of constituents with which<br />

they usually collocate, that is, according to the structure of the phrase as a whole.<br />

19 Nominalizations where both members are of Romance origin have been excluded from the count here.<br />

193

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!