z-logo
open-access-imgOpen Access
Oosgrensafrikaans: ’n te eksklusiewe begrip?
Author(s) -
Heinrich Grebe
Publication year - 1999
Publication title -
literator
Language(s) - English
Resource type - Journals
SCImago Journal Rank - 0.126
H-Index - 4
eISSN - 2219-8237
pISSN - 0258-2279
DOI - 10.4102/lit.v20i1.446
Subject(s) - cape , variety (cybernetics) , population , history , genealogy , geography , sociology , demography , mathematics , archaeology , statistics

Eastern Cape Afrikaans (Oosgrensafrikaans): as concept too exclusive? Based upon historic-geographical considerations Van Rensburg (1984:514; 1989:436-467; 1990:66-67) distinguishes three early varieties of Afrikaans, i.e. Eastern Cape Afrikaans (Oosgrensafrikaans), Cape Afrikaans (Kaapse Afrikaans) and Orange River Afrikaans (Oranjerivierafrikaans). Standard Afrikaans is then considered to be based upon Eastern Cape Afrikaans. In the light of especially this last claim, the theoretical status of Eastern Cape Afrikaans becomes of paramount importance in any study delving into the development of the Afrikaans language.

This article discusses the outcome of a critical analysis of relevant literature dealing with particularly Eastern Cape Afrikaans. The outcome of this analysis has indicated that the theoretical basis upon which the positing of Eastern Cape Afrikaans as an early separate variety of Afrikaans has been based, has serious theoretical flaws. A critical shortcoming of the present hypothesis bears upon the assumed geographical positioning of Eastern Cape Afrikaans. A culturally and numerically important component of the Cape Colony's burger population is seemingly not accounted for.

It is suggested that the possibility of broadening the geographical base of Eastern Cape Afrikaans should be considered. Serious empirical research should also be undertaken before any claim regarding the genealogy of Standard Afrikaans could be considered at all

The content you want is available to Zendy users.

Already have an account? Click here to sign in.
Having issues? You can contact us here