Editing for a Consistent Register | Indonesian Grammar

Register consistency is a grammatical pattern across a text, not a blacklist of slang words. Replacing gue with saya does not make a paragraph formal if its verbs remain conversational roots, its negator is nggak, its address shifts between kalian and Bapak/Ibu, and its punctuation imitates excited chat.

This page gives a whole-text editing method. It coordinates pronouns, affixes, negators, particles, vocabulary strata, punctuation, and audience. The register continuum supplies the broader map. This page does not reteach each paradigm or prescribe one register for every communicative purpose.

Define the target before editing

An editor needs four decisions:

Decision	Question	Example consequence
audience	friends, colleagues, customers, officials, or unknown public?	aku, saya, title, or institutional kami
purpose	chat, request, record, instruction, persuasion?	fragment versus explicit action and deadline
channel	speech, group chat, post, email, report?	particles and line breaks versus edited punctuation
relationship	familiar, equal, upward, service, public?	kamu, name, Bapak/Ibu, or omission

Din, berkasnya aku kirim habis makan siang, ya.

Din, I’ll send the file after lunch, okay? (close coworker chat; informal)

Bu Dina, berkas tersebut akan saya kirim sebelum pukul dua siang.

Ms. Dina, I will send the file before two in the afternoon. (professional/upward)

Kami akan mengirimkan berkas tersebut kepada seluruh peserta sebelum pukul dua siang.

We will send the file to all participants before two in the afternoon. (institutional/formal)

The proposition is similar; the social role, precision, and morphology change together.

💡

Never begin a register edit by replacing individual words. Write the target audience, channel, purpose, and relationship at the top of your checklist first.

Diagnose the whole system

Use seven passes:

Person reference: Are first and second persons socially compatible?
Affixation: Do active and passive forms match the target register and participant roles?
Negation: Are tidak/bukan/belum or colloquial nggak consistent?
Particles: Do stance markers suit the relationship and channel?
Vocabulary: Are technical, bureaucratic, English, and colloquial strata coherent?
Punctuation: Does the text behave like edited prose, speech transcription, or chat?
Audience obligations: Are action, owner, time, and contact explicit enough?

Saya nggak bisa menghadiri rapat tersebut, ya.

Mixed but possible in some speech: formal saya/tersebut with colloquial nggak and relational ya.

Saya tidak dapat menghadiri rapat tersebut.

I am unable to attend that meeting. (formal/neutral)

Aku nggak bisa ikut rapatnya, ya.

I can’t join the meeting, okay? (peer conversation; informal)

The first is not universally ungrammatical. It may be intentional careful speech. The editing question is whether the larger text sustains that middle register or drifts unpredictably.

Pronouns and address must form one relationship

Monitor every first-person and second-person expression, including possessors and titles. Saya–Bapak/Ibu, kami–Anda, aku–kamu, and names can be coherent pairings in the right context. Randomly mixing them is not warmth.

Bu Rina, apakah Ibu sudah menerima laporan yang saya kirim?

Ms. Rina, have you received the report I sent? (respectful professional)

Rin, laporan yang aku kirim kemarin sudah masuk belum?

Rin, did the report I sent yesterday come through? (close peer; informal)

Pelanggan dapat memperbarui alamat melalui akun Anda.

Inconsistent generic reference—pelanggan is third person but Anda abruptly addresses the reader.

Anda dapat memperbarui alamat melalui akun Anda.

You can update the address through your account. (direct formal instruction)

Pelanggan dapat memperbarui alamat melalui akun masing-masing.

Customers can update their addresses through their respective accounts. (third-person formal)

Choose direct or third-person audience design and maintain it.

Affixes encode more than formality

Formal writing often favors complete standard forms: memberi tahu, mengirimkan, memeriksa, memperbarui. Casual speech may use bare or reduced forms where licensed: kasih tahu, kirim, cek. A bare imperative such as perbarui alamat Anda can remain fully standard because imperative syntax—not casualness—licenses the form without the actor prefix. Editing must preserve voice and valency, not mechanically add meN-.

Nanti aku kasih tahu kalau jadwalnya berubah.

I’ll let you know if the schedule changes. (informal)

Kami akan memberi tahu peserta apabila jadwal berubah.

We will notify participants if the schedule changes. (formal)

Tim akan ngecek datanya besok.

The team will check the data tomorrow. (informal Jakarta-associated morphology inside an otherwise neutral sentence)

Tim akan memeriksa data tersebut besok.

The team will examine the data tomorrow. (formal/neutral)

Do not “formalize” hadir into a nonexistent affixed form or turn every active clause passive. Grammar and information structure remain primary.

Negators and particles reveal stance

Tidak is nationally standard; nggak is widespread colloquial Indonesian; tak may be concise, literary, or fixed depending on context. Bukan negates nominal identity and corrects alternatives; belum means “not yet.” A register edit cannot replace all of them with one form.

Aku belum selesai, bukan nggak mau bantu.

I’m not finished yet; it’s not that I don’t want to help. (informal)

Pekerjaan tersebut belum selesai, bukan tidak dikerjakan.

The work is not yet complete; it is not the case that it was left undone. (formal)

Mohon periksa lagi, ya, Pak.

Please check again, sir. (careful spoken; ya sustains cooperation)

Mohon Bapak memeriksa kembali dokumen tersebut.

We ask that you recheck the document. (formal written)

Particles such as ya, dong, sih, deh, nih, and kok are not merely slang decorations. They encode stance. Removing them from a transcript can erase interpersonal meaning; retaining several in an official letter can falsely presume intimacy.

Vocabulary strata and punctuation work together

Formal Indonesian can include established technical terms and necessary loans. Casual Indonesian can use standard vocabulary. The problem is uncontrolled switching that gives no audience benefit.

Kami akan melakukan follow-up terkait issue pembayaran tersebut.

Mixed corporate code; potentially acceptable internally but opaque to a broad public.

Kami akan menindaklanjuti masalah pembayaran tersebut.

We will follow up on that payment issue. (public-facing formal Indonesian)

Guys!!! info meeting di-reschedule ya!!!

Highly expressive workplace chat with mixed vocabulary and punctuation. (informal)

Teman-teman, rapat dipindahkan ke hari Selasa pukul sembilan.

Colleagues, the meeting has moved to Tuesday at nine. (clear work-group message)

Punctuation cannot make vague content precise. Three exclamation marks do not identify a new time; a semicolon does not make a colloquial fragment formal.

A mixed-register paragraph

Here is a deliberately inconsistent announcement:

Yth. Bapak/Ibu peserta, gue mau ngabarin bahwa jadwal workshop nggak jadi hari Jumat, soalnya pembicaranya berhalangan nih. Kalian harap cek emailnya, ya!!! Info lengkap akan kami sampaikan via email. Makasih atas perhatiannya.

Dear participants, I want to let you know that the workshop won’t happen Friday because the speaker is unavailable. Please check your email. Complete information will be sent by email. Thanks for your attention. (deliberately mixed register)

Diagnose it feature by feature:

Yth. Bapak/Ibu peserta opens an institutional, respectful frame.
gue changes the speaker to Jakarta-associated peer identity, then kami changes it again to an institution.
ngabarin, nggak, soalnya, nih, makasih form an informal cluster.
workshop, email, info, via create a mixed vocabulary stratum; some may be purposeful, but four are not needed here.
kalian conflicts with Bapak/Ibu.
harap ... ya!!! combines formal directive vocabulary, an interactional particle, and excited punctuation.
emailnya lacks a stable possessor: whose email?

Editing only gue → saya would leave the other mismatches intact.

Revision 1: formal participant notice

Yth. Bapak dan Ibu Peserta, kami informasikan bahwa lokakarya yang semula dijadwalkan pada hari Jumat dipindahkan ke hari Senin karena narasumber berhalangan.

Dear Participants, we inform you that the workshop originally scheduled for Friday has been moved to Monday because the speaker is unavailable. (formal notice)

Mohon periksa surel yang terdaftar untuk mengetahui jadwal lengkap dan tautan kegiatan.

Please check the registered email account for the complete schedule and event link. (formal notice)

Terima kasih atas perhatian Bapak dan Ibu.

Thank you for your attention. (formal notice)

The revision aligns institutional kami, respectful Bapak dan Ibu, standard affixation and negation, lokakarya/narasumber/surel, and edited punctuation. It also supplies the new day and identifies which email account.

Revision 2: familiar participant-group chat

Teman-teman, jadwal workshop-nya pindah dari Jumat ke Senin karena pembicaranya berhalangan.

Friends, the workshop schedule has moved from Friday to Monday because the speaker is unavailable. (participant group chat; informal)

Cek email yang dipakai saat daftar, ya; jadwal lengkap dan link acaranya sudah dikirim.

Check the email you used to register; the full schedule and event link have been sent. (participant group chat; informal)

Makasih, sampai ketemu hari Senin!

Thanks, see you Monday! (participant group chat; informal)

This version is not an unedited copy. It chooses a coherent warm group voice, keeps key facts explicit, and uses only locally supported colloquial resources. Workshop, email, link, and makasih are retained because this imagined group already uses them.

💡

A coherent casual revision may still be carefully edited. Register consistency concerns the relationship and system, not the absence of planning.

A practical final pass

Read the revised text from beginning to end and ask:

Siapa yang berbicara: saya, kami, atau sebuah lembaga yang disebutkan namanya?

Who is speaking: saya, kami, or a named institution? (editing question)

Bagaimana pembaca dirujuk: Anda, Bapak/Ibu, teman-teman, atau tidak disebutkan?

How are readers referred to: Anda, Bapak/Ibu, friends, or not overtly? (editing question)

Apakah tindakan, penanggung jawab, dan batas waktunya dapat ditemukan dengan cepat?

Can the action, responsible person, and deadline be found quickly? (editing question)

Apakah setiap partikel dan singkatan membantu hubungan yang dituju?

Does each particle and abbreviation support the intended relationship? (editing question)

Consistency does not mean monotony. A formal presentation can include careful-spoken nah during explanation, and quoted dialogue can preserve a character’s informal voice. Mark those local shifts instead of flattening them.

Common Mistakes

1. Correcting only slang vocabulary

❌ Dengan hormat, saya ingin memberi tahu kamu bahwa meeting-nya diundur, dong.

Still inconsistent—the formal opening and saya conflict with kamu, meeting, and dong.

✅ Dengan hormat, kami informasikan bahwa rapat ditunda hingga pukul dua siang.

Respectfully, we inform you that the meeting is postponed until two in the afternoon. (formal)

2. Replacing every colloquial verb with meN- mechanically

❌ Bentuk “seluruh peserta akan hadir” diubah menjadi “seluruh peserta akan menghadirkan”.

Incorrect morphology—menghadirkan changes the meaning to ‘cause/present someone or something to be present.’

✅ Seluruh peserta akan hadir dalam rapat tersebut.

All participants will attend that meeting.

3. Standardizing a quoted character’s voice

❌ Semua dialog tokoh diubah menjadi “saya tidak tahu” meskipun perbedaan hubungan penting bagi cerita.

Over-editing—the quotation’s social characterization disappears.

✅ “Aku nggak tahu,” jawab tokoh itu kepada adiknya.

‘I don’t know,’ the character answered her younger sibling. (informal dialogue preserved and labeled)

4. Using formal punctuation to hide vague responsibility

❌ Sehubungan dengan hal tersebut; akan ditindaklanjuti sebagaimana mestinya.

Vague despite the semicolon—actor, action, and time remain absent.

✅ Tim layanan akan memeriksa pengaduan tersebut dan menjawabnya dalam dua hari kerja.

The service team will review the complaint and respond within two working days.

5. Flattening every local shift

❌ Karena teks utamanya formal, sapaan hangat dalam satu kutipan wawancara harus dihapus.

Incorrect editing principle—quoted register can differ when its boundary and function are clear.

✅ Pewawancara menulis, “Baik, Bu, kita mulai dari pengalaman pertama Ibu, ya.”

The interviewer writes, ‘All right, ma’am, let’s begin with your first experience.’ (careful spoken quotation within formal prose)

Key Takeaways

Register consistency emerges across person reference, morphology, negation, particles, vocabulary, punctuation, and audience obligations.
Diagnose audience, purpose, channel, and relationship before changing words.
Affixes encode voice and meaning, so register editing is never mechanical prefix addition.
Revise a mixed paragraph toward a complete coherent system, not a halfway inventory of substitutions.
Quotation and intentional local shifts may differ from the surrounding register when their boundaries are clear.

Now practice Indonesian

Reading grammar gets you part of the way. The exercises are where it sticks — free, no signup needed.

Start learning Indonesian →