Ra-nuki kotoba and other usage shifts: when to correct and when to leave it

Every proofreader of Japanese eventually meets 見れる. It turns up in a company newsletter, a product page, a translated interview, a novel manuscript. The checker on this site flags it, most style guides for formal writing would change it to 見られる, and a large share of Japanese speakers say 見れる every day without a second thought. So what do you do with it?

The honest answer is that it depends on what kind of text you are holding. This piece explains what ra-nuki kotoba (ら抜き言葉, "words with the ra dropped") are, why they exist, and how to decide case by case. The same thinking applies to a handful of other usage shifts that a careful reader will notice, so those get a section too.

What a ra-nuki form actually is

Japanese verbs make their potential form ("can do") in two ways. Godan verbs (the "u-verbs" in many textbooks) have a separate potential verb: 書く becomes 書ける (kakeru, "can write"), 読む becomes 読める (yomeru, "can read"). Ichidan verbs (the "ru-verbs") and the irregular 来る use 〜られる:

• 見る → 見られる (mirareru, "can see")
• 食べる → 食べられる (taberareru, "can eat")
• 来る → 来られる (korareru, "can come")
• 起きる → 起きられる (okirareru, "can get up")

A ra-nuki form drops the ら: 見れる, 食べれる, 来れる, 起きれる. That is the whole change, one mora.

There is a reason it spreads. The form 〜られる does three jobs on ichidan verbs: potential, passive and respectful. 見られる can mean "can see", "is seen" or, as an honorific, "(a superior) sees". Dropping the ら gives the potential meaning a form of its own, which is exactly what godan verbs already have. Linguists often describe ra-nuki as the same regularising process that produced potential verbs like 書ける in an earlier period, now reaching the ichidan class. That does not make it standard in formal writing yet, but it explains why it feels natural to so many speakers, and why "it's just lazy" is the wrong way to think about it.

The Agency for Cultural Affairs (文化庁) has asked about these forms in its regular opinion survey on the Japanese language (国語に関する世論調査), which tells you something on its own: this is a recognised question of usage, not a typo.

Why a proofreader still cares

Even if you are relaxed about language change, ra-nuki forms carry social information. In a business report, a press release, a university application or a printed book's narration, many readers will take 見れる as casual or careless. They may not be right to do so, but the writer usually wants to avoid that reaction. In those texts the correction is a service to the writer.

In other texts the same correction damages the writing. If a teenage character in a novel says 「明日来れる？」, changing it to 来られる makes her sound like a newsreader. If an interview subject said 見れる, a verbatim transcript should keep it.

So the decision is never "is this correct Japanese?" in the abstract. It is "who is speaking, in what kind of text, to whom?"

A decision table

The one thing that is almost always worth flagging, whatever the register, is inconsistency inside a single voice. If the narration uses 見られる on page 3 and 見れる on page 40 with nothing in the story to explain the change, the author will want to know.

Fixing it without making the sentence stiff

The textbook fix is mechanical: put the ら back. Sometimes that produces something clumsy, especially with 来る, where 来られる is also a common respectful form. 「部長は明日来られますか」 could be "Can the manager come tomorrow?" or a respectful "Will the manager be coming tomorrow?". Usually context settles it, but when it does not, a rephrase is cleaner than a mechanical fix.

Some options:

• 見れる → 見られる, or 見ることができる when you want a neutral, slightly formal tone.
• 来れる → 来られる, or 来ることができる, or in a request 来ていただけますか.
• 食べれない → 食べられない, or for allergies and dietary notes 召し上がれない (respectful) or simply 食べることができない.

A worked example. Say a translator hands you this line for a hotel website:

当館のレストランでは、地元の新鮮な魚が食べれます。

Corrected:

当館のレストランでは、地元の新鮮な魚をお召し上がりいただけます。

The ra-nuki form was the visible problem, but the real fix was register: a hotel addressing guests would normally use a respectful construction anyway. When you find one usage issue in a sentence, read the whole sentence again for the level it should be pitched at. Our keigo checklist for business email covers that side in more detail.

Related shifts worth knowing

Ra-nuki is the best known, but not the only, usage shift that readers argue about. These come up often enough in proofreading to recognise on sight.

Sa-ire kotoba (さ入れ言葉)

The opposite movement: an extra さ added where it does not belong. The causative of a godan verb takes 〜せる (読む → 読ませる), and only ichidan and する verbs take 〜させる (食べさせる, 勉強させる). Sa-ire forms add さ to godan verbs, most often inside させていただく:

• 読まさせていただきます → 読ませていただきます
• 休まさせていただきます → 休ませていただきます
• 行かさせていただきます → 行かせていただきます

Unlike ra-nuki, this one rarely has a characterisation defence in formal writing, because it usually appears exactly where the writer is trying hardest to be polite. Correct it in business text. In dialogue, leave it if the speaker is meant to sound like they are overdoing the politeness.

Re-tasu kotoba (れ足す言葉)

An extra れ on a godan potential verb, which is already a potential form: 行けれる for 行ける, 書けれる for 書ける, 読めれる for 読める. It is less widespread than ra-nuki and more likely to be seen as an error. In formal text, correct it. In dialogue, leave it.

全然 with an affirmative

Many learners are taught that 全然 (zenzen, "at all") must be followed by a negative: 全然わからない. In casual speech, 全然大丈夫 ("totally fine") is very common, and some readers object to it. The "negative only" rule is less solid than it looks: older written Japanese has examples of 全然 with affirmative predicates, and dictionaries discuss both uses. For a proofreader the practical point is the same as with ra-nuki. In formal writing, 全然 with an affirmative reads as casual, so suggest まったく問題ありません or something similar. In dialogue and casual writing, leave it.

Meaning shifts in set expressions

Some expressions keep their form but drift in meaning, and different readers will understand them differently. 役不足 (yakubusoku) traditionally means the role is too small for the person's ability, but it is widely used to mean the person is not up to the role, which is the opposite. 気が置けない (ki ga okenai) traditionally means someone you can relax with, and is often taken to mean someone you cannot trust.

These are different from ra-nuki because the problem is ambiguity, not register. Even if the writer used the word in the newer sense and most readers will follow, some will read the opposite. Suggest a plainer phrase: 力不足 for "not up to it", or 気楽に付き合える for "easy to be around".

Misremembered set phrases

Then there are the outright mix-ups: 的を得る for 的を射る (mato o iru, "hit the mark"), 汚名挽回 where 汚名返上 ("clear one's name") or 名誉挽回 ("restore one's honour") was meant. These sit closer to errors than to usage shifts, though 的を得る in particular has defenders and some dictionaries now treat it as acceptable. The front-page checker flags several of these; the legend of issue types explains how it groups them and why some flags will be false alarms.

How to raise it with the writer

How you mark a usage point matters as much as whether you mark it. A few habits help.

1. Separate corrections from queries. A doubled particle (をを) is a correction. A ra-nuki form in narration is a query: "見れる → 見られる? Standard written form; keep if intentional." The writer can accept or reject it in a second.
2. Say why, briefly. "Formal register" or "inconsistent with p. 3" is enough. Long explanations in the margin slow everyone down.
3. Fix the pattern once. If a long document uses 来れる fifteen times in narration, raise it once with a note ("all instances in narration, dialogue left as is") instead of fifteen separate queries.
4. Respect a decision. If the author or client says they want the casual form, record it in the style sheet and stop flagging it.
5. Be careful with quotes. If you cannot tell whether a passage is a direct quote, ask. Correcting a real person's words in quotation marks is a bigger problem than leaving a ra-nuki form in place.

When a checker flags it

Rule-based checkers, including the one on this site, are good at finding 見れる and 来れる because the pattern is easy to match. They cannot tell whether the word sits in narration, dialogue or a quote, so they flag every instance. That is the right behaviour for a tool: it shows you where to look. The decision is still yours.

A sensible routine for a mixed document (say, a feature article with interview quotes):

• Run the text through the checker on the front page and note every ra-nuki flag.
• Go through the flags with the original in front of you. Mark each as narration, dialogue or quote.
• Correct the narration according to the house rule, leave quotes alone, and query anything unclear.
• Note the decision in the style sheet so the next person does not have to repeat it.

A rule of thumb

If you remember one thing, make it this: correct usage shifts where the writer is speaking in their own formal voice, and protect them where someone else is speaking. Ra-nuki forms are part of living Japanese, and a proofreader's job is not to stop language changing. It is to make sure each text says what it means, in the register its readers expect, consistently from start to finish. Most of the time that means putting the ら back in a business email and leaving it out of a character's mouth.