|Product Name||Magical Alphabets: The Secrets And Significance Of Ancient Scripts -- Including Runes, Greek, Ogham, Hebrew And Alchemical Alphabets|
|Category||Book / Magazine / Publication|
|Amazon.com||Buy on Amazon ~ 0877287473|
|Price New||9.94 US Dollars (curriencies)|
|Price Used||3.30 US Dollars (curriencies)|
|Width||0.58 inches (convert)|
|Height||8.25 inches (convert)|
|Length||5.38 inches (convert)|
|Weight||11.2 ounces (convert)|
|Long Description||Using the premise that languages and the alphabets that comprise them are metaphorical microcosms of our world, Nigel Pennick demonstrates how various alphabets function as a metaphysical description of reality. Magical alphabets actually enable seekers to experience a transformative process. This inner transformation is one of the main objectives of all esoteric traditions, and it can be accomplished by using any of the alphabet systems described in this book. Pennick's exciting exploration of Western alphabetical systems includes information about the origins of Hebrew and Greek alphabets, Celtic oghams, and medieval and Renaissance magical and alchemical alphabets. His examination uncovers evidence of the widespread use of runes throughout northern and central Europe, as well as the use of letter systems for operative and ceremonial magic. From grid ciphers to numerology to modern uses, this book provides an in-depth study of the magic present in a tool we use every day-- the alphabet.|
|Similar Items||9781855381056: Rune Magic: The History And Practice Of Ancient Runic Traditions|
9780892818679: The Pagan Book Of Days: A Guide To The Festivals, Traditions, And Sacred Days Of The Year
9780962604638: Futhark: A Handbook Of Rune Magic
9780877285489: Futhark: A Handbook Of Rune Magic
9780875427836: The Book Of Ogham : The Celtic Tree Oracle
9781620553152: The Book of Primal Signs: The High Magic of Symbols
9780850308716: Runic Astrology: Starcraft And Timekeeping In The Northern Tradition
9780738533100: The Watkins Dictionary of Magic: Over 3,000 Entries on the World of Magical Formulas, Secret Symbols and the Occult
9781842931523: The Watkins Dictionary of Magic: Over 3,000 Entries on the World of Magical Formulas, Secret Symbols and the Occult
9781862041004: The Complete Illustrated Guide To Runes
9780007129997: The Complete Illustrated Guide to Runes
9780892819195: Ogam: The Celtic Oracle Of The Trees: Understanding, Casting, And Interpreting The Ancient Druidic Alphabet
9780760707265: Reading The Past: Ancient Writing From Cuneiform To The Alphabet
9780976568117: Ogham: The Secret Language Of The Druids
9780877287520: Secret Games Of The Gods: Ancient Ritual Systems In Board Games
|Search Google||by EAN or by Title|
Article of interest
The data feed API is URL based, but if you prefer to use the REST interface, you can do most things using that method.
Your API key should be in the request header "x-api-key" but will also work on the URL if you prefer using keycode=????????
When accessing the API using REST, the URL needs to be in this format:
version: The API version you are trying to access starting with the letter "v" followed by the version number as an integer. (ie: v3 or v2)
action: The action you wish to perform. Not all actions are currently available using the API. The ones that work currently are:
- find: perform a data lookup
- search: perform a text search
- asin-to-ean: convert an Amazon ASIN into an EAN
- imdb-to-ean: convert and IMDB ID into an EAN
dataID: This is the data you are searching for. For "find" this is an EAN or UPC code. For "search" this can be any text properly encoded for he URL.
To get your data back as XML, put "application/xml" in your "accept" header. If you prefer JSON (the default format) you can leave off the "accept" header or send "application/json". You can also include your preference on the URL using mode=json or mode=xml but using the request header is the preferred method.
We will continue to add more REST interface features in the future so be sure to check back on this page every once in a while.
*** Updating data via the REST interface is not ready yet but will require test=1 on the URL as the first variable if you are testing your application to prevent actual data updates. Placing it later on the URL could cause this variable to be skipped if you have errors in your URL.