Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Korean translation issue: "Slice" used instead of "Segment" in guides/examples/types #819

Copy link
Copy link
Open
@JaegeonJo

Description

@JaegeonJo
Issue body actions

Hi, I'd like to report an important mistranslation in the Korean version of the following English paragraph from the Feature-Sliced Design documentation:

Original (EN):

:::warning
Resist the temptation to create a `shared/types` folder, or to add a `types` segment to your slices. The category "types" is similar to the category "components" or "hooks" in that it describes what the contents are, not what they are for. Segments should describe the purpose of the code, not the essence.
:::

Current Korean translation:

:::warning
`shared/types` 폴더를 생성하거나 각 슬라이스에 `types`라는 세그먼트를 추가하고 싶은 마음이 들 수 있지만, 그렇게 하지 않는 것이 좋습니다.<br/>
`types`라는 카테고리는 `components``hooks`와 마찬가지로 내용이 무엇인지를 설명할 뿐, 코드의 목적을 명확히 설명하지 않습니다. 슬라이스는 해당 코드의 목적을 정확히 설명할 수 있어야 합니다.
:::

Original:
Segments should describe the purpose of the code, not the essence.

Current Korean translation:
슬라이스는 해당 코드의 목적을 정확히 설명할 수 있어야 합니다.

🔍 Issue:
In the FSD context, Slice and Segment are clearly distinct concepts:

  • Slice refers to domain units (e.g., auth, profile)
  • Segment refers to role-based subfolders within a slice (e.g., model, ui, api)

However, the Korean translation incorrectly replaces "Segment" with "슬라이스", which significantly alters the meaning of the sentence and misleads readers.

🛠️ Suggested fix:

세그먼트는 코드의 종류나 형태가 아니라, 그 코드가 수행하는 목적에 따라 이름 지어야 합니다.

Thank you for your attention and all your hard work on this translation!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      Morty Proxy This is a proxified and sanitized view of the page, visit original site.