From 959c7ed9564ae8822bca770a493a03e3ed1e30c3 Mon Sep 17 00:00:00 2001 From: Martin Hickey Date: Thu, 2 Feb 2017 11:33:08 +0000 Subject: [PATCH] Extract translation strings from the index pattern create page into translation file This commit is where the strings are now localized for this page and therefore will be loaded by the Angular globalization framework. It also associates a translation ID to each string block and therefore enables translation of the strings into different languages. It also provides the pattern for localizing other pages in the UI. --- .../management/sections/indices/_create.html | 81 +++++++------------ src/core_plugins/kibana/translations/en.json | 29 ++++++- webpackShims/ui-bootstrap.js | 2 +- 3 files changed, 57 insertions(+), 55 deletions(-) diff --git a/src/core_plugins/kibana/public/management/sections/indices/_create.html b/src/core_plugins/kibana/public/management/sections/indices/_create.html index 90a9017e11832f..1e5f74abc705ef 100644 --- a/src/core_plugins/kibana/public/management/sections/indices/_create.html +++ b/src/core_plugins/kibana/public/management/sections/indices/_create.html @@ -3,19 +3,15 @@
- -

Patterns allow you to define dynamic index names using * as a wildcard. Example: logstash-*

-

Patterns allow you to define dynamic index names. Static text in an index name is denoted using brackets. Example: [logstash-]YYYY.MM.DD. Please note that weeks are setup to use ISO weeks which start on Monday. — - Date Format Documentation

+ +

KIBANA-WILDCARD_DYNAMIC_INDEX_PATTERNS

+

KIBANA-STATIC_TEXT_IN_DYNAMIC_INDEX_PATTERNS — + KIBANA-DATE_FORMAT_DOCS

KIBANA-H1_CONFIGURE_INDEX_PATTERN type="text" class="form-control"> - Note: - I noticed you're using weekly indices. Kibana requires ISO weeks be used in your index creation. - See Wikipedia: ISO Week Date + KIBANA-NOTE_COLON  + KIBANA-WEEKLY_ISO_NOTICE + See KIBANA-WIKI_ISO_WEEK_DATE
@@ -38,18 +34,18 @@

KIBANA-H1_CONFIGURE_INDEX_PATTERN

- Index contains time-based events + KIBANA-CONTAINS_TIME_BASED_EVENTS_CHECKBOX
- Do not expand index pattern when searching (Not recommended) + KIBANA-EXPAND_INDEX_PATTERN_WARNING
- This index pattern will be queried directly rather than being - expanded into more performant searches against individual indices. + KIBANA-NOT_EXPANDABLE_PART1 - Elasticsearch will receive a query against {{index.name}} - and will have to search through all matching indices regardless - of whether they have data that matches the current time range. +
-

- By default, searches against any time-based index pattern that - contains a wildcard will automatically be expanded to query only - the indices that contain data within the currently selected time - range. -

+

KIBANA-WILDCARD_DEFAULT_EXPANDED_TO_CURRENT_TIME_RANGE_HELP

-

- Searching against the index pattern logstash-* will - actually query elasticsearch for the specific matching indices - (e.g. logstash-2015.12.21) that fall within the current - time range. -

+

KIBANA-WILDCARD_DEFAULT_EXPANDED_TO_CURRENT_TIME_RANGE_EXAMPLE_HELP

-

Time-interval based index patterns are deprecated!

-

- We strongly recommend using wildcard pattern names instead of - time-interval based index patterns. -

-

- Kibana is now smart enough to automatically determine which - indices to search against within the current time range for - wildcard index patterns. This means that wildcard - index patterns now get the same performance optimizations when - searching within a time range as time-interval patterns.

+

KIBANA-ALERT_INDEX_PATTERN_DEPRECATED

+

KIBANA-RECOMMEND_WILD_CARD_PATTERN

+

KIBANA-RECOMMEND_WILD_CARD_PATTERN_DETAILS