est. 1996

Want to Write for Us?
The Editor apologizes for the harsh tone of these instructions
- they are like that because the people they are for don't read them... [hint hint]

If you have any questions, please email the Classical Editor!

Every byte of Ink is ©1996-2001, us.

Write For Us
Infrequently Updated on
12 Dec, 2004
: Contact Us!
General enquiries:
classical@inkpot.com


CD submissions & sponsorship enquiries: benjamin@inkpot.com
(this means you sponsoring us.)


For individual writers, check the Inkpotters Page


: More Things
More Praise We try not to remember the bad ones.
The Inkpot in the News! We're a popular bookmark!
  Our Web Awards!!! Hey, we're not bad.

 

: The Inkpotters

Did you know that the people who write for the Inkpot are all volunteers? Cool huh? Meet

THE INKPOTTERS of today and yesterday!

 
 


You want to write for us? Sure... please read the following notes...

  • You may wish to note that we are a Singapore-based group and publication.

  • If you are not in Singapore, you can still submit CD reviews. We have a handful of American and British friends who continue to do so, and we are very proud to have them here. The exception to concert reviews is the Malaysian Philharmonic Orchestra. We very much welcome your input if you ever attend an MPO performance. Malaysians reviewing the MPO absolutely welcome too.

  • We try to maintain very high standards at The Flying Inkpot. Your review may not be accepted immediately. Rest assured however, that much consultation and advice will be offered to you to improve your review; and of course, you will always have your right to defend yourself. Don't be frightened - we love music because there is something in it that we want to express. Reviewing it and sharing with others is one way of doing it, but it is a complex process fraught with great and serious responsibilities that should never be underestimated.

  • Don't try to submit a review if you have not read any of ours. It's very obvious to the Editor (who has read all 900+ articles in the Classical Inkpot) when you do so. Familiarise yourself with the tone, style, length, depth and information required in our reviews by reading them; then, write and submit your review accordingly. Our reviews are all archived permanently in the Inkvault Classical Reviews Archive.

  • Download this simple template (text file) for submissions for CD reviews. Simply fill it in like a form. A concert review template is also available. Remember to include your tagline.

  • Email the whole review either as a Rich Text Format (*.rtf) attachment or in a simple text email to The Classical Music Editor. MS Word documents are not advised, due to their vulnerability to viruses and incompatibility problems . If you use MS Word to type your article, "Save As" Text or Rich Text Format.

  • Images. You need not provide images, as we can usually get our own. Images which you would like to offer for use should be sent as separate files. Images sent MUST NOT exceed 30 Kb each.

  • Avoid sending reviews of deleted CDs, ancient CDs (unless they are classics), or CDs which are available only on Mars.

  • Observe international characters. Language must be respected - always use international characters where required, for example: Pathétique, Laß Fürstin, Alliance Française, Fauré, Thaïs, Saint-Saëns, Eugène Ysaÿe, etc. If you do not know how to produce these on the keyboard, learn to. (Eg. Use MS Word and search for Help. Remember to save your reviews in Rich Text Format).

  • Please don't rush your review. Write it. Put it aside for a few days. Come back to it and refine it, then send it.

  • Word Length. As a *general* rule of a thumb, reviews should be between 500 to 1200 words. Reviews exceeding 1500 words are not unheard of, but that's a bit too long.

  • Detail. If the music is not well-known, you are expected to "dwell a bit" on an inktroduction. Do some research - writers must learn too.

  • Insight. The best reviews are those which offer insight, to even the oldest CDs or the most-discussed music.

  • Please be coherent. The Editor sometimes gets incoherent reviews and is willing to clean up your language for you; but as far as you can, write coherently.

  • Copyright. Copying someone else's words as your own is a major crime. If you quote from another's writing, make sure you provide full bibliographical details of your source: Author, Title of Publication, Publisher, Place and Date of Publication; and any other pertinent details.

  • Yourself. Please do introduce yourself when you contact us! We want to know what music you love! And you will find that identifying your name in full is VERY USEFUL too.

  • Tagline. Please include a tagline for your review. (Those lines about yourself at the end of articles).

  • Email the whole review either as a Rich Text Format (*.rtf) attachment or in an email to The Classical Music Editor.

  • The Editor is Derek Lim; please do not be surprised or run away screaming when he replies to you.... :)


If you have any other questions, just email the Classical Editor!

THE FLYING INKPOT
Chief & Film Editor (Retired): Rebecca Wan
Theatre Editors: Arthur Kok/Kenneth Kwok
Classical Music Editor: Derek Lim

Writers and Past Contributors

FILM

Rebecca Wan
WenQing
Jack Choo
Lee Su Fern
Dominic Ow
Sherrie Lee
Adele Tan
Lau Chee Nien

THEATRE

Arthur Kok
Sherrie Lim
Kerryn Chan
Chong Tze Chien
James Koh
Kenneth Kwok
Daniel Teo
Adele Tan

CLASSICAL

Derek Lim
Benjamin Chee
Jonathan Yungkans
James Wegg
Steven Ang
Tan Beng-Ti
Chia Han-Leon
Johann D'Souza
William Beh
The Inkpot Sibelius Nutcase
Marc Bridle
Adrian Tan
Ng Yeuk Fan

Darrell Ang

Michael Anthonio
Ong Yong Hui
Soo Kian Hing
Isaak Koh

Anthony Guneratne
Evan Stephens
Jonathan Bushrod
Jeffrey Dane
Kerryn Chan
Marc Bridle
Roy Chan

René Chia
May Lynn
Rebecca Wan
Priscilla Kang
Lim Tee Heong
Lim Song Ann
Timothy Lum

 

 

 

The Flying Inkpot is proud to be This website is created with
Macromedia Dreamweaver and Fireworks
· est.1996 · I don't use Photoshop!
 
Every byte of Ink is ©1996-2001, us.
Permission to reproduce original content can be sought from the Classical Editor