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 214,331 1,439,509 9,225,448
Source 7,743 82,340 542,182
Approved 0% 0 0% 0 0% 0
Waiting for review 45% 97,579 39% 574,673 40% 3,689,983
Translated 49% 105,322 45% 657,013 45% 4,232,165
Needs editing 1% 271 1% 903 1% 6,499
Read-only 3% 7,743 5% 82,340 5% 542,182
Failing checks 15% 32,976 11% 164,144 11% 1,077,726
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 50% 108,738 54% 781,593 54% 4,986,784
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% 3,938
Arabic 18% 3,095 18,589 116,784 3,094 494
Assamese 31% 2,596 16,490 103,920 2,596 720
Bengali (India) 30% 2,656 16,596 104,658 2,656 661
Bodo 31% 2,596 16,490 103,920 2,596 1,064
Bulgarian (Bulgaria) (bg_BG) 4% 3,651 21,160 133,183 3,651 119
Catalan 8% 3,497 20,750 130,701 3,497 40
Chinese (China) (zh_CN) 91% 342 2,681 16,836 311 2,290
Chinese (Taiwan) (zh_TW) 87% 467 3,940 24,561 437 2,363
Czech 70% 1,129 8,467 53,111 1,100 485
Dutch (Netherlands) (nl_NL) 28% 2,717 17,755 112,518 2,712 42
English (Australia) 74% 982 7,171 45,044 959 55
English (United Kingdom) 99% 17 304 1,826 17 171
Esperanto 81% 927 10,201 68,178 927 574
Filipino 2% 3,709 21,251 133,742 3,709 15
Finnish (Finland) (fi_FI) 28% 3,065 22,216 142,942 3,062 92
French 86% 619 5,405 37,379 588 582
Georgian (Georgia) (ka_GE) 83% 637 9,549 59,151 637 1,418
German 75% 1,376 19,985 135,749 1,376 415
Greek 2% 3,733 21,344 134,321 3,733 5
Gujarati 31% 2,596 16,490 103,920 2,596 771
Hebrew 5% 3,593 21,025 132,373 3,593 61
Hindi 30% 2,647 17,024 107,417 2,647 808
Hungarian 12% 3,336 20,161 127,130 3,336 41
Indonesian 94% 425 4,960 33,854 425 1,579
Italian 61% 1,462 10,431 65,819 1,442 151
Japanese 76% 1,150 12,316 84,096 1,150 2,512
Kannada 33% 2,550 16,392 103,346 2,547 760
Kashmiri 31% 2,612 16,534 104,266 2,605 1,100
Konkani 31% 2,596 16,490 103,920 2,596 759
Korean (South Korea) (ko_KR) 59% 3,154 51,026 338,599 3,154 2,133
Lao 2% 112 407 2,667 112 2
Maithili 31% 2,596 16,490 103,920 2,596 166
Manipuri 30% 2,656 16,597 104,669 2,656 1,049
Marathi 32% 2,594 16,478 103,859 2,594 79
Nepali 31% 2,634 16,577 104,692 2,634 418
Persian 73% 370 4,276 30,043 370 499
Polish (Poland) (pl_PL) 52% 1,827 12,454 78,318 1,819 113
Portuguese (Brazil) 78% 924 9,235 59,729 893 290
Portuguese 12% 3,339 20,309 128,106 3,339 10
Punjabi (India) (pa_IN) 34% 2,500 16,155 101,946 2,493 287
Russian 67% 2,552 48,796 319,866 2,552 1,208
Serbian 25% 2,828 17,791 112,674 2,828 71
Slovenian (Slovenia) (sl_SI) 14% 3,246 19,931 125,681 3,246 47
Spanish (Mexico) 20% 3,022 18,927 119,596 3,017 32
Spanish 92% 290 2,341 14,552 290 278
Tamil 32% 2,595 16,489 103,912 2,595 815
Telugu (India) (te_IN) 2% 3,725 21,335 134,247 3,725 40
Thai 40% 69 263 1,704 69 5
Turkish (Turkey) (tr_TR) 77% 847 6,464 40,515 817 478
Urdu 32% 2,582 16,456 103,781 2,575 853
Vietnamese (Vietnam) (vi_VN) 1% 3,769 21,532 135,542 3,769 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