Closed VincentTam closed 5 years ago
In response to @onweru's comment in issue #24 (comment).
⚠️ In the future, please avoid adding English words directly into any visible components of the theme. Instead, put a i18n string like
{{ i18n "stringToBeTranslated" }}
in the template, and add the entrystringToBeTranslated
to each i18n file. It's OK to leave string untranslated in some languages. We aren't necessarily language experts. But please, follow the internationalization framework set up in #26.
Makes sense. Noted 👍
In addition, gohugoio/hugoThemes issue 668. (I don't add a link here to avoid being referenced from that issue.)
Edited: If application, please consider using one single {{ i18n "variable" [arguments] }}
for one whole expression due to the diference in word order, plural/singular form, etc.
Inside i18n/*.toml
, it might be possible to use one = "cheval"
and other = "chevaux"
to handle plural/singular, but that's not always the case. See Hugo's docs for details at https://gohugo.io/content-management/multilingual/#translation-of-strings.
In response to @onweru's comment in issue https://github.com/onweru/hugo-swift-theme/issues/24#issuecomment-520856972.
:warning: In the future, please avoid adding English words directly into any visible components of the theme. Instead, put a i18n string like
{{ i18n "stringToBeTranslated" }}
in the template, and add the entrystringToBeTranslated
to each i18n file. It's OK to leave string untranslated in some languages. We aren't necessarily language experts. But please, follow the internationalization framework set up in #26.