# Problems with Korean's translation on Weblate

**URL:** <https://discourse.slicer.org/t/problems-with-koreans-translation-on-weblate/25296>\
**Category:** Support\
**Tags:** internationalization\
**Created:** [September 16, 2022, 5:57am UTC](https://discourse.slicer.org/t/problems-with-koreans-translation-on-weblate/25296 "2022-09-16T05:57:53Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![DDinghoya](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/ddinghoya/32/16545_2.png) [@DDinghoya](https://discourse.slicer.org/u/DDinghoya)\
**Post date:** [September 16, 2022, 5:57am UTC](https://discourse.slicer.org/t/problems-with-koreans-translation-on-weblate/25296/1 "2022-09-16T05:57:53Z")

</div>

HI everyone!!!

First of all, I am honored to have had the opportunity to experience this great program.

Basically the Korean translation was 100% completed on weblate, and there were two problems.

1. Korean translation was made, but some items are not reflected. (Photos to be attached later)

Even if I downloaded the language pack from github and applied it manually, it was not reflected.

1. Some HTML tags disappear after saving the translation on Weblate as below;

```auto
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/REC-html40/strict.dtd">
<html><head><meta name="qrichtext" content="1" /><style type="text/css">

```

is changed to

```auto
&lt;html&gt;<meta name="qrichtext" content="1"><style type="text/css">

```

Also, some style strings are changed, like

```auto
</span><span style=" font-size:8pt; font-weight:600;">

```

to

```auto
</span><span style="">

```

I think the problem arises when using a 2 byte charset.

It is hoped that the cause of the problem and improvement will be addressed through this post.

Best regards.

---

<div class="post-metadata">

**Author:** ![pieper](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/pieper/32/8_2.png) [@pieper](https://discourse.slicer.org/u/pieper)\
**Post date:** [September 16, 2022, 4:32pm UTC](https://discourse.slicer.org/t/problems-with-koreans-translation-on-weblate/25296/2 "2022-09-16T16:32:16Z")

</div>

Thank you for reporting this and for your translation contributions 👍

Internationalization of the full interface is complex, with many special cases that need to be handled carefully to avoid breaking core functionality. Fortunately we have a team in Senegal, Canada, and the US working to make improvements with funding from CZI:

> **[3D Slicer in My Language: Internationalization and Usability Improvements -...](https://chanzuckerberg.com/eoss/proposals/3d-slicer-in-my-language-internationalization-and-usability-improvements/)**

Could you file your findings on the github issues for the effort?

> **[Issues · Slicer/SlicerLanguagePacks](https://github.com/Slicer/SlicerLanguagePacks/issues)**
>
> 3D Slicer extension for creating, editing, and storing translations for Slicer core and extensions - Issues · Slicer/SlicerLanguagePacks

---

<div class="post-metadata">

**Author:** ![DDinghoya](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/ddinghoya/32/16545_2.png) [@DDinghoya](https://discourse.slicer.org/u/DDinghoya)\
**Post date:** [September 17, 2022, 5:28am UTC](https://discourse.slicer.org/t/problems-with-koreans-translation-on-weblate/25296/4 "2022-09-17T05:28:28Z")

</div>

Thank you for your strong reply! 🙂

I’ll try it! → Done
