Journal article
Educating Croesus: talking and learning in Herodotus' Lydian logos
- Abstract:
-
Two themes, the elusiveness of wisdom and the distortion of speech, are traced through three important scenes of Herodotus' Lydian logos, the meeting of Solon and Croesus (1.29–33), the scene where Cyrus places Croesus on the pyre (1.86–90), and the advice of Croesus to Cyrus to cross the river and fight the Massagetae in their own territory (1.207). The paper discusses whether Solon is speaking indirectly at 1.29–33, unable to talk straight to Croesus about his transgressive behavior: if so,...
Expand abstract
- Publication status:
- Published
- Peer review status:
- Peer reviewed
Actions
Authors
Bibliographic Details
- Publisher:
- University of California Press Publisher's website
- Journal:
- Classical Antiquity Journal website
- Volume:
- 25
- Issue:
- 1
- Pages:
- 141-177
- Publication date:
- 2006-04-01
- DOI:
- EISSN:
-
1067-8344
- ISSN:
-
0278-6656
Item Description
- Language:
- English
- Keywords:
- Subjects:
- UUID:
-
uuid:39a41626-a092-4164-8e32-4de52097cf4b
- Local pid:
- ora:1511
- Deposit date:
- 2008-03-14
Related Items
Terms of use
- Copyright holder:
- The Regents of the University of California
- Copyright date:
- 2006
- Notes:
- Published as Pelling, C. (2006). 'Educating Croesus: talking and learning in Herodotus' Lydian logos', Classical Antiquity, 25(1), 141-177 © 2006 by the Regents of the University of California. Copying and permissions notice: Authorization to copy this content beyond fair use (as specified in Sections 107 and 108 of the U. S. Copyright Law) for internal or personal use, or the internal or personal use of specific clients, is granted by the Regents of the University of California for libraries and other users, provided that they are registered with and pay the specified fee via Rightslink® on Caliber (http://caliber.ucpress.net/)/ AnthroSource (http://www.anthrosource.net) or directly with the Copyright Clearance Center, http://www.copyright.com.
If you are the owner of this record, you can report an update to it here: Report update to this record