From 23ed3d5647a3ad335257145dcae6fa666b848eda Mon Sep 17 00:00:00 2001 From: Cory LaViska Date: Thu, 28 Jul 2022 09:16:37 -0400 Subject: [PATCH] add RTL info --- docs/getting-started/localization.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/getting-started/localization.md b/docs/getting-started/localization.md index df1ca4362..7623deeca 100644 --- a/docs/getting-started/localization.md +++ b/docs/getting-started/localization.md @@ -1,6 +1,6 @@ # Localization -Components can be localized by importing the appropriate translation file and setting the desired [`lang` attribute](https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes/lang) on the `` element. Here's an example that renders Shoelace components in Spanish. +Components can be localized by importing the appropriate translation file and setting the desired [`lang` attribute](https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes/lang) and/or [`dir` attribute](https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes/dir) on the `` element. Here's an example that renders Shoelace components in Spanish. ```html @@ -57,7 +57,7 @@ If you have any questions, please start a [discussion](https://github.com/shoela ## Multiple Locales Per Page -You can use a different locale for an individual component by setting its `lang` attribute. Here's a contrived example to demonstrate. +You can use a different locale for an individual component by setting its `lang` and/or `dir` attributes. Here's a contrived example to demonstrate. ```html @@ -70,7 +70,7 @@ You can use a different locale for an individual component by setting its `lang` ``` -For performance reasons, the `lang` attribute must be on the component itself, not on an ancestor element. +For performance reasons, the `lang` and `dir` attributes must be on the component itself, not on an ancestor element. ```html