2. Cacti
3. core (v1.2.x)
4. Japanese
5. Zen

2357 include/global_settings.php:1148
	English Show business hours
	Japanese ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ — 営業時間 4/190 · 19 Needs editing
2412 include/global_settings.php:1378 • include/global_settings.php:1379 • include/global_settings.php:1380 • include/global_settings.php:1435 • include/global_settings.php:1449
	English %s Hour
	Japanese ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ — %s時 3/100 · 7 Needs editing
2497 include/global_settings.php:1760 • user_domains.php:423
	English The "Distinguished Name" syntax, applicable for both OpenLDAP and Windows AD configurations, offers flexibility in defining user identity. For OpenLDAP, the format follows this structure: <i>"uid=&lt;username&gt;,ou=people,dc=domain,dc=local"</i>. Windows AD provides an alternative syntax: <i>"&lt;username&gt;@win2kdomain.local"</i>, commonly known as "userPrincipalName (UPN)". In this context, "&lt;username&gt;" represents the specific username provided during the login prompt. This is particularly pertinent when operating in "No Searching" mode, or "Require Group Membership" enabled.
	Japanese ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ — 0/5920 · 592 Needs editing
2626 include/global_settings.php:2296
	English Use a separate subfolder for each hosts RRD files. The naming of the RRDfiles will be one of the following:<br><ul><li>&lt;path_cacti&gt;/rra/host_id/local_data_id.rrd,</li><li>&lt;path_cacti&gt;/rra/device_id/data_query_id/local_data_id.rrd,</li><li>&lt;path_cacti&gt;/rra/device_hash/device_id/local_data_id.rrd,</li><li>&lt;path_cacti&gt;/rra/device_hash/device_id/data_query_id/local_data_id.rrd.</li></ul><br>You can make this change after install by running the CLI script <b>structure_rra_paths.php</b> after you make the change. NOTE: If you change Max Directories value to decrease the number of directories, or if you change the Directory Pattern, empty directories will not be pruned after you rerun the <b>structure_rra_paths.php</b> script.
	Japanese ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ — 0/7550 · 755 Needs editing
3457 lib/installer.php:2154 • lib/installer.php:2166
	English Database User: <b>%s</b>
	Japanese ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ — あなたのデータベースユーザがテーブルを作成する権限がありません。私たちは、単にテーブルを空にすることによって復元しようとします。これは、a）あなたは同じデータベース構造でWordPressのバージョンから復元しているのように動作する必要があり、およびb）あなたのインポートされたデータベースは、すでにインポートサイトに存在しない任意のテーブルが含まれていません。 181/240 · 24 Needs editing
3723 lib/utility.php:1065 • lib/utility.php:1071
	English When performing joins, if they are below this size, they will be kept in memory and never written to a temporary file. As this is a per connection memory allocation, care must be taken not to increase it too high. The sum of the join_buffer_size + sort_buffer_size + read_buffer_size + read_rnd_buffer_size + thread_stack + binlog_cache_size + Core MySQL/MariaDB memory should be below 80%. If the recommendation is negative, you must decrease this and or the sort_buffer_size until the recommendation fits within the allowable memory.
	Japanese ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ — 0/5380 · 538 Needs editing
3737 lib/utility.php:1155
	English %s will divide the innodb_buffer_pool into memory regions to improve performance for versions of MariaDB less than 10.5. The max value is 64, but should not exceed more than the number of CPU cores/threads. When your innodb_buffer_pool is less than 1GB, you should use the pool size divided by 128MB. Continue to use this equation up to the max the number of CPU cores or 64.
	Japanese ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ — 0/3780 · 378 Needs editing
3738 lib/utility.php:1155
	English %s will divide the innodb_buffer_pool into memory regions to improve performance for versions of MySQL upto and including MySQL 8.0. The max value is 64, but should not exceed more than the number of CPU cores/threads. When your innodb_buffer_pool is less than 1GB, you should use the pool size divided by 128MB. Continue to use this equation up to the max of the number of CPU cores or 64.
	Japanese ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ — 0/3930 · 393 Needs editing
The translation has come to an end.