translate tutorials(elasticsearch_metrics, etcd_metrics, golang_metri…#22121
Conversation
…cs, haprozy_metrics, iis_logs)
💚 Build Succeeded |
💚 Build Succeeded |
| defaultMessage: 'The `elasticsearch` Metricbeat module fetches internal metrics from Elasticsearch. \ | ||
| [Learn more]({learnMoreLink}).', | ||
| values: { | ||
| learnMoreLink: '{config.docs.beats.metricbeat}/metricbeat-module-elasticsearch.html', |
There was a problem hiding this comment.
Will this link always lead to the EN version of the Elastic site?
https://www.elastic.co/guide/en/beats/metricbeat/6.3/metricbeat-module-elasticsearch.html?
Answer is not stopping this PR. I'm just curious if the i18n framework can change a URL part based on locale
There was a problem hiding this comment.
@azasypkin maybe you could help with clarification?
There was a problem hiding this comment.
There is a high chance that the set of locales we support in Kibana and have documentation for will be different so I'd not rely on anything "automatic" here, but we can add context field where we ask localizers to ping us and check whether we have docs for the locale they are currently working on so that every time we generate these labels for vendor to translate they will see that context field and can get back to us and clarify. For that to work we also will have to construct this link differently so that localizers can have access to this guide/en/beats part.
elastic#22121) translate tutorials(elasticsearch_metrics, etcd_metrics, golang_metrics, haprozy_metrics, iis_logs) # Conflicts: # src/core_plugins/kibana/server/tutorials/iis_logs/index.js
#21957
translate tutorials(elasticsearch_metrics, etcd_metrics, golang_metrics, haprozy_metrics, iis_logs)