Postcolonial Theory and the Arab–Israeli Conflict
Postcolonial Theory and the Arab–Israeli Conflict is a 2008 book edited by Philip Carl Salzman and Donna Robinson Divine and published by Routledge Press. The book is based on the proceedings of a conference on "Postcolonial Theory and the Middle East" held at Case Western Reserve University in 2005.[1] The essays were first published in a special issue of the journal Israel Affairs.[2]
Contents
The book contains the following essays:
- Irfan Khawaja, “Essentialism, Consistency, and Islam: A Critique of Edward Said’s Orientalism”
- Ronald Niezen, “Postcolonialism and the Utopian Imagination”
- Ed Morgan, “Orientalism and the Foreign Sovereign: Today I am a Man of Law”
- Laurie Zoloth, “Mistaken-ness and the Nature of the ‘Post”: The Ethics and the Inevitability of Error in theoretical Work"
- Herbert Lewis, “The Influence of Edward Said and Orientalism on Anthropology, or: Can the Anthropologist Speak?”
- Gerald M. Steinberg, “Postcolonial theory and the Ideology of Peace Studies”
- Efraim Karsh, “The Missing Piece: Islamic Imperialism”
- David Cook, “The Muslim Man’s Burden: Muslim Intellectuals Confront their Imperialist Past”
- Andrew Bostom, “Negating the Legacy of Jihad in Palestine”
- Philip Carl Salzman, “Arab Culture and Postcolonial Theory”
- Richard Landes, “Edward Said and the Culture of Honour and Shame: Orientalism and our Misperceptions of the Arab–Israeli Conflict”
- Gideon Shimoni, “Postcolonial Theory and the History of Zionism”
- S. Ilan Troen, “De-Judaising the Homeland: Academic Politics in Re-Writing the History of Palestine”
- Donna Robinson Divine, “The Middle East Conflict and its Postcolonial Discontents”
- Irwin J. Mansdorf, “The Political Psychology of Postcolonial Ideology in the Arab World: an analysis of ‘Occupation’ and the ‘Right of Return’"
gollark: All the parser implementations around should accept that as valid, and you can use a fixed amount of size.
gollark: Okay, very hacky but technically workable: have an XTMF metadata block of a fixed size, and after the actual JSON data, instead of just ending it with a `}`, have enough spaces to fill up the remaining space then a `}`.
gollark: XTMF was not really designed for this use case, so it'll be quite hacky. What you can do is leave a space at the start of the tape of a fixed size, and stick the metadata at the start of that fixed-size region; the main problem is that start/end locations are relative to the end of the metadata, not the start of the tape, so you'll have to recalculate the offsets each time the metadata changes size. Unfortunately, I just realized now that the size of the metadata can be affected by what the offset is.
gollark: The advantage of XTMF is that your tapes would be playable by any compliant program for playback, and your thing would be able to read tapes from another program.
gollark: Tape Shuffler would be okay with it, Tape Jockey doesn't have the same old-format parsing fallbacks and its JSON handling likely won't like trailing nuls, no idea what tako's program thinks.
References
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.