From 26c3ce67d510a2f1ee854eb0951be5c40f5cb52e Mon Sep 17 00:00:00 2001 From: camperbot Date: Mon, 2 Jan 2023 09:17:35 -0800 Subject: [PATCH] chore(i18n,docs): processed translations (#48893) --- docs/i18n/chinese-traditional/codebase-best-practices.md | 4 ++-- docs/i18n/chinese/codebase-best-practices.md | 4 ++-- docs/i18n/espanol/codebase-best-practices.md | 4 ++-- docs/i18n/german/codebase-best-practices.md | 4 ++-- docs/i18n/italian/codebase-best-practices.md | 4 ++-- docs/i18n/japanese/codebase-best-practices.md | 4 ++-- docs/i18n/portuguese/codebase-best-practices.md | 4 ++-- docs/i18n/ukrainian/codebase-best-practices.md | 4 ++-- 8 files changed, 16 insertions(+), 16 deletions(-) diff --git a/docs/i18n/chinese-traditional/codebase-best-practices.md b/docs/i18n/chinese-traditional/codebase-best-practices.md index 31a6762cde1..af0fdb2b6b8 100644 --- a/docs/i18n/chinese-traditional/codebase-best-practices.md +++ b/docs/i18n/chinese-traditional/codebase-best-practices.md @@ -15,9 +15,9 @@ The `!important` keyword may be used to override values in some cases (for ex.: We are striving to support right-to-left (RTL) layout in the codebase for languages that are read in this direction. For this you need be mindful of how to style components. Here are some quick rules of thumb to follow: - Don't use `float` properties: Although it may seem best to have the component in the "perfect position", you will be climbing mountains to reach that perfect positioning in responsive layout, and you will need to reach higher heights to have it supported in RTL. -- - Use Flexbox and Grid layouts instead, as they have RTL support already built-in, and those will be easier to maintain and review. +- → Use Flexbox and Grid layouts instead, as they have RTL support already built-in, and those will be easier to maintain and review. - Don't define the direction while using `margin` and `padding`: it may seem harmless to use `padding-right` and `margin-left`, but these directions aren't mirrored when the layout changes to RTL, and adding counter values for them in the RTL file makes maintaining the codebase harder. -- - Use logical properties for them: You can add the same spacing by using `padding-inline-end` and `margin-inline-start`, and you won't need to worry about RTL layout, as they follow where the line start and ends, and you won't need to add any extra values in the RTL files, so people won't need to remember to change the same values in two files. +- → Use logical properties for them: You can add the same spacing by using `padding-inline-end` and `margin-inline-start`, and you won't need to worry about RTL layout, as they follow where the line start and ends, and you won't need to add any extra values in the RTL files, so people won't need to remember to change the same values in two files. - Don't use `!important` in `font-family`: RTL layout is using different font from the LTR layout, when you add `!important` in the `font-family` property it affects the RTL layout too, which causes a UI bug. ## General JavaScript diff --git a/docs/i18n/chinese/codebase-best-practices.md b/docs/i18n/chinese/codebase-best-practices.md index 31a6762cde1..af0fdb2b6b8 100644 --- a/docs/i18n/chinese/codebase-best-practices.md +++ b/docs/i18n/chinese/codebase-best-practices.md @@ -15,9 +15,9 @@ The `!important` keyword may be used to override values in some cases (for ex.: We are striving to support right-to-left (RTL) layout in the codebase for languages that are read in this direction. For this you need be mindful of how to style components. Here are some quick rules of thumb to follow: - Don't use `float` properties: Although it may seem best to have the component in the "perfect position", you will be climbing mountains to reach that perfect positioning in responsive layout, and you will need to reach higher heights to have it supported in RTL. -- - Use Flexbox and Grid layouts instead, as they have RTL support already built-in, and those will be easier to maintain and review. +- → Use Flexbox and Grid layouts instead, as they have RTL support already built-in, and those will be easier to maintain and review. - Don't define the direction while using `margin` and `padding`: it may seem harmless to use `padding-right` and `margin-left`, but these directions aren't mirrored when the layout changes to RTL, and adding counter values for them in the RTL file makes maintaining the codebase harder. -- - Use logical properties for them: You can add the same spacing by using `padding-inline-end` and `margin-inline-start`, and you won't need to worry about RTL layout, as they follow where the line start and ends, and you won't need to add any extra values in the RTL files, so people won't need to remember to change the same values in two files. +- → Use logical properties for them: You can add the same spacing by using `padding-inline-end` and `margin-inline-start`, and you won't need to worry about RTL layout, as they follow where the line start and ends, and you won't need to add any extra values in the RTL files, so people won't need to remember to change the same values in two files. - Don't use `!important` in `font-family`: RTL layout is using different font from the LTR layout, when you add `!important` in the `font-family` property it affects the RTL layout too, which causes a UI bug. ## General JavaScript diff --git a/docs/i18n/espanol/codebase-best-practices.md b/docs/i18n/espanol/codebase-best-practices.md index fe15d7d4f66..39edb633151 100644 --- a/docs/i18n/espanol/codebase-best-practices.md +++ b/docs/i18n/espanol/codebase-best-practices.md @@ -15,9 +15,9 @@ The `!important` keyword may be used to override values in some cases (for ex.: We are striving to support right-to-left (RTL) layout in the codebase for languages that are read in this direction. For this you need be mindful of how to style components. Here are some quick rules of thumb to follow: - Don't use `float` properties: Although it may seem best to have the component in the "perfect position", you will be climbing mountains to reach that perfect positioning in responsive layout, and you will need to reach higher heights to have it supported in RTL. -- - Use Flexbox and Grid layouts instead, as they have RTL support already built-in, and those will be easier to maintain and review. +- → Use Flexbox and Grid layouts instead, as they have RTL support already built-in, and those will be easier to maintain and review. - Don't define the direction while using `margin` and `padding`: it may seem harmless to use `padding-right` and `margin-left`, but these directions aren't mirrored when the layout changes to RTL, and adding counter values for them in the RTL file makes maintaining the codebase harder. -- - Use logical properties for them: You can add the same spacing by using `padding-inline-end` and `margin-inline-start`, and you won't need to worry about RTL layout, as they follow where the line start and ends, and you won't need to add any extra values in the RTL files, so people won't need to remember to change the same values in two files. +- → Use logical properties for them: You can add the same spacing by using `padding-inline-end` and `margin-inline-start`, and you won't need to worry about RTL layout, as they follow where the line start and ends, and you won't need to add any extra values in the RTL files, so people won't need to remember to change the same values in two files. - Don't use `!important` in `font-family`: RTL layout is using different font from the LTR layout, when you add `!important` in the `font-family` property it affects the RTL layout too, which causes a UI bug. ## General JavaScript diff --git a/docs/i18n/german/codebase-best-practices.md b/docs/i18n/german/codebase-best-practices.md index 2584c5ec1e9..b4bfead253f 100644 --- a/docs/i18n/german/codebase-best-practices.md +++ b/docs/i18n/german/codebase-best-practices.md @@ -15,9 +15,9 @@ The `!important` keyword may be used to override values in some cases (for ex.: We are striving to support right-to-left (RTL) layout in the codebase for languages that are read in this direction. For this you need be mindful of how to style components. Here are some quick rules of thumb to follow: - Don't use `float` properties: Although it may seem best to have the component in the "perfect position", you will be climbing mountains to reach that perfect positioning in responsive layout, and you will need to reach higher heights to have it supported in RTL. -- - Use Flexbox and Grid layouts instead, as they have RTL support already built-in, and those will be easier to maintain and review. +- → Use Flexbox and Grid layouts instead, as they have RTL support already built-in, and those will be easier to maintain and review. - Don't define the direction while using `margin` and `padding`: it may seem harmless to use `padding-right` and `margin-left`, but these directions aren't mirrored when the layout changes to RTL, and adding counter values for them in the RTL file makes maintaining the codebase harder. -- - Use logical properties for them: You can add the same spacing by using `padding-inline-end` and `margin-inline-start`, and you won't need to worry about RTL layout, as they follow where the line start and ends, and you won't need to add any extra values in the RTL files, so people won't need to remember to change the same values in two files. +- → Use logical properties for them: You can add the same spacing by using `padding-inline-end` and `margin-inline-start`, and you won't need to worry about RTL layout, as they follow where the line start and ends, and you won't need to add any extra values in the RTL files, so people won't need to remember to change the same values in two files. - Don't use `!important` in `font-family`: RTL layout is using different font from the LTR layout, when you add `!important` in the `font-family` property it affects the RTL layout too, which causes a UI bug. ## General JavaScript diff --git a/docs/i18n/italian/codebase-best-practices.md b/docs/i18n/italian/codebase-best-practices.md index 7e19bd6aae7..e31b8c02470 100644 --- a/docs/i18n/italian/codebase-best-practices.md +++ b/docs/i18n/italian/codebase-best-practices.md @@ -15,9 +15,9 @@ La parola chiave `!important` può essere usata per sovrascrivere i valori in al Stiamo cercando di supportare il layout da destra a sinistra (right-to-left, RTL) nel codebase per le lingue che sono lette in questa direzione. Per questo è necessario essere consapevoli di come definire lo stile dei componenti. Ecco alcune rapide regole pratiche da seguire: - Non utilizzare le proprietà `float`: anche se può sembrare meglio avere il componente in "posizione perfetta", dovrai scalare una montagna per raggiungere quel posizionamento perfetto nel layout responsivo e dovrai fare ancora più fatica per averlo supportato in RTL. -- Invece, utilizza i layout Flexbox e Grid poiché hanno già integrato il supporto RTL e saranno più facili da gestire e revisionare. +- → Use Flexbox and Grid layouts instead, as they have RTL support already built-in, and those will be easier to maintain and review. - Non definire la direzione usando `margin` e `padding`: potrebbe sembrare innocuo usare `padding-right` e `margin-left`, ma queste direzioni non sono rispecchiate quando il layout cambia in RTL e l'aggiunta di valori contatori per loro nel file RTL rende il mantenimento del codebase più difficile. -- Usa le proprietà logiche per loro: puoi aggiungere la stessa spaziatura usando `padding-inline-end` e `margin-inline-start` e non dovrai preoccuparti del layout RTL, dato che seguono l'inizio e la fine della riga e non è necessario aggiungere alcun valore aggiuntivo nei file RTL, così le persone non dovranno ricordarsi di cambiare gli stessi valori in due file. +- → Use logical properties for them: You can add the same spacing by using `padding-inline-end` and `margin-inline-start`, and you won't need to worry about RTL layout, as they follow where the line start and ends, and you won't need to add any extra values in the RTL files, so people won't need to remember to change the same values in two files. - Non usare `!important` in `font-family`: il layout RTL utilizza caratteri diversi dal layout LTR, quando si aggiunge `!important` alla proprietà `font-family` influisce anche sul layout RTL, causando un bug della UI. ## JavaScript generale diff --git a/docs/i18n/japanese/codebase-best-practices.md b/docs/i18n/japanese/codebase-best-practices.md index 43073e75457..dd8523c2453 100644 --- a/docs/i18n/japanese/codebase-best-practices.md +++ b/docs/i18n/japanese/codebase-best-practices.md @@ -15,9 +15,9 @@ The `!important` keyword may be used to override values in some cases (for ex.: We are striving to support right-to-left (RTL) layout in the codebase for languages that are read in this direction. For this you need be mindful of how to style components. Here are some quick rules of thumb to follow: - Don't use `float` properties: Although it may seem best to have the component in the "perfect position", you will be climbing mountains to reach that perfect positioning in responsive layout, and you will need to reach higher heights to have it supported in RTL. -- - Use Flexbox and Grid layouts instead, as they have RTL support already built-in, and those will be easier to maintain and review. +- → Use Flexbox and Grid layouts instead, as they have RTL support already built-in, and those will be easier to maintain and review. - Don't define the direction while using `margin` and `padding`: it may seem harmless to use `padding-right` and `margin-left`, but these directions aren't mirrored when the layout changes to RTL, and adding counter values for them in the RTL file makes maintaining the codebase harder. -- - Use logical properties for them: You can add the same spacing by using `padding-inline-end` and `margin-inline-start`, and you won't need to worry about RTL layout, as they follow where the line start and ends, and you won't need to add any extra values in the RTL files, so people won't need to remember to change the same values in two files. +- → Use logical properties for them: You can add the same spacing by using `padding-inline-end` and `margin-inline-start`, and you won't need to worry about RTL layout, as they follow where the line start and ends, and you won't need to add any extra values in the RTL files, so people won't need to remember to change the same values in two files. - Don't use `!important` in `font-family`: RTL layout is using different font from the LTR layout, when you add `!important` in the `font-family` property it affects the RTL layout too, which causes a UI bug. ## General JavaScript diff --git a/docs/i18n/portuguese/codebase-best-practices.md b/docs/i18n/portuguese/codebase-best-practices.md index afdb7b8fe0e..9330c26fb82 100644 --- a/docs/i18n/portuguese/codebase-best-practices.md +++ b/docs/i18n/portuguese/codebase-best-practices.md @@ -15,9 +15,9 @@ A palavra-chave `!important` pode ser usada para substituir valores em alguns ca Estamos nos esforçando para apoiar o layout da direita para a esquerda (do inglês, right-to-left, ou RTL) na base de código para os idiomas que são lidos nessa direção. Por isso, você precisa estar atento à maneira como estilizar os componentes. Seguem aqui algumas dicas práticas para isso: - Não use as propriedades `float`: embora possa parecer o melhor para ter o componente na "posição perfeita", você estará fazendo um esforço incrível para alcançar o posicionamento perfeito no layout responsivo e precisará de um esforço ainda maior para dar o suporte aos idiomas lidos da direita para a esquerda. -- - Em vez disso, use layouts com Flexbox e Grid, pois eles já têm incorporado o suporte a esses idiomas e serão mais fáceis de manter e revisar. +- → Use Flexbox and Grid layouts instead, as they have RTL support already built-in, and those will be easier to maintain and review. - Não defina a direção ao usar `margin` e `padding`: pode parecer inofensivo usar `padding-right` e `margin-left`, mas essas direções não são espelhadas quando o layout muda para RTL. Adicionar valores opostos para eles no arquivo RTL torna a manutenção da base de código mais difícil. -- - Use as propriedades lógicas para eles: você pode adicionar o mesmo espaço, usando `padding-inline-end` e `margin-inline-start`. Você não precisará se preocupar com o layout RTL, já que ele seguirá onde a linha começa e termina. Além disso, você não precisará adicionar valores a mais nos arquivos RTL. Então, não será necessário lembrar de alterar os mesmos valores em dois arquivos. +- → Use logical properties for them: You can add the same spacing by using `padding-inline-end` and `margin-inline-start`, and you won't need to worry about RTL layout, as they follow where the line start and ends, and you won't need to add any extra values in the RTL files, so people won't need to remember to change the same values in two files. - Não use `!important` em `font-family`: o layout RTL usará uma fonte diferente do layout da esquerda para a direita (do inglês, left-to-right, ou LTR). Quando você adiciona `!important` na propriedade `font-family`, isso afeta o layout RTL também, o que causa um bug de UI. ## JavaScript em geral diff --git a/docs/i18n/ukrainian/codebase-best-practices.md b/docs/i18n/ukrainian/codebase-best-practices.md index e80559e1a88..5936622b9e4 100644 --- a/docs/i18n/ukrainian/codebase-best-practices.md +++ b/docs/i18n/ukrainian/codebase-best-practices.md @@ -15,9 +15,9 @@ The `!important` keyword may be used to override values in some cases (for ex.: We are striving to support right-to-left (RTL) layout in the codebase for languages that are read in this direction. For this you need be mindful of how to style components. Here are some quick rules of thumb to follow: - Don't use `float` properties: Although it may seem best to have the component in the "perfect position", you will be climbing mountains to reach that perfect positioning in responsive layout, and you will need to reach higher heights to have it supported in RTL. -- - Use Flexbox and Grid layouts instead, as they have RTL support already built-in, and those will be easier to maintain and review. +- → Use Flexbox and Grid layouts instead, as they have RTL support already built-in, and those will be easier to maintain and review. - Don't define the direction while using `margin` and `padding`: it may seem harmless to use `padding-right` and `margin-left`, but these directions aren't mirrored when the layout changes to RTL, and adding counter values for them in the RTL file makes maintaining the codebase harder. -- - Use logical properties for them: You can add the same spacing by using `padding-inline-end` and `margin-inline-start`, and you won't need to worry about RTL layout, as they follow where the line start and ends, and you won't need to add any extra values in the RTL files, so people won't need to remember to change the same values in two files. +- → Use logical properties for them: You can add the same spacing by using `padding-inline-end` and `margin-inline-start`, and you won't need to worry about RTL layout, as they follow where the line start and ends, and you won't need to add any extra values in the RTL files, so people won't need to remember to change the same values in two files. - Don't use `!important` in `font-family`: RTL layout is using different font from the LTR layout, when you add `!important` in the `font-family` property it affects the RTL layout too, which causes a UI bug. ## General JavaScript