This illuminated and illustrated copy of the Khamsah (quintet) of Niẓāmī Ganjavī (d. 605 AH / 1209 CE) was executed in Safavid Iran and dates to the middle of the tenth century AH / sixteenth CE. There are six colophons in Arabic that supply neither the date nor the scribe’s name (fols. 31b, 119a, 175a, 238a, 325a, and 371a). The text is written in black nastaʿlīq script with section headings in blue. Twenty paintings attributable to the Shiraz school illustrate the text. The dark brown leather binding with central ovals and pendants, all brushed with gold, is original to the manuscript.
Colophon of the publisher Aldus Manutius (Italian, 1450-1515), established the Aldine Press in 1493 in Venice to published numerous Greek and Latin classics, greatly contributing to the spread of the Renaissance.
If you do not know what writing is, you may think it is not especially difficult… Let me tell you that it is an arduous task; it destroys your eyesight, bends your spine, squeezes your stomach and your sides, pinches your lower back, and makes your body ache… Like the sailor arriving at port, so the writer rejoices on arriving at the last line.
We are so proud of our designer Helen Yentus who is bringing Riverhead Books into the new year with a “fiercely contemporary” new colophon. Check out Paste Magazine’s interview with her to learn more…and be sure to check in throughout the week to see our new colophon on new surfaces and locations throughout NYC!
Illuminated Manuscript, Collection of poems (masnavi), A wise man and a peacock plucking out its feathers not to be attractive to people, Walters Art Museum Ms. W.626, fol. 220b detail by Walters Art Museum Illuminated Manuscripts Via Flickr: This is an illustrated and illuminated copy of the collection of poems, known as Mas̱navī-i maʿnavī, of Jalāl al-Dīn Rūmī (d. 672 AH / 1273 CE). According to the colophon (fol. 314b), the text, written in black nastaʿlīq script, was completed in India in 1073 AH / 1663 CE. Each section of the work is introduced by a double-page illuminated incipit containing a preface in prose, followed by two illustrations and an illuminated incipit page for the masnavi. In total, fifty paintings illustrate the text. The green leather binding is modern.
Five Years / Available at www.draw-down.com / Printed in an edition of 300 copies / FIVE YEARS catalogues twenty-six typefaces made from 2009–14 by Colophon type designers Anthony Burrill (UK), Benjamin Critton (US), Alison Haigh (UK), Oscar & Ewan (SE), Studio Makgill (UK), The Entente (UK), and Dries Wiewauters (NL). Featuring 26 compositions made on behalf of the aforementioned typefaces, an essay by Aileen Kwun of Project Projects and Superscript, and information on each typeface and its provenance, FIVE YEARS is a near-exhaustive catalogue raisonné of the first half-decade of Colophon Foundry. #graphicdesign #typography #colophon #book #art #letters #type #design #modern
At Menoovr we are at a junction where we are on our way to meet our first milestone as a startup on May 2, 2011 since our start (at #swsj (@SWsj) on Aug 15 2011) and the key component of it is laying the technology foundation.
One of the most common questions that keeps coming back are related to which technologies/tools to use and the main theme around all of these questions can be put into two buckets:
Familiarity vs Trend
Time to market vs Solid Foundation
And when I am asked for my opinion or sometimes asked to make a decision to go one way or the other, as a Non-Developer Tech Guy schooled in Technology Risk Management I look at things from the following angle:
1. What are the risks of using one framework/tool vs another.
2. Can we mitigate the risks?
3. Do we have to accept/consume any risks?
4. If we must, do we have the appetite for it?
When I go down this route…the first set of things I look at it is:
1. Who’s behind a tool/framework?
2. Who’s using it?
3. How active is the community?
4. What is its roadmap?
Oh..and if at anytime we have to pivot to a different tool/framework…can we?
Asking these questions to Developers can be challenging as more often than not Developers/Engineers have a technology bias based on experience. Which I respect!
However, when you are working with a solid team (one of the very few companies I have seen that showcase Open Employee Testimonials on their client facing website) like my friends at Karthavya (http://www.karthavya.com/index.html) it becomes a fairly friction free conversation.
On having looked at the above and making a Non-Developer assessment of the facts and extensive technology commentary such as this:
I leaned towards Node.JS and had a good chat with my team-mates regarding the same.
The team is going to decided by COB today taking into account the above items from the lens of these two themes “Familiarity vs Trend” & “Time to market vs Solid Foundation”.
However, I’d like to share this with the community here on our blog & on twitter to get more feedback/advice/pointers. We are not just building a community tool but a community experience, thus getting feedback from the commnity and incorporating it into not just our product but our decisions is an integral part of what we do here at menoovr.
Please share your thoughts, advice, feedback and do invite your network of tech ninjas to opine as well.