[Book Feedback] MVVM 'View' should be consistently translated as '뷰' (transliteration) instead of '보기' (noun). #285
Description
Please provide the title of the book
For e.g. "Architecting Cloud-Native .NET Apps for Azure". Assign a corresponding label (if applicable)
eShopOnContainers Reference Application
The specific link is: https://learn.microsoft.com/ko-kr/dotnet/architecture/maui/mvvm
What do you think could be improved in this book?
The Korean translation of the article linked above (MVVM chapter) uses the noun '보기' for the technical term 'View' in the Model-View-ViewModel (MVVM) pattern.
Change Request:
The term 'View' should be consistently translated as '뷰' (transliteration/loanword) in the Korean version to align with common IT/programming terminology in Korea. Using '보기' can be confusing as it is a general noun.
Example of necessary changes (within the linked document):
The text often refers to the View as '보기'. For example, sections like 'The Role of the View' should be translated to '뷰의 역할' instead of '보기의 역할'.
Additional context
Add any other context or screenshots about your feedback.
This issue specifically concerns the consistency and quality of the Korean technical translation. In modern software development (especially for patterns like MVVM, MVC), using the transliteration '뷰' is the standard practice for 'View' in Korean documentation and communication.