Skip to content
Interface language: English
Oriens / Signal

A website localisation brief for Korea and Japan: what to provide before translation

Prepare a localisation brief covering audiences, the offer, glossary, page views, forms, URLs and language review.

Article language: English

An arched bridge spans calm water, with mountains and a low sun behind it.
In this article

The translator receives text, the designer receives a mock-up and the person responsible for the form hears about the new version last. Localisation can come apart before anything is published. Describe the audience in Korea or Japan, the actual offer and how enquiries will be handled. Then connect the work on language, design and code. A list of paragraphs matters, but it is not a market-entry plan by itself.

The Korean and Japanese versions need separate audience descriptions. Do not assume one decision about an “Asian version” will suffice. Even where the service itself is the same, confirm the materials, language of service and contact route for each version.

What should the visitor do?

Describe how they arrive: a referral, a conversation with a partner, search or a campaign. Identify their role and the questions they bring. An importer evaluating a Polish manufacturer may need different information from a company seeking a service provider in Poland. In Korean edtech (in Polish), distinguish material for teachers, learners and the commissioning organisation: each may need a different explanation of the roles of content and platform.

Record one main action and the information needed before it. Should the visitor send a specification, arrange a conversation or check documentation? Establish who handles that step and in which language. The brief should support an honest button label and a message shown after the action.

Add differences from the Polish version. If product availability, timing or the area served changes, mark it before translation. Do not expect the translator to decide commercial conditions independently.

How should the source text and glossary be prepared?

Provide the approved content with section identifiers. Mark working passages and questions requiring a decision. Ambiguity left in the source may later appear in several language versions.

The glossary should include brand, service and product names, roles and recurring terms. For each entry record its meaning, permitted variants and what should remain in the original language. For difficult terms, add an example sentence.

Ask someone who knows the offer to check the glossary. A linguistically correct name may still describe a different scope from the one intended. Keep decisions in one place so they do not recur on every screen.

Why does a list of text need views and context?

Provide screenshots, mock-ups or access to a working version. Mark where each string appears and what the button does. A short word such as “save” might concern a file, a submission or an event. Without context it is hard to choose the right equivalent.

Show phone and large-screen layouts, empty states, errors and confirmations. Include form labels, page titles, sharing descriptions and image alternative text. Mark materials with lettering embedded in the image.

W3C's internationalisation quick tips cover language identification, encoding, local formats and text preparation, among other things. They are a reference for the implementation team. The brief should say who checks these elements in the project.

How should forms, dates and contact details work?

Record which formats the site must accept and display. Check given names, family names, phone numbers, addresses, dates and meeting time zones. Specify which fields are actually necessary for the task. Validation should not reject data merely because the team tested only a Polish example.

Prepare the whole enquiry path: labels, error messages, on-page confirmation and any subsequent message. Establish whether the answer will come in the same language. If not, say so before the form is sent.

Also record who maintains the contact channel and takes over during an absence. A site may look finished before the service process is ready; the brief needs both. When planning a Rakuten Ichiba shop (in Polish), separately check the language of the content and day-to-day handling of orders and questions. Translating a catalogue alone does not describe the resources needed to run that sales channel.

How should linguistic and technical acceptance be planned?

Name the person who approves the meaning of the offer and the person who checks naturalness of language. Agree where comments go and how they are resolved. Acceptance should include the working site: line breaks, typeface and button context all affect how a message is received.

  • Approved scope and audience for each version.
  • A glossary of names and terms with an owner for decisions.
  • Main content, forms and system messages.
  • Phone and larger-screen views.
  • A contact route supported in the appropriate language.
  • An update plan for changes to the source version.

Plan separate addresses and language annotations for counterparts that actually exist. The Poland-Asia localisation guide (in Polish) describes the foundations; acceptance of a language-version implementation (in Polish) also covers URLs and the switcher. A switcher that only changes labels should not promise a translation of an entire article.

Aeneia conceptual photography

How can one language decision be recorded?

Working example: a service name remains in Polish as a proper name, but its description is written afresh for a Korean audience. The glossary retains the original, the agreed description, where it is used and the reason. At the button, add which contact path it opens.

If someone later proposes another variant, the approver can return to the context. Apply the agreed wording in every relevant place: menu, offer card, form and sharing preview. A small record like this reduces discrepancies without requiring a lengthy manual for every sentence.

How can a source sentence be linked to its place on the live site?

Give recurring passages stable identifiers. In one row, connect the Polish meaning, target version, page URL, interface element and approver. Record the state too: ready for translation, question for the offer owner, corrected or accepted in the view. A comment about a button then reaches the right place.

Working example: the identifier “usluga-kontakt-opis” refers to information about the language of a conversation. The Polish version says service is available in Polish and English; the Korean version requires separate confirmation that the person handling it is available. The translator flags the question, the process owner decides the scope and the designer checks the message length on a phone. Nobody has to guess the company's terms from a short label.

Base these dependencies on the site's B2B information architecture (in Polish). Establish the service-page content (in Polish) before handing over headings for translation. Otherwise a well-kept glossary will be organising an offer whose meaning is still changing.

What sample data should be prepared for a form test?

Prepare entirely fictional test data with names of different lengths and permitted characters. Go through entry, correction of an error, submission and reading the message on the receiving side. The same entry should survive every place it passes through: the form, notification and enquiry-handling tool.

W3C describes different ways of writing personal names and assumptions that can interfere with form design. Consult its official guidance on personal names rather than imposing a Polish given-name and family-name pattern without justification. We checked the document on 27 October 2026. Design the actual fields around information the company genuinely needs.

For each error, record the expected result and the person accepting the fix. If contact is the page's main goal, connect this test to B2B contact-form design (in Polish). A well-translated error message will not help if a visitor cannot enter valid data.

How should a source change be handled after translation approval?

Agree a simple update procedure. The offer owner identifies the changed passage, explains why and lists the versions affected. The localisation lead assesses the effect on the glossary and neighbouring sentences. After correction, the team reviews the relevant screen again, including the button and the post-action message.

Adding a new sentence at the end of a spreadsheet is not enough. A changed service name may affect the menu, URL, form, image lettering and metadata. A list of usage locations makes them easier to find. For a larger change, keep a project decision register (in Polish) so the next person understands why versions are not identical.

In the quotation, distinguish correction of an error from new scope and agree how additional work is approved. That makes discussion easier even when a change is small. It protects the schedule from a series of minor requests that together require the whole path to be accepted again.

Which errors appear only in the finished view?

Read the heading and description together. Check that a line break does not split a product name and that the font actually contains the necessary characters. Also inspect prices, units, meeting dates and error messages with enlarged text. A cut-off passage can change meaning as effectively as a bad translation.

Arrange separate acceptance of premium-site typography (in Polish) using the real text of each version. Where a translation is missing, check the visible message and link destination. The reader should know which language they will see after following the link. Finish the test by having the person who will answer an enquiry read it; only then have you followed the whole route from content to service.

Localisation also works in the other direction. When an Asian company enters Poland (in Polish), its audience, channel, local materials and enquiry handling need to be established. That project needs its own brief: do not simply reverse a task list made for a Polish exporter.

What should be supplied for a quotation and project start?

Include the list of pages, number of versions, state of the materials and dependencies. Mark what must be written from the beginning and what already has approved text. Record when work can start, which materials are needed then and how the agreed schedule depends on acceptance of successive stages.

At the end of the brief, enter an owner, date and version number. When the offer changes, the team can identify which translations need review. Website acceptance (in Polish) helps check the result, while contact with a Korean partner (in Polish) illustrates the value of a coherent proposal. The scope of audience research is described by Oriens; Design can lead the website project.

Agree in advance how to review a Korean or Japanese translation of the offer (in Polish). Confirm names, numbers and the meaning of conditions in the actual view. Acceptance of a text file does not automatically cover errors introduced during later page layout.

Aeneia / Aeneia editorial

Editorial article. Source links are included in the text.

About Aeneia

Brands we have worked with

  • L’Oréal
  • Garnier
  • Netflix
  • Carrefour
  • Warner Bros. Discovery
  • Biedronka
  • HBO Max
  • Wolt
  • Żabka
  • COSRX
  • Embassy of China in Poland
  • Mixa
Aeneia / Initium

From knowledge to a decision

Tell us what you want to put in order. We will agree on where to start.

Contact Aeneia

We partner with and use solutions from:

  • Google
  • OpenAI
  • Microsoft
  • Stripe
  • Anthropic
  • Linear