Summary

Project website opendev.org/openstack/horizon
10/20/2026

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 229,754 1,764,404 11,510,721
Source 8,711 103,046 688,081
Approved 0% 0 0% 0 0% 0
Waiting for review 43% 100,823 36% 646,635 36% 4,204,687
Translated 47% 109,534 42% 749,681 42% 4,892,768
Needs editing 1% 274 1% 952 1% 6,868
Read-only 3% 8,711 5% 103,046 5% 688,081
Failing checks 17% 40,691 12% 218,997 12% 1,474,119
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 52% 119,946 57% 1,013,771 57% 6,611,085
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes
OctNovDecJanFebMarAprMayJunJulAugSep

Quick numbers

0
Hosted words
0
Hosted strings
0%
Translated
0
Contributors
0
Components
0
Languages
0
Translations
0
Screenshots
and previous 30 days

Trends of last 30 days

—
Hosted words
—
—
Hosted strings
—
—
Translated
—
—
Contributors
—
Language Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
English (United States) 100% 4,246
Arabic 18% 3,137 18,886 118,594 3,136 599
Assamese 31% 2,640 16,814 105,928 2,640 846
Bengali (India) 29% 2,700 16,920 106,666 2,700 787
Bodo 31% 2,640 16,814 105,928 2,640 1,188
Bulgarian (Bulgaria) (bg_BG) 4% 3,691 21,429 134,827 3,691 246
Catalan 8% 3,537 21,019 132,345 3,537 167
Chinese (China) (zh_CN) 75% 1,204 22,379 155,548 1,173 2,396
Chinese (Taiwan) (zh_TW) 70% 1,438 24,547 170,090 1,408 2,357
Czech 56% 2,104 29,025 198,264 2,075 500
Dutch (Netherlands) (nl_NL) 28% 2,760 18,040 114,258 2,755 159
English (Australia) 73% 1,033 7,569 47,573 1,010 74
English (United Kingdom) 99% 31 674 4,344 31 169
Esperanto 67% 1,898 30,405 210,757 1,898 564
Filipino 2% 3,749 21,520 135,386 3,749 142
Finnish (Finland) (fi_FI) 28% 3,112 22,481 144,561 3,109 246
French 71% 1,563 25,668 179,826 1,530 592
Georgian (Georgia) (ka_GE) 67% 1,564 30,045 203,851 1,564 1,421
German 74% 1,725 28,782 197,685 1,725 476
Greek 2% 3,773 21,613 135,965 3,773 132
Gujarati 31% 2,640 16,814 105,928 2,640 897
Hebrew 5% 3,633 21,294 134,017 3,633 308
Hindi 30% 2,691 17,348 109,425 2,691 881
Hungarian 12% 3,378 20,433 128,785 3,378 168
Indonesian 93% 598 8,398 57,671 598 1,705
Italian 60% 1,510 10,773 67,937 1,490 174
Japanese 77% 1,342 16,391 112,228 1,342 3,221
Kannada 32% 2,594 16,716 105,354 2,591 885
Kashmiri 31% 2,656 16,858 106,274 2,649 1,223
Konkani 31% 2,640 16,814 105,928 2,640 885
Korean (South Korea) (ko_KR) 55% 3,849 68,506 460,861 3,849 2,276
Lao 2% 112 407 2,667 112 2
Maithili 31% 2,640 16,814 105,928 2,640 910
Manipuri 29% 2,700 16,921 106,677 2,700 1,173
Marathi 31% 2,638 16,802 105,867 2,638 854
Nepali 31% 2,680 16,904 106,725 2,680 1,259
Polish (Poland) (pl_PL) 51% 1,875 12,796 80,436 1,867 285
Portuguese (Brazil) 74% 1,339 19,200 127,903 1,308 392
Portuguese 12% 3,380 20,579 129,755 3,380 137
Punjabi (India) (pa_IN) 34% 2,544 16,479 103,954 2,537 1,046
Russian 62% 3,271 68,081 455,654 3,271 1,249
Serbian 25% 2,871 18,098 114,540 2,871 197
Slovenian (Slovenia) (sl_SI) 14% 3,286 20,200 127,325 3,286 174
Spanish (Mexico) 20% 3,062 19,196 121,240 3,057 157
Spanish 73% 1,262 22,933 159,915 1,261 285
Tamil 31% 2,639 16,813 105,920 2,639 940
Telugu (India) (te_IN) 2% 3,765 21,604 135,891 3,765 206
Thai 40% 69 263 1,704 69 5
Turkish (Turkey) (tr_TR) 61% 1,821 27,076 186,068 1,791 493
Urdu 31% 2,626 16,780 105,789 2,619 979
Vietnamese (Vietnam) (vi_VN) 1% 3,810 21,802 137,191 3,810 18
User avatar weblate:commit

Changes committed
Changes committed 10/05/2026
User avatar admin

File uploaded
Processed 167 strings from the uploaded files (skipped: 0, not found: 0, updated: 167).
File upload mode: Add as translation 10/05/2026
User avatar admin

Translation uploaded
In the Ocata release of Horizon a new "OpenStack Profiler" panel was introduced. Once it is enabled and all prerequisites are set up, you can see which API calls Horizon actually makes when rendering a specific page. To re-render the page while profiling it, you'll need to use the "Profile" dropdown menu located in the top right corner of the screen. In order to be able to use "Profile" menu, the following steps need to be completed:
Horizon???의 Ocata ??????????????? ????????? "OpenStack Profiler" ????????? ???????????????. ?????? ????????? ??????????????? ?????? ??????????????? ????????????, ????????? ?????? ???????????? ???????????? ??? Horizon??? ????????? ?????? API??? ??????????????? ??? ??? ??????. ???????????? ????????????????????? ?????? ?????? ?????????????????? ?????? ????????? ?????? ???????????? ?????? "????????????" ???????????? ????????? ??????????????????. "????????????" ????????? ??????????????? ?????? ????????? ???????????? ??????릴리스에는 새로운 "OpenStack Profiler" 패널이 도입되었다. 일단 그것이 활성화되고 모든 전제조건이 설정되면, 당신은 특정 페이지를 렌더링할 때 Horizon이 실제로 어떤 API를 호출하는지 알 수 있다. 페이지를 프로파일링하는 동안 다시 렌더링하려면 화면 오른쪽 상단 모서리에 있는 "프로파일" 드롭다운 메뉴를 사용하십시오. "프로파일" 메뉴를 사용하려면 다음 단계를 완료해야 한다.
10/05/2026
User avatar admin

Translation uploaded
Note that once a package is released, you can not "un-release" it. You should never attempt to modify, delete or rename a released package without a lot of careful planning and feedback from all projects that use it.
?????? ???????????? ???????????? "??????"??? ??? ????????? ?????? ??????????????????. ???????????? ???????????? ???????????? ?????? ????????????????????? ?????? ????????? ????????? ???????????? ?????? ???????????? ???????????? ??????, ?????? ?????? ????????? ???????????? ????????? ??? ??????일단 패키지가 출시되면 "해제"할 수 없다는 점에 유의하십시오. 릴리스된 패키지를 사용하는 모든 프로젝트로부터 많은 세심한 계획과 피드백을 받지 않고서는 패키지를 수정, 삭제 또는 이름을 바꾸려고 해서는 안 된다.
10/05/2026
User avatar admin

Translation uploaded
ESLint is part of the automated unit tests performed by Jenkins. The automated test use the default configurations, which are less strict than the configurations we recommended to run in your local development environment.
ESLint???는 Jenkins??? ?????? ????????? ???????????? ?????? ???????????? ???????????????. ???????????? ???????????? ?????? ????????? ???????????????, ??? ????????? ?????? ?????? ???????????? ??????????????? ????????? ???????????? ??? ????????????에 의해 수행된 자동화된 단위 테스트의 일부분이다. 자동화된 테스트는 기본 구성을 사용하는데, 이 구성은 로컬 개발 환경에서 실행하도록 권장한 구성보다 덜 엄격하다.
10/05/2026
User avatar admin

Translation uploaded
ESLint is a great tool to be used during your code editing to improve JavaScript quality by checking your code against a configurable list of checks. Therefore, JavaScript developers should configure their editors to use ESLint to warn them of any such errors so they can be addressed. Since ESLint has a ton of configuration options to choose from, links are provided below to the options Horizon wants enforced along with the instructions for setting up ESLint for Eclipse, Sublime Text, Notepad++ and WebStorm/PyCharm.
ESLint??? ?????? ????????? ?????? ????????? ???????????? ????????? ?????????????????? JavaScript ????????? ??????????????? ?????? ?????? ?????? ?????? ????????? ??? ?????? ????????? ?????????. ????????? JavaScript ???????????? ESLint??? ???????????? ????????? ????????? ??? ?????? ????????? ??????????????? ???????????? ???????????? ??????. ESLint?????? ????????? ??? ?????? ?????? ?????? ????????? ????????????는 구성 가능한 검사 목록과 비교하여 코드를 확인함으로써 JavaScript 품질을 향상시키기 위해 코드 편집 중에 사용할 수 있는 훌륭한 툴이다. 따라서 JavaScript 개발자는 ESLint를 사용하여 문제를 해결할 수 있는 오류를 경고하도록 편집자를 구성해야 한다. ESLint에는 선택할 수 있는 많은 구성 옵션이 있으므로 Eclipse???용 ESLint, Sublime Text, Notepad+ ???및 WebStorm/PyCharm ?????? ????????? ?????? Horizon?????? ??????????????? ????????? ?????? ????????? ????????? ????????????설정 지침과 함께 Horizon에서 적용하려는 옵션에 대한 링크가 아래에 제공된다.
10/05/2026
User avatar admin

Translation uploaded
When reviewing / writing, please refer to the sections of this guide. If an issue is encountered, note it with a comment and provide a link back to the specific issue. For example, code should use named functions. A review noting this should provide the following link in the comments:
??????/?????? ??? ??? ???????????? ????????? ??????????????????. ????????? ???????????? ???????????? ???????????? ?????? ????????? ?????? ????????? ??????????????????. ?????? ?????? ????????? ????????? ????????? ???????????? ??????. ?????? ???????????? ????????? ???????????? ????????? ?????? ????????? ???????????? ??????검토/작성 시 본 가이드의 섹션을 참조하십시오. 문제가 발생하면 코멘트로 기록하고 특정 문제에 대한 링크를 제공하십시오. 예를 들어 코드는 명명된 기능을 사용해야 한다. 이에 주목하는 검토는 논평에서 다음과 같은 링크를 제공해야 한다.
10/05/2026
User avatar admin

Translation uploaded
Source-code formatting – (or "beautification") is recommended but should be used with caution. Keep in mind that if you reformat an entire file that was not previously formatted the same way, it will mess up the diff during the code review. It is best to use a formatter when you are working on a new file by yourself, or with others who are using the same formatter. You can also choose to format a selected portion of a file only. Instructions for setting up ESLint for Eclipse, Sublime Text, Notepad++ and WebStorm/PyCharm are provided_.
소스 코드 포맷 – (또는 "보관")을 권장하지만 주의하여 사용해야 한다. 이전에 동일한 방식으로 포맷되지 않은 전체 파일을 다시 포맷하면 코드 검토 중에 해당 파일이 다른 파일을 망치게 된다는 점을 명심하십시오. 당신이 혼자서 또는 동일한 포맷터를 사용하고 있는 다른 사람들과 새로운 파일을 작업할 때 포맷터를 사용하는 것이 가장 좋다. 파일의 선택한 부분만 포맷하도록 선택할 수도 있다. Eclipse, Sublime Text, Notepad+ 및 WebStorm/PyCharm용 ESLint 설정 지침이 제공됨_
10/05/2026
User avatar admin

Translation uploaded
Do not use '``with`` object {code}'. The ``with`` statement is used to access properties of an object. The issue with ``with`` is that its execution is not consistent, so by reading the statement in the code it is not always clear how it is being used.
'"with" ??????개체 {code}"???(???) ???????????? ????????????. "with"?????? ????????? ????????? ????????? ???????????? ?????? ????????????. ``with"??? ????????? ??? ????????? ???????????? ?????? ????????? ????????? ??? ????????? ??????????????? ????????? ????????? ???????????? ????????? ?????? ??????????????? ??????을(를) 사용하지 마십시오. "with"라는 문장은 개체의 속성에 접근하기 위해 사용된다. ``with"의 문제는 그 실행이 일관되지 않기 때문에 코드로 그 문장을 읽음으로써 그것이 어떻게 사용되고 있는지 항상 명확하지는 않다.
10/05/2026
User avatar admin

Translation uploaded
Do not put variables or functions in the global namespace. There are several reasons why globals are bad, one being that all JavaScript included in an application runs in the same scope. The issue with that is if another script has the same method or variable names they overwrite each other.
????????? ????????????????????? ????????? ????????? ?????? ????????????. ???????????? ?????? ????????? ?????? ????????? ?????????, ????????? ?????? ??????????????? ????????? ?????? ????????????????????? ????????? ???????????? ???????????? ????????????. ????????? ?????? ??????????????? ????????? ???????????? ?????? ????????? ????????? ?????? ?????? ?????? ??????????????? ?????????글로벌 네임스페이스에 변수나 기능을 넣지 마십시오. 구상체가 나쁜 이유는 여러 가지가 있는데, 하나는 응용 프로그램에 포함된 모든 자바스크립트가 동일한 범위에서 실행되기 때문이다. 문제는 다른 스크립트가 동일한 방법이나 변수 이름을 가지고 있는 경우 서로 덮어쓴다는 것이다.
10/05/2026
Browse all project changes