Abstract

The permanent changes in the dynamics of discourse marker use in conversation triggers the necessity of re(modeling) the already existing patterns of analysis in such a way as to adapt them to the new discursive realities and practices. The best analysis of discourse marking functions and discursive roles can be done in real instances of conversation. Therefore, the corpus on which the analysis is performed is composed of conversations in Romanian, my own samples of recorded conversation between Romanian speakers. The analysis of discourse markers in conversation requires a pragmatic-functional perspective. Hence, I suggest a different classification of the discursive attributions that discourse markers have in conversation by advocating for the pragmatic-functional categories of discursive roles and discursive functions. These two categories, in which the various discursive attributions of markers were placed, represent the framework for the analysis of the discourse markers “deci” and “şi” which is conducted in this paper. Furthermore, a presentation of the discursive functions and roles of two of the most frequently used Romanian discourse markers: “deci” and “şi” will be made. The functions and roles of these markers are supported by relevant illustrative examples which demonstrate the importance of the conversational context in establishing the pragmatic role that markers could have in casual and formal conversations.

Full Text
Paper version not known

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.