Frequently asked questions regarding the Honyaku mailing list, this website, and translation in general.
"Two heads are better than one," the saying goes, or, in Japanese, "sannin yoreba monju no chie."
The Honyaku mailing list is an open mailing list, started in 1994 by Dan Kanagy. The list currently is running on Google Groups under the guidance of a crack team of moderators. There are about 530 members as of this writing.
If you are a translator and have become stuck over how to handle a particular phrase, ask your question here. Other questions or discussions related to translation are welcome. Then be amazed at what you can learn from the collective mind.
You don't have to be a professional translator to participate in the list. Everyone with an interest in the English and Japanese languages and in establishing connections between them is welcome.
The Honyaku mailing list is currently hosted by Google Groups, which has a straightforward web-based system for subscribing, unsubscribing, and managing your list preferences . I recommend doing it via the web, but you can do it the old-fashioned way by e-mail, too--see below.
Google Groups has its own FAQ for basic subscription mechanics at http://groups.google.com/support/
To subscribe to the Honyaku mailing list, send an e-mail message to:
honyaku-subscribe@googlegroups.com
This message must be from the address you want to use, but can contain any kind of message
When you are subscribed to the list, you can post your own messages for distribution to everyone else. Send your post to:
honyaku@googlegroups.com
You must send your post from the same e-mail address at which you subscribed to Honyaku.
To unsubscribe from the Honyaku mailing list, send an e-mail message to:
honyaku-unsubscribe@googlegroups.com
This message must be from the address you subscribed from, but can contain any kind of message
As near as I can tell, this is something that you must handle via the Google Groups website. You can choose to have mail delivery stopped (but can still read messages on the web), or have digest delivery.
Honyakuhome.org (formerly the Honyaku home page) is an adjunct to the Honyaku mailing list.
This website has been in existence in some form since 1994. It currently runs on the Drupal content-management system, with some custom code for translator profiles. It is administered by Adam Rice.
The site has a few key features.
Translators and interpreters can set up profiles showing their language pairs, fields of specialization, etc. These profiles can also be searched by language pair and specialization using the "Search Profile" box on every page.
The original function of this site was to be a human-compiled index of sites useful to translators, similar to dmoz. Any registered member of the site can suggest a link, and members are encouraged to do so. Suggested links are always vetted before they go live on the site.
The site serves as a conduit by which anyone can pass along a job offer to members of the Honyaku mailing list. These offers are always vetted before being passed on.
This site has a forum for discussing site issues.
I will consider adding additional features if they are technically feasible and there is demand for them
One of the main reasons for the Honyaku mailing list is terminology research. This site could serve as a structured memory for terminology discussions.
Local and international events of interest to translators could be publicized here.
In theory, it is possible to tie the Honyaku mailing list to a forum, with posts made in one place propagating to the other.
Brian Chandler maintains a text archive of Honyaku traffic (previously maintained by Tom Gally).
Ryan Ginstrom has created a searchable database of the Honyaku archives, called honyaku-archive.org appropriately enough. This is up to date, and takes over from a previous version created by Asako Mizuno.
Not Honyaku: For discussions not suited to the Honyaku list.
Honyaku OSX: For discussions of interest to Japanese translators using the Mac OS X operating system.
Nihongo-computing: For discussions of Japanese-language issues in computing.
The Japan Association of Translators holds monthly meetings in Japan, publishes a newsletter, and sponsors the IJET conference.
The Society of Writers, Editors, and Translators is based in Tokyo, holds monthly meetings and other events, publishes a newsletter, Wordcraft (a compendium of articles from its newsletter) and the Japan Stylesheet.
The Honyaku mailing list has a lot of traffic, and has developed its own culture. Some of the guidelines here are specific to Honyaku, some are just good netiquette in general.
This question is occasionally debated on the list, but hasn't been resolved. Many feel that the list should be kept tightly focused on specific terminology- and translation-related questions; that the list should serve as a tool for getting jobs out the door quickly. Others like to use the list to discuss more peripheral issues, such as getting Japanese-processing capability on one's computer, discussing office set-ups and practices, and general socializing. This difference has occasionally caused members of the list to consider splitting the list into one list for hard-core translation questions, and another for socializing. So far, this hasn't happened, as the list-splitters have not achieved a majority and in any case, it would make more work for Dan, the list administrator. Also, since Honyaku moved to a fairly expensive service that specializes in running mailing lists, it seems very unlikely to happen. To accomodate everyone, a number of tips on posting style have evolved. See the section below, "Is there a preferred format for posts".
Regardless of whether you feel the list should have a tight or loose focus, there are a lot of issues that keep coming up, and many people justifiably feel that rehashing the same problems is a waste of bandwidth on the list. (As previously mentioned, one of these issues is using Japanese on computers, but there are others.) Although this FAQ is nominally the place for the answers for all these questions to be stored, the range of issues is too great for a FAQ to handle properly. One suggestion that we would like to pursue is that people knowledgeable in a specific subject area would write up an informative document on that subject. This would create a standing "knowledge base" for the list members. These documents would be available to Honyaku members the same way the FAQ is, but would address these other issues in more detail than this FAQ can handle. If you would like to contribute an article, mention it on the list. Note: I (Adam Rice), am the person to contact if you want to contribute to this project.
Generally, the only restriction is that your post should pertain to translation between Japanese and English. Please don't cross-post information from other lists or Usenet newsgroups unless it relates directly to discussion on the list. Since the list is concerned with the use of language, we sometimes do discuss crude language, but we still try to be polite about it.
Newcomers to the Internet inevitably get scared by one of the numerous hoax virus warnings on the Internet, like the "Good Times" virus, and pass along the warning to Honyaku. Unless the rumour can be substantiated, don't pass it along.
Whenever you run into a translation-related question, it may be tempting to post that question to the list. But Honyaku is a very busy place, so try to be a good Honyaku "citizen" by keeping traffic down. Stop and try to exhaust your own resources first. If it is not a terminology-related question, it might be answered in this FAQ, or somewhere on the web (the Honyaku home page might help). For terminology questions, you might try searching for the term through one of the web search engines. And if you have a big hard disk and really want to go the extra mile, you can download the entire Honyaku archive to your hard disk and search through that on your computer (a number of Honyakkers do this already). Often your question has been asked before. The same questions do come up now and then. This doesn't mean that it isn't OK to ask them again: the membership of the list changes, and new people can bring new insights. It is possible that there was no satisfactory resolution to the question in the past.
Advertising, commercial postings, or publicity is OK within certain limits. Your product or service should be directly related to translation. Dan recommends that you should limit the post to about a screenful of text and invite people to contact you directly for more information. He also recommends that if you are worried about catching flack for posting an ad, then you should clear it with him first.
Although it is acceptable to recruit translators to do pro-bono work for good causes, it is not acceptable to send out personal requests asking members of the list to do work for free (such as personal letters, homework assignments, etc). This is a list for professional translators doing professional work.
Offering or soliciting translation work is not merely OK, but positively encouraged.
The honyaku list, as you will learn (if you haven't already), is a very active one, and is meant to be a tool for professional translators. As such, we have gradually evolved a bunch of practices to make the list work more efficiently. The list below is admittedly long, and can only be thought of as suggestions, not rules, but I'll go out on a limb here and say that most of these suggestions would be appropriate for just about any mailing list. The guiding principle behind all these suggestions is to make your posts more convenient for everyone else. The extra work you put into writing your message is paid back many times over by the hundreds of people who will have an easier time reading it.
Here are some of the abbreviations that crop up in Honyaku posts:
Some abbreviations common in e-mail in general:
This is the sort of question that the Department of Justice would probably rather I don't discuss, as it could be construed as anti-trust, but I'm probably on their shitlist anyhow, so here goes.
There is no single system for assessing the length of a translation. Very few translators bill for their translation on the basis of time: almost all bill based on the length of either the source text or the translated text. Sometimes there is non-translation work involved in doing a translation (research, DTP, etc), and this is the sort of thing that might be billed on a time basis, if you can convince the client to pay you for it at all.
Your client may already have a preferred basis for calculating the length of the job. If so, you'll probably want to go along with that. If not, read on and decide on a system that makes sense for you.
The ways to determine the number of units of work in a job seem to be as various as translators themselves. J-E translators that bill based on the length of a source Japanese document will usually bill by the 400-character genkou youshi. Using the source as the basis for billing has the advantage of being readily understood by the client--in fact, the client can know in advance how much you will charge. It also does not penalize the translator for concision, or reward him for verbosity. One disadvantage is that not all jobs come in a form that makes it easy to count the number of characters.
Billing based on the translated text gets more complicated. This may be by the word, by a certain number of characters (for instance, 1000), or by the page. Calculating the page length raises another question though. Some translators call 200 words a page. Some call 1000 characters a page. Some use an actual printed page that is laid out, for example, 60 characters wide and 25 lines long (assuming use of a monospaced typeface, of course). For that matter, I have heard of calculating one word as being six bytes, not a string of letters that sit between spaces on a line. But of course there will be variations in the exact numbers used. With work being more and more electronic, using a printout as the basis for billing a job seems a bit archaic, but can work to your advantage if the printed pages are sparse (as is the case with spec sheets).
Anecdotal evidence is incomplete, but gives us a general sense of billing practices in different countries. Translators in the USA and Canada seem to charge by the English word, for both E>J and J>E translation. In the UK, translators commonly bill in units of 1,000 Japanese characters for translations in either direction (though I also heard from an E>J translator who bills in units of 1,000 English words). Translators in Australia bill either by the English word, or in units of 100 English words. In Japan, most J>E translation is billed by the page, where a page is variously defined as a certain number of words (ranging from 200-250), or a certain number of characters (anywhere from 1,000 to 1,300), or even as a physically printed page. E>;J translations may be billed by the number of words in the English source, or by 400-character translated pages.
It is worth noting that if you are using your word-processor's word-count feature to help you calculate your bill, you should be aware that not all word processors will give the same word count for a given document. Some will not count numbers as words, which can be a significant consideration. Some don't count hyphenated words as multiple words, which can really set you back if you are given to oh-so-extended-hyphenated-phrases.
Another consideration is whether or not to bill for translator's notes. Again, different translators approach this differently. If you are using footnotes as opposed to inserting your notes in the main body of the text, your word-processor's word-count feature can probably report the length of the footnote text separately, allowing you to separate it out if desired/required.
Let's assume you have the source document, preferably in electronic form, so that you can do a character/word count easily. Without the source, it is pointless to try guessing the length of the translation.
I have analyzed a few of my past jobs to determine a ratio of Japanese characters to English words, and found the ratio is 3.46:1 at the high end to 2.24 on the low end. For the purposes of giving advance estimates, a good rule of thumb is 2 Japanese characters for 1 English word. This will usually give you a little slack, and is easy for the customer to understand.
The short answer is "as much as you can." In the USA, I have heard of rates ranging anywhere from 5 cents per word (from scummy translation job-shops) to 30 cents per word (for specialty work done by a certified professional in that field). Agencies commonly pay from 10 to 15 cents; direct customers usually pay somewhere in the ballpark of 20 cents, although there are some direct clients that deal with their translators very much like agencies do, and pay them agency rates. In Japan, low-ball agency rates may be as low as Y2,500 per page, and at the pinnacle of the profession (where the job is more like writing copy than translating), I have heard of Y10,000 per page. Y3,500 or a little higher is quite common, with Y5000 evidently being the upper limit of commonly-available rates. Japanese clients tend to pay somewhat higher rates than do American clients, although the the end of the bubble era has pushed rates down in Japan as well. Rates in Australia may be 20-30 Australian cents per word, or higher for specialized work. Rates in England range from 35 to 90 pounds per 1,000 Japanese characters, which works out (very roughly) to 10 cents to 25 cents per English word (assuming about 2 Japanese character per 1 English word). These figures are anecdotal.
Everybody has their own logic in setting rates, but a generally-agreed principle is that you should charge a rate that keep you busy with work you want to do. Some people accept fairly low rates because it allows them to gather large quantities of work that they can do very efficiently, so they wind up making a good deal of money on an hourly basis. Others price their services high, allowing them to work more slowly--perhaps because the nature of the work precludes speed--without compromising their earning power. Other factors that figure into people's logic are whether or not they have a proven track record, pride preventing them from taking a low rate, etc.
Ideally, of course, you will get work that both pays well and permits quick work. Inevitably, you will wind up with clients that pay different rates, and the trick becomes juggling them so that the cheap work does not crowd out the more lucrative work. Just remember that a job is not lucrative just because it has a high unit rate: other factors (illegible manuscripts, convoluted writing, difficult clients, etc) may make it much slower or more frustrating than other work, negating any perceived advantages.